There is a funny mix of content at matrix.org/docs.
While there isn't a formal definition of what content belongs there or not, as an m.org website maintainer I feel that the website is already torn between content about at least the Matrix ecosystem, the Matrix technology, the Matrix network, the matrix.org homeserver, and The Matrix.org Foundation. This is pretty hard to make approachable to readers.
The content of /docs is mostly "user facing" content in some way, i.e. chatters, community mods, server admins. Ignoring the legacy docs, there is also https://github.com/matrix-org/matrix.org/tree/main/content/docs/spec-guides, which is "implementer facing".
The spec by nature is also implementer facing. I think the guides would better fit into a non-normative part of the spec website.
There is a funny mix of content at matrix.org/docs.
While there isn't a formal definition of what content belongs there or not, as an m.org website maintainer I feel that the website is already torn between content about at least the Matrix ecosystem, the Matrix technology, the Matrix network, the matrix.org homeserver, and The Matrix.org Foundation. This is pretty hard to make approachable to readers.
The content of /docs is mostly "user facing" content in some way, i.e. chatters, community mods, server admins. Ignoring the legacy docs, there is also https://github.com/matrix-org/matrix.org/tree/main/content/docs/spec-guides, which is "implementer facing".
The spec by nature is also implementer facing. I think the guides would better fit into a non-normative part of the spec website.