Server forwarding
Next Route Handlers forward requests to OneHub and keep site context off the visible UI layer.
Platform architecture
Neon front end, contract-first backend.
Gulia is wired to the OneHub API through server-side route handlers, keeping backend context and future credentials out of client bundles.
Public settings
Runtime configuration can be read from OneHub when public values are available.
Request diagnostics
Request IDs and rate-limit state are preserved in responses so support has a trail when something fails.
No fake success
Dynamic modules show loading, empty, rate-limited, or error states instead of inventing backend content.
Locale routing
The deterministic default sends the root path to English while Chinese remains directly linkable.
Policy routes
Account consent links resolve to real Terms, Privacy, and Acceptable Use pages in both languages.
Operations
Built for site launches that keep changing after the first deploy.
OneHub site header
Requests send the configured site context header when ONEHUB_SITE is present in the environment.
Anonymous analytics
Page views are posted to the event endpoint with locale and surface metadata.
Subscriber tagging
Newsletter submissions include game and tournament tags for later segmentation.
Contact source URL
Inquiry submissions preserve the browser URL so operators know which page created the lead.
Credentials stay server-side
The implementation does not expose admin tokens, API keys, or session secrets in NEXT_PUBLIC variables.
Workers compatible
Runtime code relies on Web APIs and avoids filesystem access in application routes.
Hydration-safe auth
Email and phone switching is controlled entirely by client state, independent of hostname.