Repository navigation
site: cities dashboard and the live feed straight after the hero - #6
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The home page now reads: hero, every city built so far, GitHub live, then how to read a city, sharing, self-hosting and the FAQ. - The dashboard is /explore's: filter, people/orgs/repos, sort (featured, latest, commits, agent- and bot-written, lines, repos) and a count. It shows two full rows, then "Show all N cities". - The live sample is one wide card: the human/bot/agent split and a longer feed side by side, with the agent roster underneath. The agent lens card's per-city ranking duplicated the dashboard's sort and is gone. - The hero's 3D city loads on "Play in 3D" instead of on idle: the viewer, a city's data and WebGL were the heaviest things on the page, and most visitors never touched them. The URL swap band, which repeated the hero's first line on a 1.7 s timer, is gone too.
azank1
force-pushed
the
site/home-dashboard-first
branch
from
October 13, 2026 10:58
b7c03ab to
fba22f5
Compare
- Events drip in the order they happened. Agents went first ("that's the
story"), so the feed showed them at many times their real share: 11% of
the last 230 events.
- The three shares round to a total of 100 (largest remainder); rounded
one by one they read 74 + 16 + 11 = 101%.
- Create and delete events say what was made: "created a branch in
owner/repo", not "created owner/repo", which read as a new repository.
All six creates in that sample were branches.
- GitHub publishes its timeline minutes behind (the newest event was 5
minutes old), so the note says how far, each row shows its age, and the
kicker says "GitHub's public timeline", not "right now".
- The copy names what this feed actually reads: agent accounts and agent
branches, other bots by their [bot] accounts. Co-authored-by trailers are
read in cities, not here.
- The hero and "Try" chips open react/react, where GitHub now keeps React;
facebook/react was a second city of the same repo.
azank1
marked this pull request as ready for review
October 13, 2026 12:22
This branch was successfully deployed
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
1 participant
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 homepage now leads with what people come for.
Checked locally with headless screenshots at desktop and phone widths, and the page's selftest route.
Second commit: the live feed shows GitHub's timeline as it is
[bot]accounts.Co-authored-bytrailers are read in cities, not here.react/react, where GitHub keeps React.facebook/reactwas a second, older city of the same repo.Checked on the dev server with production's gallery, featured metas and the live timeline: 64% + 27% + 9% = 100%, and the feed is chronological.