When I read coding style guides, such as the AirBnB Javascript Style Guide I just realized that these often do not provide deeper explanations why something should be done in a particular way.
At most there are brief statements, rarely links e.g. "It won't work in IE8. More info."
Why is that that so? At least a list of references or a link to an annotated version would be more helpful, e.g. to new employees that must work with such a style guide.
Are there notable counterexamples, for any language? (Cannot read them all)
I'd consider these style guides as "living documents", and over time I would expect them to grow into more verbose versions with many links, conserving lessons learned and documenting how to avoid obscure edge-cases.
It's okay to start with a bare-bones document. That's easier to read. but shouldn't evolve these documents, a longer version indicating a more "mature" style-guide?