<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Markdoc on Nicola Iarocci</title>
    <link>https://nicolaiarocci.com/tags/markdoc/</link>
    <description>Recent content in Markdoc on Nicola Iarocci</description>
    <generator>Hugo -- 0.143.1</generator>
    <language>en</language>
    <copyright>Produced / Written / Maintained by Nicola Iarocci since 2010</copyright>
    <lastBuildDate>Fri, 13 May 2022 07:05:25 +0100</lastBuildDate>
    <atom:link href="https://nicolaiarocci.com/tags/markdoc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stripe releases MarkDoc and that&#39;s a good thing</title>
      <link>https://nicolaiarocci.com/stripe-releases-markdoc-and-thats-a-good-thing/</link>
      <pubDate>Fri, 13 May 2022 07:05:25 +0100</pubDate>
      <guid>https://nicolaiarocci.com/stripe-releases-markdoc-and-thats-a-good-thing/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://stripe.com/docs&#34;&gt;Stripe docs&lt;/a&gt; are a marvel, and every developer who&amp;rsquo;s had to deal with them knows
it. After years of painful PayPal interactions, I remember the amazement and
the feverish grin on my face the first time I landed on their API reference.
Stripe API is beautifully designed, but it&amp;rsquo;s the combination of good design and
excellent documentation that paved Stripe&amp;rsquo;s fulgid success.&lt;/p&gt;
&lt;p&gt;A few days ago, they unexpectedly released &lt;a href=&#34;https://markdoc.io/&#34;&gt;MarkDoc&lt;/a&gt;, the &amp;ldquo;powerful,
flexible, Markdown-based authoring framework&amp;rdquo; they use internally to build
their documentation. I skimmed through it only rapidly and, unsurprisingly, got
a great first impression.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://stripe.com/docs">Stripe docs</a> are a marvel, and every developer who&rsquo;s had to deal with them knows
it. After years of painful PayPal interactions, I remember the amazement and
the feverish grin on my face the first time I landed on their API reference.
Stripe API is beautifully designed, but it&rsquo;s the combination of good design and
excellent documentation that paved Stripe&rsquo;s fulgid success.</p>
<p>A few days ago, they unexpectedly released <a href="https://markdoc.io/">MarkDoc</a>, the &ldquo;powerful,
flexible, Markdown-based authoring framework&rdquo; they use internally to build
their documentation. I skimmed through it only rapidly and, unsurprisingly, got
a great first impression.</p>
<p>Fabrizio Ferri Benedetti, who <a href="https://passo.uno/about">knows better than me about docs</a>, published
a solid first-glance <a href="https://passo.uno/markdoc-review/">review of MarkDoc</a> that I think is worth reading.
Spoiler alert, I&rsquo;m quoting below his excellent closing thoughts.</p>
<blockquote>
<p>The secret to Stripe docs does not lie in superior tooling or magical markup
variants: rather, the reason for their success must be found in the quality
of their docs team, whose information architecture needs caused Markdoc to
happen. This is the kind of magic that happens when you provide enough
technical resources to your technical writers and trust them to do the right
thing.</p></blockquote>
<p><em>Update</em>: MarkDoc even received <a href="https://daringfireball.net/linked/2022/05/19/markdoc">John Gruber&rsquo;s endorsement</a>. That&rsquo;s quite an
achievement as Gruber is renowned for dismissing most Markdown extensions.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
