This week we have the first homework of DevRel Uni Cohort 6 where we have to make a 30-60-90 day plan as if we had joined the Arbitrum Foundation as a Developer Advocate.

This quarter one of the Foundation's objectives is to increase the adoption of Arbitrum Stylus, where thanks to a WASM VM, you can deploy different languages smart contracts with seamless interoperability with the EVM. You can learn more about it here.

Deep dive into Stylus: Collaborate closely with the engineering team to understand its features and posibilities, know if there are going to be critical changes or updates in the short term and their opinion on key features that are not being used.

Content creation: Develop comprehensive onboarding guides and tutorials on implementing popular ERC standards in C/C++ as they have already done with Rust.

Community engagement: Join developer forums, Discord channels and other social media groups to share resources and start building relationships, ask where we can improve and their needs, gather feedback and knowledge of our products and features.

Internal alignment: Sync with marketing, product and other teams to ensure consistent messaging and set clear KPIs for Stylus adoption, review actual metrics and help set future goals.

SMART goals for this period:

• Achieve full technical proficiency by day 10 thorugh 20 hours of collaboration with the engineering team

• Publish the first tutorial by day 15 and complete 5 guides by day 30

• Join 3 developer communities and contribute meaningful content at least twice a week

• Set clear KPIs with the marketing team by the end of the first week

Advanced tutorials: Building more foundational content, create in depth guides on complex topics, this includes optimization techniques, security best practices and advanced features that are only available within the Stylus framework.

Case studies: Collaborate with early adopters and projects that have successfully implemented Styles to create case studiues. These real world examples will showcase the tangible benefits of Styles. Sharing these stories will provide social proof and inspire other developers to explore the framework.

Interactive Sessions: Host AMA sessions on platforms like X or Discord and participate in podcasts or event talks to engage with a broader audience. These interactive sessions provide opportunities to address common questions, share insights and build a personal connection with the developer community.

Communities collaboration: Partner with various developer communities such as Developer DAO to organize workshops or live sessions to expand our reach.

SMART goals for this period:

• Release 3 in depth guides on complex topics by day 45

• Publish 2 case studies featuring early adopters by day 55

• Host 2 AMA sessions by day 60, each with at least 30 live participants.

• Partner with 2 developer communities to share or create content about Arbitrum Stylus by day 60

Events and workshops: Organize workshops and live coding sessions demonstrating practical applications in Stylus. Focus on hands on learning and real time problem solving, offering more practical value and engage a wider audience.

Community Building: Establish regular meetups featuring guest speakers and project showcases. Implement programs to recognize and reward active community contributors.

Scaling Resources: Expand documentation, create standard libraries for common token standards in Stylus, and translate key resources into multiple languages, explore new ways to create resources based in the feedback collected.

Strategic Partnerships: Partner with educational communities such as Cyfrin to include Stylus in curricula and collaborate with other projects providing teaching materials and guest lectures ensuring the next generation of developers know Stylus.

Measure & Refine: Review KPIs to assess progress and adjust strategies based on our tracking metrics like the number of active developers, engagement levels of our content, attendance at events and community growth indicators.

SMART goals for this period:

• Organize and conduct 2 workshops by day 85

• Host the first meetup by day 80

• Translate key resources into 3 languages by day 90

• Establish partnerships with 2 educational communities by day 90

• Review KPIs at the end of each 30 day period and adjust strategies to ensure goals are met

This 30-60-90 day plan is designed to accelerate the adoption of Arbitrum Stylus by focusing on technical expertise, creating valuable content, and actively engaging with the developer community. By setting specific goals for each phase, we aim to build a strong foundation, enhance resources for developers, and foster lasting relationships within the 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.

This week we have the first homework of DevRel Uni Cohort 6 where we have to make a 30-60-90 day plan as if we had joined the Arbitrum Foundation as a Developer Advocate.

This quarter one of the Foundation's objectives is to increase the adoption of Arbitrum Stylus, where thanks to a WASM VM, you can deploy different languages smart contracts with seamless interoperability with the EVM. You can learn more about it here.

Deep dive into Stylus: Collaborate closely with the engineering team to understand its features and posibilities, know if there are going to be critical changes or updates in the short term and their opinion on key features that are not being used.

Content creation: Develop comprehensive onboarding guides and tutorials on implementing popular ERC standards in C/C++ as they have already done with Rust.

Community engagement: Join developer forums, Discord channels and other social media groups to share resources and start building relationships, ask where we can improve and their needs, gather feedback and knowledge of our products and features.

Internal alignment: Sync with marketing, product and other teams to ensure consistent messaging and set clear KPIs for Stylus adoption, review actual metrics and help set future goals.

SMART goals for this period:

• Achieve full technical proficiency by day 10 thorugh 20 hours of collaboration with the engineering team

• Publish the first tutorial by day 15 and complete 5 guides by day 30

• Join 3 developer communities and contribute meaningful content at least twice a week

• Set clear KPIs with the marketing team by the end of the first week

Advanced tutorials: Building more foundational content, create in depth guides on complex topics, this includes optimization techniques, security best practices and advanced features that are only available within the Stylus framework.

Case studies: Collaborate with early adopters and projects that have successfully implemented Styles to create case studiues. These real world examples will showcase the tangible benefits of Styles. Sharing these stories will provide social proof and inspire other developers to explore the framework.

Interactive Sessions: Host AMA sessions on platforms like X or Discord and participate in podcasts or event talks to engage with a broader audience. These interactive sessions provide opportunities to address common questions, share insights and build a personal connection with the developer community.

Communities collaboration: Partner with various developer communities such as Developer DAO to organize workshops or live sessions to expand our reach.

SMART goals for this period:

• Release 3 in depth guides on complex topics by day 45

• Publish 2 case studies featuring early adopters by day 55

• Host 2 AMA sessions by day 60, each with at least 30 live participants.

• Partner with 2 developer communities to share or create content about Arbitrum Stylus by day 60

Events and workshops: Organize workshops and live coding sessions demonstrating practical applications in Stylus. Focus on hands on learning and real time problem solving, offering more practical value and engage a wider audience.

Community Building: Establish regular meetups featuring guest speakers and project showcases. Implement programs to recognize and reward active community contributors.

Scaling Resources: Expand documentation, create standard libraries for common token standards in Stylus, and translate key resources into multiple languages, explore new ways to create resources based in the feedback collected.

Strategic Partnerships: Partner with educational communities such as Cyfrin to include Stylus in curricula and collaborate with other projects providing teaching materials and guest lectures ensuring the next generation of developers know Stylus.

Measure & Refine: Review KPIs to assess progress and adjust strategies based on our tracking metrics like the number of active developers, engagement levels of our content, attendance at events and community growth indicators.

SMART goals for this period:

• Organize and conduct 2 workshops by day 85

• Host the first meetup by day 80

• Translate key resources into 3 languages by day 90

• Establish partnerships with 2 educational communities by day 90

• Review KPIs at the end of each 30 day period and adjust strategies to ensure goals are met

This 30-60-90 day plan is designed to accelerate the adoption of Arbitrum Stylus by focusing on technical expertise, creating valuable content, and actively engaging with the developer community. By setting specific goals for each phase, we aim to build a strong foundation, enhance resources for developers, and foster lasting relationships within the 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.