Files
web-at-transit-mock/flow_ui/flow-summary.md
T

37 lines
1.5 KiB
Markdown

# Frontend Web Transit Flow Summary
## Diagram
- File: flow_ui/frontend-web-transit-flow-live.png
- Alternate export: flow_ui/frontend-web-transit-flow-live.jpg
- Generated by: flow_ui/build_live_flow.py
## Coverage
- Total pages covered: 5
- Total key actions mapped: 5
- Total visual states captured: 5
## Pages Included
- /
- /stops
- /stops/details?code=at_main_terminal
- /routes
- /routes/101
## Key Actions Mapped
- HOME -> STOPS: click "ค้นหาป้ายหยุดรถ"
- STOPS -> STOP: click a stop card from the stop directory
- HOME -> ROUTES: click "รายละเอียดสายรถ"
- ROUTES -> ROUTE: click a route card from the route directory
- STOP -> ROUTE: click route number inside the stop timetable card
## Layout Notes
- The home page spans both rows so stop discovery and route discovery remain visually connected.
- The top row captures stop discovery ending at the new query-based details page.
- The bottom row captures route discovery ending at the merged route detail page.
- The cross-link from stop timetable to route detail documents the updated user journey after route cards were removed from stop details.
## Assumptions
- The sample stop code remains `at_main_terminal` and sample route remains `101` unless overridden by environment variables.
- The legacy pages `/stops/<code>` and `/routes/<id>/expanded` are now compatibility paths and are intentionally excluded from the primary flow diagram.
- The live capture uses the running frontend at `FRONTEND_BASE` and reflects current backend data.