Placeholder: what an enterprise system remembers

Placeholder text. This post exists only so the layout can be reviewed. Fran replaces it.

Every large system carries a memory of the decisions that shaped it. A field that is never empty because a report in 2009 needed it. A batch job that runs at three in the morning because a data centre in another country once closed at midnight. None of this is written down, and all of it is load-bearing.

This paragraph is here to show what a comfortable reading measure looks like at sixty-five characters, with body text set in Newsreader at 1.2rem and a line height of 1.6. It should feel unhurried, and it should not need a border, a card or a shadow to hold your attention.

A second-level heading

Headings inside the body use the same serif as the title, one step smaller. They should read as pauses, not as signposts.

A pull quote is set in the serif, a little larger and muted, with no rule beside it. It should feel like someone lowering their voice.

A short list, to check the spacing:

  • Cloud, and what it changed about who owns the boring parts
  • AI, and what it changes about who writes the boring parts
  • SAP, where the boring parts live

Inline code such as SELECT SINGLE and a small block:

SELECT SINGLE bukrs FROM t001 INTO @DATA(company) WHERE bukrs = '1000'.

Links look like this one: underlined, and coral only while you hover.

Back to Work