Routing (views, routes, internal links)

Understand Wappler’s modern hybrid routing: routes, layouts, content pages, and route-aware links.

Modern Wappler routing uses routes, layouts, and content pages

Use this bridge to understand where App Connect fits into modern Wappler routing. The recommended workflow is not inline dmx-route components. Instead, Routing Manager stores the generated route definitions, Pages Manager shows the routed layout and content files, and the layout renders the selected content page through dmx-view as partial content.

App Connect still matters in this flow, but in a different role: it powers the interactive page once the route has already selected the correct layout and content page. Internal links and route-aware components should align with the generated route map rather than reintroducing deprecated inline routing patterns.

Hybrid routing

Use this as a focused routing bridge, then continue into route-aware pages, security, and server data.

Continue with

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.

Open tour

Security: Restricting Access to Your Page

Use the App Root security properties to understand shared layout protection, page-specific access rules, and the inspector fields that control login and permission redirects.

Open tour

Server Connect Actions: URL inputs (GET + Param)

Understand URL inputs in Server Connect: query string ($_GET) and path params ($_PARAM), plus how to test them reliably.

Open tour

Go to

Routing and URL Rewrite

Start here for modern Wappler routing: Routing Manager routes, layout pages, content pages, and the URL patterns that shape how users reach your app.

Open destination

App Connect

Your guided index of App Connect tours: reactive model, data components, bindings, events/actions, and common workflows — explained visually in Wappler’s panels and pickers.

Open destination

Wappler Docs Index

Browse Wappler tours by topic and jump into areas like Why Wappler, Learning the Basics, and Wappler's UI.

Open destination

Start with the real Routing Manager map

Start with the live Routing Manager map in Demo Projects HQ. This is the source of truth for route-aware App Connect work, because links and routed content should follow the real generated route tree instead of reviving old inline dmx-route patterns.

Pages Manager overview

Keep the full Pages Manager surface in view before focusing on a specific node. This is the second half of the routing picture: the generated route map points to real layout and content files that live here.

Pages Manager shows the routed files

After the route map is clear, switch to the real Pages Manager structure. In Demo Projects HQ, that is where the actual layout and content files behind those routes become visible and selectable.