Add architecture documentation

[K3UL]

Hello,

As a decently experienced C# developer who has been out of the C# world for some years, I am trying to get up-to-date with GUI design, and I found your app to be exactly what I would like to be able to do. I love that it has all things I want to learn :

• It looks like a native, modern Windows app. It really has the look and feel of W11
• The modularity using MEF
• The fact that it makes use of UWP packaging which is completely foreign to me. For the anecdote, I wanted to look into WinUI 3, but the lack of a visual designer in visual studio is a big no-no.

So all that to say thank you, because your program is both very useful to me as a tool, and also a big inspiration in what I want to achieve on the desktop.

Now, when I tried to understand the architecture of the solution, I must say I have been having trouble with it. I think the project would benefit from having some documentation about the basics of its architecure. I am personally a convinced maker of ARCHITECTURE.md files. A great example is the one of Prometheus : https://github.com/prometheus/prometheus/blob/main/documentation/internal_architecture.md.

So I would like to propose the addition of such a file (or files). It could also very well be a wiki.

Of course I realize this project does not have as many maintainers as Prometheus, but I really think it would be good for people like me as well as for contributor. I also realize there is some of this in the CONTRIBUTING file, but in my opinion it is not enough.
If you help me understand the basics I would even love to help write it. I know some of the things I don't understand are just practice, but it's just that having to read the whole MEF documentation, the whole UWP documentation, plus some others, is a bit tedious compared to a good architecture doc.

Some example of things that are not clear to me :

• Extending a little the explainations about MEF as they are in the CONTRIBUTING
• What exactly the OutOfProcService does and how
• How are things separated between DevToys and DevToys.OutOfProcessService (and Shared, but I guess Shared is the things commong to DevToys and OutOfProcessService)
• Why the MonacoEditor is a separate project and how they interact
• A sum up of the interfaces
• I also don't understand what is the meaning of the OOP folders, like how you choose what goes in them

Again, thank you for the tools but especially thank you for the inspiration, this is by far the best open-source GUI I know on Windows.