Dashboards first 20 lines optimization

[florent-leborgne]

Summary

This PR updates the page opening of all Dashboards docs pages. In particular:

• Check that the frontmatter is correct and contains the right metadata
• More generally, frontmatter is often missing an intentional description in many docs files
• Optimized H1
• Optimized page intro based on basic content types (tutorial/explanation/guide/reference) that provides better context and sets better expectations

These changes follow instructions provided to AI following an onweek project: https://github.com/florent-leborgne/mi-instructions

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 with Claude Sonnet 4.5

[github-actions]

Vale Linting Results

Summary: 5 suggestions found

💡 Suggestions (5)

File	Line	Rule	Message
explore-analyze/dashboards.md	25	Elastic.WordChoice	Consider using 'efficient' instead of 'simple', unless the term is in the UI.
explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md	16	Elastic.FutureTense	'you'll have' might be in future tense. Write in the present tense to describe the state of the product as it is now.
explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md	16	Elastic.FutureTense	'you'll have' might be in future tense. Write in the present tense to describe the state of the product as it is now.
explore-analyze/dashboards/import-dashboards.md	14	Elastic.WordChoice	Consider using 'efficient' instead of 'easy', unless the term is in the UI.
explore-analyze/dashboards/using.md	16	Elastic.FutureTense	'You'll also' might be in future tense. Write in the present tense to describe the state of the product as it is now.

[github-actions]

🔍 Preview links for changed docs

• explore-analyze/dashboards.md
• explore-analyze/dashboards/add-controls.md
• explore-analyze/dashboards/arrange-panels.md
• explore-analyze/dashboards/building.md
• explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md
• explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md
• explore-analyze/dashboards/create-dashboard.md
• explore-analyze/dashboards/drilldowns.md
• explore-analyze/dashboards/duplicate-dashboards.md
• explore-analyze/dashboards/import-dashboards.md

More links …

• explore-analyze/dashboards/managing.md
• explore-analyze/dashboards/open-dashboard.md
• explore-analyze/dashboards/sharing.md
• explore-analyze/dashboards/tutorials.md
• explore-analyze/dashboards/using.md

[benironside]

Overall I like this. Most of my suggestions were very minor. After a while I stopped commenting about possibly using attributes in the page description frontmatter, in case it's not applicable. Was this all done by AI or did you participate too?

[florent-leborgne]

Thanks @benironside - to answer your questions:

• yes all of this is AI-generated as I'm working on refining a set of instructions, which explains some of the styling here - we're missing this kind of things in about every single page we have, so we must find a way to implement it in a way that requires minimum creation and review efforts yet still leading to significant improvements and good (enough) quality.
• we can't use variables in the frontmatter right now

[alaudazzi]

I left a few suggestions that AI might reconsider :)

[florent-leborgne]

Noticed a few things were wrong with the privilege terminology - I fixed them here and will fix them in the instructions too.
I think it's merge-able but lmk if you think otherwise

[bmorelli25]

@alaudazzi can you pls take another look at this

[alaudazzi]

Left a few more comments.

[alaudazzi]

@florent-leborgne I started reviewing, and I can continue tomorrow.
It looks good. A couple more points for your consideration:

1/
Some screenshots could be removed (Use filter pills) and
some screenshots could be retaken (Apply a global time range to an entire dashboard)

2/
It's weird to have the headings in reverse order between landing page and nav:

[alaudazzi]

@florent-leborgne I scanned through the remaining pages, they look good to me. I haven't tested every single step of the many procedures documented in these pages. Tutorials are OK because they were recently refreshed against the current UI.

[alaudazzi]

LGTM