[Informational DIP] digibyte.org Website Redesign 2026 — a growth & developer-acquisition pitch

[DennisPitallano]

Hi DIP editors and community,

I'd like to vet a proposed Informational DIP before opening a PR to the
dips repository, per the DIP 1 workflow.

Live working preview: https://dg-bio.vercel.app/
Click through and run your own Lighthouse audit before reading further —
30 seconds is worth more than 600 lines of mediawiki.

Why this matters (the pitch)

digibyte.org is the single highest-traffic surface the project controls
and the first artefact prospective users, developers, exchanges and
journalists encounter. Today it visually reads as a 2018-era project — a
material drag on every outreach effort, partner conversation and developer
recruitment attempt.

This DIP reframes the site as an active funnel for new community members
and developers, not a static brochure:

• Newcomers see live block height, hashrate and price within the first
  viewport — answering the implicit "is this project still alive?"
  question in the 1–2 seconds before most bounce decisions are made.
• Developers land on a DevHub that links Core, RPC docs, DigiAssets
  and Digi-ID, with copy-pasteable Esplora + Coinpaprika integration
  examples taken straight from the chain dashboard's source.
• Site contributors get a zero-build, MIT-licensed, plain-HTML
  codebase: clone, edit index.html, open in a browser, ship a PR.
  Empirically, lowering this bar is what converts front-end contributors
  into Core contributors over 12–24 months.
• Translators get tools/sync-locales.mjs, which propagates English
  changes across all 35 other locales automatically — no more copy-paste
  tax.
• Partners (exchanges, hardware wallets, journalists) get a site that
  visually matches the calibre of the integrations they're considering.

Suggested success metrics (12-month, open to community ratification)

• +25% unique visitors to digibyte.org
• +50% organic Discord/Telegram joins from web referrals
• ≥10 new external contributors merged into DigiByte-Core/DGBio
• ≥3 new active locale maintainers
• ≥5 developer-facing PRs across the org that cite the site or DevHub
  as the entry point

These numbers are starting points — please push back, raise or lower them
in this thread.

What's actually changing (technical summary)

• Drop the legacy jQuery + 9 plugins stack (≈400 KB) for vanilla ES modules
• Blue-only brand palette (cyan → brand blue → deep blue), dark-only theme
• Canvas-based isometric blockchain hero (cubes, chain links, confirmation
  pulses) with the DGB symbol embedded in ~25% of cubes
• Live chain telemetry from DigiExplorer (Esplora) + Coinpaprika
• Mobile burger menu rewrite, full 36-locale parity, PWA service worker
• Lighthouse: Perf 56→95, A11y 78→86, BP 73→100, SEO 92→100

Updated community links:

• Telegram → t.me/DigiByteCoin
• Discord → dsc.gg/DigiByteDiscord
• DigiStats → digibyte.io

What this DIP deliberately does NOT do

No CMS, no first-party DigiAssets explorer, no web wallet, no analytics
platform change, no backend. Each of those could be a future DIP.

Full draft

docs/dip-pitallano-website-redesign.mediawiki on the
redesign-2026 branch.

Before/after screenshot gallery will follow as a comment on this thread.

Questions for the community

1. Are the suggested 12-month success metrics the right ones?
2. Migrate UA → GA4 as part of this DIP, or leave for a follow-up?
3. Concerns about DigiExplorer or Coinpaprika as data sources?

Thanks for reading — happy to revise based on feedback before opening the PR.

[DGBNOOB]

In my personal opinion, the website’s aesthetics are long overdue for a makeover. I would strongly recommend staying away from reintroducing any third‑party links. DigiByte.org should function as an informational tool that spreads awareness about DigiByte, not as a directory of external services.

In the past, the website hosted third‑party information about social media, wallets, exchanges, and services to help point community members toward the broader DigiByte ecosystem. While that made sense at the time, DIP‑0002 established a clear direction: official communication and documentation should live within the DigiByte‑Core organization, and all third‑party links should be moved to the community section of the GitHub Wiki.

I like the example you provided, but if you want broad community support, it would probably help to present several different UI samples or design variations. I would focus on keeping the new design educational and awareness‑driven, with embedded links that lead directly to DigiByte‑Core repositories — such as DigiByte-Core/digibyte, Issues, Discussions, and the Wiki.

