Carbide docs

Directory structure

The repo separates framework source, generated Bun/React/Tailwind frontend code, Go backend code, tests, infrastructure, automation, and published documentation from the start.

Layout

.
|-- .github/workflows/
|-- bin/carbide
|-- cmd/carbide/
|-- internal/carbide/
|-- docs/engineering/
|-- docs/site/
|-- examples/hello/
|-- include/carbide/
|-- include/carbide/ui/
|-- infra/compose/
|-- infra/schemas/
|-- scripts/
|-- src/
|-- src/ui/
|-- templates/default/
|   |-- controller/
|   |-- model/
|   |-- src/
|   `-- view/web/
|-- tests/fixtures/
|-- tests/integration/
|-- tests/regression/
|-- tests/unit/
|-- go.mod
`-- install.sh

Ownership

Rule

Empty directories are placeholders until a real file belongs there. When a directory gains behavior, its first file should make that behavior testable.