Project Structure

A quick tour of the directories you'll touch most often.

Top level

• app/ — the routes. Public marketing pages, the authenticated dashboard, and the API handlers all live here.
• components/ — app-specific React components shared across routes.
• config/ — the app's configuration: paths, navigation, features, and theme.
• content/ — the Markdown that powers the blog and these docs.
• lib/ — server and client helpers, including the data layer and auth glue.

Routes in detail

The app/ directory follows the App Router conventions:

• (marketing)/ groups the public site — the landing page, blog, docs, and legal pages.
• The dashboard holds the signed-in experience for personal and team accounts.
• api/ exposes route handlers for the platform's services.

Configuration

Most of what makes the app yours is data, not code. The files in config/ control the app's name, domain, enabled features, navigation, and theme — change them there rather than hunting through components.

Content

Add a Markdown file to content/posts to publish a blog post, or to content/documentation to add a docs page. The routes, sidebar, and styling pick it up with no further wiring.