On Sat, Jan 4, 2025 at 10:39 AM Max Nikulin <maniku...@gmail.com> wrote: > > On 29/12/2024 11:26, Nikolaos Chatzikonstantinou wrote: > > I should probably try to do this, but I got inspired by Worg's website > > which does not do any backend hacking as far as I can tell, but > > instead puts some javascript to collapse the table of contents. > > Not all users are happy with current CSS with :hover to show the table > of contents on Worg: > > Samuel Wales. [accessibility] worg obscures text. Wed, 8 Jun 2022 > 14:51:55 -0700. > <https://list.orgmode.org/CAJcAo8uTOpEazLNCr0t1kFqPGTLz=G=adnklhuo1-ura8-m...@mail.gmail.com> > > There is a trick with a hidden checkbox to implement menu without > JavaScript. See languages selector in Wikipedia > <https://en.wikipedia.org/wiki/Org_mode> > and the main Org site top menu when accessed from a mobile device > <https://orgmode.org> > > Perhaps a similar effect may be achieved with <details>/<summary>.
org-publish (or is it org-html?) should just structure the HTML document properly, as there is already an <aside> element, and even if those semantic elements are not used, at least if the <div>'s of the various parts of the page are placed sequentially one should be able to deal with the rest. As it stands now the div is inside the article content and it's hard to position it right. There's an urge to send the entire org file contents inside the main content of the HTML page, but then it makes it difficult to incorporate the sitemap with #+INCLUDE. Proper placement of elements would solve the issue addressed in my e-mail and in your link as well. Then the user can just use flexbox to get everything to be responsive. > > If you check my blog now, it looks almost OK in mobile phones. > > In desktop version of Firefox, when responsive design mode is enabled, > the sidebar is rendered over main text (at least with active NoScript). The sidebar's default property is to be unexpanded, accounting for those without javascript enabled. If it's running over the text it's because your screen is too small. It's far from perfect, but I haven't gotten around to hacking the org backends yet. Regards, Nikolaos Chatzikonstantinou
