[JakeSCahill]

The playbook's site.start_page is ROOT:get-started:intro-to-events.adoc, but the docs repo's component is now named streaming, so every build warns Start page specified for site not found. New repos copy this playbook, so the warning spreads. Found by @Feediver1 while reviewing #5.

[Feediver1]

Technical check: point the site start page at the streaming component

Overall: Correct and ready to merge.

• The docs repo's antora.yml is name: streaming on main (26.2) and beta (26.3), and modules/get-started/pages/intro-to-events.adoc exists. Without a version, streaming:get-started:intro-to-events.adoc resolves to the latest stable version, which is what a start page should do.

Follow-up (not for this PR)

• New repos copy this playbook, and it includes aggregate-terms, but it doesn't pull in docs-site's home component. Once docs-extensions-and-macros#370 ships and docs-site#264 merges, new repos would start out with no glossary to link to. Consider adding the docs-site source (start_paths: [home, …]) and glossarypage: home:ROOT:glossary.adoc. Also, package-lock.json resolves the latest dependency to 3.7.0, so copied repos start on a very old release.

[Feediver1]

Docs-standards review, second pass (head 1df695a)

No merge-blockers. It's ready to merge and only needs an approval. Nothing has changed since my 10/13 check. streaming:get-started:intro-to-events.adoc resolves to the latest stable Streaming version, and this fixes the Start page specified for site not found warning that new repos inherit.

My 10/13 follow-up (pulling in the home component and the glossary setting) is now #7. The two PRs edit different parts of local-antora-playbook.yml, so they don't conflict, and they can merge in either order.