16 docs tagged with "documentation"

When building projects—especially smaller ones like CLIs—I’ve experimented with various architectural approaches. Two key strategies...

Story of a Simple Issue

About this Site

Learn about bookmark features and functionalities within Docusaurus, a popular open-source documentation site generator.

This documentation page provides detailed information on a particular subject, aiming to facilitate understanding and ease of navigation.

Before writing a single line of code, define the interface. This article explores the power of writing your README first—shaping your application's architecture, revealing edge cases, and driving clarity through documentation.

An overview of essential resources for developers, including documentation, tools, and community links to enhance productivity and knowledge.

Asked to capture design notes for a scanner, the agent filed them under tools/. That directory is only for portfolio-site automation — a convention that existed nowhere in the repo, because the README meant to state it was empty.

Asked to bring internal docs up to date, the agent read a 15-month-old planning doc and declared the feature unbuilt. It had shipped months earlier — including the exact session-tracking code the doc sketched.

This markdown reference guide provides formatting examples for headings, text styles, images, and quotes, specifically for use with Docusaurus documentation.

This document appears to be a placeholder or disabled page with minimal metadata and no specific content.

A handy reference guide summarizing essential basics for quickly picking up or refreshing knowledge of a programming language or stack.

An article generated with an LLM recommended a command as the canonical way to list kitty keybindings. The command returns nothing, and always did. It sat published for months on one of my better-performing pages.

How Docusaurus calculates document routes, including the interaction between routeBasePath, directory structure, doc IDs, filenames, and custom slugs.

A reflection on manual structure, the role of audit tools, and when automation is worth it.

A running case file of assumptions a coding agent made that didn't hold — recorded in a fixed format so the collection can eventually answer when a human actually needs to be in the loop.