AI-Assisted Dashboard and Manifest Editing
Essential knowledgeCore knowledge to understand Fluent Commerce
Changed on:
19 Aug 2026
Overview
[Warning: empty required content area]Key points
- Describe a desired dashboard change in plain language, with enough detail for an assistant to draft a manifest change
- Review a generated manifest draft for correctness without needing to read raw JSON fluently
- Distinguish between draft changes ready to use as-is and those requiring developer follow-up
If you completed the UX Framework Knowledge Track, you've already been introduced to what a manifest is. In short, a manifest is a file that tells the dashboard what to show and where to show it. When you ask AI to implement a dashboard change, it will draft changes to this file.
Describing a Dashboard Change in Plain Language
The three things a good request specifies:- What to add, remove, or change (a field, a widget, a layout section, etc.)
- Where it should appear on the dashboard
- What data it should show
Example request structure
"Add a(n)`object` to `dashboard name`, that shows `information`, positioned `in location`."The request does not have to explicitly following the structure above, but it is recommended to add as much detail as possible. Some sample requests can include:`Add a dashboard tile above the table showing the order count``Add a mystique component that shows a Google Map on a card. Assume the data input is a connection of orders. Show an icon for the fulfillment collection address of each order and zoom accordingly.`