<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Documentation on Software Factory</title><link>/tags/documentation/</link><description>Recent content in Documentation on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Technical Documentation</title><link>/use/practices/code/technical-documentation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/practices/code/technical-documentation/</guid><description>&lt;h2 id="practices-for-writing-technical-documentation"&gt;Practices for writing technical documentation&lt;a class="td-heading-self-link" href="#practices-for-writing-technical-documentation" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Here are some best practices for writing clear and effective technical documentation:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Know Your Audience&lt;/strong&gt;: Understand who will be reading the documentation
(developers, end-users, stakeholders) and tailor the content to their level of expertise and needs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clear Structure and Organization&lt;/strong&gt;: Use a logical structure with clear headings and subheadings.
Maybe include a table of contents for easier navigation, especially for lengthy documents.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clarity and Conciseness&lt;/strong&gt;: Break down complex concepts into manageable sections or steps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consistency&lt;/strong&gt;: Maintain consistent terminology, tone, and style throughout the document.
Also use a consistent format for headings, code blocks, and lists.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Code Examples&lt;/strong&gt;: Include code snippets to demonstrate concepts and provide real-world examples.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maintain and Update&lt;/strong&gt;: Regularly review and update the documentation to keep it current
with any changes in the project or software.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="useful-links"&gt;Useful links&lt;a class="td-heading-self-link" href="#useful-links" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developers.google.com/tech-writing/overview" class="external-link" target="_blank" rel="noopener noreferrer"&gt;Google technical writing&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.gitlab.com/ee/development/documentation/styleguide/" class="external-link" target="_blank" rel="noopener noreferrer"&gt;GitLab doc style guide&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="presentation-of-diatixis"&gt;Presentation of Diatixis&lt;a class="td-heading-self-link" href="#presentation-of-diatixis" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The Diataxis framework is a comprehensive approach to organizing technical documentation.&lt;/p&gt;</description></item></channel></rss>