TLDR: The current Radix developer docs are fragmented across 6+ domains. Iāve run 8 workshops onboarding developers to Radix and maintained RADIX.wiki since 2022. Iām offering to host all documentation for free on a Wikipedia-style platform where anyone can contribute and earn points for keeping it current.
The site is live at radix.wiki
Introduction
The existing developer documentation for Radix is fragmented across docs.radixdlt.com, developers.radixdlt.com, academy.radixdlt.com, learn.radixdlt.com, radix-engine-docs.radixdlt.com, radix-core-api.redoc.ly and Github. This architecture and the tendency of documentation to become quickly outdated has made developer onboarding much less efficient than it could have been.
My conviction is that developers are the primary customers of digital ledgers so in 2024 I organized the Radix Wiki Hackathon (radixdlt.com/blog/the-radix-wiki-hackathon) and have run eight āDappInADayā (radix.wiki/contents/history) workshops at London universities since then.
In planning those events I found it useful to create a Developer Resources (radix.wiki/contents/resources/radix-developer-resources) page on RADIX.wiki that the students could use as a reference in preparation for and during the events.
Now, with the Radix Foundation dissolving, there is an opportunity to rationalize and improve the entire documentation and onboarding flow for the hordes of developers weāre expecting to descent on Xiāan. My proposal is to host that documentation on RADIX.wiki - a site that Iāve maintained since 2022.
I built the wiki around July 2022 and received a Dandelion grant (radixdlt.com/blog/dandelions-program-update) to develop it in October of that year. My main rationale was that the only proven model for maintaining knowledge bases of this magnitude is distributed contribution with low friction, i.e. the Wikipedia approach. A comprehensive, up-to-date documentation of the Radix ecosystem can only be successful at scale with a Wikipedia-style knowledge base that anyone could contribute to.
Not being a developer, I wasnāt able to develop the site as a Radix-native app, but with the advancements in AI Iāve finally been able to build what I originally envisioned. The staging site is radix-wiki.vercel.app and once thereās parity Iāll move it to RADIX.wiki.
Iāve started to sketch out the developer docs here: radix.wiki/developers
The Offer
Iāll host the documentation indefinitely, at no cost to the community. Iāve been following Radix since 2017 and Iām building caper.network on Radix so Iām not going anywhere. I also have a vision to host more workshops and build an ETH Global / Superteam for Radix so itās in my interest to make sure the documentation is accurate and effective.
RADIX.wiki already has the infrastructure, the domain, and a track record of continuous operation. There are no hosting fees or grants needed. The documentation simply needs a home and community buy-in.
The question of redirects from the existing documentation is up for debate but Iād argue that the current structure is such a mess that it would be better to add a blanket redirect rather than invest a lot of time and effort to preserve individual links.
Functionality
The wiki platform is designed to be as decentralized as possible. Users connect their Radix wallet to create and edit wiki pages organized in a hierarchical tag system. The app features a block-based content editor with support for rich text, code blocks with syntax highlighting, tables, tabs, YouTube/iframe embeds, and image uploads. Pages support revision history, threaded discussions, and user reputation scoring. Certain actions require minimum XRD token balances, creating an quasi-economic moderation system. Community members automatically get personal profile pages, and the platform tracks contribution statistics including pages created, edits made, and account age. Eventually Iāll work out a way of backing everything up to the Radix ledger or even hosting it on an RNS domain.
Postscript - Governance & Long Term
Iāve always planned on governing the wiki as a DAO on Caper with its own governance token. I also plan to honor the idea I sketched out here: t.me/EasyMoonDiscussion/5142, meaning that $EMOON will be exchangeable for the new governance token.
Contributors currently earn points for maintaining and improving the documentation. These points recognize effort and create accountability, which aligns incentives: people who use the documentation have a direct path to improving it and being recognized for that work.
The long-term objective of the DAO will be to raise its own funding on the Caper platform and thereafter run as a profitable entity so that it never has to seek external funding. A future Radix Global is part of that vision but any future plans will be decided by the DAO members and is beyond the scope of this immediate proposal.
Why Not Github?
So many reasonsā¦
Not Radix native.
Not suitable for illustrated or interactive tutorials.
Unsuitable for beginners.
Even Dan Robinson (
x.com/danrobinson/status/2006684676291965094) finds it too complicated.Horrible UIX.
Limited embedding.
Canāt be governed as a DAO.
What We Need From the Community
Consensus that community-maintained documentation is preferable to abandoned official documentation.
Content access to existing documentation sources (or permission to scrape/migrate).
Contributors willing to help with the initial migration and ongoing maintenance.
Conclusion
Poor documentation does more harm than good.
RADIX.wiki was created for this situation. The infrastructure exists. The commitment exists. The model is proven across thousands of successful wikis.
Letās give Radix documentation a permanent, community-owned home.
Connect your wallet to join the discussion.