Project list and progress
Authenticated workspace routes summarize project state, categories, and progress for repeated review.
Case study
Structured Work Platform
A structured knowledge-work prototype for turning projects into stages, tasks, steps, progress state, document context, and multilingual authenticated workflows.
01 / 06
Product inventory
Repository evidence: routes, data model, interface screens, and workflow code.
- Page routes
- 10
- UI components
- 174
- Schema files
- 8
- Content files
- 81
- Module files
- 82
Project overview
A structured knowledge-work prototype for turning projects into stages, tasks, steps, progress state, document context, and multilingual authenticated workflows.
Project plans, task ownership, documents, step-by-step progress, discussion, permissions, and context usually fragment across separate tools. Vyshyvka explores a model where work is planned as stages, tasks, and steps that remain navigable from board, tree, dashboard, and detail views.
What was built
A broad product-system prototype for dense operational software across collaboration UX, backend modeling, realtime interfaces, and administration.
Interactive project board
Pan, zoom, staged columns, draggable task rows, optimistic ordering, and visible status context support project planning.
Task detail workspace
Task modals organize ideal outcome, plan, work, discussion, permissions, documents, and activity context.
Structured data layer
Drizzle schemas model projects, stages, tasks, steps, users, documents, permissions, support, settings, and translations.
Document infrastructure
Local Wrangler R2 and Cloudflare R2 paths support upload and document-backed work contexts.
i18n
Dictionaries and translation EAV patterns.
Selected details
Implementation details from the product, data, workflow, and infrastructure layers.
- 01
Board, tree, dashboard, and modal views all point back to a staged project model.
- 02
Next.js and Cloudflare infrastructure support the public pages, authenticated routes, data access, and deployment path.
- 03
Reusable feature systems cover grids, forms, hierarchy, documents, feedback, breadcrumbs, and navigation.
- 04
Provider actions and settings routes establish the shape of account, subscription, and workspace administration.
- 05
Document-backed work contexts connect uploads, project records, task detail, and review views.
- 06
Dashboard and hierarchy views expose the same staged work model at different levels of detail.
Systems overview
How the public pages, staff workflows, data, review steps, and infrastructure connect.
Dashboard
Boards, tree, calendar, messages.
Workspace
Authenticated project planning routes.
Work model
Projects, stages, tasks, steps.
Task context
Outcome, plan, work, discussion, files.
Data layer
Drizzle schemas, D1, translations.
Technology
The platform stack behind the build.
Design language
A dark operational map for staged work: columns, compact status rows, teal active states, modal task context, and diagram views that make project structure visible.
Philosophy
A map of work, not a chore list
Vyshyvka keeps stages, tasks, steps, ownership, documents, and context visible across board, tree, and detail views.
Staged project boardsTask context modalsProgress signalsDocument-backed work
Aa
System sans, mono utility, status marksWorkspace UI, counts, project state
Navy#071722
Panel#102636
Teal#22c7b8
Cyan#67e8f9
Mist#d8edf0
Selected screens
Additional screens from the case study.