Conversation
Documents the four dashboard widget types (Chart, Text/Markdown, Control, AI) as dedicated pages under a new Widgets group, mirroring the structure used by Omni's Tiles section. Also adds a package.json for the Mintlify docs site so the dev server can be started with `yarn dev` on port 3002. Made-with: Cursor
- Use "dashboard builder" (the actual product term) instead of "dashboard editor" - Split the Control page into separate Filter widget and Time Grain widget pages, matching the product's Add Filter / Add Time Grain toolbar buttons and the FILTER / TIME_GRAIN widget types - Document the real way to add chart widgets (the Charts picker in the toolbar) - Reflect the AI Widget label and Add AI Widget button used in the UI - Update the product taxonomy rule with the Widget hierarchy under Dashboard builder so future docs use the same terms Made-with: Cursor
- Use plural, widget-free titles in the sidebar: Charts, Text, Controls, AI summary - Combine the separate Filter widget and Time grain switcher pages into a single Controls page with Filter and Time grain switcher sections - Rename the AI page to AI summary and align the docs with the product rename of "AI Widget" / "Add AI Widget" to "AI Summary" / "Add AI Summary" - Document filter / time grain switcher Visibility (Visible, Hidden, Disabled) - Document Controls mapping: automatic mapping when dimensions match, manual remap or disable per chart from a chart's settings menu, time grain switchers restricted to time-typed dimensions, and the fact that AI agents configure these mappings when building dashboards - Replace the bullet list of supported Markdown syntax on the Text page with a link to the Markdown Guide - Update the namings rule to match the new widget taxonomy Made-with: Cursor
|
Claude finished @keydunov's task in 1m 45s —— View job Review of PR #10744: docs: dashboard widgets
Overall this is a well-structured addition of dashboard widget documentation. The content is clear, well-organized, and the navigation hierarchy makes sense. Here are my findings: Issues to address1. The PR adds a new This seems like a local development artifact that shouldn't be committed — the 2. Line 31 has a trailing space after Minor, but worth cleaning up. Suggestions (non-blocking)3. In 4. In 5. Markdown link style is consistent — Good use of reference-style links ( What looks good
SummaryThe documentation content itself is excellent. The main concern is the |
Check List