Requesting Input: Bazzite Documentation

We recently were requesting feedback on the Bazzite website and thankful for all of the input that we have received for it.

Bazzite is on its way to Bazzite 41 soon and the team feels that Bazzite is past its formative years and would like to hear constructive criticism on the documentation at https://www.docs.bazzite.gg.

docs.bazzite.gg homepage

Thanks in advance for your feedback! :slight_smile:

New to Bazzite and been reading the docs in order to see if I want to distro hop to it. I’ve been quite impressed with them. They are short and to the point, and while there a few things here and there I’d like to see elaborated on, those may be more specific to my use case then the broader use case the docs are hitting.

Quick thoughts since it feels empty to a LGTM comment without any criticism (but really they are quite good you all should be proud).

  • I would highlight the FAQ more as it’s open top bar item, rather then pulling it under resources. I get the organization but the FAQ is very useful and should highlighted more
  • The What Bazzite image do I use? section in FAQ feels like it could be pulled out and expand as a top level in the Getting Started page. Personally, I really want to read that first, before I getting into the details of installing.
  • Per the last point, I’d love to see an expansion of what makes Bazzite special in both desktop and deck images.
    • For the Deck section maybe reorganize parts of the Handheld & HTPC Hardware section under the deck section of What Bazzite image do I use?. Feels like you want to high light the use case and clear confusion for the user up in a single place.
    • For the Desktop section I’d love to see an expansion on what makes Bazzite special if you aren’t in an HTPC scenario. What’s their feels like a good start, but it feels like the use case of HTPC is better highlighted.

Hope this is helpful!

1 Like

I’m going to go through whole documentation step by step, so I’ll probably chime in with more thoughts, but just at the beginning - I went to FAQ and there is chart Bazzite image chart that is wrong:

There are listed like “bazzite-gnome” “bazzite-gnome-nvidia” etc. But in download page there is distinction between “-nvidia” and “-nvidia-open” images. “-open” ones aren’t marked on chart.

And it’s probably good idea to write down what “-open” means in this context.

Especially because this can cause some misunderstandings. Like on the Bazzite website there is section on Waydroid. It’s bad enough that website doesn’t give asterisk like *not working on -nvidia images, but at least it links to the docs. But now - in docs it says that Waydroid doesn’t work on Nvidia proprietary drivers. But… there is “nvidia-open” in the image name, so if “-open” - there are not proprietary, so Waydroid will work, right…? RIGHT???

Basically, some mismatch between docs and website in that regard which can cause unnecessary confusion to users.

Also, I really HATE this Windows vs Bazzite table.

I mean, I get why. Everyone does it. It’s still better that one other similar distro pulled off (not gonna namedrop). But still… Out of the box gaming is similar. You have to login to Steam on Bazzite, on Windows you have to open terminal and paste one command that would install Steam, then login to Steam - difference is one click and three keystrokes. Gaming centric user interface is on like half of Bazzite images, so not exactly clear advantage. Open source - well this at least is 100% true. Although it’s kinda nitpicky, but I just HATE with passion these things, maybe because I work in marketing, and I have to deal with it all the time. Seems like generic marketing approach of “cherry pick 4-5 aspects where we are better + 1 to give a plus to the competition, because otherwise it would seem sketchy”. What if the categories were like this: “App Store, full DLSS frame generation support, full native gaming experience without any translation layers, ability to install almost any driver by clicking on downloaded executable”. That’s not to say that these are more important - just to make a point that you can do any red and green checkmarks depending on what arbitrary things you choose.

And well, I don’t want to sound like I’m hating on you or Bazzite - after all, I use it, I want it to grow and expand. It’s just… you can do better. You have such a good system, that will be fine without such cheap marketing tricks.

1 Like

I will probably edit the documentation soon to reflect some of the critiques you brought up, but I want to clarify that the -nvidia-open images are still the propriety drivers, but with the open kernel modules. Waydroid does not work with these either, and I will edit the image chart when I get a chance this week to make sure that -nvidia-open is documented properly, so thanks for that suggestion.

Yup! That’s exactly what I was referring to when it comes to these “open” drivers.

Docs say that Waydroid won’t work on proprietary drivers, but it also don’t mention that nvidia-open version even exist.

Meanwhile on site you get two versions - Nvidia and nvidia-open - which may lead to thinking that “proprietary” is about “Nvidia” and nvidia-open is well… open.

I was also confused with this - I thought that “open” means “nouveau”.

If course it’s not like that, I know that it just means that new proprietary Nvidia drivers have some open module hence “open” but it’s knowledge I acquired elsewhere and I think it would be nice to clear things up in docs just to be sure that someone won’t be like “man why Waydroid won’t work for me, it said that it won’t work on proprietary drivers but I specifically installed open drivers version”.

One last word for now - Ublue docs are EXCELLENT overall. Really appreciate the work you put in those. There is so much stuff around in Linux world that seem to be great but docs are so half assed like “take this, figure out how to use it”.

1 Like

This topic was automatically closed after 6 days. New replies are no longer allowed.