<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Judd's Publication]]></title><description><![CDATA[Judd's Publication]]></description><link>https://judd.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6a589c2cbc7087ec2139a255/23989897-467d-4ee1-8d04-ceae0885ab39.png</url><title>Judd&apos;s Publication</title><link>https://judd.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 04 Sep 2026 14:16:30 GMT</lastBuildDate><atom:link href="https://judd.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Why I built SVOCS: Svelte-first docs in 2026]]></title><description><![CDATA[The Frustration That Started It All
In 2026, building great documentation should be simple. You write Markdown (or MDX-like files), get beautiful navigation, search, theming, and interactivity—and shi]]></description><link>https://judd.hashnode.dev/why-i-built-svocs-svelte-first-docs-in-2026</link><guid isPermaLink="true">https://judd.hashnode.dev/why-i-built-svocs-svelte-first-docs-in-2026</guid><category><![CDATA[Svelte]]></category><category><![CDATA[Sveltekit]]></category><category><![CDATA[documentation]]></category><category><![CDATA[markdown]]></category><dc:creator><![CDATA[Judd]]></dc:creator><pubDate>Thu, 16 Jul 2026 08:57:46 GMT</pubDate><content:encoded><![CDATA[<h3>The Frustration That Started It All</h3>
<p>In 2026, building great documentation should be simple. You write Markdown (or MDX-like files), get beautiful navigation, search, theming, and interactivity—and ship a fast, static site.</p>
<p>Yet most tools felt... off for me.</p>
<ul>
<li><p><strong>React-heavy ecosystems</strong>: Docusaurus, Nextra, Fumadocs, Vocs, and many others are excellent—but they're built around React (or Next.js). If you're in the Svelte/SvelteKit world, you're either porting styles/components awkwardly or dealing with framework mismatch.</p>
</li>
<li><p><strong>Dated or convoluted alternatives</strong>: Some older generators lack modern polish (no runes, weak component integration, sluggish builds). Others bury you in complex config files, fragile plugins, or heavy dependencies.</p>
</li>
<li><p><strong>The "just works" gap</strong>: I wanted file-system routing from folders, <code>_meta.json</code> for clean ordering, zero-config full-text search, and seamless Svelte components inside Markdown.</p>
</li>
</ul>
<p>So I did what any self-respecting developer does when annoyed enough: <strong>I built it myself</strong>. For the sake of building it, yes—but mostly because I wanted a docs tool that <em>feels</em> like Svelte.</p>
<p>Meet <a href="https://svocs.dev/"><strong>SVOCS</strong></a> — Beautiful docs with Svelte &amp; Markdown.</p>
<h3>What SVOCS Actually Is</h3>
<p>SVOCS is a Svelte-first static documentation site generator. Drop Markdown (<code>.md</code>) or enhanced Svelte Markdown (<code>.svx</code>) into a <code>content/</code> folder, and you get:</p>
<ul>
<li><p><strong>File-system routing</strong> — Folders = routes. <code>_meta.json</code> handles titles, ordering, and grouping. No maze of config files.</p>
</li>
<li><p><strong>Full-powered UI out of the box</strong> — Top nav, sidebar tree, breadcrumbs, table of contents, heading anchors, reading time, dark/light mode.</p>
</li>
<li><p><strong>Zero-config search</strong> — Pagefind indexes everything at build time. Fast, client-side, no servers or API keys. (Plus pluggable backends: Orama, FlexSearch, etc.)</p>
</li>
<li><p><strong>Markdown meets real Svelte</strong> — Write fast in Markdown. Drop live interactive Svelte components wherever you need them. Perfect for demos, charts, etc.</p>
</li>
<li><p><strong>Runes-first reactivity</strong> — Built with Svelte 5 runes. Theme state, sidebar, search—all modern Svelte, no legacy stores.</p>
</li>
<li><p><strong>Tiny &amp; fast</strong> — Static export via <code>adapter-static</code>. ~100KB JS gzipped, 95+ Lighthouse scores, quick cold builds.</p>
</li>
<li><p><strong>Flexible tooling</strong> — First-class support for Bun, pnpm, Deno. Works with your preferred runtime.</p>
</li>
<li><p><strong>Batteries included</strong> — SEO + sitemap, copy/view as Markdown, <code>llms.txt</code> for AI tools, Mermaid diagrams, LaTeX math, accent-color theming, sub-path deploys, and even AI-generated docs from a repo.</p>
</li>
</ul>
<pre><code class="language-bash"># Quick start feel
$ bun run dev   # or pnpm / deno
➜ ready in ~300ms
</code></pre>
<h3>Why "For the Sake of Building It" Matters</h3>
<p>Yes, there was a practical need. But honestly? Building SVOCS was fun. Svelte 5's runes make state management delightful. The compiler's power lets you push a lot to build time. And integrating something like Pagefind feels seamless.</p>
<p>In a React-dominated docs landscape, carving out a native Svelte path felt like the right itch to scratch.</p>
<p>If you're already in SvelteKit, this means:</p>
<ul>
<li><p>No context-switching between frameworks.</p>
</li>
<li><p>Full access to your existing Svelte components.</p>
</li>
<li><p>The joy of runes everywhere.</p>
</li>
<li><p>A docs site that ships as tiny static files.</p>
</li>
</ul>
<h3>Who Is It For?</h3>
<ul>
<li><p>Svelte/SvelteKit users tired of React-centric tools.</p>
</li>
<li><p>Open-source maintainers wanting polished, low-maintenance docs.</p>
</li>
<li><p>Teams that value simplicity, performance, and Git-based workflows (Markdown in repo = ownership and history).</p>
</li>
</ul>
<h3>Try It Yourself</h3>
<p>Head to <a href="https://svocs.dev/">https://svocs.dev/</a> and explore the starter docs.</p>
<p>Quick start (from the site):</p>
<ol>
<li><p>Scaffold a new project.</p>
</li>
<li><p>Add content in <code>content/</code>.</p>
</li>
<li><p><code>bun run dev</code> (or equivalent) and iterate.</p>
</li>
</ol>
<p>The full docs cover components, theming, search backends, AI features, deployment, and more.</p>
<h3>What's Next?</h3>
<p>SVOCS is young and opinionated (by design). I'd love feedback from the community—especially on pain points it solves (or doesn't yet).</p>
<ul>
<li><p>Star it / open issues on GitHub (link in the footer of svocs.dev).</p>
</li>
<li><p>Share your docs sites built with it.</p>
</li>
<li><p>What missing feature would make this your default?</p>
</li>
</ul>
<p>The Svelte ecosystem keeps growing because we build the tools we want to use. SVOCS is my contribution to that.</p>
<p>Thanks for reading—now go write some docs that don't suck.</p>
]]></content:encoded></item></channel></rss>