Docs beta launch communications plan

[jessicaschilling]

Docs beta launch communications plan

Note: These are taken from the instructions in the IPFS Q4 Comms Plan.

3 weeks before launch (c. 27 Nov)

• Clone and fill in the comms doc template, highlighting the core messages (new interface and nav, improved search, but content on parity with legacy site)
• Share that master comms doc with core WG participants and comms owners
• Start drafting artifacts, with an emphasis on CTAs of contributing content and participating in user research: blog post, Reddit post, HN post, tweets, forum posts, IRC posts, canned responses, important links

1 week before launch (1 Jan)

• Make sure artifacts are complete and in the comms doc: blog post, Reddit post, HN post, tweets, forum posts, IRC posts, canned responses, important links
• Create a PR on the ipfs/blog repo and request review
• Confirm completion or deferral of all items in the barebones beta launch milestone

1 day before launch (7 Jan)

• Double-check all links in blog post and comms doc are correct
• Ensure CTAs are still clear, correct and actionable
• Merge blog PR for automatic CI rollout (double-check the post date first!)
• Merge callouts on legacy site from PR On legacy, adds link to each page's equivalent page on docs beta #384

Launch day (8 Jan)

• Confirm blog post is live
• Send to shipped@
• Share remaining artifacts: Reddit post, HN post, tweets, forum posts, IRC posts

Two weeks following launch

• Monitor response on Reddit, Twitter, HN, forum, IRC and respond accordingly

[jessicaschilling]

Comms plan is here: https://docs.google.com/document/d/16gC5HmP9zzQQR8vNm8baHX6x3nxQ1lallB2kqjzqDAs

We should be good to go until a week before launch -- marking this issue as "review/QA" until then.

[jessicaschilling]

Assigning @johnnymatthews to this issue as well, since he's offered to draw up a mind map of the new/updated content plan that can be used in the blog post (and elsewhere as possible).

[johnnymatthews]

Map should be finished in the next couple of days. There's a lot of figuring out where current posts go, where the holes are, and how to fill them in.

[terichadbourne]

Just popping in to say that this comms plan looks great. ❤️

[jessicaschilling]

@johnnymatthews -- I've moved the mind map into issue #389 since it's maybe a little early-stage for the blog post, but SUPER useful for that issue. Thank you!

[johnnymatthews]

Mind map of the current docs hierarchy and content.

[jessicaschilling]

@johnnymatthews This is awesome! Thanks.

[jessicaschilling]

Update: Remainder of plan will be delayed pending the final outcome of IPFS hosting decisions discussed in design review tomorrow; see #271 for progress on that. However, all the materials in the comms plan are ready to ship as soon as we confirm a ship date for the docs themselves.

[jessicaschilling]

Dates changed to January pending directive given regarding #271.

[jessicaschilling]

Launch complete and all artifacts shared. I have space allocated in my calendar for the next two weeks for monitoring all the channels above, and will comment on this issue if anything relevant needs capturing -- but will close the issue in the interim.