Multi-page apps

Most real apps are more than one screen. Vorx handles the pages, the links between them and the navigation that ties them together.

Add a page

Ask for it directly: "add a Reports page," "add a settings screen with a profile section." Vorx creates the page, gives it a route, and adds it to the navigation so people can actually reach it — a page nobody can navigate to is a common thing to end up with by accident elsewhere.

Navigation stays in sync

When you add or remove pages, the nav updates with them. Ask to reorder items, group them, or hide a page from the menu while keeping its route:

Move Billing under Settings, and hide the admin page from the main nav.

Link pages together

Describe the connections and Vorx wires them: "clicking a project opens its detail page," "add a back button to the invoice view." Detail pages, breadcrumbs and cross-links are all just requests.

Shared layout

Headers, sidebars and footers live in a shared layout, so every page gets the same frame. Change the layout once — "add a search bar to the top of every page" — and it applies across the app.

Protect the right pages

As soon as an app has more than one screen, some of them shouldn't be public. Say which: "require sign-in for everything except the landing page and pricing." See Authentication.

Pages and search engines

Each page gets its own title and meta description, and public pages are crawlable. If your app has a marketing surface, tune it under Settings → SEO — see SEO.

Next steps

• Authentication — deciding who reaches which page
• Components and design — keeping pages consistent
• SEO — titles, sitemaps and social previews