<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Markdown on galvanist</title>
    <link>/tags/markdown/</link>
    <description>Recent content in Markdown on galvanist</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 28 Apr 2019 10:16:33 -0700</lastBuildDate>
    <atom:link href="/tags/markdown/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Better Documentation of Data with Markdown Tables</title>
      <link>/posts/2019-04-28-markdown-tables-from-dicts/</link>
      <pubDate>Sun, 28 Apr 2019 10:16:33 -0700</pubDate>
      <guid>/posts/2019-04-28-markdown-tables-from-dicts/</guid>
      <description>&lt;h1 id=&#34;documentation--markdown-tables&#34;&gt;Documentation &amp;amp; Markdown Tables&lt;/h1&gt;&#xA;&lt;p&gt;Documentation is a vital part of almost any technical project. However, maintaining good documentation is hard for many reasons, one being that the time needed to document things is time you&amp;rsquo;re &lt;em&gt;not&lt;/em&gt; spending on the &amp;ldquo;building / fixing / operating / assisting&amp;rdquo; aspects of your work &amp;ndash; this is especially painful when you have lots of other urgent or important work to do.&lt;/p&gt;&#xA;&lt;p&gt;Therefore, an important value of any documentation system is to make it  &lt;strong&gt;as easy as possible&lt;/strong&gt; for the would-be documenter to access, create, and edit content at any time. This includes enabling the documenter to express their ideas without requiring excessive authentication, cumbersome markup, or slow / complex UI interactions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
