On Wed, Apr 11, 2018 at 09:22:47AM +0200, Ben Franksen wrote:

Is there a bug tracker for hackage where one can make suggestions to improve the UI?

https://github.com/haskell/hackage-server/issues/741 The points made in this thread: - non markdown readmes (like [1]) - very-long-module-names (like [2]) - (maybe) some whitespace on the sidebars could be trimmer [1] http://hackage.haskell.org/package/animascii [2] http://hackage.haskell.org/package/distributed-process I am putting Nuno Alexandre (who did an excellent job on the redesign!) in CC:, as I am pretty sure he's not subscribed to -cafe -F

World treating text tiles as markdowns (or even converting them to markdowns) be an option? I really don't like the idea of small/different font sizes... Regards, Alexey On Wed, Apr 11, 2018 at 4:06 PM Gershom B wrote:

The problem with that particular README is that it is a text file. Nearly all the readme files these days are in markdown, which wraps. For text files, we do something very basic and render in a <pre> block, which does not wrap.

To improve display of such readme files I see three options. A) use a smaller font only for pre blocks, so that more text fits, without rewrapping. B) allow text files to rewrap. C) force the content _only_ for such files to always be below a clear, and as such, below the entire properties table. I’m leaning towards A here at the moment. Thoughts?

-g

On April 10, 2018 at 6:56:47 PM, Ben Franksen (ben.franksen@online.de) wrote:

The new hackage style has nice colors but severe problems w.r.t. readability. The right column with the package meta data causes the Readme text to be cut off. This make it almost impossible to read it. I attached a screenshot for illustration.

Cheers Ben _______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.

2018-04-11 8:05 GMT+02:00 Gershom B :

[...] I’m leaning towards A here at the moment. Thoughts?

+1 for that. In addition, I think that the 40% width of the right column (the "properties" div) is a bit excessive, 25% looks better IMHO. The left column ("description", "modules", "flags", ... divs) is probably more interesting for the average user, so it deserves more screen space.

2018-04-11 10:03 GMT+02:00 Ben Franksen :

[...] It should also use all of the available horizontal space.

That's a good point, too. Currently it only uses 75% of the viewport (75vw in the "content" div), perhaps 90% (or even 94%) would be quite an improvement. Changing the font size for the preformatted content from 17px to e.g. 14px makes things fit for my screen and doesn't screw up things too much typographically IMHO. pre-wrap is useful as a fallback. So in a nutshell: "properties": change from 40% to 25% "content": change from 75vw to 90vw pre within "embedded-author-content": change font-size from 17px to 14px, and add white-space: pre-wrap

Am 11.04.2018 um 08:05 schrieb Gershom B:

The problem with that particular README is that it is a text file. Nearly all the readme files these days are in markdown, which wraps. For text files, we do something very basic and render in a <pre> block, which does not wrap. To improve display of such readme files I see three options. A) use a smaller font only for pre blocks, so that more text fits, without rewrapping.

B) allow text files to rewrap. If you throw in replacing start-of-line blanks with   this even

Not enough space for that. preserves indentation. Also, use a fixed-width font. It's going to look ugly though.

C) force the content _only_ for such files to always be below a clear, and as such, below the entire properties table.

This is going to be horrible. Site visitors will find the same information in different places, depending on something that they don't know before they visit the page. Let me add a few more options: D) Redesign the page so that the README always takes up the full width. E) Redesign the sidebar so that it is narrower. This sidebar is way too wide, you almost have a two-column layout here. F) Move the sidebar content into its own full-width section. G) Look at how GitHub, GitLab, etc. place this kind of information, steal the best layout ideas from there. H) Move the sidebar information into a mouse-over flyout. (Not sure whether that's a good idea.) Hope this helps. Regards, Jo