I don’t think that would be useful for users. A user usually has in mind what goal to accomplish. That goal is not “torrc”, but “make it work” or “censorship circumvention”. Instructions on how to modify torrc to accomplish various goals is documented on various documentation pages.
What specifically does the tails support page do better? Please create a new forum thread.
“if they have read and understood the documentation properly” - As sad as that is, it is an entirely unrealistic assumption. The redirection of support questions of generic upstream project questions to other upstreams was actually done by me to save time and space in Whonix forum.
Side menus waste a lot space and look awful on small screens.
There is a lot room for lots of opinions here. @bnvk, the new Qubes usability designer, once told me, that he isn’t offended by long scrolling pages.
If you desire any changes to that blog post, I can do them. If you like to have your own blog account to make the edits/posts yourself, I would not mind about that either. If not deemed useful, we can also put the blog post on hold. (usability is not a democracy.)
Might be an idea worth considering, would however for the time being be a rather low priority.
Not sure whether that would make sense for Whonix. Reasonable for a host OS like Qubes which employs extensively modified tech, not so much for something like Whonix whose essential “architecture page” would contain of look at VBox/KVM/Qubes.
Has somewhat already been discussed in another thread about changing the way the documentation is sorted. Will thus be likely done once the “wiki question” is decided.
Not sure what wouldn’t overlap there, as Whonix doesn’t change anything about Tor…
We had that discussion quite a lot of times actually. I am caught somewhere inbetween here. Trimming the documentation down is the wrong approach in my eyes, yet I see why people might think of the documentation as overwhelming. Digging up an old concept, which wasn’t realisable with mediawiki might be a good idea now, namly the idea that there should be a “button based” system which allows to seperatly display advanced and beginners guides.
I can see where you are coming from and am able to agree on the space aspect, however the alternative would be to force users to click through dozens of sites before finding what they need. Was somewhat inspired by this: Redirecting…
Maybe a drop-down menu or a which may be called when needed could be a solution here.
I think I might understand where you are coming from and I guess you have a valid point.
Assumption: When users click the quick start guide they may wish to click through it page by page.
Now, when we had a quickstart documentation overview (similar to our current one, but much, much smaller)… People would click a page, read it. And then be stranded. Bad. They would have to use their browser’s back button to click the next page. This may not be good UX. With a sidebar, this might be better. Impossible for me to answer, I hope there is a clear UX designer answer somewhere.
Does that nail it?
What I find interesting is the backwards / forwards button feature of the Tails documentation. (example)
←System requirements | Features and included software→
It’s at the top and button of each and every of their documentation pages. I dunno if it is great at the top, but at the bottom I guess it is great. Happy to be corrected.
If you look at the current draft, you may notice that I already included “Next >” and “< Back” buttons. The idea of that was, like you suggested, to allow a constant stream of information, letting users read the most important things in one go.
So maybe keeping these buttons, but replacing the bar with a drop-down menu may be a solution…
First of all, I have to say that I feel like, while the list used by Qubes on their documentation would be detrimental for something like a Quick-Start-Guide, I also feel that it does make at least some sense and serves a purpose when it comes to a “real/complete/long” documentation. It gives you the ability to quickly scan over every available article, to find what you need. It isn’t that pretty and shouldn’t be the default/first thing a user sees, but as an optional addition to make a wiki more accessible, gets the job done. What we actually use as the front page for our documentation currently (Whonix ™ Documentation), should probably not be the first thing a newcomer sees/reads, but shouldn’t be removed for that reason alone.
Now, the Mozilla approach is interesting. Just like myself, with the Quick-Start-Guide, they move the bar with the main topic below the text, when in “mobile mode”. Works and preserves screen-estate.
The implementation Elementary used looks good as well. Making subtopics in a site “clickable” to link to them directly is a nice way of keeping a long page manageable. A combination, like you suggest would definitely have benefits. Making “Isolation”, “Safety”, etc on the first page, for example, clickable makes the whole thing appear more rounded.
I can agree that “hamburger menus” should be avoided, as they’d just make looking for a certain topic even more tedious, than such a task already is.
Now, I’d love using a side-bar like “zurb”, blending in and out once someone hovers over it with a curser. This though seems to be only possible with JS, according to my research. Now, as for making the current page highlighted, that will be implemented by me. Shouldn’t be to hard. Either by changing the color of the current topic or using pictures instead of text. Should have gotten that idea myself…