Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog posts for demo and AMA announcements + AMA moderation #118

Open
16 of 38 tasks
ninabreznik opened this issue Jul 9, 2023 · 6 comments
Open
16 of 38 tasks

Blog posts for demo and AMA announcements + AMA moderation #118

ninabreznik opened this issue Jul 9, 2023 · 6 comments

Comments

@ninabreznik
Copy link
Member

ninabreznik commented Jul 9, 2023

@TODO

  • STARTING: week 1 of September 2023

  • write and design demo & AMA session announcements (Diego & Nina)

    • create custom intro video for each demo (Nina)
      • PicoStack
    • add intro and outro to the existing demos (reuse outro from the interviews or make new) (Nina)
      • PicoStack
    • publish finished demo videos to the Dat ecosystem Youtube channel (Diego)
      • upload videos (Nina)
        • PicoStack
      • add Youtube thumbnail image (custom for each demo, but same style - see Interview series thumbnails
      • add the description
        • video summary (use Merlin extension to generate one)
        • project links (copy from the interview description + add demo specific links)
        • dat ecosystem text and links (copy from interview description and adapt to demos)
      • create a template for demo blog posts (Diego)
        • select graphic elements that can be customized (added projects logo etc.)
          • for interviews we selected a big logo and a robot and added logo for each project
          • for demo templates we could select one scientists and add logo to the dat logo they are holding + a standing robot and add project logo instead of that dat logo (see assets)
        • add a clickable preview image for the video or import youtube directly to the page
        • decide how to structure the text so all demo posts feel similar
      • write the post for each demo and customize the template design for it (Diego)
        • choose the style (for the interviews we played with Hichikers guide to the galaxy style, maybe we can keep that or go with Rick and Morty style or just plain style, you can use chat cpt to get some version in that style and then choose best parts out)
        • to the text add the invitation to the AMA session and share a link to the issue for this AMA and ask people to submit questions for the AMA
        • don't forget to fill out the front-matter section so we have cover etc. for the socials
        • we could publish on Friday and make an AMA on Sunday? Or we publish on Tuesday and make an AMA on Friday?
  • moderate AMA sessions (Diego)

    • make a plan to organize these comm comm AMA sessions every 2 weeks(one week we post a blog and make a AMA 3 days after + week after we post a thank you with notes => then rinseand repeat for the next demo)
    • contact each project founder who did the demo and ask them whih week they would have time + ask them to invite people from their community to join
    • prepare questions for each session
    • invite dat ecosystem members personally so we make sure we have at least 5 participants on the call
    • make notes of each session
    • let's use Keet or https://meet.jit.si/dat-ecosystem
    • we can start each AMA with playing the demo recording first OR if the project maintainer decides, they can do a new live demo again
    • after the demo we have questions time (to warm people up, we have some questions ready and then hopefully others will join and ask too)
  • announce (Diego)

    • create a github post event (under comm comm)
    • create also Discord event and link to GH
    • publish blog post 3 days before the event + on the day of AMA
    • publish a new blog post after (reusing the custom design for that project):
      • notes from the ama + a little thanks for attending & invite to the next one after te event
      • publish to all the channels listed under each Interview blog post (discord/cabal, mastodon, twitter etc) because people are on different channels and might not see it + consortium email

## Info

Budget:

  • $120 per announcement + demo video preparation
  • $100 per AMA session moderation & communication and publishing to the social media
@ninabreznik ninabreznik changed the title Blog posts for demo announcements & 10 year anniversary Blog posts for demo and AMA announcements + AMA moderation Jul 9, 2023
@ninabreznik ninabreznik moved this from To Do to In Progress in Communication & Engagement Jul 9, 2023
@ninabreznik ninabreznik moved this from In Progress to To Do in Communication & Engagement Jul 9, 2023
@dpaez
Copy link
Contributor

dpaez commented Oct 6, 2023

Personal Update Progress - October, 6th 2023

Articles (demo sessions / 60 usd each):

  • PicoStack
  • HOP Protocol
  • Sher
  • Agregore

AMA Sessions (100 usd each):

  • PicoStack
  • HOP Protocol
  • Sher
  • Agregore

@ninabreznik
Copy link
Member Author

ninabreznik commented Oct 6, 2023

Videos (60 usd per video)

  • create intros and outros

  • add them to the demo videos

  • upload videos to youtube

  • PicoStack

  • HOP Protocol

  • Sher

  • Agregore

@dpaez
Copy link
Contributor

dpaez commented Oct 28, 2023

Update Progress - October, 28th 2023

Articles (demo sessions / 60 usd each):

  • Cabal

AMA Sessions (100 usd each):

  • Cabal

@dpaez
Copy link
Contributor

dpaez commented Dec 3, 2023

Update Progress - Decemeber, 3rd 2023

Articles (demo sessions / 60 usd each):

  • Dcent Reads

@dpaez
Copy link
Contributor

dpaez commented Dec 18, 2023

Update Progress - December, 18 2023

Articles (demo sessions / 60 usd each):

  • Āhau

@ninabreznik ninabreznik moved this from To Do to In Progress in Communication & Engagement Jan 21, 2024
@ninabreznik
Copy link
Member Author

Update Progress - January 27 2024

Articles (demo sessions / 60 usd each):

  • Keet

Videos (60 usd per video)

  • Keet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants