Repository navigation
Redesign of the statistics box - #6745
Merged
Merged
Conversation
dtdesign
force-pushed
the
63-stats-box-redesign
branch
from
October 21, 2026 18:43
906ba38 to
aba8f4f
Compare
dtdesign
marked this pull request as ready for review
October 21, 2026 19:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The statistics have long been overdue for a redesign. The current form is just a elongated wall of text, enumerating metrics in the most unappealing way and without any structure. It is functional but does not really fit in our over-arching vision for a modernized layout.
We have preserved the existing phrases in all apps so that the change itself is fully backwards compatible. Customized template will continue to show the old metric without breaking.
One thing we did drop is the display of the latest member. This is leaking a username even if users are unable to view the members list plus causes increased cache resets due to it requiring to be updated when a new user signed up. Furthermore this requires a cached user object for performance reasons with the risk of it becoming stale to some extend. A surprising amount of work for such a tiny detail. For the time being we will keep the user around to prevent the legacy stats in modified templates to work.