Dashboard Page Checks
Checks to run against the files of a finished dashboard page. Each failure below compiles, builds and previews cleanly, so only the code shows it.
Dashboard page UI only. tsc, wix build, and wix preview all check that the code compiles and runs — none of them check that it's the dashboard the UX Success Model describes. A page with a bare, un-summarized, un-openable table compiles cleanly and still fails the requirement — that gap is exactly how a generated dashboard passes every technical check and still disappoints. Measured runs confirm it: a page can compile clean and still ship with none of the three items below, because the earlier checklist entries were a stated intention rather than something re-checked against the code that actually landed.
Re-open every page file you just wrote and check the actual code — not what you intended to include:
The page has a
SummaryBaronly if the request asked for one. Grep for it: an uninvited bar is a defect, not a bonus, and deleting it is the fix. If the request did ask, every metric earns its place and the headline counts what matches the filters (state.collection.total, fed byfetchTotal), not what has been paged in — any metric derived fromkeyedItemsis labelled as such.If a
SummaryBarnumber is fed byfetchTotal, follow that function to the call it makes and confirm the call counts. AfetchTotalthat resolvesundefined— the usual cause beingpagingMetadata.total, which a cursor-paged response does not carry — makes the bar report0beside a table full of rows, and it compiles, runs and passes every other check on this list. It must resolve a number from a count endpoint (items.query(id)…count(), a vertical's own count, or offset paging withreturnTotalCount: true); if the API has none, deletefetchTotaland label the metric as loaded rows. See TABLE_STATE.md.Every row opens an editable entity page by default:
onRowClickcallsnavigateToEntityPage, and the destination has anEntityPage, a working form, and a real save operation. A read-only route is justified by one of the three cases in DRAFT_TEMPLATE.md, and the final response names which one; report-only/export-only requests need no drill-in. The save calls the source's real update method and lets a failed call throw, so the page shows its error — no no-op, local-state-only save, orcatchthat swallows the failure. If Preview is available, change one field, reload to confirm it saved, and change it back; otherwise report the save as unverified. ASidePanelin a collection page file is the defect this replaces.grep -n "<SidePanel" <page files>should return nothing — match the JSX tag, not the bare word, or the templates' own "never a SidePanel" comments fail the check and invite someone to "fix" correct code.Every filter name declared in the toolbar also appears inside
fetchData's query construction — grep for the name in both places if unsure.The table wires
errorState— without it a failed query is indistinguishable from a slow one, and the page you just shipped cannot tell you which it is.Routed templates only (all but the settings one) — the entry file both passes and guards
location.PatternsReactRouterthrows at open whenlocationis missing or stillundefinedon the first render, andtsc,wix buildand even a green build all pass regardless. Both halves are required — thelocation={location}prop and thelocation ? … : nullguard around it, sinceobserveStatehas not fired yet on the first render. Grep the entry file rather than trusting recall:grep -n "observeState\|location={location}\|location ?" src/extensions/dashboard/pages/<page>/<page>.tsx # the file the builder's `component` points atThree hits is correct. A missing guard is the failure mode that has actually shipped: a measured run produced a page whose plumbing looked present and still crashed on open, while a re-run of the same prompt produced a working one — so this is intermittent, and re-running is not a check.
Every
@wix/*vertical imported by the page's api module is a declared dependency, and each one's scope is named in the final report. Any call to a secondary vertical (an enrichment lookup, a filter's options, a search term resolved to ids) is wrapped so its failure degrades that feature instead of failing the page.
If a box fails and no exception applies, add the missing piece now. Do not let "it compiles" stand in for "it satisfies the checklist" — validation (tsc, build, preview) checks the former, this list checks the latter, and they are independent.