Looks good as a concept, I love version control in Git and having that focus in documentation is good.
I'm worried that the way the content is written feels "clunky" - Almost like reading a technical manual when I buy a new gadget, feels like work instead of a joy to read.
https://askalmanac.com/articles/649/product-launch-playbook
So whilst the content is correct it feels a bit lifeless, also whilst some words are heavily explained, other terms for a newbie are just thrown in.
"Defining “too much” depends on the size of your team and your sprint size"
Sprint size? What is a sprint? We've not covered sprints previously.
Same with MVP - You assume that the brand new person to product launch has heard the term, minimum viable product, what about most valuable player.
So whilst anything is better then Confluence, I'm worried about the type of content and the style that it is written in.
I do deep dive to learn content, when I compare the product launch handbook to something like this: https://medium.com/@bweinstein/moving-beyond-the-net-promoter-score-9b560f3767ba - It feels so much better.
Maybe instead of just focusing on technical accuracy, can you also look at the content being engaging - https://askalmanac.com/articles/199/how-to-hold-a-weekly-sales-review-meeting
"If you remember nothing else" - What is listed there genuinely feels like "how to sales for dummies" which is fine if you want a basic, boring sales team.
So in summary, I'm very confused by what this is trying to do - It is possible to do content that is technically correct AND engaging AND of a quality that moves teams from "ok" to "excellent" performance. - Compare it with content just on Reddit or Medium. Tech's top wisdom?....Whilst the content is correct is it really that good? Hard to say...
Only 3 free articles without an account? Tsk tsk, give us more :) - Maybe have a call to action script with a timer, only get X more free articles, sign up.