Create tweets for our accounts

[thulieblack]

Create a batch of tweets that will promote and announce v3

[thulieblack]

Before v3 Announcement!

1. Get ready for the most awaited release of the year - v3 of AsyncAPI spec! 🚀 We've got some exciting updates and features in store for you. Stay ahead and anticipate what's coming by checking out our blog post: https://www.asyncapi.com/blog/the-new-era-approaches. Don't miss out! #asyncapiv3 #spec #comingsoon

2. Mark your calendars for December 6! The AsyncAPI 3.0 is about to drop, and it's going to be epic. Get pumped for all the exciting features and improvements we have in store. Get a sneak peek of what's coming for Request and Reply in v3: https://eventstack.tech/posts/asyncapi-v3-request-reply!
   #asyncapiv3 #spec #newrelease

After v3 Announcement

1. Exciting news! 📢 We're thrilled to announce the launch of AsyncAPI v3! 🚀🎉 Join us in celebrating this major milestone for our community. 🥳 Want to learn more? Check out our latest blog post to discover all the details about AsyncAPI v3 and its features. 📚 Don't miss this chance to stay updated and enhance your knowledge. Read the blog post now! 💡 #asyncapi #releaseannouncement

[thulieblack]

cc @fmvilas

[fmvilas]

I'd take a radically different approach:

• I'd take the opportunity to take the audience to YouTube so they can click the "Set reminder" button. This way, they'll get a notification once we're live.
• I'd not share the articles https://www.asyncapi.com/blog/the-new-era-approaches and https://eventstack.tech/posts/asyncapi-v3-request-reply. These are a big spoiler 😄 We can share them later down the track. Like two weeks after the announcement or so, to keep posting about it.
• I'd be consistent with hashtags. For instance: use #AsyncAPIv3, #apis, #eda, and #eventdriven in every tweet. Since Twitter seems to penalize using too many hashtags, I'd stop there.
• The announcement tweet has way too much text. That usually doesn't perform well. Instead, I'd convert the announcement tweet into a thread. The tweet of the announcement could be something like this:

📢 We're thrilled to announce we just released AsyncAPI v3! 🚀🎉

Request/reply, no more publish/subscribe confusion, multiple operations per channel, and more.
[link to announcement blog post or landing page]

That said, I'd follow the approach Astro did to announce their v3. I love it because it's smart: https://twitter.com/astrodotbuild/status/1696170401875853743. This way, a couple of days before the announcement, you already start engaging the community. And, after that, there's a full week of goodies. All in a single thread. If we accumulate all the comments from our community in a single thread, the Twitter algorithm will boost it, making it easier for everyone to learn about all the other tweets of the thread.

As additional goodies for the week(s), we could use:

• Each of the live scheduled streams.
• Each of the podcasts.
• A contest or giveaway.
• New stuff you can do with CLI, Studio, Glee, Modelina, and VS Code extension.
• And to close, we can finish thanking all the contributors that made it happen and a reminder of all the initiatives we're running at AsyncAPI.

What do you think?

[thulieblack]

Before Release

Nov 22

• 📢Mark your calendars! The AsyncAPI 3.0 is launching on December 6. You won't want to miss out on all the exciting new features and improvements we have in store. Stay tuned and set reminders for the live stream. #asyncapiv3 #apis #eda

Week of the Release

4 - 6 December

Monday 4th

• It's Release Week🚀🚀🚀 Stay tuned to our socials for some big news and exciting updates!

🔒Tuesday:🎁 🤔🎁
🔒Wednesday: AsyncAPI v3! 🚀
🔒Thursday: Any guesses on what's coming next? Stay tuned! 😉
🔒Friday: 🏆 🏆
#asyncapiv3 #apis #eda

Tuesday 5th

• It Give Away Time!! Stand a chance to win an exclusive AsyncAPI Swag to celebrate the V3 release. To Enter:
  1. Like and Retweet this post.
  2. Detail the contest details
  3. Use the #asyncapiv3

Winners will be announced during the live stream (following week). #asyncapiv3 #apis #eda

Wednesday 6th

• Today is the D-Day! 🚀 We're dropping AsyncAPI v3.
  Say goodbye to the publish/subscribe confusion and introduce request/reply and multiple operations per channel. Read about it in our latest blog post [link to announcement blog post]. #asyncapiv3 #apis #eventdriven.

Thursday 7th

• Join Alejandra and Ace on the upcoming livestream as we explore the new request/reply feature and demonstrate its functionality with real code examples. Set your reminders, and don't miss out! #asyncapiv3 #apis #eda

Friday 8th

• Happy Friday Folks🚀🚀
  We want to thank all the contributors who made the v3 release possible through their participation! We couldn't have done it without you. {insert a picture of all contributors or make a gif]
  #asyncapiv3 #apis #eventdriven

Hey @fmvilas how is it now?

[fmvilas]

Looks great! Just want to make clear that there will be a full week of live streams the week after so that tweet on Thursday should actually become a bunch of them.

And that said, we should publish more on the first week (like twice what we have so far) and start thinking about the second week. But this is definitely a good start 👍

[thulieblack]

Okay for the second week, it will be easy once we get all the podcasts and blogs ready 😉

[thulieblack]

https://ga-dev-tools.google/campaign-url-builder/

when we start the social posts, blogs, and newsletter

[thulieblack]

Campaign URLs for Release Blog:

Newsletter: https://www.asyncapi.com/blog/release-notes-3.0.0?utm_source=newsletter&utm_medium=email&utm_campaign=v3-release&utm_id=v3-release

Twitter + LinkedIn: https://www.asyncapi.com/blog/release-notes-3.0.0?utm_source=posts&utm_medium=socials&utm_campaign=v3-release&utm_id=v3-release