v1.39.0 ·
A page for each task
The website taught, with tutorials, and listed facts, with the CLI, phases, templates and glossary. It had no page for "I want to do X, give me the steps." Someone who already knew AIDLC and wanted to run two pieces of work at once had to dig the answer out of a deep-dive chapter written to teach, not to be followed.
What changed
There is a new How-to section at /how-to/, in the main menu between Tutorials and Blog, and site search finds every page. Each page is one task: what you will do, the exact steps, and one thing to run that shows it worked.
Six ship. Add AIDLC to a project you already have. Run two pieces of work at the same time. Change a requirement after its phase is finished. Send your roadmap to GitHub Issues and a Project board. See what a piece of work cost. Keep AIDLC up to date.
I followed every page step by step against the real command line before writing it down. Three of them changed, because the commands did not behave the way my first draft said. This serves people using the product. It adds no lifecycle gate.
Keeping the pages honest
The pages live in the content package under a howto folder, next to the tutorials, so they ship with every install and the website reads them like everything else. I picked a website section over a page set in the repository or a command that prints them.
Every page has exactly three headings, in the same order, and nothing else at that level. A missing, misordered or extra heading fails the website build instead of shipping. The strict shape also keeps each page to one title, which screen readers rely on.
To stop them going stale, I added the pages to the test the tutorials already had. It checks every command shown against the tool's own list of commands and options. One check to maintain, not two. The test lives in packages/website/src/test/tutorial-drift.test.ts. Before trusting it, I broke a page on purpose with a misspelt command and option. The test failed and named the page, the line and the missing part.
What it does not do
It catches a command or option the tool no longer has. It cannot tell you that a page's steps stopped working in some other way.