Draft: Restructure Streams docs#6665
Conversation
Reorganizes streams.md to lead with what Streams is, why to use it (Organize logs / Get meaning from logs / Find problems in logs), prerequisites, real-life use cases, and recommended paths for novice and expert users. All original reference sections are preserved. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
🔍 Preview links for changed docs |
Vale Linting ResultsSummary: 1 warning found
|
| File | Line | Rule | Message |
|---|---|---|---|
| solutions/observability/streams/streams.md | 44 | Elastic.Spelling | 'expirations' is a possible misspelling. |
The Vale linter checks documentation changes against the Elastic Docs style guide.
To use Vale locally or report issues, refer to Elastic style guide for Vale.
alaudazzi
changed the title
|
@copilot resolve the merge conflicts in this pull request |
Co-authored-by: alaudazzi <46651782+alaudazzi@users.noreply.github.com>
Resolved the merge conflict and merged |
…ic/docs-content into alaudazzi/streams-page-restructure
|
@copilot fix the CI checks |
Agent-Logs-Url: https://github.com/elastic/docs-content/sessions/87f3636c-365c-495d-9c83-d02974363f56 Co-authored-by: alaudazzi <46651782+alaudazzi@users.noreply.github.com>
Fixed the CI-breaking docs links in |
…ic/docs-content into alaudazzi/streams-page-restructure
|
@copilot fix the CI checks |
Agent-Logs-Url: https://github.com/elastic/docs-content/sessions/babda2a1-ef0d-4216-a196-0df69879452c Co-authored-by: alaudazzi <46651782+alaudazzi@users.noreply.github.com>
Fixed the current docs-build error in |
…ic/docs-content into alaudazzi/streams-page-restructure
===== PLEASE DO NOT REVIEW =====
Summary
Restructures
solutions/observability/streams/streams.mdaround a user-first narrative.The current pages jump straight into implementation details without explaining what Streams is, why someone should care, or how to get started. We want to reorganize the content around user needs.
This is an example of how the landing page could be reworked:
And this is an example of how the new Getting started could look:
@mdbirnstiehl This high-level flow originates from the various docs I've been going through. It needs to be tested.