Playbook is a modern documentation platform that eliminates technical hurdles, making it easy to create, manage, and publish beautiful docs. Focus on writing great content while Playbook handles hosting, deployment, and infrastructure automatically.
Replies
Best
Playbook streamlines documentation and lets me focus on what matters - creating great content.
congrats on the launch PD! The page looks very nice and clean! May I learn for a starter like me, how you differentiate yourself with notion? Thank you!
Playbook looks like a seriously thoughtful solution to a longstanding pain point. The “docs always come last” problem is real, and you’ve nailed why — tooling either scares off non-devs or slows down devs. Playbook seems like it finally hits the sweet spot.
Some things I love:
✅ GitHub sync + in-app editing – best of both worlds
✅ LLM draft assist – huge time-saver for solo builders and small teams
✅ Clean, professional themes out of the box – credibility boost FTW
✅ Living changelogs – underrated feature that keeps users engaged
Report
Unfortunately, I'm trying to sign up with Google, but I'm getting this message: Access blocked: Balance can only be used within its organization.
@adigold1 hey sorry about that. Just pushed a fix for this.
Report
Awesome product! Wasn’t prepared for the landing, it took me a few seconds to understand: this is the actual product.
Awesome job @pd2905
Report
Love the focus on simplicity and clean infrastructure. Creating great documentation shouldn’t require dev resources or deployment headaches, and this looks like a great step in that direction. Excited to see how it helps teams ship better docs faster!
Report
💡 Bright idea
Playbook looks great, the integration with GitHub is great in that we would not have to move outside GitHub to edit the documentation. Biggest question I have is if the published site can be "private" requiring username & password and possibly MFA to access the documentation?
@stuartxt great question. This is not supported out of the box but I've definitely been thinking about something like private docs. There's are some great use cases like internal company handbook, runbooks, private APIs, ebooks, etc. Are you looking for something specific?
Report
@pd2905 Specifically looking to protect internal documentation. I could consider integrating Auth0 if you have the ability to inject custom js in the same way as MkDocs
Replies
Balance
With custom code, you can use analytics tools like @Plausible Analytics or @Fathom Analytics to inject the snippet right into your site.
Currents AI
Elisi : AI-powered Goal Management App
Congrats on your first launch, PD! 🎉
Playbook looks like a seriously thoughtful solution to a longstanding pain point. The “docs always come last” problem is real, and you’ve nailed why — tooling either scares off non-devs or slows down devs. Playbook seems like it finally hits the sweet spot.
Some things I love:
✅ GitHub sync + in-app editing – best of both worlds
✅ LLM draft assist – huge time-saver for solo builders and small teams
✅ Clean, professional themes out of the box – credibility boost FTW
✅ Living changelogs – underrated feature that keeps users engaged
Unfortunately, I'm trying to sign up with Google, but I'm getting this message: Access blocked: Balance can only be used within its organization.
Balance
@adigold1 hey sorry about that. Just pushed a fix for this.
Love the focus on simplicity and clean infrastructure. Creating great documentation shouldn’t require dev resources or deployment headaches, and this looks like a great step in that direction. Excited to see how it helps teams ship better docs faster!
Playbook looks great, the integration with GitHub is great in that we would not have to move outside GitHub to edit the documentation.
Biggest question I have is if the published site can be "private" requiring username & password and possibly MFA to access the documentation?
Balance
@stuartxt great question. This is not supported out of the box but I've definitely been thinking about something like private docs. There's are some great use cases like internal company handbook, runbooks, private APIs, ebooks, etc. Are you looking for something specific?
@pd2905 Specifically looking to protect internal documentation.
I could consider integrating Auth0 if you have the ability to inject custom js in the same way as MkDocs