Jump to content

LummoxJR

Premium Member
  • Posts

    19
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by LummoxJR

  1. Just noticed your reply on this and I've addressed it in my most recent update to the style fixes. https://github.com/LummoxJR/Nexusmods-style-fixes
  2. 1080p is still a lot of users, including myself. Likely it's even a majority. Higher resolution only goes so far anyway unless the monitor is scaled up as well. A design that doesn't work well at 1080p doesn't work.
  3. If there are people who want the list view, I don't see any reason it couldn't be an option. It shouldn't be the only option. Standard view is working very well apart from the egregious padding and a couple of minor issues that are fixable through CSS. With better markup, it'd be trivial to switch between different views.
  4. Zooming in is the opposite of helpful. Classic view fits a decent amount on screen but if you zoom in it no longer will; when zoomed to increase thumbnails to what Standard currently shows it would actually use space less effectively because of some aspects of that layout (namely updated/uploaded dates being on separate lines). The current Standard view works well with the larger images and text, with my tweaks that snip out most of the ridiculous padding that was added in the beta. The designers are still overly committed to that padding for some reason.
  5. Again, you're being needlessly dismissive. Even people without these issues don't want to have to hit pagedown every time they've looked at just 3 or 4 items.
  6. That's fine for you but you're being too dismissive of the effect this has on all users. Anyone with repetitive strain injury will want to avoid scrolling more than they need to. Yes, this does add up, and it gets annoying very fast. A design that puts only three or four items on the visible part of the page is simply unworkable. Moreover, being able to see more items on-screen at once, balanced of course with making sure the info presented is adequate to the user's needs, is of paramount importance to any design.
  7. The "way too few" part is the problem. It isn't about the next page button because you can already customize how many mods you see per delivered page, but the problem is per viewport. The effort of having to scroll down to see the next batch of just a few mods can and does get tiresome, so fitting more mods in the viewport is objectively to the good; it just comes with a balancing act of also showing all the other relevant information. The display of each mod looks clean, yes, but it also leaves enough negative space for entire civilizations to take up residence; it fights the design imperative to maximize visual choice to the user. I think some people might like the general concept, especially if that horizontal layout were moved into more of a limited grid. But it's still too low on density of mods per viewport; we're talking like three or four per scroll in its current form, which is insane. With my current tweaks to the Standard tile view, I can get about 12 mods showing per scroll: 6 columns, roughly 1.9 rows. I'd prefer if I could get that to 2.2 rows for ease of view, but it seems to strike a good balance as far as still having larger thumbnails and very readable titles. 12 mods per scroll is a pretty decent number. Lower than 10 would be annoying to work with. Anyway like I said there doesn't have to be a one-size-fits-all. With some small tweaks to the markup of the Standard view to provide functional classes for CSS, and importantly to remove all the Tailwind BS like .pb-2, .space-y-2, etc., it'd be very straightforward to restyle the entire grid/list into multiple formats. CSS grids allow huge flexibility in rearranging elements of the page, if they're not hindered by the markup. Currently the markup is poor because it's saddled with unnecessary nested elements and classes that are little better than inline styles, so that's a limiting factor to restyling and rearranging.
  8. Repeating my survey answers: Standard view (current) is the winner, at least with my style cleanups. There's basically nothing wrong with it that removing a ton of padding can't fix, and making the descriptions up to 5 lines. I'd be okay with moving the category line just above the bottom. Classic view was okay but the bigger images and slightly bigger description font of Standard are actually really helpful. And even though I preferred full dates for last update and upload date, having them on two lines is just a waste. It's time to let this view go. Simple view would be a nice option for some people. I didn't like it because it had too little information, but if it's an added option I think some people would really like it. Don't make this the only choice. List view shows way too few mods on a page. It looks clean but it's also even more wasteful of space than all of the other changes. A reimagining of this where the image is to the left of the description and other info, but it was presented in 2-3 columns (or more on ultrawide displays) wouldn't be bad. But again this should not be the only option. Standard view needs to stay. If Simple and (modified) List are added as choices for users who want them, that's good. But if only one view is to exist, for maintainability reasons, it should be Standard. However, (I didn't mention this in the survey), I don't think you're limited to a one-size-fits-all solution or having to maintain multiple views. Improving the CSS for the mod tiles to give a functional class (.mod-thumbnail, .mod-title, .mod-author, etc.) to every element of the tile would make it possible to switch between views easily by just changing a class. The individual items in a tile could be moved to anywhere via CSS's grid layout, hidden, or even made visible by expanding on hover.
  9. 2% of registered users is a much larger percentage of active users. Even if it were only 2%, when those 2% have highly detailed and specific criticisms, those criticisms should be taken seriously. Any feedback that's targeted and detailed, positive or negative, should be weighted hundreds of times above a simple "I like it" or "I hate it". I've had good things to say as well as bad, all specific, and I am not part of the "change it all back" chorus. Reverting the whole thing is not a tenable solution, but certain aspects of the new design aren't tenable either. A lot of the same issues are being repeated because management is either ignoring them or completely dropping the ball on communication. I have yet to see any response at all to the vertical space issue, which is actually like several dozen issues under one umbrella. (Individually most of those items are small, but in totality they severely undercut usability and presentation.) I have finally seen one response to the loss of per-game colors, but it wasn't a good one. We all know the staff is busy. We all know that any kind of change at all will spark negative reactions. I think most people are still understanding of that. It's just a lot harder to stay understanding when the communication is this bad and there's no apparent attempt to fix the most glaring problems, most of which were brought up during the beta. What was the point of the beta if feedback was going to be chucked directly into the bin and the identified problems rolled out as-is? I want to acknowledge that I have seen work done on some things that people were begging for, like changing back the quick search (I didn't have a strong opinion on the new one), and bringing back comment searching which is huge. But there's an awful lot that could be done to address other widely shared specific feedback, most of which is just a matter of tiny QoL tweaks. Some things are harder to change—e.g., people wanting to get rid of the big collections section, move it, or make it optional based on user prefs, all of which require thinking through. I think Nexus will find the user base a lot more patient if there's better communication.
  10. Bug report: Filtering a list of mods by a date range is using UTC, not the user's time zone. I would naturally expect when filtering by date that the filter be based on midnight in my own time zone, not midnight UTC.
  11. I've said this elsewhere but it's worth repeating. The wasted space, especially wasted vertical space, is the single worst aspect of the new design. My custom stylesheet with fixes is here, and it's a good guideline for how to fix space waste in a lot of places: https://github.com/LummoxJR/Nexusmods-style-fixes The worst offender by far is any list of mods, where the tiles have too much padding in just about every section, and too much of a gap in the grid. The description is limited to 4 lines, where 5 would be better and usually there's more than enough room to show 5 lines anyway. The bigger thumbnails, and being able to move filters to the side and hide them, are the only things I think improved over the old layout. On mod pages, the title font needs to go back to being condensed. It doesn't have to be Bebas Neue. I found Saira Condensed is a very good choice, but Cabin Condensed isn't bad either; Saira Condensed gives a slightly better use of space and avoids wrapping titles. The short description needs to be above the fold. On the main page for a game, the trending section is GIGANTIC. It needs to be shrunk down to size. Collections should be either made optional via a user config, or moved to a sidebar area. Most users will either not care about collections at all, or will only care at specific points in their modding journey (i.e. when picking out a collection to use). My stylesheet improves the trending area a little bit, but that could benefit from a full rethink. The collections area needs to be optional.
  12. Nope, I don't mind at all. My changes are a basis for others to make their own. I put them up partially as a reference so the site's designers can fix the problems.
  13. For the titles in a tile view, I don't think there's a way to make a single line readable while also keeping a decent amount of text on it. On a 1920x1080 display I get 6 columns with the filter section closed, and accounting for margins and padding it's 255px of width for the text. Compressing the text makes it very difficult to read the titles at a glance, and making the font smaller would have a similar problem.
  14. The problem with restricting the mod titles within a grid tile to one line is that the majority of mods have longer titles than that, so a lot of information is lost. Ellipses aren't a good solution because some might have names like: Super Special Fighter Armor - SPID where the last part gets cut off. Unlike on a mod page, where I changed to a condensed font, I found a condensed font is all but unreadable at smaller sizes in the list view. Inter is a terrible choice for titles on mod pages, but for titles within the list view it's much better.
  15. I saw no evidence of responsiveness to those expansive critiques at all. There was barely any acknowledgment. I had a long and very specific list of issues, not one of which has been addressed. Obviously I'm just one person with one opinion and don't expect my ideas to hold more weight than anyone else's, but many of them were widely shared. Changes that resulted: zero. And this goes for other users' suggestions as well, where I've seen no action whatsoever. The only things they've changed to my knowledge were bugs that were found. Good on them for fixing bugs, I guess, but why ask for feedback if they were gonna ignore literally all of it? However, to be entirely fair to Nexus, I am not against change. I also know that you can't please everyone, and it takes time to agree on and implement changes. It's just insulting that they've made absolutely none at all. That still needs to change. What's still broken? A quick list: Multiple users have spoken out about the quick search having usability problems that are a distinct downgrade from the old quick search. I haven't used it enough to really have trouble with it, but somebody needs to hear them out. Vertical space wasted to a ridiculous degree in almost every aspect of the new design, which is a very bad thing for PC users on widescreen monitors—i.e. 99% of all users on the Nexus. Many pages have changed so that information that was once above the fold is no longer so, and lists of mods can't even display 2 grid rows per screen. This shouldn't be treated as one list item, but like a dozen all under the same umbrella. I can't overstate how bad this is. The loss of per-game colors in favor of making everything orange is almost universally hated. Mod pages' title fonts are no longer compressed, which means many of them wrap to two lines. Inter is simply not an appropriate font for this purpose, and it looks like crap there. You can't restrict mod searches by date range anymore. This is a highly useful feature and some people use it a lot. I wasn't one of them, but there doesn't seem to be a reason to have gotten rid of it. This is functionality we need restored. Some of these changes I've been able to fix with my own personal stylesheet, but I can't alter functionality. I might be able to fix some more with a script for Tampermonkey if the backend functionality is still there.
  16. The previous mod title font was Bebas Neue, a highly condensed all-caps font. The new title font is Inter, a relative of Helvetica or Arial that was already used for most other sans-serif fonts on the site. The only problem with Inter for this purpose is it's way too wide. It works everywhere else, but in titles it looks very wrong. My stylesheet uses Cabin Condensed, which still refreshes the look with something new, but because it's condensed it works much better in titles. My initial experiments used Saira Condensed, which also looks very nice; it's slightly more condensed and it has a very subtle sci-fi look that feels a little closer to the old Bebas Neue. My stylesheet imports Saira Condensed as well if you want to change the font family.
  17. My stylesheet fixes the mod titles by switching from the Inter font (not suited to this purpose) to a condensed font. I chose Cabin Condensed, but in earlier tests I really liked Saira Condensed also so I put both of them as options in the stylesheet. I linked to that a few posts back.
  18. If you mean my styles, I'm not sure why they would cause stuttering; all they're doing is altering the styles in the stylesheet and making relatively small changes, nothing that should conceivably cause churn. Whether it's my styles or the default, though, the fact that it doesn't happen for you in Edge (which is built on the same engine) or that it happens with extensions off suggests Chrome itself is having an issue, unrelated to anything about the styles.
  19. Free style sheet for use with the Stylus extension, or whatever equivalent you have: https://github.com/LummoxJR/Nexusmods-style-fixes It covers mod pages and mod listings. I didn't explore much else with the beta so I'm sure I'll find other things to update when more of it rolls out.
  20. Can we not have it look exactly like it did during the beta? I had to apply a special stylesheet to make up for its faults. As usual with all site rollouts (not just Nexus), I saw no evidence the company listened to a darn thing we said. Most of which boiled down to: STOP WASTING VERTICAL SPACE.
  21. I didn't notice this earlier, but the Report Abuse and Share buttons on a mod page are terribly placed. They should be up toward the top, possibly in the header with the other buttons, not taking up space below the short description. Right now they're just sitting in the middle of the page, interrupting flow for no reason.
  22. Oh. I hate that. They shouldn't do that.
  23. On the classic site I was seeing blue buttons and blue breadcrumb links, which has a much more pleasing color. Having all of the buttons and breadcrumb links in a pale orange is a step back. What's weird is that the body class scheme-theme-DeepBlue is still in the HTML, but the colors for that aren't being loaded in beta.css like they were in the classic CSS file. I'd like to request those be brought back. The blue was so much nicer. Edit: Taking the theme color sections and putting them in my custom CSS override with !important brings back the deep blue, and it's so much nicer. The forced override to orange in the beta is unnecessary. Please get rid of that.
  24. I can at least post my own CSS tweaks I've just worked up in a stylesheet. In making this stylesheet I noticed there's a real problem with the way CSS is being used. Those classes like pt-4, pb-6, etc. are basically little better than inline styles. Most of the elements on the page aren't given functional class names, but instead have classes that define styles on them. Styles like this are hard to maintain and hard to override for readability. The mod list page needs more functional classes like these: page-header page-header-nav page-header-game-title sort-options results-count content-block-notice mod-tile-image mod-tile-title mod-tile-author mod-tile-time mod-tile-desc mod-tile-stats Classes whose only purpose is to specify a specific amount of padding and such are fundamentally at odds with how CSS is supposed to be written. I know this kind of thing has infected a lot of sites, but I think we can do better here.
  25. I just tested all of these (except for Open Sans Condensed). PT Sans Narrow and Saira Condensed are absolute winners at the current font size of 44px. Encode Sans Condensed would be fine at a smaller size, but it's naturally bigger than its peers for some reason. Out of all of the fonts I've looked at, Saira Condensed is my favorite. It's striking and still leaves room for longer mod titles.
×
×
  • Create New...
OSZAR »