Architecture as code
Treating architecture like code promises docs that evolve with the system. This collection looks at the C4 model, diagrams-as-code tooling, and templates teams keep up to date instead of abandoning.
Building a hosted MCP server for architecture docs
A request-bound MCP server, OAuth with PKCE, and YAML compilation through the existing document services, including the limits of validation.
The C4 model in practice
Separate system context from container detail, use a copyable YAML example, and review the diagram for responsibilities the schema cannot check.
ERDs and sequence diagrams as code
Copy valid YAML for typed entities and an ordered login exchange, then review the schema and failure paths that syntax alone cannot verify.
Forking Excalidraw for structured diagrams
How structured ERD and API cards share geometry across editing and export, and why sequence diagrams use a separate element.
Architecture docs that stay alive
ArchDocs keeps diagrams and docs in sync with your systems instead of letting them rot. Create a free account to start documenting your architecture.