Skip to content

Add product documentation hub pages - #7964

Draft
florent-leborgne wants to merge 5 commits into
mainfrom
docs-hub-pages-v1
Draft

Add product documentation hub pages#7964
florent-leborgne wants to merge 5 commits into
mainfrom
docs-hub-pages-v1

Conversation

@florent-leborgne

@florent-leborgne florent-leborgne commented Aug 14, 2026

Copy link
Copy Markdown
Member

Summary

Adds first-cut product hub pages at /products/<product> for Elasticsearch, Kibana, Logstash, and Elastic Stack, using the shipped {hero} / {get-started} / {whats-new} / {explore} directives.

Relates to docs-content-internal#1561 (architecture: #1550).

  • Hub pages live in products/ (layout: hub). There is no /products/ landing page.
  • {whats-new} cards for Elasticsearch, Kibana, and Logstash are authored in hub-whats-new.yml from the published 9.5 release notes and the Elastic 9.5 blog.
  • The Elastic Stack hub uses a regular What's new card group that links to Elasticsearch, Kibana, Logstash, Observability, and Security release notes. It does not use {whats-new}.
  • get-started/the-stack.md is unchanged and does not link to the hub.
  • Refresh skill: .agents/skills/docs-hub-whats-new/ (user-invoked).

CODEOWNERS follow the same team split as the rest of the repo (last match wins, so these replace the catch-all @elastic/docs):

Path Owners
products/elasticsearch.md @elastic/developer-docs @elastic/admin-docs
products/kibana.md @elastic/ski-docs @elastic/admin-docs
products/logstash.md @elastic/ski-docs
products/elastic-stack.md @elastic/core-docs
products/ (toc and future files) @elastic/docs
hub-whats-new.yml @elastic/developer-docs @elastic/ski-docs @elastic/core-docs

The /triage team-path table is updated to match. Easy to change if a team should own a hub instead.

Out of scope here: v8/v7 hubs, the top-bar Products dropdown (docs-content-internal#1589). Adding toc: products will create a Products primary-nav item until that lands.

Follow-up

Elastic Stack hero icon: elastic/docs-builder#3875. Until that merges, the hub falls back to an E chip.

Test plan

  • Preview /products/elasticsearch, /products/kibana, /products/logstash, and /products/elastic-stack
  • Confirm What's new cards render for ES, Kibana, and Logstash, and that the Stack hub shows five release-notes cards
  • Confirm get-started/the-stack has no link to the hub
  • Confirm a Products item appears in the primary nav
  • Confirm hub links resolve in the preview build
  • Confirm GitHub requests the CODEOWNERS above on this PR

Screenshots to add or update

None. Hub pages are directive-composed and do not add product UI screenshots.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

Tool(s) and model(s) used: Cursor Grok 4.6 (drafting hub Markdown, hub-whats-new.yml, the refresh skill, and CODEOWNERS from the POC branches, published 9.5 release notes, and the 9.5 blog)

…c Stack

Give each product a documentation landing page at /products/<product>, with What's new cards sourced from the 9.5 release notes.

AI-Assisted: Cursor Grok 4.6
Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

Route each hub to the same docs team that owns the matching product area, and keep the triage mapping in sync.

AI-Assisted: Cursor Grok 4.6
Co-authored-by: Cursor <cursoragent@cursor.com>
Point Fleet and Elasticsearch clients at their index pages, and send Logstash plugin links through logstash-docs-md.

AI-Assisted: Cursor Grok 4.6
Co-authored-by: Cursor <cursoragent@cursor.com>
Comment thread .github/CODEOWNERS Outdated
@florent-leborgne

Copy link
Copy Markdown
Member Author

@bmorelli25 @leemthompo you can continue your hub edits on this branch if you like - the elastic-stack one I haven't reviewed at all yet it's just based on some specs I passed

Point Console at Dev Tools, send get-started ingest to the manage-data overview, and surface data views, KQL, serverless, Spaces, and AI Assistant.

Co-authored-by: Cursor <cursoragent@cursor.com>
@bmorelli25

bmorelli25 commented Aug 14, 2026

Copy link
Copy Markdown
Member

Cool. I'll move what I have in #7910 over to this PR.

Never mind, I see you're (at least) one step ahead of me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants