Documenting components and their relations in a distributed microservice ecosystem is crucial to maintain clarity and avoid confusion. The C4 Model provides a compact and clear way to describe the system structure. The heavy lifting of detailed description of service relations is deferred to the service owners. This workflow implements distributed storage of documentation with a centralized renderer using GitHub Actions. The renderer knows the names of fragment owners, but does not know the contents of fragments. Fragments are fetched with a script every time the diagrams are rendered. Centralized renderer owns the main frame that includes all fragments. Every time any of the fragments change, central renderer is triggered to rebuild the full picture, thus keeping the diagrams up to date without any manual effort. See the article for a demo and an example of a syntax for a C4 diagram in UML.
