Developers
Build on top of the metadata-driven platform instead of around it
The developer page should make it obvious how builders extend the system: new metadata, new surfaces, new portal experiences, and new runtime integrations that still respect platform rules.
Developer priorities
This is the public-facing layer for builder education before deeper tooling and docs arrive.
- +Respect metadata flow and worker-based schema creation
- +Reuse shared surface and shell primitives
- +Keep routing, visibility, and landing decisions backend-owned
Metadata flow
Required
New platform tables always start in sys_db_object and sys_dictionary.
Runtime
Composable
Forms, lists, portals, and pages reuse the same backend contracts.
Access
Fail closed
Auth and route safety stay in the server layer.
Developer areas
Metadata patterns
Learn how tables, fields, routes, landing, and page metadata fit together.
Surface contracts
See how public, backend, and portal experiences consume shared runtime payloads.
Extension guidance
Add new public pages, portal pages, or backend capabilities without bypassing the platform rules.