docs: export individual dashboard panels as JSON (#7611) - #7956
Open
florent-leborgne wants to merge 13 commits into
Open
docs: export individual dashboard panels as JSON (#7611)#7956florent-leborgne wants to merge 13 commits into
florent-leborgne wants to merge 13 commits into
Conversation
AI-Assisted: OpenAI Codex (GPT-5)
Contributor
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. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! 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. |
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
AI-Assisted: OpenAI Codex (GPT-5)
Contributor
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: Mostly solid; one inline comment on a list-punctuation/Oxford-comma inconsistency in the new "Export a panel as JSON" section.
- Jargon: None found — panel/control/library terms are already used consistently elsewhere on the page.
- Frontmatter and applies_to: New section-level
applies_toblock (stack: preview 9.6+,serverless: preview) is correctly placed directly under the heading with no blank line, matches the linked issue's stated availability (Stack v9.6.0 preview, Serverless preview), and doesn't conflict with the page-levelgatag since it's properly scoped to the new section. - Content type fit: Fits the existing how-to page structure; the new section follows the same pattern as sibling "Export JSON" section (intro paragraph, numbered steps, screenshot).
- Contradictions: No contradictions found against published docs or the rest of this page.
- Parent issue satisfaction: Satisfied — the PR adds the panel-level Export JSON entry point, describes the Show full configuration switch for library-linked panels, and clarifies scope differences (filters/time range) as requested in #7611.
Notes
- Pre-existing Vale warning on line 2 (
mapped_pages) is untouched by this PR and out of scope for this review.
Generated by Docs review agent for #7956 · sonnet50 · 40.5 AIC · ⌖ 6.5 AIC · ⊞ 17.1K
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
florent-leborgne
marked this pull request as ready for review
August 13, 2026 19:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #7611.
Product sources reviewed: elastic/kibana#273427, elastic/kibana#281795, and current Kibana
main. Product PR #273427 merged tomainwith thev9.6.0label before the 9.6 branch cut.Validation
git diff --checkpassedapplies_to, content type, frontmatter, and link checksGenerative AI disclosure
Tool(s) and model(s) used: OpenAI Codex (GPT-5). Used to triangulate the docs issue and related product work, verify the current implementation, draft the change, and run documentation checks.