That said, the current GitHub Wiki articles need improvement. When someone visits DigiByte.org and clicks an embedded link to the Wiki, there should be a clear, well‑written source of information that corresponds to the topic they selected. The tabs you added in your example, which take the viewer directly to relevant Wiki pages, are a great step in that direction. I also like the code snippets — they’re inviting and useful for developers who are new to the DigiByte ecosystem.

For broader feedback, I’d recommend sharing this idea across the different sub‑community social media platforms and communication channels. The DigiByte community is growing, and tapping into active community members who are already spreading DigiByte awareness will help gather more perspectives and circulate the idea.

Lastly, I want to acknowledge that you’ve been consistently helping improve DigiByte.org and Digi-ID.io. You’re building amazing tools and solutions with dgbwalletapp and DigiPay, and now you’re contributing to modernizing the website’s aesthetics. Thank you for that. Get comfortable with the different personalities across the sub‑communities, build rapport and relationships, and make yourself at home.

[DennisPitallano]

@DGBNOOB — thank you for the thoughtful review and the kind words. A few
specific responses:

On DIP-0002 alignment

You're right that DIP-0002 is the governing document here. After
re-reading it I'm committing the redesign to the following relocations,
which I'll document in a "Compliance with DIP-0002" section of the DIP
draft:

• Telegram and Discord direct links removed from the homepage and
  relocated to the DigiByte Wiki social-media page, per DIP-0002
  §"Community: Social Media" and §"Community: Telegram".
• Standalone social-media icons (Facebook, LinkedIn, Instagram,
  YouTube, Reddit, Medium, X) — none are in the current draft, and a
  "do not reintroduce" note will go into the contributor docs.
• DigiByte Alliance, DGBAT, Awareness Team, Founder/Creator modules
  — not in the current draft and will not be added.
• Community section replaced with prominent links to:
  • DigiByte-Core GitHub Discussions
• Footer cleaned to point at GitHub + Wiki only for community/contact
  paths.

One general reservation about "everything moves to GitHub / the Wiki"

Before extending the principle further than DIP-0002's text actually
goes, I'd like to flag a UX concern that applies to any category of
content we consider relocating off the homepage:

Non-technical users cannot navigate GitHub or a MediaWiki. For most
newcomers, sending them from digibyte.org →
github.com/DigiByte-Core/... is a four-step funnel:

1. Visit digibyte.org
2. Click out to GitHub or the Wiki
3. Parse a developer-oriented platform / MediaWiki-formatted page
4. Click an outbound link to whatever they actually came for

That's three bounce points, and it sends users who've never used a
version-control platform into a UI built for engineers. Every successful
crypto project keeps newcomer-facing answers — what it is, where to use
it, how to get started — one click from the homepage. Pushing those
answers onto the Wiki would directly work against the
awareness-and-onboarding mission DIP-0002 is trying to strengthen.

This is why I think it matters that DIP-0002's removal scope is specific
and bounded (social media, advocacy groups, duplicate communication
channels, founder modules) rather than a blanket "no third-party links."
The DIP targets fragmented communication and misinformation, not
all external references. Sections that are educational and serve
informed user choice should still be evaluated on a per-section basis,
with the homepage's role as the canonical onboarding surface in mind.

Happy to discuss any specific section the community feels should move,
but I'd like that conversation to be explicit and per-section rather
than a general "all third-party content goes to the Wiki" sweep.

On the Wiki as the destination

Strongly agree the Wiki content is the load-bearing piece of any
"send users to the Wiki" plan. A possible sequencing:

1. This DIP commits to the homepage relocations above.
2. A follow-up effort — separate DIP or coordinated PRs — populates the
   Wiki pages those relocations depend on (social media, community,
   external services).

I'd rather make that dependency explicit than ship a redesign that points
users at thin Wiki pages. Happy to help on the Wiki side too if there's
appetite.

On the other suggestions

• Multiple UI variations — happy to mock 2–3 alternatives once the
  DIP-0002 alignment scope above is settled, so the variations don't
  have to be redone as the scope shrinks.
• Wider community circulation — good call. Could you point me at the
  specific channels you'd recommend? I want to route feedback back to
  this thread rather than fragment it across Telegram, Discord and X.
