Layout

how a page sits on the screen

A page has the sidebar on the left and the article beside it, and the two scroll separately.^[1] How a page's parts are named is described on Pages.

Sidebar

The sidebar is exactly the window's height and never scrolls as a whole: the logo and the search box stay at its top, and only the list of pages beneath them scrolls.^[1] Scrolling that list never moves the article, and scrolling the article never moves the sidebar.^[1] A page far down a long list opens with its own link scrolled into view.^[2]

Article

Every code block has a Copy button in its top right corner.^[3] A code block beside the infobox is narrowed to fit beside it, so its button is never hidden underneath.^[4] A table in a page is drawn as a wiki table, and scrolls inside its own frame when it is wider than the screen.^[5] A list is indented and spaced like the references at the foot of the page.^[6] A link that leaves the wiki opens in a new tab and ends in an arrow.^[7] A flowchart or other diagram written in a mermaid code block is drawn as a diagram, the way GitHub draws one, and the page's markdown keeps the block as written.^[8] The drawing needs no network, and only a page with a diagram loads it.^[8] How to write one is described on Diagrams.

Footer

Every page ends with a footer the build writes: when the page last changed, how many words it has, about how long it takes to read, how many sources it cites, and how many of its claims have no source.^[9] A reader-facing build leaves out the two citation counts.^[9] So does a page excused from citations, such as the goals page, because it has nothing to count.^[9] The reading time counts 250 words a minute, the pace a 500-word page answering in about two minutes assumes.^[10]

Narrow screens

Below 900 pixels wide, the sidebar sits above the article, and its page list opens from a Menu button.^[11]