Redesign homepage with community-first copy, feature bento, and shared footer

[aXenDeveloper]

The homepage previously led with implementation details and a technology animation, making it harder for visitors to understand why they would choose VitNode. This redesign explains the benefits for community owners and their teams, while clearly communicating how early the canary release is.

What changes

• A new “Your people. Your kind of place.” hero with an early canary notice before the pitch and direct links to setup and GitHub.
• A light, neutral palette with primary blue retained, plus a coordinated dark palette scoped to the main website. Existing header navigation, account, language, and theme controls remain available.
• Responsive feature bento covering AdminCP, plugins, content tools, permissions, and languages, with links to the supporting documentation.
• An illustrative community preview, the existing real AdminCP screenshot, and a small SVG plugin diagram. The preview is explicitly labeled as an illustration, not a bundled theme.
• Plain-language business benefits and a balanced comparison with hosted community platforms and general app starters, including development, hosting, and maintenance trade-offs.
• A personal introduction for Maciej using his locally stored public GitHub avatar, with an invitation to contribute.
• Detailed canary expectations, including breaking changes and unsuitability for business-critical use.
• A shared footer outside the main landmark for every _main route, including public plugin pages.
• Updated homepage metadata and website maintenance notes describing the copy sources and asset provenance.

Motion and accessibility

Motion uses CSS and SVG only: a short entrance and a finite connection animation, tied to scrolling where supported. Reduced-motion users receive static content. No new dependencies, hidden-on-load copy, autoplay carousels, or homepage animation-library imports. Images have dimensions, alternative text, and lazy loading. Internal links use the existing locale-aware router.

Validation

• pnpm install --frozen-lockfile
• pnpm build:plugins
• pnpm --filter web typecheck
• pnpm --filter web build (final source; client and server build passed)
• ESLint on changed TypeScript/TSX files
• Prettier check on changed text files
• git diff --check
• Verified all 11 linked documentation destinations exist and both local images decode with the declared dimensions.

Browser/visual testing was not run. The repository's docs:check script currently points to a missing apps/web/scripts/check-docs.mjs; documentation destinations were checked directly instead. No new unit tests were added because this is presentational composition without new business logic.

Copy is grounded in the repository's setup, plugin/AdminCP, Content Engine, staff permissions, i18n, blog, and self-hosting docs. The visual direction draws on the supplied Mintlify, Linear, and other references; the maker section takes inspiration from Zero to Shipped without importing its claims or credentials.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
vitnode-prod	Ready	Preview	Sep 5, 2026 7:18am UTC

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Redesign homepage with community-first copy, feature bento, and shared footer". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7c00d2f531

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Localize the shared footer

When a visitor uses the supported Polish locale on a _main route such as /pl/login, the route renders this new shared footer while all of its headings, link labels, status copy, and ARIA labels remain fixed in English. The surrounding header and core screens use the selected locale, so these routes now present a mixed-language interface; move the footer strings into the existing i18n message system and load the corresponding namespace with the main shell.

Useful? React with 👍 / 👎.