Blame Documentation/Tcar-ug/Manuals.docbook
|
|
018d85 |
<part id="manuals">
|
|
|
460d3e |
|
|
|
460d3e |
<title>Documentation</title>
|
|
|
460d3e |
|
|
|
460d3e |
<partintro>
|
|
|
e68d9f |
<para>
|
|
|
163dee |
&TCAR; documentation work line is implemented through
|
|
|
163dee |
documentation manuals. Documentation manuals are
|
|
|
364b72 |
implemented through different documentation formats
|
|
|
364b72 |
provided inside &TC;; (e.g.,
|
|
|
364b72 |
<application>Docbook</application>,
|
|
|
364b72 |
<application>Texinfo</application>,
|
|
|
364b72 |
<application>LaTeX</application>, etc.). Structuring
|
|
|
364b72 |
tasks related to documentation systems (e.g., creating,
|
|
|
364b72 |
editing, deleting, copying, renaming, etc.) are
|
|
|
10607e |
standardized through the help functionality
|
|
|
018d85 |
of <command>centos-art.sh</command> script, as described
|
|
|
018d85 |
in <xref linkend="scripts-bash-help" />. This way, people
|
|
|
d58617 |
writting documentation don't need to deal with underlaying
|
|
|
018d85 |
tasks like creating files, updating menus, nodes, cross
|
|
|
d58617 |
references and wondering where to put everything in
|
|
|
d58617 |
&TCAR;.
|
|
|
e68d9f |
</para>
|
|
|
460d3e |
|
|
|
e68d9f |
</partintro>
|
|
|
460d3e |
|
|
|
10607e |
&manuals-production;
|
|
|
10607e |
&manuals-formats;
|
|
|
460d3e |
|
|
|
460d3e |
</part>
|