Hub pages 3/4: {get-started}

[florent-leborgne]

Part 3 of 4, based on #3826. Implements elastic/docs-content-internal#1382.

Demo: Demo: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/3827/examples/products/docs-builder

The onboarding section of a hub page. It gives a new reader one opinionated path to a first success, before they face the full link list. The section is optional.

Structure

Three steps, following the prototype. The first offers two equally weighted ways to start, and the rest are single steps.

Shape	Fields	Renders as
Options	title, options[]	Two or more equally weighted paths side by side, each with a command or a link
Link	title, description, link, link-label	The whole card is clickable
Plain	title, description	A static card

Nothing renders between the intro and the numbered list. An install command belongs in steps[0].options[], which keeps the whole path inside the numbered sequence. The prototype's install and tutorial fields are removed: they placed content above the steps, which the structure does not call for.

Implementation choices

A step option's command uses the standard code block. It renders inside .highlight pre with a language class, which is what the site's copy button and syntax highlighter select on. Both attach with no extra wiring, because the hub layout kept the markdown-content id in #3825. That gives the Copy affordance the designs show.

Step numbering sits before the title. The section describes a sequence, and the number is what carries that. The designs put it in the card corner, which turns it into a decorative counter the reader meets after the title.

No per-step icon. The prototype has steps[].icon, resolved through EuiSvgIcons. It is removed. In the designs the icons restate the step title, the number badge is already the card's visual anchor, and a schema field that exists for decoration means every author picks icons that then drift between hubs.

Machine-readable output. The LLM export renders steps as an ordered list, with options as sub-items carrying their command or link. The search body gets nothing, as with the other hub directives.

Example page

The example hub's section uses every field once and shows all three step shapes, so it can be copied and trimmed rather than extended.

Testing

./build.sh unit-test passes. dotnet format and npm run fmt:check are clean. A full docs build reports 0 errors and 0 warnings.

tests/authoring/Blocks/Hub/GetStarted.fs covers all three step shapes, a step option's command landing in a highlightable code block, automatic numbering, that nothing renders above the steps, and two failure paths.

Screenshots to add or update

None attached. The side-by-side option layout in step one is worth checking on the preview.