Platform deferred ideas
One page per deferred idea (not now — with a revisit trigger). Check here and rejected before adding a roadmap item or proposal — never re-argue a decided idea.
- AI resource generation — first-ever LLM dependency is a platform decision, not a create-form tweak
- API / SQL dataset providers — external data sources need secret storage + SSRF/injection work with no consumer yet
- Azure AI Search — the only paid parity item;
ilike→pg_trgmcovers current volumes - Blade nav filter + groups — menu furniture over four blades is pure chrome
- Brand kit resource — no cross-editor theming seam exists to consume it
- Create wizard tabs — a wizard over name-only forms is ceremony
- Cross-resource activity feed — needs a second user-keyed table for a feed of your own actions
- Dangling dataset references — delete-time consumer rewrites need real machinery; re-resolve fails soft today
- Dashboard kiosk mode — auto-refresh of baked snapshots refreshes nothing; needs live reads first
- Dataset joins — a query language's first feature; design only after tracked participants create real demand
- Dataset row-cap pagination — no consumer has hit the 1000-row cap
- Draft version history — session undo + publish snapshots cover recovery today
- Resource collaboration — ACLs + concurrent editing are each their own project; publishing covers read-sharing
- Email sending — needs a delivery service, domain, and compliance subsystem
- Esbabbler link unfurl — OG meta tags unfurl for free; embeds touch the message pipeline
- Create gallery search + categories — seven tiles fit on one screen
- Global calendar — cross-resource content query for one flow; the Calendar blade covers it
- Public discover feed — a browse surface before shared content circulates is a feed of nothing
- Publish scheduling — one-click publish needs no timer until publishes have audiences
- Realtime dataset refresh — fetch-on-load + manual refresh covers review workflows
- Comments on published resources — needs identity + moderation; esbabbler is the discussion system
- Resource groups — type facets + search suffice; a group column would be speculative schema
- Resource references — a maintained lineage index is a second source of truth; design with dangling-references
- Resource locks — delete guard + recycle bin cover the single-owner threat model
- Saved views — URL-synced state already makes any view a bookmark
- Survey response push — anonymous writes need digest-first design or they're a harassment vector
- Unauthenticated local resources — a second persistence path doubles every save/load