Papers
Long-form and reference
Where work too long for an article lives. Sample entries follow.
What belongs here
Anything a reader would print, cite, or return to with a specific question: specifications, methodology write-ups, benchmark reports, position papers.
The distinguishing test is not length but re-entry. If someone will arrive looking for one section rather than reading start to finish, it belongs here and needs a table of contents.
Reference formatting
| Element | Convention |
|---|---|
| Headings | Sentence case, stable wording |
| Dates | ISO 8601 in datetime, long form visible |
| Figures | Numbered, captioned, described in alt text |
| Tables | Header row marked with <th scope="col"> |
| Corrections | Dated note at the head, original text struck |
Accessibility of long documents
Wide tables sit inside the theme's .table-wrap, which gives them their
own scroll container so the page body never scrolls sideways at 320 px —
the most common WCAG 1.4.10 failure in technical writing.
Headings step by exactly one level. Skipping from h2 to h4 breaks the
document outline that screen-reader users navigate by.