[Website] Track post-OINK improvements

## Goal

Coordinate the website improvements that follow the OINK 1.0 migration in #466.

This parent issue is the single place to review scope, progress, dependencies, and decisions. Implementation remains in focused child issues.

## Child workstreams

- UI direction and visual evolution
- Community contributor showcase

Progress is tracked through GitHub sub-issues below. Add future website follow-ups here only when they have a clear scope and acceptance criteria.

## Coordination

- Keep user-facing behavior, screenshots, and design decisions in the relevant child issue.
- Summarize cross-cutting decisions and blockers on this parent issue.
- Close this parent after every required child issue is complete or explicitly deferred.
- Treat unrelated documentation content and release-validation work as separate scopes.

## Background

The OINK 1.0 migration was delivered by #466. The production migration itself is complete; this issue tracks subsequent website improvements rather than reopening the migration.

This is a parent coordination issue rather than an implementation task. Start with the OINK 1.0 migration in #466 and the GitHub sub-issues for UI direction and the community contributor showcase; use those child scopes and acceptance criteria to identify actionable work. The parent is done when required child issues are complete or explicitly deferred.

Written by the indexing model from the issue text.