Subject
7 entries
Documentation
Bookmarks
Claude Interactive Documentation Workflow: markdown before code
A structured interview-to-implementation workflow using Claude Code: document first, then code. The methodology produces specs that keep LLMs guardrailed and documentation that doesn't require clarifying questions.
Lightweight Architecture Decision Records
Peter Evans' lightweight ADR repo is a minimal five-section template for capturing architecture decisions in plain markdown files stored alongside code. The approach lowers the adoption barrier enough that even skeptical teams can accept the overhead, keeping decisions documented at the moment they're made.
Architectural Decision Records (ADRs)
The ADR (Architectural Decision Records) site is the canonical resource for documenting significant design choices alongside their context and rationale. It matters because decision records address the institutional memory problem in software teams—why something was built a certain way is often lost over time, leaving future developers unable to distinguish intentional choices from accidents.
Documentor: documentation aggregator for AI assistants
Documentor is a tool for aggregating external documentation into a format optimized for LLM consumption — crawling docs sites, building search indexes, and storing structured outputs that AI assistants can query during development work.
React Docs Beta
The beta rewrite of the React documentation — hooks-first, with interactive examples and a complete rethinking of how React concepts are taught. This eventually became the official react.dev site.
Raneto — Markdown-Powered Knowledgebase for Node.js
Raneto is an open-source, flat-file knowledgebase for Node.js that stores all content as Markdown files — no database required. A 2014 example of the then-emerging pattern of Markdown-as-content-store that later influenced tools like Obsidian and Notion.
GitBook — Documentation and Book Publishing Platform
GitBook (2014) is a platform for writing and publishing books and documentation from Markdown and Git. It combined the Git workflow developers already knew with a clean web publishing layer, making it natural for technical writers and open source projects.
