I originally wrote this yesterday but my browser ate my post so I'll have another go:
Having each black box self contained is fine, but expecting these to work together in any way I can see as being problematic.
Even if you standardise a language, there is far more than that which needs to be consistent for things to have a hope of working together in a consistent manner - that's why projects have coding guidelines, style guidelines etc.
There are different religious beliefs / fashion as to how things should be done, and people don't always agree. e.g. We must use ECS everywhere, smart pointers, garbage collection, no STL, etc etc etc, and things would quickly become a mess if everyone had a different style. Likewise codebases of any size tend to have a hierarchy where higher level concepts are expressed in terms of lower level concepts (vector3, vector2 etc), which again dictate a certain way of working.
At this point you have to ask whether you are indoctrinating beginners with what might be a flavour of the month style guide. But I guess this is true in any codebase.
Tree indexing
Related to the idea of the snippets but perhaps valid on its own, it occurred to me that what might be useful is a more in depth way of indexing the snippets / forum posts. At the moment the forum is a very rough tree structure, and the articles. Once you go above that you start having to use text search. What might be useful is to have a far more detailed indexing tree, so it is easy to find articles / snippets on your subject of interest.
e.g.
Programming
->AI
->Pathfinding
->A star
->Navmeshes
->Graphics
->Visibility determination
->Portals
->BSP
->PVS
->Occlusion culling
->Lightmaps
->Radiosity
Art
->3d
->Animation
->2d
Sound
->Music
Design
The nodes .. forum threads, snippets, articles, blog posts might appear in more than one leaf of the tree. Personally I'd find this approach very useful and could spend hours researching through the tree with the information on this site.