<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mohsin Ali</title>
    <description>The latest articles on DEV Community by Mohsin Ali (@mohsin_ali_dev).</description>
    <link>https://dev.to/mohsin_ali_dev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4151575%2F20b8babf-ba14-41c8-a2dc-619e76cda633.jpeg</url>
      <title>DEV Community: Mohsin Ali</title>
      <link>https://dev.to/mohsin_ali_dev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mohsin_ali_dev"/>
    <language>en</language>
    <item>
      <title>Why I built a headless CMS just for blogs</title>
      <dc:creator>Mohsin Ali</dc:creator>
      <pubDate>Wed, 30 Sep 2026 06:57:37 +0000</pubDate>
      <link>https://dev.to/mohsin_ali_dev/why-i-built-a-headless-cms-just-for-blogs-3c9f</link>
      <guid>https://dev.to/mohsin_ali_dev/why-i-built-a-headless-cms-just-for-blogs-3c9f</guid>
      <description>&lt;p&gt;Hey DEV 👋 I'm Mohsin, a software engineer with 6+ years building SaaS at ContentStudio, Replug, and Linkwatcher.&lt;/p&gt;

&lt;p&gt;Every product I worked on needed a blog, and every time we hit the same problem. WordPress was easy for writers but slow and theme-locked. Generic headless CMSs gave freedom, but meant days of schema design and building publishing workflows ourselves.&lt;/p&gt;

&lt;p&gt;So I built ContioReach, a headless CMS made only for blogs.&lt;/p&gt;

&lt;p&gt;It connects to any stack through a REST API:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;https://cms-api.contioreach.com/v1/blogs&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;X-API-Key&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;CMS_API_KEY&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;posts&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;res&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When an editor publishes, a webhook tells your site to revalidate, so content goes live without a deploy. It also has built-in SEO &amp;amp; GEO guidance, semantic internal linking, and Google Search Console indexing and tracking.&lt;/p&gt;

&lt;p&gt;It's free to start: contioreach.com&lt;/p&gt;

&lt;p&gt;I'd love to know: how do you run the blog on your projects, and what annoys you most about it? 🙌&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
