Hey All - As we’d posted to the original WFC back in early April, which had kicked off the open sourcing of the website’s source code, I wanted to just cross-post how folks can submit requests! Moving forward, if you’d like to contribute to performance improvements, security optimizations, or bug fixes, please feel free to submit PRs to this Github repo: https://github.com/Distractive/polkadotcom.
For contributions around brand elements, product messaging, or design, there will be stricter controls–but you can still open an issue with your suggestions or questions here: https://github.com/Distractive/polkadotcom/issues.
Review process
Our team strives to provide thorough reviews of all community contributions and will reply as quickly as schedules allow (Over the first ~6 weeks, we’ve been able to review within 48 hours of submission).
In the case of requested changes, we ask contributors to address feedback within two weeks to keep the review process active. PRs that remain inactive for more than two weeks may be closed to maintain a clean project board.
Please note that review times may be extended during major releases, holiday periods, or times of high submission volume. For urgent security-related PRs, mark them clearly in the description—we’ll prioritize them accordingly.
If you’ve got any questions, please don’t hesitate to reach out to digital@distractive.xyz
Nate (for the Distractive Crew)
2 Likes
Hello @NateHam1, thanks a lot for sharing this and for open-sourcing the site it’s a great step toward broader community collaboration.
That said, I wanted to raise a small structural concern from a contributor’s perspective:
Given that the Polkadot website (polkadot.network) is the official public-facing portal for the ecosystem, wouldn’t it make more sense for the canonical repository to be hosted under the @w3f GitHub organization, rather than under Distractive’s personal namespace?
This would:
- Better reflect the site’s status as the official communication channel of the Polkadot project,
- Improve discoverability and trust for external contributors,
- Align the repo with the rest of the ecosystem’s governance structure (Parity for core tech, W3F for coordination).
Of course, Distractive can still maintain ownership via permissions, and possibly use a mirror or fork on your org’s GitHub for internal workflows but hosting the primary repo under w3f/ would provide clearer institutional framing.
Totally open to your view on this just wanted to raise it as part of the broader reflection on ecosystem transparency and structure.
Thanks again for your work and openness!
2 Likes
Hey! Thanks so much for the kind words, and I’m happy to answer your questions. Since Polkadot is decentralized, there are many teams now contributing to Polkadot. We’re currently tasked with managing and maintaining the site, which is why it lives in a Distractive repo, but if/when these responsibilities are handed off to another team, we can move it. 100% true that the majority of things have fallen under Parity and W3F historically, but this will continue to change and evolve as the ecosystem further decentralizes.
2 Likes