Overview
When publishing a Rich Hypertext rendition of a Word or Word-compatible document, Hyper.Net separately captures both the content in the document and the formatting created by the author. This allows you to choose how you wish to present the content to end-users:
| |
· |
You can use the original document formatting created by the author
|
| |
· |
|
Delivering content using the originally authored formatting has a number of benefits:
| |
· |
It allows the end-user to continue receiving the same formatting he or she received when using a paper form of the document, thus preserving document "familiarity"
|
| |
· |
It allows the organization to take advantage of formatting that may have been defined in corporate authoring templates
|
In situations where standard authoring templates have not been in use, however, the result of publishing the originally authored formatting can be negative. The following could occur:
| |
· |
Every document has an appearance in all of its renditions that is different from other documents, making the presentation inconsistent and thus more difficult for the end-user
|
| |
· |
Document sets may differ significantly in appearance between authors, groups, divisions and business units
|
| |
· |
The appearance of published content may not conform to the Corporate Image and thus be unusable on various corporate Web sites that require conformance
|
| |
· |
Published content may look good in one WCMS application but not in another—the applications are not able to control the appearance of the content they present to achieve the desired effect
|
In the above cases, it may be better to enforce a consistent look-and-feel across document sets through the use of cascading style sheets.
Delivering content using the originally authored formatting is the default mode in Hyper.Net's sample WCMS application. If you choose to deliver the originally authored formatting to end-users, therefore, you don't need to change anything unless you're creating your own WCMS application. In this case you will need to copy the approaches used in the sample WCMS application for your own use.
The topic.aspx generated into the Topic folder is responsible for generating the HTML for the end-user. The HTML may refer to a binary object like a PDF or Flat HTML file, for example, or may display the content of the selected topic in the Rich Hypertext rendition.