Skip to content

Organizations: Add GitHub-style views and subpages - #58

Draft
whereareiam wants to merge 1 commit into
devfrom
feat/organization-pages
Draft

whereareiam wants to merge 1 commit into
devfrom
feat/organization-pages

Conversation

@whereareiam

@whereareiam whereareiam commented Sep 16, 2026 •

Copy link
Copy Markdown
Owner

Organization pages now use GitHub-style navigation, an overview with repository cards and a member sidebar, and dedicated repository filters. Members, teams, projects, packages, package versions, and organization settings share responsive layouts while retaining Forgejo's permissions, forms, links, pagination, and confirmation dialogs.

Shared sidebar, search, button, and select-menu primitives now serve organization pages and repository Issues. Shared controllers handle sidebar preferences, responsive collapse, focus, and menu dismissal. Profile pages reuse the repository filter and sort templates. Contributor guidance documents the component hooks.

The organization title uses the same Mona Sans family as GitHub at weight 600. Header actions align at the top and use 34px controls; migration precedes repository creation; the sidebar separator is straight; New team uses a compact secondary button; team statistics are muted plain text. The repository listing has a full-height sidebar, contextual heading, full-width search, results count, and sort menu.

Dropdowns use explicit shared single-choice, multiple-choice, and action-menu variants. Filters use GitHub-style square checkboxes and a separate Clear filters button. Filtering updates only the repository results, keeps the overview and multi-select menu open, preserves search/sort and pagination context, and cancels obsolete requests. Popup borders and hover colors match GitHub; sidebar counts and chevrons are muted, and repository rows highlight on hover.

Validation: production build and TypeScript checks pass; all 382 Vitest tests pass. Checked desktop, 390px mobile, light/dark, populated and empty states, search, project creation, team forms, package versions, and owner/anonymous route visibility in Forgejo 16.0.3. Verified description markup and long website/email links at desktop and mobile widths. Issues search fills the content column, and both sidebars meet the bottom of the navigation without a gap. ESLint is blocked because the repository's typescript-eslint dependency does not support its configured TypeScript 7.

CI: build, formatting, TypeScript, Vitest, and release-label checks passed.

Before/after comparisons use the same organization, page state, and desktop viewport.

Overview
Before After
Overview before Overview after
Members
Before After
Members before Members after
Teams
Before After
Teams before Teams after
Projects
Before After
Projects before Projects after
Packages
Before After
Packages before Packages after
Settings
Before After
Settings before Settings after
Repositories

The baseline is the original combined organization and repository listing.

Before After
Repositories before Repositories after
Multi-select filtering

Two criteria remain selected with the overview and filter menu open after the results update.

Multi-select filters

Repository row hover

Repository row hover

@whereareiam whereareiam added the feature New user-facing capabilities or themes label Sep 16, 2026
@whereareiam
whereareiam force-pushed the feat/organization-pages branch 3 times, most recently from 77a25cb to 66e8caf Compare September 16, 2026 19:16
@lutinglt

Copy link
Copy Markdown

WoW, Is the screenshot in After the current implementation? That's so cool—did you write it yourself or use AI to implement it?

@whereareiam

Copy link
Copy Markdown
Owner Author

WoW, Is the screenshot in After the current implementation? That's so cool—did you write it yourself or use AI to implement it?

Hi, it was developed entirely by AI, using a custom testing and reproduction environment to iterate on the GitHub and Forgejo themes. It still required some input from my side.

@lutinglt

Copy link
Copy Markdown

WoW, Is the screenshot in After the current implementation? That's so cool—did you write it yourself or use AI to implement it?

Hi, it was developed entirely by AI, using a custom testing and reproduction environment to iterate on the GitHub and Forgejo themes. It still required some input from my side.

Awesome, that must have cost quite a lot of tokens, right?

@whereareiam

Copy link
Copy Markdown
Owner Author

WoW, Is the screenshot in After the current implementation? That's so cool—did you write it yourself or use AI to implement it?

Hi, it was developed entirely by AI, using a custom testing and reproduction environment to iterate on the GitHub and Forgejo themes. It still required some input from my side.

Awesome, that must have cost quite a lot of tokens, right?

Not really. It's about 2-3% of the X20 ChatGPT plan.
The most frustrating part is not knowing when the real AI model is being used and not some cheaper or older model behind the scenes.

@whereareiam
whereareiam force-pushed the feat/organization-pages branch 4 times, most recently from c3e7379 to 33fde70 Compare September 23, 2026 15:58
@whereareiam
whereareiam force-pushed the feat/organization-pages branch from 33fde70 to f3d5915 Compare September 23, 2026 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New user-facing capabilities or themes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants