Image 1 — Over the past 4 years I've been building an OSS documentation tool designed for software architecture, would love any feedback you have
Image 2 — Over the past 4 years I've been building an OSS documentation tool designed for software architecture, would love any feedback you have
Image 3 — Over the past 4 years I've been building an OSS documentation tool designed for software architecture, would love any feedback you have

Over the past 4 years I've been building an OSS documentation tool designed for software architecture, would love any feedback you have

Hey folks,

My name is Dave Boyne, and I build and maintain my OSS project called EventCatalog. This is a documentation tool designed for software architects and teams that want to document their architecture (not just generic pages in confluence). It focuses on practices from domain driven design and software primitives rather than implementation details of your architecture.

Your docs are stored and versioned in git and everything owned by you and your team.

I built this 4 years ago as a personal need.. and now I get to work on this thing full time ❤️.

Anyway, I just thought I would share it with you, and if you have a spare few minutes, would love to get any feedback or initial thoughts you had about the project, about the ways you document things etc.

If anyone would like a deeper dive let me know happy to help and show you around too.

Have a great day.

u/boyneyy123 — 13 days ago

EventCatalog v4 - An open source documentation tool built for software architecture focusing on software primitives not generic doc pages, maybe something that can help you?

Hey folks,

Just wanted to share with you the latest major version of my open source project (4 years in the making) for EventCatalog.

For those new, EventCatalog was a side project many years ago, when I wanted to document my events for an organization I was working for, and got some some traction from users feeling the same pain.

Fast forward 4 years, and now the project is being used across many teams around the world helping them document their software architecture, as we added new primitives and patterns from domain-driven design (e.g domains, systems, entities etc), and other things like documenting business workflows (flows), schema evolution etc....

I feel documenting things shouldn't feel painful, and our tools should let us document how we actually model our architecture not just generic pages stuck in confluence etc... and that's the generic vision for the project. Allowing you to document domains, language, schemas, APIS, users/teams etc....

Anyway, if you have a need to document your architecture, or visualize it maybe it can help you... just thought I would share this year.

As I said it's open source, almost all of its free to use (it's open core model, to help sustain the project, but majority of features are free).

Love to hear if you have any feedback, or if you end up trying it out.

Here are a bunch of links that can help:

Site: https://www.eventcatalog.dev/
GitHub: https://github.com/event-catalog/eventcatalog

Star if you want to share some love: https://github.com/event-catalog/eventcatalog/stargazers

Video Demo: https://www.youtube.com/watch?v=jI5qxQM2JSE
Demo of a catalog: https://demo.eventcatalog.dev/

Hope you have a great day

u/boyneyy123 — 28 days ago

Documenting and visualizing your AI Agents with EventCatalog (open-source)

Hey folks,

I'm the maintainer of an open source project called EventCatalog, and I'm just sharing a new feature I added, which is the ability to document AI Agents and their tools (e.g MCP)

EventCatalog let's you document domains, messages, and your distributed systems, and how things connect, but as we use more agents, I thought it would nice to let people document their agents too.

You can assign the agents to your domains, assign ownership to your teams, and document any messages the produce/consume.

Just thought I would share in case anyone would find it useful.

Here is the repo: https://github.com/event-catalog/eventcatalog

LMK if you have any questions or feedback, would love to hear if you have.

Thanks,
Dave

u/boyneyy123 — 3 months ago