Skip to content

Add React/Vite web client to Phase 1.0 MVP scope - #25

Closed
mforce wants to merge 1 commit into
mainfrom
spec/mvp-frontend
Closed

mforce wants to merge 1 commit into
mainfrom
spec/mvp-frontend

Conversation

@mforce

@mforce mforce commented Jul 15, 2026

Copy link
Copy Markdown
Owner

The scaffold is backend-only (JSON API + Postgres + Traefik) — no frontend. A bare API is not shippable to a farmer, so Phase 1.0 now includes a React/Vite SPA in web/ consuming the JSON API.

Spec changes (specs/product/specs.md)

  • §6 Phase 1.0: new item 10 — web client (login, daily-entry capture, stock view, customers, sales flow, list/history).
  • §7: new Sprint UI block; each screen lands once its API slice exists.

Companion issues (Gitea)

Added frontend slices to the Phase 1.0 milestone: #20 [F0] SPA scaffold + auth, #21 [F1] daily-entry screen, #22 [F2] stock view, #23 [F3] customers + sales flow, #24 [F4] list/history. Epic #13 updated with the frontend track.

Frontend #20 can start in parallel with the backend spine (#6 → #8).


Migrated from Gitea PR #25 (https://gitea.mforcelabs.com/mforce/cluckwork/pulls/25).

The scaffold is backend-only (JSON API + Postgres + Traefik) with no
frontend. MVP is not shippable to a farmer as a bare API, so Phase 1.0
now includes a React/Vite SPA in web/ consuming the JSON API: login,
daily-entry capture, stock view, customers, sales order flow, and
list/history screens.

Adds §6 item 10 and a Sprint UI block in §7.
@mforce

mforce commented Jul 15, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #26 — that branch already contains this commit (ff6d057) plus the SPA scaffold. Merging #26 brings both.

@mforce mforce closed this Jul 15, 2026
@mforce
mforce deleted the spec/mvp-frontend branch July 15, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant