Docs

Documentation

Engineering notes that explain how the personal site is built and why.

This folder documents the technical structure of the site, the content model, and the decisions that shape the build. The material is written to be readable in the repository and rendered at /docs when the site is built.

Read this like a walkthrough

Each page is a focused slice of the system. Start with architecture, follow the content pipeline, and then explore deployment and testing to understand how everything stays fast and observable.

Static first Data driven Telemetry aware Cache conscious

Start here

System map Architecture

See the major layers, routes, and shared layout decisions.

Content flow Content pipeline

Follow how markdown becomes pages, feeds, and search metadata.

Ship it Deployment

Learn how builds, previews, and telemetry connect end to end.

Cross-post Syndication

Automated publishing to Hashnode and Dev.to with canonical URLs.

Live demos

Telemetry Pipeline status

See live build and repo activity signals.

Previews Work in progress

Preview deployments and active branches.

Interactive Project detail views

Expand cards and load markdown snapshots.

Explore the stack

Technology Tech stack

Frameworks, libraries, and services in use.

Tooling Tools library

Categories of software and services we lean on.

Projects Live examples

Where the stack and tools show up in practice.

How the docs fit together

01. Foundation

Tech stack and architecture set the ground rules.
02. Content systems

Pipeline and docs explain how content becomes pages.
03. Operations

Deployment, telemetry, and testing keep things stable.

Markdown + data

Build pipeline

Static pages

Telemetry + search

Sections

Tech stack overview
Architecture and routing map
Content pipeline and frontmatter conventions
Decisions and tradeoffs
Deployment and operational notes
Telemetry, caching, and API integrations
Testing and QA

Documentation map

Each page covers a specific slice of the architecture and tooling.

Tech stack

Core frameworks, libraries, and services that power the site.

/docs/tech-stack Architecture

How pages, components, and content sources fit together.

/docs/architecture Content pipeline

How markdown becomes pages, feeds, and search data.

/docs/content-pipeline Decisions and tradeoffs

Why the site favors static generation and file-based content.

/docs/decisions Deployment

Build, hosting, and environment configuration.

/docs/deployment Syndication

Automated cross-posting to Hashnode and Dev.to with canonical URLs.

/docs/syndication Testing

Browser and unit test coverage for the site.

/docs/testing