Routing Structure

A guide to Recura's URL organization and Next.js App Router conventions.

Architectural structure

Recura utilizes the Next.js App Router for highly modular, nested routing, leveraging Server Components to optimize performance.

Project filesystem

Live architectural tree of the platform

src
app
(auth)
dashboard
layout.tsx
page.tsx
settings
documentation
terms-of-service
layout.tsx
globals.css
components
modules
next.config.ts
tsconfig.json
tailwind.config.ts

Routing manifest

Public and internal route map

/
Public Front

Landing & Marketing

/auth
Identity

Sign-in / Sign-up

/dashboard
Enterprise

Main product hub

/settings
Configuration

Preferences engine

Technical blueprint

Core framework configurations

next.config.ts

Framework Control

Defines asset optimization, image loaders, and server-side headers for the platform.

tsconfig.json

Type Safety

Orchestrates path aliases (@/*) and ensures strict type checking across the module system.

package.json

Dependency Graph

Manages all third-party libraries, from React 19 to the documentation's Lucide icon set.

App-centric routing

By leveraging Layout Overlays, Recura provides instant transitions between platform segments without reloading shared navigational states.

Route GroupsDynamic SegmentsClient ComponentsParallel Routes
( )
Groups

Organize folders without affecting URLs

[ ]
Dynamics

Handle user-specific data segments

layout
Shared

Maintain state across navigations

page
Endpoints

Terminal visual entry points