<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Diplomats can code too! (Posts about documentation)</title><link>https://wintermade.it/blog/</link><description></description><atom:link href="https://wintermade.it/blog/categories/documentation.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 20 Oct 2019 20:05:34 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>"What nobody tells you about documentation"</title><link>https://wintermade.it/blog/posts/what-nobody-tells-you-about-documentation.html</link><dc:creator>Alessandro Balzano</dc:creator><description>&lt;div&gt;&lt;p&gt;&lt;a class="reference external" href="https://www.divio.com/blog/documentation/"&gt;What nobody tells you about documentation - Divio.com&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This link from Hacker News' frontpage catched my attention.
Despite the clickbaity title, it is a thorough blog post about documentation, its role and how to write documentation
users will actually enjoy reading.&lt;/p&gt;
&lt;p&gt;To summarize, Daniele (the author of the blog post) defines four kinds of documentation: tutorials, how-to guides, explanations and reference documentation.
They also explain the scope and the role of each kind, and do/don't rules for writing an effective tutorial, how-to guide, &lt;em&gt;et cetera&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;I am not going to summarize that great article: just go read it. Recommended!&lt;/p&gt;&lt;/div&gt;</description><category>documentation</category><guid>https://wintermade.it/blog/posts/what-nobody-tells-you-about-documentation.html</guid><pubDate>Sat, 19 Oct 2019 08:52:16 GMT</pubDate></item></channel></rss>