[ReenigneArcher]

Description

Project cards currently derive banner, activity, and language paths from repository names, so newly discovered organizations and renamed projects can display the wrong assets. Consume dashboard_paths, dashboard_key, and dashboard_aliases directly to preserve the dashboard's stable asset identities and Read the Docs links across transfers.

Add organization labels, project search, and an organization filter driven by LizardByte/.github/organizations.json. The archived-project link follows that scope, including organizations with no active cards. Filtering reuses existing cards without repeating asset requests. Titles and banners use each repository's configured HTTP(S) homepage, so project subdomains do not require another domain mapping or umbrella-site probes.

Deployment dependency: Merge dashboard PR #379 and publish its catalog before deploying this website change. This consumer requires the new metadata fields.

Screenshot

No browser screenshot captured in this session.

Issues Fixed or Closed

Roadmap Issues

Testing

• All 30 tests across 10 Jest suites passed with 100% statement, branch, function, and line coverage (node node_modules/jest/bin/jest.js --runInBand --coverage).
• npm run test:lint and git diff --check passed. Project discovery is now included in the configured ESLint check.
• The transferred/renamed-asset regression failed against the base implementation (renamed_624x312.png instead of the supplied Sunshine_624x312.png) and passes with this change.
• Added same-name repository, stable asset path, homepage protocol, SSH/HTTPS docs alias, organization/search filter, archived scope, registry validation/outage, and no-refetch coverage. Tests mount the real homepage Projects section.
• Replayed the migration rehearsal catalog: 84 public repositories produced 55 eligible cards, with all 21 owner-qualified asset mappings validated and zero additional requests when filtering.

Hosted CI-Node, Common Lint, Jekyll build, Codecov, and Sonar analysis pass for commit 5a87988. Sonar reports zero open PR findings and quality gate OK. CodeQL Actions, JavaScript, and Ruby analyses passed. Browser visual verification was not performed.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (dcede9d) to head (5a87988).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #523   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          999      1047   +48     
  Branches       131       141   +10     
=========================================
+ Hits           999      1047   +48     

Files with missing lines	Coverage Δ
assets/js/projects.js	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dcede9d...5a87988. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud