
<h2 id="routing">Routing</h2>
<ul>
  <li>The site uses the Next.js pages router under <code>pages/</code>.</li>
  <li>Static pages live at routes like <code>/about-me</code>, <code>/projects</code>, <code>/tools</code>, and <code>/hobbies</code>.</li>
  <li>Blog content is rendered from dynamic routes under <code>/blog</code>, including tags, categories, and series.</li>
  <li>Documentation renders from <code>/docs</code> and <code>/docs/[...slug]</code> using markdown in the <code>docs/</code> folder.</li>
</ul>
<h2 id="core-layout">Core layout</h2>
<ul>
  <li><code>components/layout.tsx</code> provides the global header, navigation, and page shell.</li>
  <li>Theme switching is handled via a client-side toggle component.</li>
</ul>
<h2 id="content-inputs">Content inputs</h2>
<ul>
  <li><code>posts/</code> stores markdown-based blog posts.</li>
  <li><code>docs/</code> stores markdown documentation that is published to the site.</li>
  <li><code>data/</code> holds structured content for projects, tools, navigation, and hobbies.</li>
</ul>
<h2 id="build-output">Build output</h2>
<ul>
  <li><code>public/</code> serves static assets, RSS feeds, and the generated sitemap endpoint.</li>
  <li>Next.js handles static generation for content pages and server-side rendering only where needed.</li>
</ul>


How pages, components, and content sources fit together.

Architecture

Routing

Core layout

Content inputs

Build output