Developer documentation

Build your application

Mettada turns entity and workspace specifications into application code and workspace contracts. You own the application: the platform supplies repeatable CRUD foundations, while your business rules, policies, and product experience remain yours to design.

Start here

1. Quickstart — scaffold a consumer, integrate the platform, author a spec, and generate a first workspace.
2. Metadata specification — learn the entity and workspace YAML formats and the versioned UI contract.
3. CLI reference — inspect the commands registered by this checkout.
4. Cookbooks — follow focused workflows for relations, lifecycle metadata, workspaces, and custom application behavior.

What Mettada generates

The backend pipeline compiles validated specs into metadata and dispatches Laravel generators for selected artifacts. The React UI generator emits a versioned workspace contract; the frontend packages consume that contract. Generated CRUD is a starting point, not a substitute for application-specific authorization or domain invariants.

Keep ownership clear

• Treat entity and workspace specs as the declarative source of generated behavior.
• Review generated diffs after every sync. Preserve application code in developer-owned areas, not generated output.
• Put transactions, workflow transitions, pricing rules, and other business-specific guarantees in consumer services and endpoints.
• Run the consumer’s tests after generation. A structurally valid spec does not prove that its business behavior is correct.