<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical Documentation on Bruno Pedro</title><link>https://brunopedro.com/tags/technical-documentation/</link><description>Recent content in Technical Documentation on Bruno Pedro</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 May 2018 10:00:15 -0700</lastBuildDate><atom:link href="https://brunopedro.com/tags/technical-documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing great documentation</title><link>https://brunopedro.com/2012/11/27/writing-great-documentation/</link><pubDate>Tue, 27 Nov 2012 18:09:35 +0000</pubDate><guid>https://brunopedro.com/2012/11/27/writing-great-documentation/</guid><description>&lt;p>&lt;a href="http://jacobian.org/writing/great-documentation/" title="Writing great documentation">Writing great documentation&lt;/a>&lt;/p>
&lt;blockquote>
&lt;p>This advice will mostly be targeted towards those documenting libraries or frameworks intended for use by other developers, but much of it probably applies to any for of technical documentation.&lt;/p>
&lt;/blockquote></description></item></channel></rss>