<?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: Jay Chung</title>
    <description>The latest articles on DEV Community by Jay Chung (@jaychung).</description>
    <link>https://dev.to/jaychung</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%2F1027745%2F145f6ce5-62e5-4585-ac13-86e9719f47ab.jpeg</url>
      <title>DEV Community: Jay Chung</title>
      <link>https://dev.to/jaychung</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jaychung"/>
    <language>en</language>
    <item>
      <title>Why I Built Another Directory Starter from First Principles</title>
      <dc:creator>Jay Chung</dc:creator>
      <pubDate>Fri, 20 Nov 2026 03:14:25 +0000</pubDate>
      <link>https://dev.to/jaychung/why-i-built-another-directory-starter-from-first-principles-nn0</link>
      <guid>https://dev.to/jaychung/why-i-built-another-directory-starter-from-first-principles-nn0</guid>
      <description>&lt;p&gt;&lt;a href="https://zerodirs.com" rel="noopener noreferrer"&gt;ZeroDirs&lt;/a&gt; is a starter for building directory sites, built on Astro and Cloudflare. When I launched it, a fair question came up on X: there are already directory templates out there, so why build another one, and why Astro instead of Next.js?&lt;/p&gt;

&lt;p&gt;This post is my answer. I will not start from the tools. I will start from the problem and work forward.&lt;/p&gt;

&lt;h2&gt;
  
  
  Habit Used to Decide the Stack
&lt;/h2&gt;

&lt;p&gt;Most directory sites I see are built on Next.js. I think the reason is simple: people choose the framework they already know.&lt;/p&gt;

&lt;p&gt;That used to be a sensible rule. Learning a new framework cost weeks, and shipping fast mattered more than picking the ideal tool.&lt;/p&gt;

&lt;p&gt;AI coding agents change this. Claude Code, Codex and Gemini write Astro, Tailwind and SQL as easily as they write React. When an agent does most of the day-to-day coding, &lt;strong&gt;your own familiarity with a framework stops being the bottleneck.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;So the question changes from "which framework do I know?" to this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Which foundation is best for this exact product?&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What a Directory Site Actually Needs
&lt;/h2&gt;

&lt;p&gt;Forget framework trends for a moment. A directory site has four basic needs:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Most pages are read-only content.&lt;/strong&gt; Listing pages, category pages and comparison pages are documents. Search engines crawl them and people read them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search traffic is how you grow.&lt;/strong&gt; A directory is not a dashboard behind a login. Page speed, clean HTML, structured data and internal links decide whether your pages rank.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interactivity is small and local.&lt;/strong&gt; A listing page only needs JavaScript for a few parts, such as search, filters, a submission form or a checkout button.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The bill should be close to zero until traffic shows up.&lt;/strong&gt; A new directory can take months to get indexed. You do not know yet if it will earn anything, so you should not pay a monthly bill while you find out.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why Next.js Is Not the Best Fit
&lt;/h2&gt;

&lt;p&gt;Next.js is a great framework for interactive apps and dashboards. I have used it many times.&lt;/p&gt;

&lt;p&gt;The mismatch is that a directory is mostly static content. Next.js can generate static pages, but it still sends a React runtime to the browser for them. On a site with thousands of generated pages, that is extra weight for pages that only display text and links. You end up using an application framework to serve what is really a content site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Astro on Cloudflare Fits Better
&lt;/h2&gt;

&lt;p&gt;Put the four needs next to each other and Astro and Cloudflare match them well:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Content pages ship no client-side JavaScript.&lt;/strong&gt; They are plain HTML. Nothing loads unless you ask for it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Islands handle the interactive parts.&lt;/strong&gt; Search or a filter can be one small interactive piece while the rest of the page stays static.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare covers hosting.&lt;/strong&gt; Workers, D1 and R2 give you global delivery, a SQL database and file storage in one place, and a small directory fits within the free plan. That keeps the hosting bill at $0 while you test your niche.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why You Still Need a Starter
&lt;/h2&gt;

&lt;p&gt;If an AI agent can write all this code, why not start from an empty folder?&lt;/p&gt;

&lt;p&gt;Because the hard part of a directory is not the pages. It is the plumbing behind them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Stripe webhooks that stay correct&lt;/strong&gt; when Stripe retries or sends the same event twice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paid submissions, featured listings and review queues&lt;/strong&gt;, where a listing moves from draft to paid to approved to live.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Programmatic SEO and internal links&lt;/strong&gt; that do not leave orphan pages or loops once you have thousands of pages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Structured data, social preview images and deployment setup&lt;/strong&gt;, which are easy to forget and slow to fix.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An agent is only as reliable as the project it works in. In an empty folder it will invent its own patterns and can miss details like webhook retries. In a project with clear conventions, an &lt;code&gt;AGENTS.md&lt;/code&gt; file, reusable skills and passing tests, it can build real features safely.&lt;/p&gt;

&lt;h2&gt;
  
  
  What ZeroDirs Is
&lt;/h2&gt;

&lt;p&gt;I built &lt;a href="https://zerodirs.com" rel="noopener noreferrer"&gt;ZeroDirs&lt;/a&gt; from this reasoning:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Choose the stack that fits directory sites: &lt;strong&gt;Astro and Cloudflare&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Package the hard plumbing once, so you do not rebuild it for every directory.&lt;/li&gt;
&lt;li&gt;Organize the repository so AI coding agents can understand it and build on it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffhs10mxgjfqviwvhjbkq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffhs10mxgjfqviwvhjbkq.png" alt="ZeroDirs AI Tools Directory Demo Preview" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You do not have to keep using the framework you learned years ago. Pick the best foundation for your product, start from a solid starter, and spend your time on the things that actually grow a directory: a good niche, good data and distribution.&lt;/p&gt;




&lt;ul&gt;
&lt;li&gt;Explore the project and live demo at &lt;a href="https://zerodirs.com" rel="noopener noreferrer"&gt;ZeroDirs.com&lt;/a&gt; or check out the &lt;a href="https://zerodirs.com/docs/" rel="noopener noreferrer"&gt;ZeroDirs Documentation&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>seo</category>
      <category>astro</category>
    </item>
  </channel>
</rss>
