Architecture
π
Project Structure
Section titled βProject Structureβ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 stylessorry 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.