We shipped a documentation section covering every product we make. It lives at fieldbw.com/docs and covers six products: Signal Recorder SR-7, Task Register TR-1, Focus Timer, MIDI Volume Control, Menu Volume, and Rock or Pop.
What’s There
SR-7 has the deepest coverage — getting started, a hardware import guide for the TP-7 and other recorders, MCP server configuration, best practices, and use cases including cross-product workflows with TR-1.
TR-1 includes a GTD primer for people new to the methodology, a full MCP tools reference covering all 40+ agent tools, a REST API reference with every endpoint, and a use cases page with practical examples — from email triage to multi-agent workflows.
Focus Timer has a getting started guide and a Pomodoro primer on when and how to use timed focus sessions.
MIDI Volume Control, Menu Volume, and Rock or Pop each have getting started guides covering setup, features, and usage.
One Place for Everything
The product line is growing — native apps, web tools, utilities, each with their own capabilities and integration points. Having documentation scattered across individual product pages, README files, and support threads doesn’t scale. A unified docs hub gives every product a consistent home for getting started guides, technical references, and practical examples.
Whether someone is setting up SR-7’s MCP server, looking up the parameter list for process_inbox_item in TR-1, or figuring out how to connect a TP-7 to import recordings — the answer is in the same place, with the same structure, linked from the same navigation.
The docs are also integrated with llms.txt, so AI tools that read that file now get documentation links alongside blog posts and product descriptions.
Everything lives at fieldbw.com/docs, linked from the main navigation and from each product page.