This is very true.
Another option I like is Python's https://devguide.python.org/ which is separate from https://docs.python.org but uses the same Sphinx tooling. That could make us feel more free to expand the scope of what a dev doc is, centralize contribution guides and so on. In general, I like their content very much.
The Technical Steering Committee will come into existence on Jan 1. This will have some impact on both this conversation and the website one as some information needs will shift. The TSC will start generating content that will need a home including meeting minutes, roadmaps, etc. That content could potentially fit alongside dev docs. I imagine the TSC will have conversations about the most appropriate place for those and will be able to comment here as well.