On Thu, Dec 9, 2021 at 11:52 AM Matthew Miller <mattdm(a)fedoraproject.org> wrote:
Sure. This topic isn't worth a battle royale for me, but I do think it would represent a regression in how we present our documentation, even though the docs are still there and findable.
This is a digression, but I agree with all of it.
That would represent a pretty significant paradigm shift. We might be able to get all of the docs to pull nav.adoc from an external repo, but that would break local preview builds. Otherwise, we'd need to combine all of those into a single repo, which presents its own set of challenges.
The other approach would be to reproduce all of the nav in each module's nav.adoc. But this would require being kept in sync manually. That content would be relatively static, so it wouldn't drift too often, but that also means we'd probably forget about it when a new change is made.
For the latter, it would be under Engineering Teams. For the former, when it exists, it would go under Quick Docs or release-specific docs, I'd say.
I agree with the fact that "where are the docs" is confusing. But using docs.fp.o to point to things that are still in the wiki for whatever reason makes it less confusing. The story is "go to docs.fp.o and follow the link you want". If that stays on docs or sends folks to the wiki or readthedocs or whatever other platform, that's okay. The point is that docs.fp.o becomes _the_ front page of our documentation.
Also, i am happy to help out implementing some of these ideas (also the ones from the other thread too).
He just need to break this down into what we acutally want done, and ill do it.
is there a central ticket queue to track overarching stuff like this?
cheers, ryanlerch