Blog
Insights & Guides
Tips on documentation, AI-powered workflows, and shipping better developer experiences.
Docs as Code vs WYSIWYG: Which Should Your Team Pick?
A head-to-head comparison of docs as code vs WYSIWYG editors across seven dimensions, with verdicts on each and a recommendation by team type.
How to Write Documentation for Non-Technical Stakeholders
Execs, sales teams, and legal read docs to make decisions, not to implement code. Rewrite technical content for each audience without losing accuracy.
How to Document a FastAPI Backend: A Three-Layer Walkthrough
Document a FastAPI backend end to end: OpenAPI reference, conceptual docs, and a quickstart. Worked example with real routers and Pydantic models.
How to Document a Supabase Backend: Schema-First
A step-by-step walkthrough for documenting a Supabase backend: tables, RLS policies, edge functions, and published docs. Worked example with a real schema.
How to Write an llms.txt for Your Documentation
What llms.txt is, why your docs site needs one, and a complete template you can copy. Plus the 80/20 rule for writing one that actually helps LLMs.
Remote Teams Should Write Docs the Same Day They Decide
Most remote teams write docs as a summary of decisions made last week. By then the context is gone. Here's the decision-day docs rule I use instead.