honest framework
Start here,
Django developer.
The framework concepts map directly to what you already know. The reading order below is chosen for Django developers: start with the persistence layer where the differences are most concrete, end with the client-side model where they are most radical.
Recommended reading order
01
02
03
04
05
06
Why should I care?
The bugs that disappear. The bugs that remain. The benchmark numbers, run yourself.
honest-persist
You know Django migrations. This replaces makemigrations and migrate with schema-first diff.
honest-type
You know Django forms and serializers. This replaces the class with a vocabulary dict and a function call.
honest-features
You know Waffle. This eliminates the Django settings dependency — the flag lives in code.
honest-observe
One log for browser events, middleware, and queries in order. What Sentry tries to reconstruct after the fact.
DATAOS
You know Django templates and HTMX. This formalizes what HTMX already implies: the DOM is authoritative.
Also in the framework
honest-test
Exhaustive enumeration from finite vocabularies. Not sampled — every valid input, every time.
honest-check
Static verification from dispatch tables. No type annotations required. The linter reads your vocabularies directly.
honest-components
Atoms, molecules, organisms. Two mounting behaviors. One CSS namespace per component, for life.
Honest Code Principles
The sixteen practices that make code honest. The prerequisite for everything else.