<?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 Aaron West's technology blog</title><link>https://www.aaronwest.net/tags/documentation/</link><description>Recent content in Documentation on Aaron West's technology blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 03 Aug 2015 12:45:00 -0500</lastBuildDate><atom:link href="https://www.aaronwest.net/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Better Documentation Using Conventional-Changelog</title><link>https://www.aaronwest.net/blog/better-documentation-using-conventional-changelog/</link><pubDate>Mon, 03 Aug 2015 12:45:00 -0500</pubDate><guid>https://www.aaronwest.net/blog/better-documentation-using-conventional-changelog/</guid><description>&lt;p&gt;One of the things I&amp;rsquo;ve been playing with at work is &lt;code&gt;conventional-changelog&lt;/code&gt; and the concept of generating a CHANGELOG.md for most projects. We&amp;rsquo;ve double-downed our effort to create more and better documentation and as part of the effort I researched ways to generate documentation automatically and have said documentation be as close to the code as possible.&lt;/p&gt;
&lt;p&gt;Our team suggested I look at &lt;code&gt;conventional-changelog&lt;/code&gt;, a tool two of our engineers were interested in baking into our process. After using it in an R&amp;amp;D capacity for a few weeks I feel comfortable talking about its usage.&lt;/p&gt;</description></item></channel></rss>