[whereareiam]

Summary

I compared Forgejo's profile Overview tab, which opens when a person has a .profile README, with the Overview on GitHub's profiles and changed what differed.

• Popular repositories under the README: up to six of the person's public repositories, most-starred first, now appear below the profile README. The cards sit two to a row on desktop and one to a row on phones.
• GitHub's repository cards: each card shows the repository icon (a fork or mirror keeps its own icon), the name, and the visibility, archived and template labels as the theme's muted pill labels. Below that come the description and a bottom row with the language, stars and forks, the last two only when there are any. Cards in a row are the same height, so their bottom rows line up as on GitHub.
• Nothing when there is nothing to show: the section stays hidden until it has cards. A person without public repositories, or a request that fails, sees the README alone, as before.

Forgejo loads no repositories for the Overview tab. A small script, profile-overview.js, therefore requests the person's Repositories tab once, sorted by most stars and filtered to public repositories, and builds the cards from that server-rendered list. It reads only from the same origin, and the cards keep Forgejo's own links, labels, language colours and star/fork aria-labels.

Already matching, so unchanged: the Overview tab and its place in the profile tabs, and the README box with its user / .profile heading.

Left out because Forgejo works differently: pinned repositories and "Customize your pins" (Forgejo has no pinning), and the "Popular" wording (Forgejo has no string for it, so the heading uses Forgejo's "Repositories"). The contribution graph and activity also stay on the Public activity tab: Forgejo loads the heatmap data only for that tab, and its heatmap starts only on page load.

Draft, for a decision: Forgejo's handler loads no repositories for the Overview tab, so profile-overview.js fetches the person's Repositories tab page and builds the six cards from that server-rendered list. That is one extra full-page request per Overview view, and it depends on the repository list's markup. The alternative is to leave the cards out until Forgejo provides the data.

Before and after

Before	After

Release notes

• The title follows Area: Description with a listed area
• The title describes the effect in the past tense, for example Branches: Fixed ...
• Exactly one label: feature, change, bug, dependencies, or skip-changelog
• bug only for a bug that shipped in a release; a fix for a bug that only existed on dev is skip-changelog
• major added when admins must act on upgrade, for example a new minimum Forgejo version
• Upgrade steps or warnings added to .github/release-notes.md, if admins need them

Checks

• Tests added or updated
• Checked in the dev preview at desktop and phone width, in dark and light mode

🤖 Generated with Claude Code