About the Routing and URL Rewrite category
Single Page Apps and URL Rewriting Made Easy! With the integrated Routing options in Wappler you can create Single Page Applications (SPA). You can also greatly
Routing and URL Rewrite
Section titled “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
Section titled “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
Section titled “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
Section titled “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.
Routing Manager Overview
Section titled “Routing Manager Overview”A quick orientation to Routing Manager so you can understand route structure, layout/content page mapping, and where URL behavior is configured.
Routing Manager Overview
Section titled “Routing Manager Overview”Use this bridge when you want a quick orientation to the current Routing Manager workflow before diving into detailed routing tasks. In Demo Projects HQ, Routing Manager is the live route map that reflects how URLs, layouts, and content pages are actually connected.
Pages Manager creates the route-backed page types. Routing Manager keeps the generated route structure. Layout pages provide the shared shell, content pages attach to routes, and the layout renders that route content through dmx-view. That is why this manager is the right place to explain navigation, route parameters, security, and page inheritance before you open a specific routed page.
Routing tree overview
Section titled “Routing tree overview”The live Routing tree is the practical surface to read first. It shows the generated route hierarchy that Wappler uses for this project, so you can reason about parent routes, nested structure, and where route-specific actions will apply.
Routes root selection
Section titled “Routes root selection”This step selects the real Routes root node. That anchors the overview in the actual Routing Manager tree instead of a static explanation and makes it clear where top-level route operations begin.
Routes root context menu
Section titled “Routes root context menu”This step opens the real context menu on the selected Routes root. That turns the overview into a real manager walkthrough: this is where route-creation and upload actions are attached in the live tree.
Close the route context menu
Section titled “Close the route context menu”Close the context menu before continuing into deeper routing topics. Keeping popup flows explicit prevents the overview from leaking temporary UI state into the follow-up tours.
