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.

Routing Manager is the live source of truth

Start from the live Routing Manager surface in Demo Projects HQ. This is where Wappler keeps the generated route map for the project, so it is the correct entry point for understanding how URLs, layouts, and routed content pages are actually connected.

Read the generated route tree

The Routing tree is the practical map to read next. It shows the route hierarchy Wappler generated for the project, which is the structure your layout pages, content pages, and route-aware links need to follow.

Routing and URL Rewrite

Use this page as the modern routing map through Wappler. The source of truth is the live Routing Manager, not inline client-side route components. In Demo Projects HQ, the real Routes root is the place where that generated map begins.

The mental model to keep is simple:

Routing Manager defines how URLs map into pages
layout pages provide the shared shell
content pages are injected into the layout and rendered as partial content
internal links should follow those generated routes

That is the hybrid routing workflow to teach now. Older inline dmx-route patterns are legacy and should not be the main path for new projects or docs.