As @Vultraz pointed out, "if you switch tabs in Download during the fade transition, it's possible to end up with both tabs' contents displayed at once". Low-priority thing that I was already aware of, really, but I should've posted it in here for future reference.

Hello,
This may be minor, but hitting the tab key after entering one's account name should probably go to the password field, but instead that moves to the search button (the magnifying glass, not even the search field). At least it does for me (SuSE/Firefox 52.3... not sure what other info you would need.)

In many cases, the race menu popups may overflow the page revealing the empty yellow space below the site footer, due to them being too tall. To alleviate this, we may use CSS column layouts.

An early attempt at this using styling on the markup wmlunits produces as of wesnoth/wesnoth@b96dc224d0c7 shows that the idea should work, but it requires major markup changes because of Firefox not supporting the column-span property yet. Without it, short menus tend to look extremely weird if the column count is greater than what the menu should actually need:

It may be possible to instruct wmlunits to annotate popup menus with extra classes to decide how many columns we need, but there's still the problem of the popup label (itself part of the list) being dragged into the first column:

So, preferably, the menu should be reworked as a <div> containing a <div> for a label (like it was already the case for the Language menu, and the elements below in a column-layout list.

Some styles for the home page rely on deprecated operator semantics for RGB color values. These are the warnings output by Sass 3.5.1 during build:

DEPRECATION WARNING on line 104 of sass/home/_download.scss:
The operation `#171a21 plus #202020` is deprecated and will be an error in future versions.
Consider using Sass's color functions instead.
http://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 105 of sass/home/_download.scss:
The operation `#171a21 plus #303030` is deprecated and will be an error in future versions.
Consider using Sass's color functions instead.
http://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 106 of sass/home/_download.scss:
The operation `#171a21 plus #404040` is deprecated and will be an error in future versions.
Consider using Sass's color functions instead.
http://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

DEPRECATION WARNING on line 107 of sass/home/_download.scss:
The operation `#171a21 plus #505050` is deprecated and will be an error in future versions.
Consider using Sass's color functions instead.
http://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions

phpBB 3.2 has a hard dependency on Font Awesome and provides its own shipped version including font files and CSS. However, Wesmere also pulls its own version of Font Awesome even when using the minimal forums stylesheet, resulting in extra code (most of it unused) and more assets to download, thus increased load times.

Would it be possible to either add a screenshot, and/or a link to show the wesmere theme in particular?

I assume the wesnoth homepage uses it, but while that may seem obvious, a newcomer may not instantly
know that, so it would be helpful if someone could sort of pinpoint where exactly the wesmere theme is
in used, how it looks, whether the pink screen is really intended (the last part is made up, I just wanted
to illustrate the point of newcomers not knowing this ... but also perhaps some oldbies too!).

It was pointed out on IRC that sometimes, the unit details page renders as a single column regardless of the viewport size:

https://units.wesnoth.org/trunk/Deep_Elves/en_US/Harbinger.html

This appears to be a problem specific to Firefox when the unit description is too narrow (i.e. because it's empty/too few characters).

To my knowledge, nobody has had access to GA or used the info therein in over a decade, not to mention that script and ad blockers are likely to make it mildly inaccurate. As it is, right now it just contributes to page load times and adds unnecessary 3rd party tracking.

(This change would impact the front page, the Wesmere MW template, and the Wesmere extension at https://github.com/shikadiqueen/weldyn2-extensions.)

The build timestamp at the bottom of the page should be logically part of the right panel so there need not be any more clunky CSS workarounds to set its layout right, and also so the panel divider renders all the way to the bottom of the page right above the site footer.

This is partly a CSS change and also a markup change potentially requiring some minor refactoring in wmlunits.

This is a suggestion for content, not site functionality, I apologize if this isn't the right venue.

If Wesnoth needs contributors as much as customers/players (and I think it still does) shouldn't a link be up near the "Download Now!" button? All the relevant info and links are included at the bottom of the page, but it would help to have one of the wiki/forum links advertised on almost-equal footing as the download button.

Especially on the forums and the wiki, not being able to distinguish which links have previously been visited is rather annoying.

The events for the sidebar menus are attached as part of a page load handler, meaning the page must finish loading for them to be registered. This is rather awkward for the unit tree pages since they have too many image resources that need to be loaded before the event fires.

This is already fixed in wesnoth/wesnoth@b96dc224d0 but its deployment is pending a site rebuild.

For example the "Places" and "Advanced" buttons open a dropdown menu (as opposed to taking you to a new page like all/most other buttons), but the button icons give no indication of that. Icons of such buttons should have an ellipsis or a downwards arrow or something similar as a visual hint.

Currently Wesmere does not support the phpBB 3.2 prosilver behaviour of removing margins around the main area of the forum on small viewports to maximize available space for content, when coupled with the Wesmere compatibility extension from weldyn2-extensions.

This is an important issue that needs to be fixed before deployment of phpBB 3.2.

Currently, any time the unit details view gets degraded to a single-column layout, the unit portraits end up buried somewhere between the damage resistances table and the terrain stats because of the markup order -- it is part of the right column, after all.

A potential solution would be to rearrange the details view into a 2x2 grid with the top left being the unit sprite and description, top right the portraits, and bottom the columns as they are now.