docs: document the dashboard 48-column grid (#5449)#6329
Closed
florent-leborgne wants to merge 6 commits into
Closed
docs: document the dashboard 48-column grid (#5449)#6329florent-leborgne wants to merge 6 commits into
florent-leborgne wants to merge 6 commits into
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
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
✅ Vale Linting ResultsNo 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. |
Contributor
🔍 Preview links for changed docs |
Co-authored-by: Cursor <cursoragent@cursor.com>
florent-leborgne
added a commit
that referenced
this pull request
May 6, 2026
- Shorten H2 to `## Best practices` to match the other three pages in this PR and parallel #6329's noun-phrase style. - Cross-link the width bullet to the new `Dashboard grid layout` section added in #6329 so readers can find concrete column widths in one click. Co-authored-by: Cursor <cursoragent@cursor.com>
florent-leborgne
added a commit
that referenced
this pull request
May 6, 2026
Move the panel sizing/arranging best-practices section to PR #6329 so it lives inside the new "Dashboard grid layout" section instead of as a standalone section at the bottom of the page. The cross-link in `create-dashboard.md` still points at `#arrange-panels-best-practices`, which #6329 will create. Co-authored-by: Cursor <cursoragent@cursor.com>
Adds an H3 Best practices subsection inside the new Dashboard grid layout H2, covering: - Match panel height to content type - Keep heights consistent within a row - Use width to signal importance (refers to the column reference table above) - Separate primary from secondary content with collapsible sections Cross-references back to Best practices for dashboard design in `create-dashboard.md` (added in PR #6330). Originally drafted in #6330, moved here so all panel sizing / arranging guidance lives in a single section with the grid mechanics. Co-authored-by: Cursor <cursoragent@cursor.com>
The link from `arrange-panels.md` Best practices to `create-dashboard.md#create-dashboard-best-practices` pointed at an anchor that only exists in #6330. Removing it lets this PR merge independently. The reverse direction (`create-dashboard.md` → `arrange-panels.md` Best practices) is kept in #6330 and will resolve once this PR lands. Co-authored-by: Cursor <cursoragent@cursor.com>
florent-leborgne
commented
May 6, 2026
florent-leborgne
commented
May 6, 2026
florent-leborgne
commented
May 6, 2026
Co-authored-by: Florent LB <florent.leborgne@elastic.co>
Co-authored-by: Cursor <cursoragent@cursor.com>
florent-leborgne
added a commit
that referenced
this pull request
May 6, 2026
The target section was renamed to 'Dashboard grid layout and best practices' in #6329, with the H2 anchor 'dashboard-grid-layout'. The old 'arrange-panels-best-practices' anchor no longer exists, so update the link target and label to match. Co-authored-by: Cursor <cursoragent@cursor.com>
Member
Author
Member
Author
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
1 participant
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
This PR addresses #5449 in full and contributes the panel-sizing/arranging portion of #5445.
Changes to
explore-analyze/dashboards/arrange-panels.md:The best practices bullets were originally drafted in #6330 and moved here so all panel-sizing and arranging guidance lives next to the grid mechanics it depends on.
Verified against
elastic/kibanasource:DASHBOARD_GRID_COLUMN_COUNT = 48(src/platform/plugins/shared/dashboard/common/page_bundle_constants.ts)DEFAULT_PANEL_WIDTH = DASHBOARD_GRID_COLUMN_COUNT / 2= 24 (src/platform/plugins/shared/dashboard/common/constants.ts)The 48-column grid is long-standing and not version-scoped, so no
applies_tois added.Resolves
create-dashboard.md,lens.md, andtext-panels.mdis in docs: add dashboard design best practices to existing pages (#5445) #6330.