Azure-PlantUML
Azure-PlantUML copied to clipboard
how to do similar plantuml support for Power Platform icons
Is it possible to use this project to also include these icons? separate repo? same approach?
https://docs.microsoft.com/en-us/power-platform/guidance/icons
Thanks & Regards, Stefan
Thank you for opening this issue. Great question!
My first impulse is to say "separate repo", especially if we take into account that we'd want to do the same thing with other icon sets (for instance Microsoft Dynamics 365 icons)
But if we want to use the same approach, we'll also want to use the same automation.
That would mean either duplicating the build scripts to multiple repos, or moving them into a separate project as well.
At that point, we might be better of "just" adding them here, but in that case the project name "Azure-PlantUML" is no longer correct, which would mean a rename (for instance to "Microsoft-PlantUML").
Or we could make a "Microsoft-PlantUML" repo anyway, which would include this repo and other (yet to be created) repos.
I'll have to think about it some more, but I am all for making sure the Microsoft Power Platform icons are also made available to PlantUML!
Maybe some of the @plantuml-stdlib/maintainers have some thoughts about this?
Thanks @Potherca, I understand your concerns. For now I forked and start playing/understanding how you do it. There is also still icons missing for power platform - I reached out to see whether they can be added. In our case the final diagram would be representing Azure and Power Platform components how they work together.
At this point, I'm leaning heavily towards splitting the scripts/
directory into a separate repository (maintaining the git history) so the code can be changed to work for other sources as well.
The Power Platform icons would be a new repository without scripts/
(since it should use the "scripts" repository).
Once everything works, the scripts/
folder could be removed here and the "scripts" repo used instead.
Any decisions regarding a "Microsoft-PlantUML" could then be postponed until later.
We are also working in as dynamics environment combination with azure amd would highly benefit of having those components