Insights · articles + practical guides

Write down the judgment, not just the answer.

Editorial articles explain the argument. Fumadocs-ready guides preserve the implementation path, limits, and operating context.

Draft directions availableEditorial and guide content await approval.

These are prototype directions—not fabricated full articles or authorship records.

Articles + guides

Content library

Search the approved editorial directions.

These are draft directions from the current prototype, not fabricated full articles or authorship records.

4 editorial directions shown
ARTICLE · DRAFT

How to make a technical decision reversible

A framing for option value, transition cost, and explicit review points.

Body required
ARTICLE · DRAFT

The architecture review is not the decision

Why ownership, sequencing, and operational constraints belong in the same room.

Body required
GUIDE · DRAFT

What self-hostable should promise

A release checklist for adoption without hidden infrastructure assumptions.

Review required
GUIDE · DRAFT

Publishing an architecture decision record

A practical structure for context, options, consequences, ownership, and review triggers.

Review required

Fumadocs-ready guides

Documentation inside the same brand system.

The production route will live under /insights/guides with generated metadata, table of contents, source-relative links, local search, and Green Plus tokens.

Current prototype scope

This static page demonstrates the information architecture. The Fumadocs runtime is connected during the Next.js production phase.

ROUTE

Catch-all guide pages

Stable slugs, static parameters, metadata, and not-found handling.

Ready
READ

TOC and relative links

Clear structure, current-heading state, and robust internal references.

Ready
FIND

Local search

Keyboard access, result counts, no-result state, and static search data.

Ready
ACCESS

Accessible MDX components

Code labels, copy status, diagrams, tables, captions, transcripts, and focus.

Ready
Editorial media requiredImages must explain, document, or establish context.

Lead images, diagrams, and project artifacts need a source, permission, intrinsic dimensions, caption, and useful alt text. Generic technology stock and invented covers are excluded.

Provide editorial assets

Editorial direction

Turn the work into knowledge others can operate.

Discuss the content system