Archive:Docs Project Style Guide - Content and Rendering

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Moved to guide)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
 +
{{Moved to guide}}
 
{{header|docs}}
 
{{header|docs}}
  

Latest revision as of 14:38, 22 March 2014

Important.png
Old page
The data in this page has been incorporated into a formal guide and is no longer being maintained.
DocsProject Header docTeam1.png


[edit] Content and Rendering

Writing documentation for display on assorted media through various technologies presents unique requirements. In general, keep the written content and rendering information separate. Rendering information is the formatting markup language to distinguish types of information, such as bold text to add emphasis. Modern technologies empower writers to use specialized markup language to enhance communication. It is imperative writers participating in collaborative projects like the Fedora Documentation Project adhere to standards and prescribed templates.

Note.png
Benefits of Content and Markup Language Separation
Keeping content material and markup language separate from each other within documentation adds an additional benefit. As new media formats develop, project coordinators easily remove markup language and re-format the original content for the new communication outlet. Therefore, separating markup language from subject matter content encourages use of the original content for future projects with little additional effort.