Content requests · evidence first
What should we build next?
A wishlist is easy to write and impossible to rank. So every request below comes with a number taken from the catalog right now — how thin the coverage actually is — measured across 289 components, 116 prompts and 91 guides. The board is ordered thinnest coverage first, and your votes pull the ones you care about to the top.
Honest limit: votes are stored in your browser, so there is no shared tally and no score to game. What is shared is the ordering rule and the measurements, which are recomputed from the catalog on every build — including the fact that this board is ranked by gap, not by popularity.
You have not voted yet, so the board reads thinnest-coverage first.
localStorage · motif:content-votesVue-native variants
Every detail page offers a Vue SFC tab, but no asset declares Vue in its stack list — the tab is generated from the React source. Ship real Vue builds so the tab is not a paraphrase.
measured: 0 of 289 assets list Vue in their stack, while all 289 detail pages render a Vue tab
Empty-state playbook
Empty states decide whether a first session survives. One essay touches them; nothing covers the copy patterns or the illustration budget.
measured: 1 guide has empty states as a tag
Press-and-hold gestures
Hold is the least-covered interaction in the catalog and the one most often needed on touch: press-to-record, press-to-confirm, press-to-reveal.
measured: 1 asset uses “hold”, 5 use “pointer”, across 289 assets
A reduced-motion guide
We ship reduced-motion handling in every animated component but have not written the field guide behind it: what to swap, what to keep, how to test it.
measured: 2 guides carry the reduced-motion tag, against 17 carrying the broader a11y tag
Whole-page templates
Templates assemble the sections into a finished page. Two exist; the section library is 35 deep, so the assembly layer is where the leverage is.
measured: 2 of 289 catalog items are whole-page templates, against 35 sections to assemble
Drag beyond sortable lists
Drag appears mostly as list reordering. Missing: split panes, kanban columns, drag-to-upload zones — the surfaces where drag is the whole interaction.
measured: 17 of 289 assets declare a “drag” behaviour, 4 carry the split tag
Depth in thin prompt industries
The prompt library is wide and shallow: most industries have exactly one brief. A second and third prompt per industry would make adjacency comparisons possible.
measured: 62 of 116 prompts belong to an industry with no other prompt
A11y-strict siblings
For briefs that demand WCAG with no discussion, every popular pattern deserves a sibling audited at 98 or better — not a replacement, an option.
measured: 77 of 289 assets audit at 98+ — 212 sit below that band
Ask with a number
“More drag components” is a feeling. “7 of {COMPONENTS.length} assets declare drag” is a request someone can act on, and it stays true if the catalog changes.
The studio's own picks
The thinnest gaps are not always the most valuable. The ordering here is a map of coverage, not a roadmap — a loud vote on a well-covered area is still a vote.
What gets built
Requests that arrive with a measurement are the ones that survive a planning pass. If a gap closes, its row drops down the board automatically.