How the topic.aspx works with content, metadata and styles
Follow these steps to get an overview of how the topix.aspx is working with content, metadata and styles:
| |
|
|
|
Step
|
|
1
|
Open a Topic folder by going to the Publishing Center, selecting a publication, choosing any topic from the publication, removing topic.aspx from the URL in the address bar and opening the resulting URL. Example:
http://hnsharepoint/Lists/Publications/240bc1a2/68319610aa774b8d0025772700634c5d/topic.aspx
The Topic folder for the selected topic will open. Inside this folder you will see an item named topic. This is a dummy page representing the topic.aspx.
|
| |
|
|
2
|
Click on the Edit document properties icon to the left of topic item. This will open the topic properties. Scroll down to the bottom part of the topic properties list. Your screen should look something like this:
For a description of the usage of many of these properties, refer to the Appendix.
|
|
3
|
Examine the property HNTransformedStyle. This property contains the style information from the original source document that is needed to present the content with exactly the same formatting created by the author.
|
|
4
|
Scroll further down to the property named TRANSFORMED. Your screen should look something like this:
The content that is presented here is a preview of the topic's content from the Rich Hypertext rendition. You can see the actual HTML code behind this by clicking on the Edit Content button and then on the Edit HTML Source button.
| |
|
|
Note
|
Although you can edit the values of any of a topic's properties on the topic form, we recommend that you do not do this in a production environment because the transformation process for the next version of the given document will overwrite the changes you make. Manual modification of these values may also constitute violation of document control best practices and cause a document control audit to fail.
Manual modification can be useful in the following situations:
| |
· |
In a production environment when metadata or content must be modified in an emergency situation, such as when content must be changed and no one with access to the source document is available
|
| |
· |
In a test or development environment where manual modification of property values helps accelerate the application development because the process of modifying the source file and waiting for it to publish can be skipped
|
|
| |
|
|
Note
|
If the HTML code stored in the TRANSFORMED property does not meet your needs or if you need to publish a different markup, refer to Rendering customized XML markup.
|
|
|
5
|
Review the other properties associated with the dummy page for the selected topic. You can use any of them in your WCMS application.
|