FWIW, I'm on desktop but I do have JS disabled (more precisely, I use NoScript).
This results in the top and left-side bars staying decorative and unobtrusive, but the concurrent visitor counter thingy is floating well above the bottom-right of the page. But then, as I shrink in the page width, the left-side bar and the concurrent visitor counter swap sides, and also a bunch of the content from the top is added to a new bar at the bottom. Eventually, the horizontal space between the side components becomes irrelevant such that they function as an additional bottom bar. At which point, maybe 40% of the vertical space is used for navigation and other shiny toys. This is really annoying, and the overall experience is inconsistent across widths.
(Also, at all widths, the top-bar has a transparent background, so main page text interferes with top-bar text as it scrolls.)
All of this is done in CSS, so presumably it can be fixed that way too.
If you want to eliminate any friction, I recommend enabling JavaScript.
Otherwise, you can read it in terminal mode with: curl -H "Accept: text/markdown" [URL]
The mobile interaction is similar; it's not a bug, it's by design. If you were able to read the article without any problems, I'm satisfied. Thanks for the feedback.
Yes, but when I stop scrolling and scroll up even a little bit (by accident, or because I want to scroll up and read something I missed) they appear again. I think the only good UX possible is to have a button to show/hide them instead.
I'm sorry, but I disagree. The lowest interaction cost is scrolling; it's a natural, continuous, and almost involuntary gesture. Having to click or tap a button requires the user to stop, evaluate whether the title interests them, and decide to make the effort to tap. The interactions you're describing are intentional and measured. I'm sorry but if the content is truly all you care about, I recommend the previous option or activating your browser's reading mode.
Exactly, which is why attaching large UI shifts to that involuntary gesture makes the experience feel very unpredictable
> activating your browser's reading mode
Reading mode is a hack that's only needed because sites aren't already readable. You shouldn't have to activate it to be able to read the content.
In addition, it doesn't always work well if the website didn't test it. On your website, for example, it removes all images from the text.
> Having to click or tap a button requires the user to stop, evaluate whether the title interests them
Purposefully doing things in a way that doesn't let the user decide if they want it is called a dark pattern. Its not far from those checkboxes that try to trick you into accepting marketing newsletters. "We can't give users an option to think if they want our emails! If they don't, why don't they just use their email's spam filtering?"
You may not see it like that yourself, but huge links to your CV, talks and courses are exactly that - an ad that covers half the screen.
You have multiple people telling you the experience is bad, and you asked for why, but when people give you the explanation you argue back. That's fine of course, it's your own site and you can do whatever you like with it without trying to suit anyone. But that doesn't make the reader experience less bad.
Generally, there is zero reasons to add moving elements to a page.