D2 is great for enabling a Docs-as-Code approach for software engineering - however this requires to docs to live alongside the code, normally in a docs/ directory.
Requiring D2 to have access to a customers source code to render diagrams is hampering my adoption, and synchronising diagrams to their own repository technically complex to setup with permissions across repos in Github Actions.
However zipping and publishing the diagram code to a Github Package or Docker Image or publishing it internally onto Github Pages already reuses tools and access commonly in place.
D2 is great for enabling a Docs-as-Code approach for software engineering - however this requires to docs to live alongside the code, normally in a
docs/directory.Requiring D2 to have access to a customers source code to render diagrams is hampering my adoption, and synchronising diagrams to their own repository technically complex to setup with permissions across repos in Github Actions.
However zipping and publishing the diagram code to a Github Package or Docker Image or publishing it internally onto Github Pages already reuses tools and access commonly in place.