|
5 | 5 |
|
6 | 6 | <div class="jumbotron jumbotron-fluid"> |
7 | 7 | <div class="container"> |
8 | | - <div class="row"> |
9 | | - <!-- |
10 | | - <div class="col-md-2"> |
11 | | - <img src="images/dita-ot-logo.svg" class="mt-3" alt="DITA Open Toolkit logo" height="128px"> |
12 | | - </div> |
13 | | - --> |
14 | | - <div class="col-md-12"> |
15 | | - <h1 class="display-3 ml-md-4 ml-lg-n2">{{ page.title }}</h1> |
16 | | - <p class="lead ml-md-4 ml-lg-n2"> |
17 | | - Darwin Information Typing Architecture (DITA) is an XML-based open standard for |
18 | | - structuring, developing, managing, and publishing content. |
19 | | - </p> |
20 | | - </div> |
21 | | - </div> |
| 8 | + <h1 class="display-3 ml-md-4 ml-lg-n2">{{ page.title }}</h1> |
| 9 | + <p class="lead">Structure your content. Scale your documentation. Deliver |
| 10 | + everywhere.</p> |
| 11 | + <!-- |
| 12 | + Darwin Information Typing Architecture (DITA) is an XML-based open standard for |
| 13 | + structuring, developing, managing, and publishing content. |
| 14 | + --> |
| 15 | + <p>Darwin Information Typing Architecture (DITA) is an XML-based open standard for structured content that |
| 16 | + empowers teams to create, reuse, and publish technical documentation at |
| 17 | + enterprise scale.</p> |
22 | 18 | </div> |
23 | 19 | </div> |
24 | 20 | <div class="container"> |
@@ -46,3 +42,209 @@ <h2>Drafts</h2> |
46 | 42 | </li> |
47 | 43 | </ul> |
48 | 44 | </div> |
| 45 | +<div class="container"> |
| 46 | + <h3 id="call-to-action-buttons">Call-to-Action Buttons</h3> |
| 47 | + <ul> |
| 48 | + <li><strong>Learn DITA</strong> (primary)</li> |
| 49 | + <li><strong>View Examples</strong> (secondary)</li> |
| 50 | + <li><strong>Find Tools</strong> (tertiary)</li> |
| 51 | + </ul> |
| 52 | +</div> |
| 53 | +<hr/> |
| 54 | +<div class="container"> |
| 55 | + <div class="row"> |
| 56 | + <h2 class="col-12" id="value-propositions-3-column-section">Value Propositions</h2> |
| 57 | + <div class="col-4"> |
| 58 | + <h3 id="write-once-publish-everywhere">Write Once, Publish |
| 59 | + Everywhere</h3> |
| 60 | + <p>The DITA language lets you structure content in topic-based modules. |
| 61 | + DITA-compatible publishing tools can then automatically generate HTML, |
| 62 | + PDF, mobile, print, and any format your team needs. No more maintaining |
| 63 | + multiple versions of the same documentation.</p> |
| 64 | + </div> |
| 65 | + <div class="col-4"> |
| 66 | + <h3 id="built-for-scale">Built for Scale</h3> |
| 67 | + <p>From startups to Fortune 500 companies, the DITA language |
| 68 | + specification provides the foundation for handling complex documentation |
| 69 | + projects with thousands of topics, multiple products, and global |
| 70 | + translation requirements.</p> |
| 71 | + </div> |
| 72 | + <div class="col-4"> |
| 73 | + <h3 id="reuse-everything">Reuse Everything</h3> |
| 74 | + <p>Stop copying and pasting. DITA’s structured markup gives you powerful |
| 75 | + ways to write content once and reuse it everywhere. Use topic-based |
| 76 | + authoring to create modular content, content references to pull in |
| 77 | + shared information, and conditional text to show different content to |
| 78 | + different audiences—all from the same source files.</p> |
| 79 | + </div> |
| 80 | + </div> |
| 81 | +</div> |
| 82 | + |
| 83 | +<hr/> |
| 84 | +<div class="container"> |
| 85 | + <h2 id="use-cases-section">Use Cases Section</h2> |
| 86 | + <h3 id="for-technical-writers">For Technical Writers</h3> |
| 87 | + <p><strong>Professional documentation language that adapts to your |
| 88 | + workflow</strong></p> |
| 89 | + <p>Transform your content creation process with DITA’s topic-based |
| 90 | + authoring syntax. Focus on writing while DITA-compatible tools handle |
| 91 | + the structure, cross-references, and publishing automation.</p> |
| 92 | + <ul> |
| 93 | + <li>Topic-based writing language that mirrors how users actually consume |
| 94 | + information |
| 95 | + </li> |
| 96 | + <li>Built-in syntax for cross-references and linking</li> |
| 97 | + <li>Content reuse markup that eliminates copy-paste errors</li> |
| 98 | + <li>Semantic structure that enables professional publishing</li> |
| 99 | + </ul> |
| 100 | + <h3 id="for-product-teams">For Product Teams</h3> |
| 101 | + <p><strong>Documentation language that scales with your |
| 102 | + product</strong></p> |
| 103 | + <p>Keep your docs in sync with rapid product development. DITA’s modular |
| 104 | + markup approach means updates in one place propagate everywhere they’re |
| 105 | + needed when processed by DITA tools.</p> |
| 106 | + <ul> |
| 107 | + <li>Single-source content markup for multiple products and releases</li> |
| 108 | + <li>Conditional publishing syntax for different audiences</li> |
| 109 | + <li>Language designed for integration with development workflows</li> |
| 110 | + <li>Structured approach that ensures consistency across all |
| 111 | + documentation |
| 112 | + </li> |
| 113 | + </ul> |
| 114 | + <h3 id="for-enterprise">For Enterprise</h3> |
| 115 | + <p><strong>Industrial-strength content language</strong></p> |
| 116 | + <p>Built for organizations that take documentation seriously. The DITA |
| 117 | + language specification provides the governance, workflow foundation, and |
| 118 | + scalability that enterprise content demands.</p> |
| 119 | + <ul> |
| 120 | + <li>Standards-based markup language backed by OASIS</li> |
| 121 | + <li>Language designed for enterprise-grade content management |
| 122 | + workflows |
| 123 | + </li> |
| 124 | + <li>Built-in translation and localization support</li> |
| 125 | + <li>Extensible language architecture for custom requirements</li> |
| 126 | + </ul> |
| 127 | + <hr/> |
| 128 | + <h2 id="problemsolution-section">Problem/Solution Section</h2> |
| 129 | + <h3 id="the-problem-with-traditional-documentation">The Problem with |
| 130 | + Traditional Documentation</h3> |
| 131 | + <p>Most teams struggle with fragmented, inconsistent documentation |
| 132 | + that’s expensive to maintain and impossible to keep current. Content |
| 133 | + gets duplicated, updates get missed, and different formats drift out of |
| 134 | + sync.</p> |
| 135 | + <h3 id="the-dita-solution">The DITA Solution</h3> |
| 136 | + <p>DITA treats content as structured data through its markup language, |
| 137 | + not just text. This fundamental approach enables intelligent reuse, |
| 138 | + automated publishing workflows, and content that adapts to your needs |
| 139 | + instead of constraining them.</p> |
| 140 | + <hr/> |
| 141 | + <h2 id="social-proof-section">Social Proof Section</h2> |
| 142 | + <h3 id="trusted-by-industry-leaders">Trusted by Industry Leaders</h3> |
| 143 | + <p>Organizations worldwide rely on DITA for mission-critical |
| 144 | + documentation:</p> |
| 145 | + <p><strong>“DITA’s structured language transformed our documentation |
| 146 | + workflow. We reduced publishing time by 80% while improving consistency |
| 147 | + across 12 product lines using DITA-compatible tools.”</strong> <em>— |
| 148 | + Documentation Manager, Fortune 500 Software Company</em></p> |
| 149 | + <p><strong>“The modular language approach lets our distributed team |
| 150 | + contribute effectively. Content reuse markup means our docs stay |
| 151 | + synchronized automatically when processed.”</strong> <em>— Technical |
| 152 | + Writing Team Lead, Global Manufacturing</em></p> |
| 153 | + <p><strong>“DITA’s structured markup integrates perfectly with our |
| 154 | + development process. Docs deploy with code automatically using our DITA |
| 155 | + publishing pipeline.”</strong> <em>— DevOps Engineer, Tech |
| 156 | + Startup</em></p> |
| 157 | + <h3 id="used-by-thousands-of-organizations-including">Used by thousands |
| 158 | + of organizations including:</h3> |
| 159 | + <ul> |
| 160 | + <li>Major software companies for API documentation language</li> |
| 161 | + <li>Manufacturing giants for technical manual markup</li> |
| 162 | + <li>Government agencies for policy documentation structure</li> |
| 163 | + <li>Healthcare organizations for compliance material authoring</li> |
| 164 | + <li>Financial institutions for process documentation language</li> |
| 165 | + </ul> |
| 166 | + <hr/> |
| 167 | + <h2 id="technical-highlights-section">Technical Highlights Section</h2> |
| 168 | + <h3 id="powerful-language-features-that-just-work">Powerful Language |
| 169 | + Features That Just Work</h3> |
| 170 | + <p><strong>Intelligent Content Reuse</strong> DITA’s content reference |
| 171 | + syntax lets you reference content fragments across topics and |
| 172 | + publications. Change once, update everywhere when processed. No broken |
| 173 | + links, no outdated copies.</p> |
| 174 | + <p><strong>Conditional Publishing</strong> Built-in markup for creating |
| 175 | + different versions for different audiences from the same source. Filter |
| 176 | + by product, platform, experience level, or any criteria you define in |
| 177 | + the language.</p> |
| 178 | + <p><strong>Professional Output Ready</strong> DITA’s semantic structure |
| 179 | + enables publication-ready HTML, PDF, EPUB, mobile apps, and more through |
| 180 | + compatible publishing tools. Integrates with modern toolchains and CI/CD |
| 181 | + workflows.</p> |
| 182 | + <p><strong>Extensible Language Architecture</strong> Adapt DITA to your |
| 183 | + specific needs through specialization. Create custom topic types, add |
| 184 | + industry-specific elements, or extend the language while maintaining |
| 185 | + compatibility.</p> |
| 186 | + <p><strong>Translation Ready</strong> Built-in language features for |
| 187 | + localization workflows. DITA’s structure supports translation memory, |
| 188 | + multilingual content management, and consistency across languages.</p> |
| 189 | + <p><strong>Open Standard</strong> DITA is an open language standard |
| 190 | + maintained by OASIS. No vendor lock-in, no proprietary formats. Your |
| 191 | + content remains accessible and portable across any DITA-compatible |
| 192 | + system.</p> |
| 193 | + <hr/> |
| 194 | + <h2 id="getting-started-section">Getting Started Section</h2> |
| 195 | + <h3 id="start-your-dita-journey-today">Start Your DITA Journey |
| 196 | + Today</h3> |
| 197 | + <p><strong>Learn the Language</strong> New to structured authoring? Our |
| 198 | + getting started guide walks you through DITA language concepts with |
| 199 | + practical examples you can try immediately. [Read the Language Guide |
| 200 | + →]</p> |
| 201 | + <p><strong>Explore Tools & Implementations</strong> Discover |
| 202 | + authoring tools, content management systems, and publishing engines that |
| 203 | + support the DITA language specification. [Browse DITA Tools →]</p> |
| 204 | + <p><strong>Join the Community</strong> Connect with DITA practitioners |
| 205 | + worldwide. Ask questions, share experiences, and learn from teams who’ve |
| 206 | + successfully adopted the DITA language. [Join Community →]</p> |
| 207 | + <hr/> |
| 208 | + <h2 id="community-section">Community Section</h2> |
| 209 | + <h3 id="built-by-the-community-for-the-community">Built by the |
| 210 | + Community, for the Community</h3> |
| 211 | + <p>The DITA language thrives thanks to contributions from technical |
| 212 | + writers, developers, and organizations worldwide. Whether you’re |
| 213 | + contributing to the language specification, building tools, or sharing |
| 214 | + your experience, there’s a place for you.</p> |
| 215 | + <p><strong>Contribute to DITA</strong> Help improve the language |
| 216 | + specification, contribute to the ecosystem, or share best practices with |
| 217 | + the community. [How to Contribute →]</p> |
| 218 | + <p><strong>Implementations & Tools</strong> Explore the rich |
| 219 | + ecosystem of authoring tools, content management systems, and publishing |
| 220 | + engines that support DITA. [Browse Ecosystem →]</p> |
| 221 | + <p><strong>Resources & Learning</strong> Comprehensive language |
| 222 | + documentation, tutorials, and real-world examples to get you productive |
| 223 | + with DITA quickly. [Browse Resources →]</p> |
| 224 | + <hr/> |
| 225 | + <h2 id="footer-value-proposition">Footer Value Proposition</h2> |
| 226 | + <h3 id="why-choose-dita">Why Choose DITA?</h3> |
| 227 | + <p>DITA isn’t just another markup language—it’s a complete structured |
| 228 | + authoring language that scales with your organization. From |
| 229 | + single-author projects to global enterprise implementations, the DITA |
| 230 | + language provides the semantic foundation that makes your content work |
| 231 | + harder.</p> |
| 232 | + <p><strong>Ready to transform your documentation with structured |
| 233 | + authoring?</strong> [Learn DITA Today →]</p> |
| 234 | + <hr/> |
| 235 | + <h2 id="key-messaging-themes">Key Messaging Themes</h2> |
| 236 | + <ol type="1"> |
| 237 | + <li><strong>DITA as a structured authoring language, not a |
| 238 | + platform</strong></li> |
| 239 | + <li><strong>Language specification that enables ecosystem of |
| 240 | + tools</strong></li> |
| 241 | + <li><strong>Semantic markup that enables professional |
| 242 | + results</strong></li> |
| 243 | + <li><strong>Open standard with broad industry |
| 244 | + implementation</strong></li> |
| 245 | + <li><strong>Language proven in enterprise environments |
| 246 | + worldwide</strong></li> |
| 247 | + <li><strong>Future-proof investment in structured content |
| 248 | + strategy</strong></li> |
| 249 | + </ol> |
| 250 | +</div> |
0 commit comments