The Arbitrum Foundation's Developer Relations (DevRel) team has made great strides in supporting developers. Focusing on educational resources and fostering innovation through programs. With the introduction of Stylus, which expands the Arbitrum ecosystem beyond Solidity, the team has strengthened its role in helping developers create more advanced apps.

In DevRelUni cohort 6 we have been asked to imagine joining Arbitrum as DevRel, we have been asked to review existing educational materials for Arbitrum and Stylus, and then propose five new resources that would complement what is currently available.

1. Localized Content for Non-English Speakers

Why It’s Needed: When I started learning programming I barely understood a tutorial in English, now Stylus opens the doors of development to many developers who only know common programming languages and unfortunately have not had the ability to learn English. Localized content in languages such as Spanish, Mandarin, Portuguese, and Hindi would make the ecosystem more accessible and inclusive

Expected Impact: Localized resources would attract a more diverse global developer base, promoting inclusivity and speeding up the adoption of Arbitrum and Stylus technologies across different regions. This ensures that language is not a limiting factor in engaging with the platform.

2. Unique Stylus Use Cases (e.g., a Regex Engine)

Why It’s Needed: Stylus stands out for its ability to support non Solidity languages and handle more complex logic. However, the current lack of real world examples showing Stylus unique advantages limits its appeal. Tutorials or sample projects, such as an onchain regex engine, could effectively highlight its capabilities.

Expected Impact: Showcasing Stylus specific features through innovative examples would inspire developers to explore and experiment with the platform. This would lead to more creative and advanced projects, showing why Stylus is a valuable addition to the Arbitrum ecosystem.

3. Community Incentive Program for Content Creation

Why It’s Needed: While existing documentation and tutorials are helpful, community-generated content provides fresh perspectives and encourages p2p learning. An incentive program that rewards technical blog posts, video tutorials, open source code samples, and other educational materials could drive consistent contributions.

Expected Impact: Community created content would quickly expand the knowledge base and keep it up to date. As developers share tips, experiences, and best practices, the overall quality and quantity of resources improve. This initiative would make onboarding easier and create a sense of shared ownership within the community.

4. A Centralized Stylus Portal for All Resources and Documentation

Why It’s Needed: Stylus related resources including documentation, tutorials, sample code, and community contributions are currently scattered across various platforms. A centralized portal would serve as a comprehensive hub for all Stylus materials, simplifying access and navigation.

Expected Impact: A well organized Stylus portal would streamline the developer experience, reduce time spent searching for information, and improve productivity. It would provide a clear learning path for newcomers and a reliable reference for experienced developers, fostering long-term engagement and satisfaction.

5. Advent of Code for Stylus

Why It’s Needed: Hands on coding challenges are a fun and effective way to learn new technologies. A Stylus focused Advent of Code, featuring daily or weekly challenges would provide practical experience with Stylus unique features while encouraging consistent learning.

Expected Impact: This interactive approach to learning would motivate developers to practice regularly, try new ideas, and engage creatively with the platform. Friendly competition within the community would strengthen bonds and generate a collection of innovative solutions, making it a tradition that attracts both new and experienced developers.

Conclusion

The Arbitrum Foundation’s DevRel team has already set a high standard for community engagement and education. By introducing these additional resources, the team can further improve developer support, accessibility, and innovation. Localized content, real world Stylus use cases, community incentives, a centralized resource portal, and hands on coding challenges would collectively address existing gaps and build a skilled developer community.

Thank you for reading. If you have any questions or recommendations, please feel free to contact me. You can connect with me on X / Twitter or LinkedIn.

The Arbitrum Foundation's Developer Relations (DevRel) team has made great strides in supporting developers. Focusing on educational resources and fostering innovation through programs. With the introduction of Stylus, which expands the Arbitrum ecosystem beyond Solidity, the team has strengthened its role in helping developers create more advanced apps.

In DevRelUni cohort 6 we have been asked to imagine joining Arbitrum as DevRel, we have been asked to review existing educational materials for Arbitrum and Stylus, and then propose five new resources that would complement what is currently available.

1. Localized Content for Non-English Speakers

Why It’s Needed: When I started learning programming I barely understood a tutorial in English, now Stylus opens the doors of development to many developers who only know common programming languages and unfortunately have not had the ability to learn English. Localized content in languages such as Spanish, Mandarin, Portuguese, and Hindi would make the ecosystem more accessible and inclusive

Expected Impact: Localized resources would attract a more diverse global developer base, promoting inclusivity and speeding up the adoption of Arbitrum and Stylus technologies across different regions. This ensures that language is not a limiting factor in engaging with the platform.

2. Unique Stylus Use Cases (e.g., a Regex Engine)

Why It’s Needed: Stylus stands out for its ability to support non Solidity languages and handle more complex logic. However, the current lack of real world examples showing Stylus unique advantages limits its appeal. Tutorials or sample projects, such as an onchain regex engine, could effectively highlight its capabilities.

Expected Impact: Showcasing Stylus specific features through innovative examples would inspire developers to explore and experiment with the platform. This would lead to more creative and advanced projects, showing why Stylus is a valuable addition to the Arbitrum ecosystem.

3. Community Incentive Program for Content Creation

Why It’s Needed: While existing documentation and tutorials are helpful, community-generated content provides fresh perspectives and encourages p2p learning. An incentive program that rewards technical blog posts, video tutorials, open source code samples, and other educational materials could drive consistent contributions.

Expected Impact: Community created content would quickly expand the knowledge base and keep it up to date. As developers share tips, experiences, and best practices, the overall quality and quantity of resources improve. This initiative would make onboarding easier and create a sense of shared ownership within the community.

4. A Centralized Stylus Portal for All Resources and Documentation

Why It’s Needed: Stylus related resources including documentation, tutorials, sample code, and community contributions are currently scattered across various platforms. A centralized portal would serve as a comprehensive hub for all Stylus materials, simplifying access and navigation.

Expected Impact: A well organized Stylus portal would streamline the developer experience, reduce time spent searching for information, and improve productivity. It would provide a clear learning path for newcomers and a reliable reference for experienced developers, fostering long-term engagement and satisfaction.

5. Advent of Code for Stylus

Why It’s Needed: Hands on coding challenges are a fun and effective way to learn new technologies. A Stylus focused Advent of Code, featuring daily or weekly challenges would provide practical experience with Stylus unique features while encouraging consistent learning.

Expected Impact: This interactive approach to learning would motivate developers to practice regularly, try new ideas, and engage creatively with the platform. Friendly competition within the community would strengthen bonds and generate a collection of innovative solutions, making it a tradition that attracts both new and experienced developers.

Conclusion

The Arbitrum Foundation’s DevRel team has already set a high standard for community engagement and education. By introducing these additional resources, the team can further improve developer support, accessibility, and innovation. Localized content, real world Stylus use cases, community incentives, a centralized resource portal, and hands on coding challenges would collectively address existing gaps and build a skilled developer community.

Thank you for reading. If you have any questions or recommendations, please feel free to contact me. You can connect with me on X / Twitter or LinkedIn.