The best way to create content is to use standard authoring tools such as Microsoft Office.
| |
|
|
| |
1. |
Standard authoring tools provide all functions for efficiently creating documents.
|
| |
|
|
| |
· |
Tables of contents
|
| |
· |
Indices
|
| |
· |
Spell and grammar check, syllabication
|
| |
· |
Integration of graphics and objects
|
| |
· |
Text components
|
| |
· |
and many more
|
| |
|
|
| |
2. |
Standard authoring tools are very popular both in organizations and in private use.
|
| |
3. |
A large amount of tool expertise is available in organizations.
|
For this reason, standard office applications should be used to create and maintain content. Using the Hyper.Net Content Transformation Service this content can be automatically prepared and distributed across platforms (optimized for the respective media).
| |
|
I) Why should content not be captured in HTML editors?
HTML editors do not offer sophisticated formatting functionality (tables, pictures, ...) and large texts cannot be structured appropriately (as every user who has tried to enter large amonts of text in web templates will confirm).
II) Why should content not be edited in Notes?
Notes is a groupware system to support team work processes, not an application for comprehensive text documentation. The editor is proprietary and texts can only be structured via additional programming logic. The formatting options are limited and even basic functions such as syllabication are not available as they are not required in the groupware context.
III) Why should content not be maintained using special web authoring systems?
Web authoring systems provide HTML editors or other proprietary editors. These systems are based on the assumption that content for specific media (the web in this case) has to be created with special tools. Hence the limitations listed under I and II apply. Additional limitations are media and data inconsistencies as well as additional efforts required for redundant maintainance of content.
IV) Should content be maintained using technical authoring systems?
Single source publishing and topic-oriented approaches can be implemented using technical authoring systems. However, these systems require a comprehensive organization of the content and processes as well as a profound expertise concerning the use of the tools. This can be achieved with less effort using standard Office applications in combination with Hyper.Net. Hyper.Net splits the documents up into topics and recombines them (as required) for distribution to relational data which can be used for a large variety of purposes. The expertise in the use of Office applications is already available and Single Source / Cross Channel Publishing is possible on the basis of standard applications with little organizational overhead.
|
Office applications can be used "as is". Also, the creation of documents can be standardized and optimized using intelligent templates. If required, Coextant can provide well-proven template techniques for efficiently creating documents with MS Word.
Functions
The philosophy behind the templates is the following: "The author writes and the system formats".
| |
|
|
| |
· |
Mask for entering profile information
|
| |
· |
Functions for inserting various objects
|
| |
· |
Style templates for all permissible formats
|
| |
· |
Optional: Hiding of all MS Word functions that are not needed
|
Technical benefits
| |
|
|
| |
· |
Standardized and unified creation of important documentations
|
Business benefits
System requirements