Web
Architecture notes for apps/web
apps/web is the end-user web interface for browsing Unicode data and store-backed content.
Role
- Renders the public frontend with TanStack Router and React Query.
- Uses server functions to talk to
ucd-storefrom the server side. - Bridges user navigation, SSR context, and data access without exposing store internals directly to the browser.
Related Docs
UCD Store
Server functions cache and use HTTP-backed store instances.
Client
Compare direct API-client consumption with the higher-level store path used here.
Store App
The web app reads store data through server-side store instances targeting the hosted store.
Docs App
Both apps use TanStack Router, but this one is an end-user product UI.
Mental Model
The web app splits into two halves:
- client-side routing, React Query, and view composition
- server-side functions that create and cache HTTP
ucd-storeinstances
That keeps file access on the server while still giving the browser a modern router/query model.
Request Flows
App bootstrap
Server-side store access
listVersionFiles and getVersionFile
Design Notes
- The app prefers
ucd-storeover raw client calls for file-oriented reads. - Store instances are cached per base URL to avoid rebuilding them on every server-function call.
- The browser does not need direct knowledge of store topology or file-serving details.
verify: falsekeeps remote read access cheap for request-time usage.
Testing Use
- server-function success and error behavior
- router/query integration with SSR context
- store caching per
apiBaseUrl - page flows that depend on file list and file content resolution