Hey, new user here, and I’m trying to get the hang of using Aurora, but I’m finding it pretty hard to search the docs. (Partly because Aurora docs are still WIP.) But also because trying to browse the docs is quite incovenient between the different images.
And I realized, “hold on” why are the docs for the different images on their own websites? The docs and the actual download pages for every image has their own website, getaurora.dev, bazzite.gg, projectbluefin.io, projectucore.io. Why not have the images on one website?
Anyway… on the docs side, I’m looking pretty much at the Fedora documentation, and they have their single documentation repository at docs.fedoraproject.org for all of their editions, and I’m proposing we have something similar, docs.universal-blue.org and then every image would have their own documentation at docs.universal-blue.org/bluefin
I see that projectucore.io is just a redirect to the github page, but I think we’re gonna need a central documentation repo instead of hosting an new Starlight instance for every image.
Also seeing that there’s this new forge, that’s being created, where should the docs live? Buy a new domain, and then host another Starlight instance?
I guess the easy answer is that they’re different products and have different people working on them with different use cases and goals. What were you searching for specifically?
Documentation has moved around constantly since the start. Universal Blue now focuses on 4 images intended for end-users that have different contributors and target audiences, even if a handful of the same people will usually end up contributing to multiple projects anyways.
Aurora and Bluefin are special cases since they’re essentially the same right now outside of branding, desktop environment, and some smaller details like Aurora not having the :gts update channel currently.
Actually, in the mean time until we have the documentation ready, use the Bluefin documentation and ignore the GNOME-specific stuff and anything that mentions the default Bluefin update cycle which is a Fedora point release behind from the current one that is out.
I originally thought a ‘general’ documentation landing would be a good idea, but also realized that it would be containing redundant information. Even the -main images that we build off of are not that much different than vanilla Fedora Silverblue, Kinoite, etc. and documentation already exists upstream for that.
I understand where you’re coming from, but I think for now this will work the best. Aurora documentation should be in a better state real soon. Also, anything in particular you want documented for Aurora?