Schema and renderer stay separate
Field metadata describes what to render; the renderer owns layout and safe input handling. This keeps new fields from becoming new branches in page markup.
SCHEMA · RENDERER · VALIDATION
Schema-driven Form Studio
Change the configuration, keep the renderer predictable.
A public, synthetic example inspired by dynamic-form patterns in local Vue teaching materials. It does not publish original business configuration, student data or database records.
Live preview
Field schema
Edit / apply JSON
Edit options and bounds here. Applying JSON clears preview values.
LOW-CODE READING MAP
Configuration is a contract
Validation is explicit
Required, email, minimum length and option rules are rendered from the same configuration that builds the control. The demo reports errors beside the affected field.
Low-code has a boundary
Complex business rules, permissions, persistence and audit trails still need application code and server checks. Configuration reduces repetition; it does not remove domain design.