A Good Docs Project community event
Blogathon 2026
Be part of the magic
Join us for a new event we're calling the blogathon. It's like a hackathon, but for doc writers! Three hours to write, network, and spark new ideas about the future of technical writing.
Share your magic with us
Spend three hours with the members of the Good Docs Project in a blog-writing jam session. You'll write and share blog posts exploring a variety of themes about the past, present, and future of documentation. You'll get high quality reviews from members of our project. After the event, we'll publish the blogs throughout the year on our website.
Pick a card to see what's in your future if you join us...
Get published
We'll publish your blog entry on our website! You'll get a byline credit for the blog and we'll include your bio, along with any links to your social media accounts.
Network with us
Meet members of the Good Docs Project! Spark new ideas about the future of technical writing with others. Get one-on-one feedback from experienced writers in our project.
Get swag
Everyone who participates in our event will get swag! Shortly after the event, we'll send you some exclusive, one-time-only swag to say thank you for joining us.
Be part of something new
Be part of a bold, new experiment in open source collaboration! This is the first event of its kind and we think it will be something magical. Help shape this event for the future!
Blogathon 2026 themes
2026 has been a year of transition for anyone passionate about documentation. If you're like us at the Good Docs Project, you're still processing what it all means. And you're not alone. We're all searching for stability and purpose in the middle of this change and churn.
Writers often best make sense of their own thoughts by writing them down. But writing isn't just a solitary activity. We share drafts, gather feedback, and collaborate with others to refine our ideas. Writing is about participating in a conversation bigger than ourselves.
Come be part of that conversation. We've got themes exploring documentation's past, present, and future. We want to hear what you have to say about them.
What makes documentation "good"?
Everyone agrees documentation should be good, but it's sometimes difficult to agree on what that means. Is it something that always stays the same or is it something that changes over time? Which technical writing best practices are staying evergreen and which are evolving?
What shaped you as a writer?
Many of us can point to an experience that changed how we write forever. What was that for you? Share a key moment in your development as a documentation writer when you had a major breakthrough or sudden realization. Tell us what you learned.
Are docs-as-code workflows changing?
The idea behind docs-as-code was to make it easier for developers to participate in docs work. Some devs dive in. Some don't. What actually shapes their level of engagement? Is it time, skill, incentives, team culture, tools? Now that AI can help, is that changing how devs show up for the docs?
Who writes the docs when there's no writer?
Not everyone who writes docs is a writer. Plenty of people end up owning the docs because someone has to, not because it's their job. If that's you, tell us what's that actually like? What helps, what gets in the way, and what do you wish professional technical writers understood, or offered, to make it easier?
Who is the audience for docs?
Writers have always tried to craft docs that meet different user needs. In the past, we had to balance between the sometimes conflicting needs of our end users and our internal stakeholders. Now that we also need to craft docs that AI will consume as well, who are we writing docs for and how does that change what we write?
What is the future of tech writing as a profession?
The tech industry is going through a period of change caused by AI. The job market feels uncertain. What value can technical writers add as documentation changes in the era of AI? How is AI changing how we read and write? How are the new tools and workflows we use to create docs shaping our craft?
Is there a life for docs after publishing?
Publishing can feel like the finish line, but it's often where the real mystery starts. Does anyone find your docs? Read them? Understand them the way you meant? A doc that reads perfectly clear to its writer can land completely differently for its audience. What happens to documentation after it goes live, and how do you actually know if it's working?
Are templates useful with AI-assisted docs?
Here at the Good Docs Project, we make templates to help define the structure and best practices for various types of technical documentation. Sometimes people tell us this work is irrelevant in the era of AI. We don't see things that way, but what do you think? All ideas welcome!
Pitch your own idea!
If you have something you want to explore and it's not on this list of themes, we still want to hear your thoughts. Tell us what's top of mind for you about the past, present, and future of documentation.
Stay in the loop
Want to hear about new blog posts (including yours!), future events, and other Good Docs Project news? We're building an email newsletter. Check back here for a signup soon.
About The Good Docs Project
The Good Docs Project is an open source, volunteer-run community of technical writers from around the world. We are passionate about teaching people how to create high-quality documentation through templates, guides, and hands-on collaboration. We believe good docs shouldn't be a mystery. They're a skill anyone can learn. Our blogathon is one of the ways we bring that community together to write, connect, and celebrate documentation out loud.