Note: It's recommended that you read the about section of the ERML docs to better understand this roadmap.

This issue addresses the feature of ERML. It's divided into multiple sections:

Parser

Necessary to build the ecosystem, and already written. Feature updates will be driven by other project parts' needs.

Visualizer

A place similar to dbdiagram for DBML, but it visualizes ERML instead. It should contain an advanced workspace, and a sufficient profiling system for users to login, save snippets, share them, and more.

Compiler from, and to DBML

A compiler from ERML to DBML, and vice versa. Still not being worked on yet.

• With the help of the visualizer, users can visualize their ERD's by writing a well-designed and easy language (ERML), saving them the frustration of having to drag and drop things around, and making sure they look good using apps like https://draw.io/.
• With the aid of the ERML-to-DBML compiler, users can transform the previously written ERML code into DBML code, then insert it into https://dbdiagram.io/ to visualize the relational model of the ERD. Which means they won't have to transform the ERD into RM anymore.
• Through the DBML-to-SQL compiler, users can transform the DBML code generated from the previous step into SQL code, and plug it into their DBMS of choice to create their database schema.

The Result: Using this project, and an ORM (like TypeORM), users will (most likely) never have to write SQL anymore.