Understand Project Structure
Find the change you want in this map, then open its edit point. Paths begin at your cloned Start repository.
| Change | Start here |
|---|---|
| Landing page composition | |
| Dashboard page or layout | |
| Shared dashboard UI | |
| HTTP endpoint | |
| Business behavior | |
| Application-table query | |
| Browser request and cache | |
| Pricing and site identity | |
| Supabase client boundary | |
| Database schema | and |
| Docs, Blog and release text |
Navigate native routes
renders the document and shared providers. A folder's
wraps its children; renders its base URL. _marketing
groups public pages without adding a URL segment. $projectId matches one
segment; $ is a catch-all. TanStack Router generates
from these files. Edit the route files rather than the generated tree; see
file-based routing.
The authenticated Dashboard parent calls before
rendering its shell. /demo/dashboard has a separate public parent and sample
data. Put protected pages under the authenticated route tree; sharing a UI
component with the demo does not make its data public.
Place server work
mounts Hono on /api/*. Browser components use hooks
calling that same-origin API. Services make product decisions; repositories
read or write application tables. Add a business endpoint in those existing
layers rather than creating another runtime.
Route components participate in server rendering and browser navigation. Keep
privileged imports inside server-function handlers or modules marked
@tanstack/react-start/server-only. Narrow Start server functions handle
route bootstrap, language preference, feedback and authorized content rendering.
They do not replace the Hono domain API.
supplies the QueryClient and SSR integration. supplies request middleware, session refresh and server-function CSRF. Use Application Architecture before changing these shared entry points.
Find content and build configuration
declares MDX collections. and load and render content at the server boundary. supplies the MDX component registry. Use the native content guides when changing routes or rendering; ordinary MDX authoring stays in the shared documentation.
connects Start, React, Fumadocs, Tailwind and Nitro. owns development and build commands; locks the root dependency graph used by the app and E2E directories.
What's next
Customize Dashboard
Backend
Documentation
Was this page helpful?