|
32 | 32 | benefit from using it, and how it is typically purchased, please see: <xref
|
33 | 33 | href="oxygen_xml_as_a_technical_documentation_solution_faq.dita"/>.</p>
|
34 | 34 | </section>
|
35 |
| - <section id="section_bjv_2jx_pbc"> |
36 |
| - <title>Storage</title> |
37 |
| - <p>Possibilities to store the DITA XML content:<ul id="ul_kl5_fjx_pbc"> |
38 |
| - <li><xref href="../git-tech-writers/using_git_for_technical_writing.dita">Using |
39 |
| - a Git project.</xref>.</li> |
40 |
| - <li><xref |
41 |
| - href="https://www.oxygenxml.com/doc/ug-editor/topics/sharepoint-connection.html" |
42 |
| - format="html" scope="external">Sharepoint</xref>.</li> |
43 |
| - <li>WebDav or eXist DB.</li> |
44 |
| - <li><xref href="https://www.oxygenxml.com/partners.html#cmssolutionpartners" |
45 |
| - format="html" scope="external">Using a commercial available |
46 |
| - CMS</xref>.</li> |
47 |
| - <li>Building your own CMS integration plugin.</li> |
48 |
| - </ul></p> |
| 35 | + <section> |
| 36 | + <title>General Advantages of Structured DITA XML Editing With Oxygen</title> |
| 37 | + <ul id="ul_gnq_mc3_1cc"> |
| 38 | + <li>You own your content, the storage is on your own servers, privacy is |
| 39 | + insured.</li> |
| 40 | + <li>You are using a standard (DITA XML) for which lots of tools and publishing |
| 41 | + choices exist.</li> |
| 42 | + <li>Reuse content and easily update the reused content in multiple places.</li> |
| 43 | + <li>Reduce translation costs by reusing content.</li> |
| 44 | + <li>Lost of publishing format choices (WebHelp, PDF, Windows Help, Word, Markdown, |
| 45 | + etc).</li> |
| 46 | + <li>Enforce consistency through structured validation (custom Schematron rules, |
| 47 | + Quick Fixes).</li> |
| 48 | + </ul> |
49 | 49 | </section>
|
50 | 50 | <section id="section_srq_s5g_4bc">
|
51 | 51 | <title>DITA Maps Manager</title>
|
|
234 | 234 | working in the desktop application.</li>
|
235 | 235 | </ul></p>
|
236 | 236 | </section>
|
| 237 | + <section id="section_bjv_2jx_pbc"> |
| 238 | + <title>Storage</title> |
| 239 | + <p>Possibilities to store the DITA XML content:<ul id="ul_kl5_fjx_pbc"> |
| 240 | + <li><xref href="../git-tech-writers/using_git_for_technical_writing.dita">Using |
| 241 | + a Git project.</xref>.</li> |
| 242 | + <li><xref |
| 243 | + href="https://www.oxygenxml.com/doc/ug-editor/topics/sharepoint-connection.html" |
| 244 | + format="html" scope="external">Sharepoint</xref>.</li> |
| 245 | + <li>WebDav or eXist DB.</li> |
| 246 | + <li><xref href="https://www.oxygenxml.com/partners.html#cmssolutionpartners" |
| 247 | + format="html" scope="external">Using a commercial available |
| 248 | + CMS</xref>.</li> |
| 249 | + <li>Building your own CMS integration plugin.</li> |
| 250 | + </ul></p> |
| 251 | + </section> |
237 | 252 | <section id="section_k5r_1vg_4bc">
|
238 | 253 | <title>Review</title>
|
239 | 254 | <p>There are several ways for people to provide feedback on technical documentation:<ul
|
|
0 commit comments