Render event storming diagrams on GitHub from fenced code blocks.
Users
7
+3 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#228K
#191K among extensions
Version
1.0.0
updated 13 Jul 2026
Users
monthly, 3 months
Latest, 16 Oct 2026:7 usersMove the mouse over the chart for any month
Ratings count
monthly, 3 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Event Storming Diagram Renderer
# Event Storming Diagram Renderer for GitHub and VS Code
π **[Playground](https://rexebin.github.io/event-storming-plugin/)** β try it live in your browser
A **browser extension** (Manifest V3) and **VS Code Markdown preview extension** that render **event storming** diagrams from fenced code blocks.
> β οΈ **Event storming diagrams should be small and concise.** A complex or sprawling event storming diagram is often a signal β not an achievement β that the underlying domain design or code structure needs simplification.
> In DDD practice, event storming is a collaborative discovery tool for building shared understanding, not a comprehensive documentation artifact.
> If your diagram feels overwhelming, consider:
> 1. are you capturing implementation details instead of bounded behaviors?
> 2. Are aggregates too fat? Is a single bounded context trying to model an entire enterprise workflow?
> Good event storming models fit on a wall and spark conversation, not serve as reference architecture documents. See [Alberto Brandolini's Big Picture Event Storming](https://www.eventstorming.com/) and the [DDD Community guidelines](https://dddcommunity.org/) for best practices.
> This project aims to accommodate moderate complexity. PRs are welcome, but simplicity wins over supporting overly complex event storming diagrams.
## Features
- π¨ Full event storming visual language: events, commands, queries, aggregates, actors, policies, views, read models, external systems, errors, and note nodes
- π¦ Container-based layout: XML DSL containers render as visual boxes for aggregates, external systems, read models, and process containers
- ποΈ Nested process groups: each child group renders inside a dashed sub-container with the group name in the top-left corner
- β¬ οΈβ Left-to-right process flows: actor β command/query/policy β event inside containers, with failure branches rendered below nodes
- βοΈ Directional arrows with shared-target fan-in layouts for commands and views
- π Interactive zoom & pan
- π‘ Notes-only tooltips: tooltips appear only for containers, groups, or nodes that have notes
- π Note badges on containers, groups, and nodes that have notes
- π― Collapsible diagrams with toggle button
- π Color-coded rectangles (black border) per event storming standard:
- **Orange** (`#FFA500`) β Domain Events
- **Light Green** (`#91D49C`) β Commands
- **Dark Green** (`#5BAA62`) β Queries / Read Models
- **Yellow** (`#FEE254`) β Aggregates
- **Yellow** (`#FEE254`) β Views
- **Gray** (`#D4D3D3`) β Actors
- **Blue** (`#859EBF`) β Policies
- **Pink** (`#FB8597`) β External Systems
- **Cyan** (`#8DCFF9`) β Errors
- **Light Yellow** (`#FFF1AA`) β Temp Objects / Notes
Growth
Window
Users
Change
Ratings
Rating
7 days
β1
β12.5%
0
0.00
30 days
+3
+75.0%
0
0.00
Chrome Web Store search rankings
Where Event Storming Diagram Renderer appears when people search the store, with the 30 day change