Log entries are wide text. However display is narrow and users fail to read the text properly: Very slow log in after entering password - #21 by Product1856
A style for viewing wide text was provided by forum administration: New forum - big change for the worse - #105 by karlmistelberger This style is currently broken.
Threads regarding screen width are closed by forum administration but issues recur.
I fully agree. There is a lot of empty space on the screen, even though I have pressed the button in the upper left corner (hide sidebar). In my opinion, pressing that button should open the conversation to the full screen without any other window next to it to show what the end result looks like. Too many clicks here and there…
This reform of the forum went in the wrong direction.
The Finnish site is otherwise clear: openSUSEa suomeksi - Etusivu
No amount of "me too"s is going to change anything. You can convince upstream developers to support it. In this case you should discuss it on Discourse forum, not complain here. Or you can find some extension to Discourse that allows configuring it and convince site admins to implement it. Finally you can find out how to do it on the user side and finally provide step by step instructions usable for others (so far, all that was posted can be summarized as “it is easy, just use CSS”).
Or you can simply use mobile view which gives you full screen width (but potentially has other drawbacks).
How do I make the width responsive? - support - Discourse Meta
@arvidjaar. I’m sorry I posted in the wrong forum. I thought this was a feedback forum. And I didn’t even know that SUSE also makes mobile phone software. However, I don’t think I’ll switch to a mobile screen at the age of 66… 
@raijar I use a user css browser extension. Since we had to put up a notice for the new user login issue, this broke css, once we can remove then normality will return…
This looks better now.
Suggestions are of course welcome, but we have a FAQ to address why most suggestions won’t be implemented in the platform itself:
More frustration!
Yep, it’s “frustrating” for a forum that’s managed by a team of volunteers to make decisions that make the system more maintainable and easier to upgrade, particularly to apply security updates to. Perhaps you don’t recall (or weren’t here for) the few times we had patches go awry on the previous platform and the forums experienced outages while people with “day jobs” had to find time to troubleshoot why the forums weren’t working.
I remember them well, because I was one of the people who did the troubleshooting (I still have a sandbox vBulletin setup in a VM, in fact, that I used for just that purpose).
Remember as well that one person’s “great suggestion” is another person’s “horrible idea”.
As the FAQ says, we welcome suggestions - but if we were to implement everyone’s suggestions, the platform would basically become unmaintainable, so we have to be selective - and that means saying “no” most of the time - often to things that we personally think are also a good idea.
The fundamental problem is that the website, like a lot of others, still uses <div>s, which were deprecated in 2011 for this purpose, rather and the semantic elements. With CSS containers managing the semantic elements, these sorts of problems can easily be addressed.
Don’t blame the volunteers. I volunteer on several websites with this antiquated setup but I have no control over the underlying design of the website.
It was never my intention to blame volunteers. What caused the current frustration:
Sites using discourse can be switched between the two views as was pointed out by @arvidjaar.
On the other hand developers make it extremely annoying to switch between the both. Even Wikipedia moved the switching button on their pages to the settings page, which is cumbersome.
Folks start pointless discussions to convince users to stick to the (in their opinion) better option.
I volunteer on several websites with this antiquated setup but I have no control over the underlying design of the website.
That’s extremely frustrating. Any idea how to convince them switching to CSS containers?
Sorry for the misunderstanding about volunteers. My experience of volunteering within the FOSS community has been overwhelmingly positive but outside that community I find I am given little respect as a volunteer.
Having switched the websites I maintain to CSS containers in 2019 I saw the immediate advantages of them both in terms of managing the look of webpages and in terms of the much clearer layouts possible for screenreader users.
So far, I have spoken about this at meetings and a conference and I tried to persuade one voluntary organisation for which I work to adopt them only to find they had given the contract to a dyed in the wool old fashioned company who give zero priority to users with disabilities.
In another organisation my advice was ignored five years ago by people who thought they knew better than a mere volunteer but a new manager who is trying to sort out the mess looks as if he might just move the organisation towards CSS containers. I live in hope!
I am familiar with that kind of issues. Companies are bad. Upon retirement things got even worse: For some 15 years I suggested to move from NetObjects Fusion Essentials 7.50 (Windows 2000 / 2003 / Vista / XP) to Wordpress. Move was eventually made a few weeks ago. 
Sidebar > Add Custom Section (“+” at the bottom of the sidebar ):
How can I use it?
“Open link in new tab”
In the meantime forum administration added button “View Code” in the upper right corner of code sections.
All those links do here is switch to the forum home page, but the admin enhancement should do well enough for reducing need to scroll code.
Now if only there was a way to replace the copious useless whitespace with wider content. Those who find web page content too wide only need narrow the window to ease discomfort. Unless they are CSS/JS superwizards with time to burn, those who find it too narrow can’t do more than complain .
I edited the two links to match yours, but the behavior didn’t change. Could this be different behavior among browsers? I’m doing this in 15.5 with Chromium 122.0.6261.128-bp155.2.75.1, normally with sidebar off, and 4-6 openSUSE forum tabs open.
