Skip to content

v0.8.69: Turn multilingual community credit into a durable website surface #3416

Description

@Hmbown

Why this matters

CodeWhale's community is one of its strongest signals, and the site should make that visible across languages without turning the homepage into a static release-credit dump. Existing issues already track adding more website/README locales; this issue is specifically about how community credit, contributor stories, reports, PRs, mirrors, and regional entry points are presented once the site becomes more professional.

Current behavior

  • web/lib/i18n/config.ts:1 only enables en and zh on the website even though the repo already has README.zh-CN.md, README.ja-JP.md, and README.vi.md.
  • The homepage hard-codes release contributor/helper arrays (web/app/[locale]/page.tsx:21, web/app/[locale]/page.tsx:63).
  • The homepage then renders those static handles as the main release credit surface (web/app/[locale]/page.tsx:440 and web/app/[locale]/page.tsx:449).
  • The community story is strong but embedded in the homepage after many unrelated sections (web/app/[locale]/page.tsx:464).

Desired behavior

  1. Create a durable community page/section that can be localized and linked from the product/docs flow.
  2. Source contributor credit from release notes, GitHub metadata, docs/CONTRIBUTORS.md, or a small generated data file instead of static homepage arrays.
  3. Preserve the visible multilingual posture: Chinese, Japanese, Vietnamese, and future locales should not be treated as afterthoughts.
  4. Highlight contribution paths, regional install/mirror needs, and community reports/PRs in a way that stays current across releases.
  5. Keep the homepage community message concise and link to the deeper community surface.

Repro or evidence

nl -ba web/lib/i18n/config.ts | sed -n '1,12p'
nl -ba 'web/app/[locale]/page.tsx' | sed -n '18,85p;440,525p'

This shows the two-locale website config, hard-coded contributor/helper arrays, and the homepage community block.

Acceptance criteria

  • A community/credits page or structured homepage section is implemented with a documented data source.
  • Release contributors and helpers are not maintained as stale hard-coded arrays in the homepage route.
  • English and Chinese copy are updated, and the design leaves an obvious extension path for Japanese/Vietnamese and future locales.
  • The page cross-links contribution docs, open issues, discussions, release notes, and mirror/regional install paths where relevant.
  • Existing localization issues remain linked and are not duplicated.
  • cd web && npm run lint && npm run test && npm run build passes.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestlocalizationLocalization, i18n, and non-English language supportuxUser experience, interaction, or presentation polishv0.8.69Targeting v0.8.69

    Projects

    Status
    In progress

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions