Overcoming the Challenges of Building and Maintaining Web3 Resource Hubs
Building a platform exclusively dedicated to Web3 content, like web3only I am building, presents its own set of challenges — especially when it comes to maintenance and keeping the platform up-to-date. If the platform doesn’t grow and stay current, it might lose its value over time.
My Head of Design once told me he has personally faced the challenge of manually adding examples to the source hub for internal needs, but he quickly realized that the hub would benefit immensely from contributions by other designers, especially those actively researching for design projects. However, convincing people to make this a habit has been tough.
One way to address this issue could be through better motivation and organization. For example, you can collect all screenshots for new projects in a single Figma file. Each project could have its own tab, organized by category, like on this screenshot (DeFi > Project Abc > Bridge Screens, Swap screens):
Imagine you have a client in the DeFi ecosystem building a dApp for lending money. Your workflow for this client could look like this:
- Search for References: Begin by gathering relevant design examples.
- Organize in Figma: Place all references in a centralized Figma file, e.g. “Web3 Patterns”
- Categorize by DeFi: Under the DeFi tab, create a section named after the client’s brand, e.g., “XYZ.”
- Curate Key Examples: After collecting references for critical user flows, clean up the selection.
- Transfer to Working File: Copy the essential references into your working file specifically for the “XYZ” client.
The remaining examples in the “Web3 Patterns” Figma file stay as a valuable resource for future projects. This approach ensures that our resource hub is continuously updated every time we start a new project.
Advantages:
- Efficiency: Saves time by providing ready access to curated design references, reducing the need to start from scratch with each new client.
- Consistency: Maintains a high standard of design quality by drawing on proven examples.
- Scalability: As more projects are completed, the resource hub becomes increasingly comprehensive, benefiting the entire team.
Just make this Figma file a part of your onboarding process for new designers. It helps them get familiar with high-quality examples from the start, ensuring they have a strong foundation as they begin their projects.
By integrating this practice into the regular workflow — something people are already getting paid for — we’re able to keep the resource hub growing and up-to-date, providing ongoing motivation to contribute. This approach turns a challenge into a sustainable solution that benefits everyone involved.
Also great example of the structure
