classdiagram-to-crud

To generate CRUD HTML fragments from a class diagram, provide your UML input in formats like PlantUML, draw.io, XMI, image, or text descriptions. The tool outputs four single-root HTML fragments per class for create, read, update, and delete operations.

Yes, draw.io diagrams are supported inputs for generating CRUD screens. The tool processes your draw.io class diagrams to produce separate HTML fragments for create, read, update, and delete operations for each class in the diagram.

Supported input formats for generating CRUD UI from UML class diagrams include PlantUML, draw.io, XMI, image files, text descriptions, and domain-model.json. Each format is parsed to produce create, read, update, and delete HTML fragments.

The generated CRUD HTML output contains no inline JavaScript and uses a single root element per fragment. This structure ensures the fragments are ready for composition with tools like crud-composer without causing DOM conflicts.

HTML files generated from class diagram entities should follow the naming convention of lowercase_classname_create.html, lowercase_classname_read.html, lowercase_classname_update.html, and lowercase_classname_delete.html for each corresponding CRUD operation.

The best way to scaffold Web app CRUD screens from a domain model is to input your domain-model.json or UML class diagram. This automatically generates single-root HTML fragments for create, read, update, and delete operations, reducing early UI design effort.