Demo walkthrough: Route, page, and action handoff
Use Demo Projects HQ to connect route-aware pages, layouts, and the real Server Connect actions that power them.
Use Demo Projects HQ to connect route-aware pages, layouts, and the real Server Connect actions that power them.
Use this bridge when you want one clear route-to-server map. In Demo Projects HQ there are two important handoffs. First, Routing Manager selects the route, Pages Manager exposes the real layout and content files behind that route, and the main layout route runs api/auth/current_user before EJS renders so shared partials can read current_user from locals. Second, once the page is in the browser, the content page can call additional Server Connect actions through dmx-serverconnect components or dmx-serverconnect-form.
That distinction matters: some data is attached server-side during route rendering, while other data is fetched client-side after the page loads. Continue into the validated Demo Projects HQ walkthroughs below depending on whether you want the layout/session path, data loading, or form posting.