The purpose isn't to teach software architecture just by looking at
diagrams in isolation. We hope it provides inspiration for creating your
own diagram by seeing how different companies and open-source projects use
different styles, abstractions, and tools to document their software. And
if you want to learn more, each diagram usually has a source that provides
more context.
Since it's crowdsourced, the contents of the diagrams aren't vetted. The
only guarantee is that someone has put effort into each diagram and it
was, at one point, publicly listed on a website to represent a popular
software project. If there are inaccuracies, leave a comment. If you like
something, leave a review. Over time the highest quality diagrams will
have the highest reviews, and the most interesting/controversial ones the
most comments.