[Roadmap] JS-only Quasar UI deployment plan #2
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-review
quasar
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/quasar-ui#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Ship
quasar-uias a browser-first, offline-first JavaScript/TypeScript spin-off of the Quasar design.Fixed architecture
Phase 0 — Foundation
Exit gate: clean checkout builds and tests; architecture boundaries are enforceable; deterministic fixtures exist.
Phase 1 — Local-first graph core
Exit gate: graphs can be created, edited through commands, saved offline, reopened, undone/redone, imported, and exported without a server.
Phase 2 — Editable workbench MVP
Exit gate: a user can open a workspace, create and connect typed nodes, edit properties, arrange the graph, save/reopen it, and operate the core editor by pointer or keyboard.
Phase 3 — JavaScript actions and optional integrations
Exit gate: a local worker action can be discovered, invoked, cancelled, validated, applied, and undone; remote integration remains optional.
Phase 4 — Investigation projections and dashboard
Exit gate: graph, table, map, timeline, dashboard, editor, and document views coordinate through stable IDs without creating duplicate canonical stores.
Phase 5 — Production deployment
Exit gate: the static PWA is reproducibly deployed, installable, offline-capable, secure under its CSP, accessible, performance-budgeted, recoverable, versioned, and rollback-ready.
Production readiness