Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: document why we chose plantuml + drawio #183

Open
AlexanderLanin opened this issue Jan 17, 2025 · 0 comments
Open

docs: document why we chose plantuml + drawio #183

AlexanderLanin opened this issue Jan 17, 2025 · 0 comments
Labels
docs-as-code infrastructure General Score infrastructure topics

Comments

@AlexanderLanin
Copy link
Member

PlantUML is being introduced in #158, however there is no explanation why PlantUML was chosen. We also support Draw.IO, again without any explanation why Draw.IO was chosen.

We need to document the decision, even if it's too late.

In case score process does not offer any advice on how to do that, have a look at https://github.com/joelparkerhenderson/architecture-decision-record

Note: it does not need to have an unreasonable level of detail or fake arguments. If it's a simple reason, document the simple reason and that's it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-as-code infrastructure General Score infrastructure topics
Projects
Development

No branches or pull requests

1 participant