RADIX.wiki is a permissionless knowledge base and community hub for the Radix ecosystem. The organization runs events such as the Radix Wiki Hackathon and the Dapp In A Day workshops, while the site hosts around 250 articles, ecosystem listings, a jobs board, and a talent pool section, all with a view to increasing the 'collision rate' between researchers, founders and contributors to Radix. Since 2022, the site has seen more than 10k visitors from over 100 countries.
How to contribute
There are several ways to contribute to the wiki:
- Apply to one of our Open Positions.
- Edit an article by clicking on the
✏️ Edit / Addbutton above. - Ask questions or make suggestions in the comments section.
- Enquire about sponsorships.
Advantages
- Utility: Knowledge and experience are wasted if they aren’t shared, but a wiki can amplify and focus the collective wisdom, experience, and intelligence of the Radix community, benefitting the whole web3 movement.
- Accessibility: Being spread across multiple locations makes information difficult and slow to find, but a comprehensive wiki can make it easier for community members to find the information they need, whether they are researching a topic or solving a problem.
- Speed: Information on a wiki can be updated within minutes of a new development, giving an immediate benefit to the community.
- Accuracy: Multiple users can contribute and edit content on a wiki, leading to a more comprehensive, balanced, accurate, and up-to-date resource that also reflects the diversity of its contributors.
- Neutrality: Hype can be off-putting for newcomers, but a neutral voice helps people to view information about Radix objectively.
- Simplicity: A user-friendly interface makes it easy for anyone to contribute to Radix, no matter how small.
- Version control: The ability to roll back changes makes it easy to correct mistakes.
- Collaboration: Bringing knowledge and creators together in one place increases the collision rate of the community, leading to more projects and shared endeavors that will compound for Radix over the coming weeks and months.
Disadvantages
- Quality control: Since anyone can contribute and edit content on a wiki, it can be difficult to ensure that the information is accurate and reliable.
- Vandalism: Because anyone can edit a wiki, it is vulnerable to vandalism and sabotage by malicious users.
- Ownership: Since the information is contributed by multiple users, there can be issues with ownership and authorship. It can be difficult to determine who should get credit for a particular contribution or how to resolve disputes between contributors.
Roadmap
Just as Wikipedia is the municipal center of the internet, our vision is to be the same for Web3, assuming that Radix will be its substrate. To this end, our next major milestone is to upgrade to a fully native web3 application that will combine the power of Radix with a user-friendly wiki system. Moving away from Notion as a backend will allow for a much broader range of content types, while integrating Radix components will enable new features, such as:
- Decentralized content creation.
- Community governance and treasury management.
- Contributor rewards.
- Integrations with other Radix projects.
- Token-gated content.
- On-ledger storage.
Techical Features
Key technical features of the application include:
- Decentralized authentication using ROLA.
- Dynamic content management through a headless CMS (Directus).
- Responsive and modular page layouts.
- Efficient search functionality.
- Integration with Radix DApp toolkit for seamless onchain interactions.
Technical Description
- Frontend:
- Next.js for server-side rendering, static site generation, and client-side navigation.
- Tailwind for responsive and customizable CSS.
- Backend:
- Directus as a headless Content Management System.
- Authentication:
- Radix DApp Toolkit for wallet-based authentication.
- Custom backend route (/api/auth/radix) for verifying signed challenges and creating/authenticating users in Directus.
This technical stack will allow the wiki to be highly performant, scalable, and extensible.