RouterPRISM routing
PRISM routing

This tutorial uses PRISM file-based routing: every folder under src/app/ becomes a URL, with nested layouts and server-side loaders.

Read the routing docs →
UIbext/ui
bext/ui

Components come from bext/ui — a faithful shadcn/ui port for bext and PRISM, styled through route_css tokens.

Explore bext/ui →
FREN
Step 11 of 11 · Wrap up

Recap & next steps

You built a real, server-rendered admin layout. Here's where to go next.

That's the layout — and every file is in the tree on the right. In a handful of files you built an admin app that:

  • routes by folder structure, with zero route config;
  • wraps every page in a sidebar + header via one layout.tsx;
  • highlights the active nav item and titles the header from route.pathname, server-side;
  • loads data in a loader and renders it — no client fetch, no spinner.

And it ships as plain HTML: no framework bundle, no hydration, instant first paint. The preview you've been watching is that app, running.

Where to next

TIP
Want a UI from a prompt instead? designer.bext.dev generates bext pages from a description, with the same live preview you saw here.
Files
src
app
products
src/app/layout.tsxread-only
localhost:3000