[PR #3851] [MERGED] fix(website): give navigation room and refresh contributors #5948

Closed
opened 2026-10-31 01:10:39 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3851
Author: @N0zoM1z0
Created: 10/15/2026
Status: ✅ Merged
Merged: 10/15/2026
Merged by: @N0zoM1z0

Base: main ← Head: fix/website-header-layout


📝 Commits (1)

  • 53a456a fix(website): give navigation room and refresh contributors

📊 Changes

24 files changed (+293 additions, -287 deletions)

View changed files

📝 website/locales/ar/messages.po (+10 -10)
📝 website/locales/de/messages.po (+10 -10)
📝 website/locales/el/messages.po (+10 -10)
📝 website/locales/es/messages.po (+10 -10)
📝 website/locales/fa/messages.po (+10 -10)
📝 website/locales/fr/messages.po (+10 -10)
📝 website/locales/id/messages.po (+10 -10)
📝 website/locales/it/messages.po (+10 -10)
📝 website/locales/ja/messages.po (+10 -10)
📝 website/locales/ko/messages.po (+10 -10)
📝 website/locales/messages.pot (+10 -10)
📝 website/locales/pl/messages.po (+10 -10)
📝 website/locales/pt-BR/messages.po (+10 -10)
📝 website/locales/ru/messages.po (+10 -10)
📝 website/locales/th/messages.po (+10 -10)
📝 website/locales/tr/messages.po (+10 -10)
📝 website/locales/uk/messages.po (+10 -10)
📝 website/locales/vi/messages.po (+10 -10)
📝 website/locales/zh-CN/messages.po (+10 -10)
📝 website/locales/zh-TW/messages.po (+10 -10)

...and 4 more files

📄 Description

Summary

Keep desktop navigation together and refresh the Contributors directory.

Problem and expected behavior

The header shared the 1080px content limit. After the GitHub star count loaded, English navigation wrapped Contributors onto a second line at 1280–1920px. Desktop navigation should fit together; smaller screens should move the whole navigation below the brand and controls.

Change and scope

  • Give the header an independent 1320px maximum; retain the 1080px content and 760px article limits.
  • Consolidate responsive header ownership: navigation gets its own row at ≤1100px; the brand caption hides below 1280px. Keep mobile links comfortably spaced.
  • Refresh the public GitHub snapshot from 214 to 216 accounts: add JNTMTMTM and Swatantra-66. Existing accounts and profile records are unchanged; the display remains alphabetical and unranked.
  • Regenerate the contributor region and catalog references/date comments. All message IDs, translations, flags and catalog metadata are unchanged.

This addresses a maintainer-reported visual bug; no separate issue. No new features or content rewrite.

Contract and boundary impact

  • Semantic owner: shared website CSS, contributor snapshot and its existing renderer.
  • Contribution scope: ordinary website usability/data maintenance; special provider/target-execution approval is not applicable.
  • CLI/MCP, providers, Evidence, target authority, package/install contracts and generated product metadata: unchanged.
  • Effects: documentation/usability only; no target interaction. The existing contributor refresh contacts GitHub; the production website's network behavior is unchanged.

Evidence and regression coverage

Executed Chromium checks with a deterministic six-digit star count (248,357, a layout fixture, not a live popularity claim):

  • Before: English desktop navigation occupied two lines at 1280, 1366, 1440, 1536 and 1920px. After: one line at those sizes.
  • 20 languages × 15 viewport widths (320–1920px) × root and /rea/ previews: 600 cases passed. Desktop links stay on one line; medium layouts move the complete nav; no horizontal overflow or control overlap; content width is unchanged.
  • Both path prefixes: language-menu bounds, keyboard/language navigation, light/dark themes, 216 alphabetical profile links, searches for both new accounts, API failure and JavaScript-disabled navigation passed.
  • Parsed comparison: every existing contributor record is preserved; all 20 source/translation catalogs retain identical messages, translations, flags and metadata.

The browser checks were ad-hoc local acceptance checks, not newly committed test infrastructure. Existing maintenance regressions remain unchanged.

Validation performed

  • website/.venv/bin/python scripts/website.py check — passed: 382 HTML pages, 26,087 local references, 380 indexable pages, 19 translation catalogs, and 16 maintenance tests.
  • npm run check:fast — passed with pinned Node 24.18.0/npm 11.16.0 after npm ci refreshed stale dependencies.
  • Focused oxfmt --check and git diff --check — passed.
  • Local Chromium acceptance checks described above — passed on both root and /rea/.
  • CI run 38684611123 — passed, including static checks, portable tests, website checks and the required aggregate. Conventional PR title check also passed.
  • Greptile review — 5/5, no actionable defects. Its own browser capture was unavailable; the executed local Chromium evidence above remains the browser verification.

Compatibility, safety, and release

No breaking changes, package release, installation changes or target/provider execution. Firefox/Safari and physical-device/browser-zoom coverage were not run. Production publishing remains the existing manual website-pages.yml workflow, targeting both hosts after merge.

Author readiness

Human owner: @N0zoM1z0

The human owner explicitly authorized this PR, CI/review follow-up, merge and website publication in the working session. The declarations below remain for the human owner to complete; automation does not attest to a human diff/evidence review.

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/3851 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/15/2026 **Status:** ✅ Merged **Merged:** 10/15/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `fix/website-header-layout` --- ### 📝 Commits (1) - [`53a456a`](https://github.com/morluto/rea/commit/53a456a7e5910442cb94d7861b059bcb8e4f3d07) fix(website): give navigation room and refresh contributors ### 📊 Changes **24 files changed** (+293 additions, -287 deletions) <details> <summary>View changed files</summary> 📝 `website/locales/ar/messages.po` (+10 -10) 📝 `website/locales/de/messages.po` (+10 -10) 📝 `website/locales/el/messages.po` (+10 -10) 📝 `website/locales/es/messages.po` (+10 -10) 📝 `website/locales/fa/messages.po` (+10 -10) 📝 `website/locales/fr/messages.po` (+10 -10) 📝 `website/locales/id/messages.po` (+10 -10) 📝 `website/locales/it/messages.po` (+10 -10) 📝 `website/locales/ja/messages.po` (+10 -10) 📝 `website/locales/ko/messages.po` (+10 -10) 📝 `website/locales/messages.pot` (+10 -10) 📝 `website/locales/pl/messages.po` (+10 -10) 📝 `website/locales/pt-BR/messages.po` (+10 -10) 📝 `website/locales/ru/messages.po` (+10 -10) 📝 `website/locales/th/messages.po` (+10 -10) 📝 `website/locales/tr/messages.po` (+10 -10) 📝 `website/locales/uk/messages.po` (+10 -10) 📝 `website/locales/vi/messages.po` (+10 -10) 📝 `website/locales/zh-CN/messages.po` (+10 -10) 📝 `website/locales/zh-TW/messages.po` (+10 -10) _...and 4 more files_ </details> ### 📄 Description ## Summary Keep desktop navigation together and refresh the Contributors directory. ## Problem and expected behavior The header shared the 1080px content limit. After the GitHub star count loaded, English navigation wrapped **Contributors** onto a second line at 1280–1920px. Desktop navigation should fit together; smaller screens should move the whole navigation below the brand and controls. ## Change and scope - Give the header an independent 1320px maximum; retain the 1080px content and 760px article limits. - Consolidate responsive header ownership: navigation gets its own row at ≤1100px; the brand caption hides below 1280px. Keep mobile links comfortably spaced. - Refresh the public GitHub snapshot from 214 to 216 accounts: add `JNTMTMTM` and `Swatantra-66`. Existing accounts and profile records are unchanged; the display remains alphabetical and unranked. - Regenerate the contributor region and catalog references/date comments. All message IDs, translations, flags and catalog metadata are unchanged. This addresses a maintainer-reported visual bug; no separate issue. No new features or content rewrite. ## Contract and boundary impact - Semantic owner: shared website CSS, contributor snapshot and its existing renderer. - Contribution scope: ordinary website usability/data maintenance; special provider/target-execution approval is not applicable. - CLI/MCP, providers, Evidence, target authority, package/install contracts and generated product metadata: unchanged. - Effects: documentation/usability only; no target interaction. The existing contributor refresh contacts GitHub; the production website's network behavior is unchanged. ## Evidence and regression coverage Executed Chromium checks with a deterministic six-digit star count (`248,357`, a layout fixture, not a live popularity claim): - Before: English desktop navigation occupied two lines at 1280, 1366, 1440, 1536 and 1920px. After: one line at those sizes. - 20 languages × 15 viewport widths (320–1920px) × root and `/rea/` previews: **600 cases passed**. Desktop links stay on one line; medium layouts move the complete nav; no horizontal overflow or control overlap; content width is unchanged. - Both path prefixes: language-menu bounds, keyboard/language navigation, light/dark themes, 216 alphabetical profile links, searches for both new accounts, API failure and JavaScript-disabled navigation passed. - Parsed comparison: every existing contributor record is preserved; all 20 source/translation catalogs retain identical messages, translations, flags and metadata. The browser checks were ad-hoc local acceptance checks, not newly committed test infrastructure. Existing maintenance regressions remain unchanged. ## Validation performed - `website/.venv/bin/python scripts/website.py check` — passed: 382 HTML pages, 26,087 local references, 380 indexable pages, 19 translation catalogs, and 16 maintenance tests. - `npm run check:fast` — passed with pinned Node 24.18.0/npm 11.16.0 after `npm ci` refreshed stale dependencies. - Focused `oxfmt --check` and `git diff --check` — passed. - Local Chromium acceptance checks described above — passed on both root and `/rea/`. - [CI run 38684611123](https://github.com/morluto/rea/actions/runs/38684611123) — passed, including static checks, portable tests, website checks and the required aggregate. Conventional PR title check also passed. - [Greptile review](https://github.com/morluto/rea/pull/3851#issuecomment-6184923515) — 5/5, no actionable defects. Its own browser capture was unavailable; the executed local Chromium evidence above remains the browser verification. ## Compatibility, safety, and release No breaking changes, package release, installation changes or target/provider execution. Firefox/Safari and physical-device/browser-zoom coverage were not run. Production publishing remains the existing manual `website-pages.yml` workflow, targeting both hosts after merge. ## Author readiness Human owner: @N0zoM1z0 The human owner explicitly authorized this PR, CI/review follow-up, merge and website publication in the working session. The declarations below remain for the human owner to complete; automation does not attest to a human diff/evidence review. - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:10:39 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#5948
No description provided.