"Traditional diagramming tools force a choice between visual flexibility (drag boxes around) and maintainability (code that can be versioned). They impose rigid hierarchies that don't match how systems actually evolve. And they assume a single persona – either the engineer who thinks in code or the product manager who thinks in boxes – when real organizations need both1.
CN is my attempt to solve this (try it out at CN Diagrams). It's a diagrams-as-code tool that renders interactive architecture diagrams with support for arbitrary levels of encapsulation, provides an intuitive domain specific language (DSL) that engineers can version control, and offers a GUI that non-technical stakeholders can actually use. The goal is a single source of truth that the entire organization can maintain."
"Traditional diagramming tools force a choice between visual flexibility (drag boxes around) and maintainability (code that can be versioned). They impose rigid hierarchies that don't match how systems actually evolve. And they assume a single persona – either the engineer who thinks in code or the product manager who thinks in boxes – when real organizations need both1.
CN is my attempt to solve this (try it out at CN Diagrams). It's a diagrams-as-code tool that renders interactive architecture diagrams with support for arbitrary levels of encapsulation, provides an intuitive domain specific language (DSL) that engineers can version control, and offers a GUI that non-technical stakeholders can actually use. The goal is a single source of truth that the entire organization can maintain."