> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day13-14-event-documentation.md). # Day13/14 Event Documentation Day 13 of 14: Move beyond Word and Excel by leveraging centralized Event Portals to streamline event cataloging, schema discovery, and lifecycle management. Efficient management of event cataloguing stands as a pivotal requirement for organizations. While conventional tools like MS Word and Excel suffice for creating diagrams and configurations, the utilization of dedicated **Event Portals** presents a more efficient approach. These portals act as centralized repositories for documenting events and their flows, thereby improving processes related to management, review, search, and version control.\ \ Organizations often opt for tailored portals or vendor solutions, commonly referred to as Event Portals. These solutions not only aid in event management and reusability but also ensure the effectiveness of event lifecycle management. Equipped with diverse viewing options (e.g., event flow view, list view) and a robust search feature, Event Portals empower users to effortlessly visualize applications, events, and schemas. Consumers can promptly locate pertinent events and access the latest schemas for coding, while publishers can efficiently target consumers for specific topics within seconds.\ \ The market has observed a surge in products specifically designed for event portals, augmenting event management within Event-driven architecture (EDA) frameworks. The evolution of these tools underscores substantial progress, signaling a persistent inclination towards prioritizing Event Portals as a strategic focal point in the market's landscape.\ \ [Shawn McAllister](https://www.linkedin.com/in/shawn-mcallister-1a697b5/) recommended Solace Event Portal in response to my earlier post (). Other products like Confluent and IBM Event Streams are also available in the market. It is crucial to select the right product that aligns with your needs. Once you have chosen a product, establishing naming standards and best practices is essential to enhance the efficiency for architects and developers in its utilization. Defining these guidelines will be a significant aspect to delve into further. ## 🚀 Let's Connect Beyond GitBook! If you found this article helpful, you can find more of my technical insights, daily discussions, and deep dives across these platforms: * **Read more of my work:** Check out my articles on [dev.to](https://dev.to/stephen_tsoi_5b2c4055f3a9) and [Hashnode](https://stephentsoi.hashnode.dev/). * **Join the daily conversation:** Connect with me directly on [LinkedIn](https://www.linkedin.com/in/stephen-tsoi-16309730/). *** #### 📬 Stay Ahead of the Curve Enjoyed this piece? I break down complex technical topics into bite-sized, actionable insights every week. 👉 **Subscribe to my** [**LinkedIn Newsletter**](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7487299517642612736) to never miss an update and get the latest articles delivered straight to your feed! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/event-driven-architecture/event-governance-the-foundation-of-successful-event-driven-architecture/day13-14-event-documentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.