feat(redesign): Homepage Features and Banner component

[g-francesca]

Preview
Note: PR created as draft while merging #2203 (since this branch was created from redesign-homepage branch)

---

This PR includes new homepage sections:

• Features section: new Features pattern component displaying a 4-card grid (Performance, APIs, Middleware, Web Applications) with a responsive layout (stacked on mobile, side-by-side title/cards on desktop). Includes a new Card primitive and corresponding i18n strings.
• Top Banner component — new Banner pattern component for full-width notification banners. Supports info/warning variants, optional date-range visibility (startDate/endDate), and optional dismiss-to-localStorage behaviour. Dismissed state is applied via an inline <style> injected before first paint to prevent layout shift on load.

Other changes

• Added --blue-975 color token and updated --color-bg-info / --color-border-info dark-mode values for better contrast.
• Refactored the inline theme-detection script in Layout.astro for readability; extended it to hide previously-dismissed banners before paint.

---

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

[netlify]

✅ Deploy Preview for expressjscom-preview ready!

Name	Link
🔨 Latest commit	1ce5bce
🔍 Latest deploy log	https://app.netlify.com/projects/expressjscom-preview/deploys/69a6d36a8f96bd00086f1409
😎 Deploy Preview	https://deploy-preview-2204--expressjscom-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 97 (🟢 up 1 from production) Accessibility: 100 (🟢 up 13 from production) Best Practices: 100 (no change from production) SEO: 100 (🟢 up 6 from production) PWA: 80 (🟢 up 50 from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​typescript-eslint@​8.53.1
	npm/​astro-expressive-code@​0.41.7
	npm/​typescript@​5.9.3

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm vite is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: astro/package-lock.json → npm/astro@5.18.0 → npm/vite@6.4.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vite@6.4.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report