• Meet individually with members of the team
    • Figure out what mode of communication they prefer
    • Understand their responsibilities
    • Ask them
      • What’s something EdgeDB allows developers to do that they can’t do otherwise?
      • What’s something developers can do better with EdgeDB than any other way?
      • What does success in developer advocacy look like to them?
      • What made you join EdgeDB?
      • Where do we need to improve?
  • Record first video of the NextJS blog app tutorial
    • Distribute internally for review
    • Revise
    • External distribution (YouTube, social)
  • Review analytics on existing content
    • Determine which content is most effective with existing developer community
  • Continue to review existing documentation and guides
    • Fix mistakes
    • Plug holes
  • Farm existing community
    • Compile support FAQs from Discord, reddit
      • Some answers to these may spin off into individual blog posts or videos, or be incorporated into documentation, guides
    • Look for opportunities to interview developers in our community and highlight what they are building
    • Review comments on HN posts
    • Start understanding what gaps the community sees
    • Review existing externally created content on EdgeDB for content opportunities, whether that be video, blog post, or documentation
    • Look for adjacent content ideas (not necessarily about EdgeDB but related or adjacent technologies; meeting developers where they are)
  • Find opportunities to borrow other audiences
    • Guest blog posts
    • Podcast guest appearances