• Code snippets / Wiki tab deep-links — glad these resonated. I can
  extend the same pattern to more developer-facing topics (RPC,
  Digi-ID auth flow, DigiAssets minting) if there's interest.

Thanks again for engaging with this seriously. I'll update the DIP draft
with the Compliance section and a revised scope, and post a link back
here once it's pushed.

[DGBNOOB]

I’ll start by saying that I’m known to be a bit pedantic, and if I point something out it’s only because that’s how I understand things. If anything I say comes across as pushback, it’s not meant that way. It’s simply to make sure you consider whether a proposal will gain support from the broader developer community. I can comment all day, but I’m not the one who decides whether a DIP gets accepted. And yes, I’m always happy offer my support to help update the GitHub Wiki — I assume that’s what you meant by “appetite.”

I completely understand what you’re saying: only move what DIP‑0002 actually requires, and don’t break onboarding UX.

Non‑technical users can’t navigate GitHub or MediaWiki. Sending newcomers off‑site creates a multi‑step funnel with multiple bounce points. Every successful crypto project keeps onboarding information one click from the homepage. And DIP‑0002 restricts specific things — it’s not a blanket ban on all external links.

However, adding third‑party links to wallets, exchanges, or external services is not in keeping with the DIP‑0002 Abstract or the Rationale as written. Both sections point to a single, unified, authoritative ecosystem centered on DigiByte‑Core GitHub Discussions, the DigiByte‑Core GitHub Wiki, and core development resources. They explicitly reject third‑party social networks, advocacy groups, informational hubs, and reliance on external platforms for authoritative information.

The stated goals are to reduce fragmentation, eliminate misinformation vectors, increase transparency and consistency, strengthen developer focus, and improve quality of life for contributors.

Third‑party services are not authoritative resources. The Abstract says the DIP strengthens focus on “core development and authoritative resources.” Wallets, exchanges, and service providers are not authoritative, not controlled by DigiByte‑Core, not part of the DigiByte‑Core GitHub ecosystem, and not aligned with the “single trusted hub” model. Adding third‑party links to wallets, exchanges, or DigiByte‑supported services is not aligned with the Abstract or the Rationale.

The DIP’s stated end‑state is a clean, unified, GitHub‑centric ecosystem with no external dependencies, no third‑party noise, and no off‑site authoritative pathways.

I think you raise valid concerns, and it may be worth reevaluating the recent changes to see whether improvements can be made to maximize DigiByte.org. I did a quick search to see which successful crypto projects align with DIP‑0002 while also matching the principle that “every successful crypto project keeps newcomer‑facing answers — what it is, where to use it, how to get started — one click from the homepage.” Bitcoin.org is the strongest example that supports your position.

Bitcoin.org demonstrates three principles that DIP‑0002 formalizes:

1. A clean, protocol‑centric homepage. Bitcoin.org focuses on protocol fundamentals — what Bitcoin is, how it works, how to use it, and where to find developer resources. It avoids promoting foundations, alliances, advocacy groups, influencers, or social media channels. This mirrors DIP‑0002’s goal of removing non‑protocol entities from DigiByte.org.
2. One‑click newcomer onboarding. Bitcoin.org keeps all essential newcomer information one click from the homepage. This reinforces that DigiByte.org should keep newcomer‑facing content on the homepage rather than pushing it into the Wiki.
3. A single authoritative ecosystem. Bitcoin.org funnels users into Bitcoin.org documentation, Bitcoin Core resources, and GitHub, while avoiding third‑party “official” communities, services, explorers, or wallets. This aligns with DIP‑0002’s goals of reducing misinformation, reducing fragmentation, strengthening developer focus, and consolidating authoritative resources.

Where Bitcoin.org differs actually strengthens the case for DIP‑0002. Bitcoin.org still includes a curated wallet chooser, a “Buy Bitcoin” page, and some third‑party references. DIP‑0002 is stricter because DigiByte has faced deeper historical fragmentation — too many “official” groups, too many competing channels, and years of misinformation. Bitcoin.org proves the model works; DIP‑0002 simply applies it more rigorously to solve DigiByte‑specific problems.

As for circulating this discussion, you can share it on X, Reddit, Telegram, or the new Facebook page. You can also reach out to community members who actively promote DigiByte; I’m sure they would be willing to support and comment.