i18n: rebrand doc download labels (DGB / DigiDollar / DigiByte Technical Architecture (White Paper)) - #180
Conversation
- DGB Integration Guide
- DigiDollar Integration Guide
- DigiDollar White Paper
- DigiByte Technical Architecture (White Paper)
Applied across:
- locales/*.json (34 locales) for downloads.docs.*, devhub.link.integration.title,
tokenomics.cta.techArch and footer.resources.* keys
- <lang>/index.html fallback text for the same keys
- Root/en/en-us HTML fallback text
Non-English locales use localized equivalents:
DGB {IntegrationGuide}
DigiDollar {IntegrationGuide}
DigiDollar {WhitePaper}
DigiByte {TechnicalArchitecture} ({WhitePaper})
…titles footer.resources.integration -> 'DGB <Integration Guide>' and footer.resources.digidollar -> 'DigiDollar <Integration Guide>', localized per locale. Applied to all 35 locale JSON files and 37 index.html fallback texts.
The i18n locales/*.json files are served cache-first by the service worker. Existing mobile clients still saw the old doc-download labels because their cached JSON wasn't refreshed. Bumping the cache name triggers the activate handler to delete old caches, so the next load fetches the rebranded translations.
bastiandriessen
left a comment
bastiandriessen
left a comment
There was a problem hiding this comment.
PR Review (Technical) – Approval
My recommendation: Approve
Overall Assessment
This is a focused, low-risk i18n/labeling change. It standardizes documentation titles across the site with consistent brand prefixes. This change improves clarity. Users can more quickly distinguish between the different guides and white papers.
The re-branding of the documentation labels is clean and consistent:
- Clear product prefixes (DGB / DigiDollar / DigiByte).
- Applied uniformly across Docs section, DevHub, tokenomics CTA, and footer.
- Full i18n coverage including HTML fallbacks.
All 35 locales are updated (both JSON catalogs and HTML fallback text). Keeping the brand names (DGB, DigiDollar, DigiByte) untranslated, while translating the descriptive part is the correct approach. This is the same pattern used by Bitcoin, Ethereum, etc. However, native speakers of the major (non-Latin script) languages (Chinese, Arabic, Japanese etc.) could be asked to spot-check the translated portions of the labels, but definitely not a blocker.
No structural or link changes. Low risk.
Minor subjective note:
“DigiByte Technical Architecture (White Paper)” is a bit long, but it is accurate and consistent with the document’s full name. I think it is acceptable.
Verdict
Approve
Clean, consistent labeling improvement with no technical risk.
Ready to merge from my side.
3 participants
Preview
Live preview of this branch: https://dg-bio.vercel.app/en-us/
Summary
Rebrand the documentation download labels site-wide to consistent, product-prefixed titles.
New labels:
The same brand prefixes are applied to the footer resource links (
Integration→DGB Integration Guide,DigiDollar guide→DigiDollar Integration Guide) and to the tokenomics CTA button + dev-hub link so the terminology is consistent everywhere the same document is referenced.Scope
locales/en.json) and the three English HTML pages (index.html,en/index.html,en-us/index.html)locales/*.jsonfiles<lang>/index.htmlfallback textsNon-English locales use localized equivalents of the branded titles, e.g.:
de:DGB Integrationsleitfaden,DigiByte Technische Architektur (Whitepaper)fr:DGB Guide d'intégration,DigiByte Architecture technique (Livre blanc)ja:DGB 統合ガイド,DigiByte テクニカルアーキテクチャ (ホワイトペーパー)zh:DGB 集成指南,DigiByte 技术架构 (白皮书)ar:DGB دليل التكامل,DigiByte البنية التقنية (الورقة البيضاء)i18n keys touched
downloads.docs.integration.titledownloads.docs.digidollar.titledownloads.docs.digidollarWhitepaper.titledownloads.docs.techArch.titledevhub.link.integration.titletokenomics.cta.techArchfooter.resources.integrationfooter.resources.digidollarfooter.resources.digidollarWhitepaperfooter.resources.techArchCommits
i18n: relabel doc downloads with brand-prefixed titlesi18n: relabel footer Integration / DigiDollar guide to match branded titlesNotes