Skip to content

Architecture

🚜

src/
β”œβ”€β”€ components/ # Reusable UI components
β”‚ β”œβ”€β”€ admin/ # Admin components
β”‚ β”œβ”€β”€ forms/ # Form-related components
β”‚ └── ui/ # General UI components
β”œβ”€β”€ config/ # Application configuration
β”œβ”€β”€ email-templates/ # Email templates
β”œβ”€β”€ layouts/ # Page layouts
β”œβ”€β”€ lib/ # Shared utilities and helpers
β”œβ”€β”€ middleware/ # Request middleware
β”œβ”€β”€ pages/ # Application routes & templates
β”œβ”€β”€ styles/ # Tailwind & FlyonUI integration, base component styles

sorry about all the files, btw that’s file-based routing, babee that’s just he way it is, grow up

diagrams, core concepts, etc honestly just the filetree thing would be fine for now

Dw making architectural decisions that minimize technical debt (and encouraging you to do the same)

middleware app config schema migrations

auth + rbac crud helper


idea is to have modular interconnected full-stack components, extendable, built on a reasonable spec.