Bug 262271

Summary: FreeBSD documentation: please consider having sidebars to the left, not the right, of content
Product: Documentation Reporter: Graham Perrin <grahamperrin>
Component: Books & ArticlesAssignee: Sergio Carlavilla Delgado <carlavilla>
Status: Closed Works As Intended    
Severity: Affects Some People CC: carlavilla
Priority: --- Keywords: accessibility
Version: Latest   
Hardware: Any   
OS: Any   
URL: https://forums.freebsd.org/posts/549007
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262270
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262660
Attachments:
Description Flags
Screenshot: sidebar moved from right, to left none

Description Graham Perrin freebsd_committer freebsd_triage 2022-03-01 12:39:45 UTC
Created attachment 232185 [details]
Screenshot: sidebar moved from right, to left

Compare the screenshot at bug 262270 comment 0 with the shot attached here. 

Moving the sidebar from right, to left, will (at least) alleviate the accessibility aspect of 262270. 

More generally
==============

From <https://forums.freebsd.org/posts/549007>: 

> One collapsible sidebar: OK
> 
> Two sidebars, with or without collapse: less usable.
> 
> Two sidebars at a **distance** from each other: far less usable, and the 
> negative effect of distance is worse whenever the user aims to perform 
> dual actions involving both sidebars. Actions such as scrolling, 
> clicking, collapsing, whatever … IMHO it's simply not good UX.
> 
> (This is the reason for me having a user style that aims to keep 
> the two sidebars **adjacent** to each other.)

Thanks
Comment 1 Sergio Carlavilla Delgado freebsd_committer freebsd_triage 2023-07-17 16:34:09 UTC
This work as intended, we can take plenty of examples about this way of organize the documentation. All the chapters in the left and the TOC on the right.

For example, the Asciidoctor documentation by itself[1]

[1] https://docs.asciidoctor.org/asciidoctor/latest/html-backend/

It's true that I need to improve the responsive in "tablet" mode, but I'm gonna handle this in the future, after the Handbook Working group