Proposal: Website redesign 2026 + full i18n catalog (35 locales)

[DennisPitallano]

Proposal: Website redesign 2026 + full i18n catalog (35 locales)

I've drafted an end-to-end rebuild of digibyte.org targeting June 2026, plus a
proper internationalization catalog so every locale ships native-language content out
of the box. Looking for community / maintainer review before merging.

Live preview: https://dg-bio.vercel.app
Branch: DennisPitallano:redesign-2026
PR: opened separately, references this issue.

Why

• The current site predates DigiAssets / Digi-ID / DigiDollar messaging and looks
  visually outdated.
• Translations rot quickly because the workflow ("copy English into <lang>/index.html,
  then translate by hand") gets overwritten every time the page changes. Nobody owns
  it, and most locale pages are partially stale English.
• We can fix both at once: ship a modern design and introduce a translation
  catalog so the next person can refine copy in one file instead of 35.

What's in the proposal

Visual / content redesign

• Blue-only palette aligned with the DGB logo.
• Isometric blockchain hero with live network metrics surfaced above the fold.
• New section layout, components, and tokens in css/ (tokens.css, base.css,
  components.css, sections.css, utilities.css).
• New hero canvas + chain dashboard + GitHub release card JS in js/.
• Animated roadmap "road" SVG with two DGB cars.
• Live-chain ticker reads directly from network endpoints — no third-party APIs.
• Tightened copy across the Why DGB / Live chain / Tokenomics / DigiAssets /
  Digi-ID / Developer hub / Wallets / Roadmap / Community / Downloads / News
  sections around a single "engineered for continuous operation" through-line.

Internationalization

• New locales/<lang>.json catalog format — 237 keys × 35 locales = 8,295
  translated strings.
• Source index.html marked up with data-i18n="key" and
  data-i18n-attr="attr:key,…" attributes.
• tools/sync-locales.mjs rewritten so it merges the catalog into each
  <lang>/index.html after the existing path-rewriting pass. Missing keys fall back
  to English. Run node tools/sync-locales.mjs --check in CI to catch drift.
• RTL (ar, fa) handled by the existing dir="rtl" rewrite.
• Language picker in the nav and js/lang-router.js updated; pt-BR browsers now
  route to /pt-br/ instead of /pt/.

Misc

• DIP draft included at docs/dip-pitallano-website-redesign.mediawiki.
• DigiDollar integration guide PDF link points at the current
  /docs/DigiDollar_integration_guide.pdf.

Scope

• 20 commits.
• ~110 files changed, ~52 K insertions / ~48 K deletions (most of the deletes are
  legacy locale HTML being replaced by the catalog-driven version).

Translation quality — honest caveat

The 35 catalogs are seeded with machine-translated values validated for
key-parity. They render naturally enough to ship, but native-speaker polish is
strongly recommended — strongest today in es / de / fr / it / pt / nl / pl / ru / ja / zh, weakest in th / hi / fil / sw / sq / af.

Refining a locale is now a one-file PR:

1. Edit locales/<lang>.json.
2. node tools/sync-locales.mjs.
3. Commit both the catalog change and the regenerated <lang>/index.html.

I'd love community volunteers to claim a locale and polish it after this lands.

Acceptance checklist

• Maintainer reviews the live preview on desktop + mobile.
• At least one RTL locale spot-checked (/ar/ or /fa/).
• At least one CJK locale spot-checked (/ja/ or /zh/).
• node tools/sync-locales.mjs --check passes.
• Language-picker entries navigate to working translated pages.
• Decision: merge as-is and polish locales in follow-up PRs, or hold for native
  review first.

Happy to address feedback, split into smaller PRs, or back any part out. CC
maintainers — what would make this easier to merge?