{% set page_title = 'Handbook' %} {% include '_header.html' %} {#- A node's Handbook view (ADR-0133 decision 3): what its team writes at length about it — its runbook, how to sign in, its policy, the reference a package ships — on a tab of its own, after Status, Series and History and before Copy, where the node's *About* card on its Status tab holds the short account. It is rendered as every text is — its tables drawn, a status it names drawn as its sign — and its headings are anchored as GitHub anchors them, `## Sign in` at `#sign-in`, so that a link into a section opens there: the one thing this page asks of the renderer that no other does. A link it writes in the short form, `handbook#sign-in`, is a section of the page itself here, and stays in it (decision 4). At the Copy page's measure, which is GitHub's for a README. Not polled: a handbook is read with the configuration, at a restart. -#}
No handbook is written for {{ node.path }}. A deployment states one as handbook:, in nodes.yaml or in its check's file, as text or as the name of a Markdown file.