# Practical recipes

Choose a file-based pattern by audience and operating responsibility. These recipes extend one Markdown workflow; they are not built-in product editions. Each includes a worked specimen, expected reader behavior and checks to run before using it in your environment.

# Compare the patterns

Begin with the personal pattern if you have not built a page yet. The team recipe adds section writing and publication ownership, not concurrent merge. The runbook specimen keeps diagnosis read-only and states when to stop. The organization recipe separates application behavior from governance and infrastructure. The audience recipe separates complete inputs/output targets rather than hiding sidebar folders.

# Keep responsibility explicit

An editor’s section assignment does not make those published pages private. Publish includes saved source, not unsaved buffers, and changes local output only. Browser drafts are recovery aids, not server page history. Review these distinctions before using a recipe as a team operating procedure.

# Adapt and accept

Build specimens in an isolated output folder, then inspect actual routes and heading links. Run the reader task described by the recipe: find the instruction, search for its heading, copy the exact code and read the expected result. Check tables and diagrams at a narrow width and both themes. A source tree that builds is not enough if a reader cannot complete the task.

Keep the smallest useful pattern. Add ownership, review, private hosting and measurement when the need is real. Before a production change, rehearse service permissions, proxy/TLS, backup restore and deployed artifact checks on the actual installation. Local handbook checks do not replace that rehearsal.

Markdown lab isolates formatting behavior. Starter download is a small generic scaffold with prompts, not a substitute for the worked recipes or runtime setup.