Files
doclink_web/project-specs/ROUTES.md
2026-04-13 11:26:58 +07:00

1.9 KiB

Routes

This is a proposed route map for the rebuilt app using server-rendered pages plus HTMX fragments.

Public

Route Purpose
/login Login page
/problem-login Login error / access problem screen
/splash Initial redirect / loading screen

App Shell

Route Purpose
/ Dashboard home
/orders Order list
/results Result list / history
/fpp FPP area
/patients Patient registration landing
/settings Account and profile area

Order Flow

Route Purpose
/orders/new Start new order / patient registration
/orders/new/demografi Demographic step
/orders/new/diagnosa Diagnosis step
/orders/new/pemeriksaan Examination step
/orders/new/qrcode QR-based entry
/orders/new/review Review and submit
/orders/:id Order detail
/orders/:id/pesan-khusus Special message

Results Flow

Route Purpose
/results/historical Historical results
/results/pending Result pending list
/results/:id Result detail

Settings

Route Purpose
/settings/change-password Change password form
/settings/account Profile/account page

HTMX Fragment Routes

Route Purpose
/fragments/orders/table Filtered order table
/fragments/orders/detail/:id Order detail pane
/fragments/results/table Result table or cards
/fragments/results/detail/:id Result detail pane
/fragments/fpp/list FPP list fragment
/fragments/forms/order-step/:step Form step content
/fragments/modals/pesan-khusus Special message modal content

Notes

  • Keep route names boring and predictable.
  • Use fragments for dynamic updates, not full page duplication.
  • Avoid the old app habit of making every step a separate top-level page unless it truly helps navigation.