Django framework
angee-django is the reference framework half of the platform — the headless backend that owns data, permissions, and the API. It is not a second framework on top of Django; it is a build-time composer for Django apps.
Every capability is an addon: a Django app shipping abstract models, a GraphQL contribution, a REBAC fragment, and resources. angee build merges every addon by Python MRO into a generated runtime/ — deterministic, byte-identical, CI-checked, with no monkey-patching and no runtime registration.
Start here
- The Composer — how
angee buildhooks Django's app-loading lifecycle to emit concrete apps from abstract addon contracts. - Backend Guidelines — the Django-native rules, package layering, naming, and how framework contracts are owned by code.
Across the platform
- The Opinionated Stack — which library owns which backend concern (strawberry-django, django-zed-rebac, channels, …) and the thin glue Angee adds.
- Concepts & Glossary — shared vocabulary: addon, composer, host, source model, REBAC, resource, seams.
- Features — the framework primitives and the addon catalog at a glance.
The React half — the rendered experience that consumes the typed contract this backend emits — lives under React SDK.