Info HTML — house style for things Zack reads

A personal house style for HTMLs that exist to be read. Not the visual-design kind. The kind that replaces what would otherwise be a long markdown reply.

First — is this even the right skill?

Two regimes of HTML work, and they don't want to share rules:

• For reading. Research, audit, spec, plan, code review, data brief, explainer. The content is the value, Zack reads it to extract info. → This skill applies.
• For looking at. Landing pages, mockups, marketing pages, demos, UI prototypes. The visual is the product, the audience may not even be Zack. → This skill doesn't apply. Use frontend-design, ui, or emil-design-eng and ignore everything below.

Don't half-apply. Restrained typography on a landing page reads flat; design flourish on an audit reads like marketing pretending to be analysis. If genuinely ambiguous, ask which it is. Don't default to Type I.

The taste

The overall feel: clean and crisp — well-set editorial nonfiction someone wrote for you. Not a dashboard, not a marketing page, not a Notion doc. Light enough to read at length, dense enough to respect the reader's time.

Copy. Write concise. Cut the wind-up, cut the meta-commentary, cut the "in conclusion" paragraph. If a sentence is doing the same work as a heading or a table cell, drop one of them. The point of putting this in HTML is information density — earn the format. A report that respects the reader's time gets re-read.