Add detailed frontend UX design spec
This commit is contained in:
4
FAQ.md
4
FAQ.md
@@ -28,6 +28,10 @@ To start with a clean backend state, stop the app and remove the corresponding S
|
||||
|
||||
No. The backend loads state from SQLite once during startup into in-memory state and serves requests from memory. Successful state mutations are then written back to SQLite.
|
||||
|
||||
## Where is the frontend UX plan documented?
|
||||
|
||||
The canonical frontend UX design lives in `UX.md` at the repository root. It defines roles, flows, screen behavior, validation/error handling, responsive behavior, and real-time update expectations to guide implementation.
|
||||
|
||||
## What does test coverage include?
|
||||
|
||||
Coverage now includes the entire backend project (`RpgRoller`), including API/hosting/bootstrap code and services. It is no longer restricted to `RpgRoller.Services.*`.
|
||||
|
||||
Reference in New Issue
Block a user