Ship a reliable integration

This is the Hextra review fixture described in the brand’s Hugo theme guidance. It exercises the states a theme has to prove before it can be approved: hierarchy, link behaviour, callouts, cards, code, status, and one primary action. Compare it against the Docsy fixture in examples/hugo-docsy/ — the two use the same content states, so a migration compares like with like.

Review release check

What the reader needs first

Link text stays blue — the Hextra configuration guide reads as a link, not as emphasis — while the accent-filled control above stays reserved for the next action. On narrow screens the table scrolls inside its own container rather than widening the page.

A card-led decision surface

Cards are scanning aids, not decoration. Their links stay links rather than becoming three competing primary actions.

Code remains a dark working surface

params:
  theme:
    default: system
    displayToggle: true
  navbar:
    width: wide

Inline code such as assets/css/custom.css stays distinct from its paragraph without looking like a second button. The block above stays dark in both theme modes, and its filename bar sits one step above the code surface rather than disappearing into it.

Status language is semantic

Release check

At 320px, check the menu, table overflow, cards, action, code block, and table of contents. At 1280px, check reading measure, the sticky navigation, sidebar hierarchy, and the balance between the content column and its table of contents. Repeat each check in light and dark mode, with keyboard navigation and at 200% zoom.