Docs
Tech stack
Core frameworks, libraries, and services that power the site.
Stack snapshot
The stack is intentionally small: a fast React framework, a markdown pipeline, and a few
integrations for telemetry. This keeps the site sharp and maintainable.
Next.js
TypeScript
Markdown
Vercel
Runtime
Next.js + React
Pages router, static generation, and client interactivity.
Content
Markdown pipeline
gray-matter, unified, remark, rehype, highlight.js.
UI
CSS modules + Emotion
Scoped styling with targeted component-level overrides.
Ops
Vercel + GitHub APIs
Telemetry, build previews, and repo activity signals.
Runtime and framework
- Next.js (pages router) for routing, static generation, and build tooling.
- React for component composition and page structure.
- TypeScript for typed components and data helpers.
Content tooling
- gray-matter for parsing frontmatter in markdown content.
- unified, remark, and rehype for markdown-to-HTML rendering.
- highlight.js for syntax highlighting in code blocks.
- reading-time (via word count) for post metadata.
Styling and UI
- CSS modules for page-specific styles.
- Emotion for targeted styled components where needed.
- Font Awesome for iconography.
Delivery and metadata
- Vercel Analytics for privacy-focused site metrics.
- GitHub + Vercel APIs for build telemetry and on-demand project detail snapshots.
- RSS/Atom/JSON feeds generated during the build.
- Sitemap generation to expose blog, taxonomy, and documentation routes.
Testing
- Jest for unit and component tests.
- Playwright for browser-based end-to-end coverage.
| Layer | Tools | Why it matters |
|---|---|---|
| Framework | Next.js, React | Fast pages with a predictable routing model. |
| Content | gray-matter, unified | Static content without a CMS. |
| Observability | Vercel, GitHub APIs | Live pipelines and build status surfaces. |
| Quality | Jest, Playwright | Unit + E2E coverage to reduce regressions. |