Still looks like ascii, doesn’t automatically wrap, nor is it responsive.

Anyone know if these projects accept PRs to improve these kinds of things, like legibility? Or is it a point of pride?

▲ rovr138 a day ago | parent | next [-]

https://www.openssh.org/releasenotes.html#10.4

    <!--
        DO NOT EDIT MANUALLY!  This is generated from:
        www/build/openssh/releasenotes.html.head
        www/build/openssh/releasenotes.html.tail
        
        See comments in www/build/openssh/Makefile for details.
    -->

▲ ninjin a day ago | parent | prev | next [-]

Well, you can have a look at the commit history to see what changes have been accepted in the past:

https://github.com/openbsd/www/commits/master

My experience is that minor improvements tend to get accepted if they come with a solid technical motivation and fits into the overall OpenBSD mindset and ecosystem. If the change is simply justified by "best practices" and is rather large, then the conservative choice of just leaving things as they are usually prevail.

For example, I think I have seen two proposals for major overhauls of the OpenBSD.org homepage by "outsiders" over the last three years or so and they were both rejected. However, as you can see by the commit log, minor improvements (including presentation ones) happen all the time.

▲ ktm5j 13 hours ago | parent | prev | next [-]

It's not supposed to wrap or be responsive.. It's a tradition of making text legible on vintage terminals. I use `fill-paragragh` in emacs to format my commit messages like this 'cause I'm a dork hehe

▲ liuchao-001 a day ago | parent | prev | next [-]

It is vintage style. I actually love it a lot.

▲ 1over137 a day ago | parent | prev | next [-]

What “responsive” mean here?

▲

hsbauauvhabzb a day ago | parent | next [-]

Narrower windows will adjust the layout of the page to be more easily accessible for narrower devices like phones. This is a css feature and does not require JavaScript or similar.

In the context of the linked site which manually uses line breaks this won’t work well aside from fixing the scroll overflow, the text is small on my iPhone when zoomed out to show the full line width. A fix is better than nothing but does not perfectly fix the issue.

	▲	em-bee 15 hours ago \| parent \| next [-]
		doesn't even need specific CSS rules, just the default. every item needs to be wrapped or even just prefixed with a <p> or <li> element
	▲	trashb 20 hours ago \| parent \| prev [-]
		[flagged]

▲

bitfilped a day ago | parent | prev [-]

Requiring thousands of node packages to malformat text for people who can't be bothered to not use a phone to read a webpage seems to be the common definition of responsive these days.

▲ PunchyHamster 14 hours ago | parent | prev | next [-]

To make it worse ? I hope they don't!

▲ stinkbeetle a day ago | parent | prev [-]

I can almost guarantee it would not be an improvement.