Working with Static Publishing in Fatwire – Part 2

Posted: January 19, 2012 in Fatwire
Tags: , , , , , , , , ,

In my previous post, we have seen the creation of Static Publishing destination. In this post, and if required in the upcoming posts, we will discuss on how to work with this static publishing.

Static Publishing or Export to Disk Publishing, as quoted by the Fatwire Developer guide, “It renders your approved assets into static HTML files, using the template elements assigned to them to format them. An administrator or automated process then copies those files to your delivery system using FTP or another file transfer method.”

The Static Publishing is mainly used when the Basic Asset Model is used. While using the Flex Asset model, it rarely makes sense to use this Static Publishing methodology.


After the asset is created (lets take a PAGE asset here) , and a default template is assigned, we need to APPROVE the asset for making it available for PUBLISH.

To approve an asset, click on INSPECT action item of the asset (a Page here). Then click on MORE drop down list, and then click on “APPROVE FOR PUBLISH”. Check the below screen for the same.


Now, The next step to proceed with is to select the Publishing destination(If not created earlier, check out this link for creation of Static Publishing Destination). Select the appropriate publishing destination, if you have created more than one. Then click on the Approve button. Check the below screen for the same.


If the asset has any dependencies, those dependencies have to be approved first, before approving this asset.

That’s it.. The asset is Approved.


If the assets are published directly, with out setting a specified file name, they will be exported with the ASSET’S ID by default. To avoid that, we need to specify a user friendly name. The STATUS screen helps us in setting a user friendly name for the asset, path for the asset (under the exported directory), and a starting point for the asset.

For setting the status, click on STATUS option of the MORE drop down menu. Then the following screen appears. Click on the “SPECIFY PATH/FILENAME, START POINTS” link in the appropriate publishing destination.


The next screen is the place where we need to set the above discussed (Path, File name, Starting points).

  1. Specify the Path and filename.
  2. If the asset needs to be published, it needs to be a starting point.  For example, if Page is a starting point, then the all the images, css, etc will automatically be exported by the page.
  3. Select the template and the wrapper page.
  4. Click on Save.

Check the below screen for the same.



Now, the final thing to do is to publish the assets. Click on the PUBLISHING option in the top of the work area. The following screen appears. Select the appropriate publishing destination. Check the below screen for the same.


The following screen appears next.  In that, we need to click on PUBLISH button.


To make sure that the files are exported correctly, we need to go to the export location, and check whether they are exported properly or not.


In this way, the  assets are exported successfully to the specified location.


Stay tuned for more posts…

  1. Your content for this article is obviously intended to provoke thought in the reader. I can tell because it made me think about the many points you stated quite clearly. I really like your style.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s