Radicle Dev Rel Strategy

As we wait for the Drips SDK to be close to completion, Dev Rel’s focus is on creating high quality developer education content on Radicle channels to build developer trust and position Radical as a place for open sourcers to learn and build.

Channels of outreach/content:

Radicle Mirror - https://radicle.mirror.xyz/

Radicle YouTube channel - https://www.youtube.com/channel/UCS_b2Xqb3O_d0kMx-D1amrw

Radicle Twitter Spaces - https://twitter.com/radicle

Each contributor will scope out their content/topics for the next couple of months. Dev Rel should keep a content calendar updated so we space our content and avoid posting repeat content. The content calendar can be found here. This Notion will be dev rel’s home. Here we will track work done, content calendar, hackathon planning, etc.

Dev rel will meet once every other week for a 30 min sync where they can align on Twitter spaces, updating the content calendar, asking questions, etc. The team is distributed globally, and as such, the team should over communicate asynchronously to keep each other informed. These biweekly calls should be used only to have bigger discussions on topics that touch different areas, and are difficult to talk about async.

Hackathons

Getting developers to build on Drips requires having excellent resources readily available to minimize friction so we don’t churn devs. Before we start sponsoring hackathons and set bounties for devs to build with the Drips SDK we should have:

• A written post showing developers exactly how to integrate a dapp with drips
• A video showing developers exactly how to integrate a dapp with drips
• A written post expanding on the use cases of drips - why would you use this over traditional solutions? What benefits are there to using drips? What audience was Drips built for?
• A developer FAQ section to address questions that arise as we attend hackathons

At hackathons, it’s important to have 2 people floating around the hackathon and gathering feedback from developers as they build on drips. The data that we should be collecting:

• What is working?
• What’s not working?
  • Are there certain dependencies that we haven't explicitly called out for developers to install that are causing errors?
  • Is the SDK well-documented or are we getting the same questions over and over again?
  • The SDK is written in TS, is this problematic?
    • We might see that a lot of these devs program in JS, good to keep in mind

Measuring Success

KPIs are a WIP

• Number of pieces of content released