[手动选题][talk]: 20230428.2 ⭐️⭐️ 3 reasons to host a docathon for your open source project.md

sources/talk/20230428.2 ⭐️⭐️ 3 reasons to host a docathon for your open source project.md

@@ -0,0 +1,83 @@
+[#]: subject: "3 reasons to host a docathon for your open source project"
+[#]: via: "https://opensource.com/article/23/4/open-source-docathon"
+[#]: author: "Lydie Modé-Malivert https://opensource.com/users/lmalivert"
+[#]: collector: "lkxed"
+[#]: translator: " "
+[#]: reviewer: " "
+[#]: publisher: " "
+[#]: url: " "
+
+3 reasons to host a docathon for your open source project
+======
+
+Your open source project's documentation is essential to your customers. Your target audience must understand the purpose of your project and how to use it, and documentation is what bridges that gap. A project is rarely ever truly done, so it's equally important for resources to be maintained and updated with your project's continuous improvement.
+
+But what happens when you have lots of documentation to maintain but lack the resources to keep it current? The answer is pretty simple: Host a docathon!
+
+### What is a docathon?
+
+A docathon is like a hackathon. A hackathon is an event where engineers and community leaders gather to improve or add new features to an existing application. In a docathon, the same kind of collaboration focuses on improving documentation.
+
+**[ Learn about writing [Docs as Code][1]. ]**
+
+A docathon can fill gaps within content, restructure large documentation sets, fix broken links, or just correct typos. The intent behind hosting a docathon is to improve a large amount of documentation in a relatively brief timeframe.
+
+Some examples of product documentation include:
+
+- Training manuals
+- User manuals
+- Installation guides
+- Troubleshooting guides
+- Quickstart guides
+- [API][2] documentation
+- Tutorials
+
+At my organization, our documentation team hosted a docathon and successfully revamped a 102-page installation guide. The docathon enabled us to focus on the project's scope, which was reorganizing for simplicity, removing duplicate content, and following the customer journey. Hosting a docathon left a lasting impression on my team and improved customer success.
+
+### 3 things you can achieve with a docathon
+
+Here are my top three reasons to host a docathon:
+
+#### 1. No more backlog
+
+Most documentation must evolve along with the product it supports. As the product changes or updates, so must the documentation. In some cases, documentation teams release new versions of their documentation alongside the engineering team's release cycle. As priorities within a team change and [GA releases][4] continue, documentation teams face the challenge of keeping up with new features, bug fixes, and tasks to complete. The changes that get left behind become part of a backlog—an accumulation of work that needs to be completed at a later time.
+
+> **Docathon tip:**During a docathon, participants can triage backlog items and complete them as they progress through the list. Non-technical participants can work on fixes related to typos, broken links, and other text-related issues.
+
+#### 2. Revamp large-scale guides
+
+By the time your documentation team realizes it's time to revamp a guide, it's probably several chapters in and hundreds of pages deep. Once the content plan has been developed, the complexity of restructuring begins. Restructuring a large amount of documentation is not for the faint of heart.
+
+> **Docathon tip:** Assemble a team to lead the docathon and provide incentives for organization-wide participation from different teams or departments. Depending on the scope of work and time constraints, your team can successfully restructure an entire guide in less time than you probably expect.
+
+#### 3. Collaboration between cross-functional teams
+
+It is common for different groups within an organization to work in isolation. Engineering, product, customer support, marketing, and documentation teams may not collaborate on projects as often as they should.
+
+Imagine hosting an event where each team member can use their expertise to improve product documentation. Docathons foster subject matter expert (SME) diversity, real-time collaboration, and communication. They also allow for an inclusive environment where individuals residing in different geographical locations can participate in person or remotely. Your documentation receives the undivided attention of experts with different viewpoints and specializations, minimizing isolated siloes, unconscious bias, and burnout.
+
+> **Docathon tip:** Enable cross-functional teams to come together for a common cause.
+
+### Documentation marathon
+
+The next time your team has a seemingly insurmountable backlog or is tasked with restructuring a huge documentation project, consider hosting a docathon. It's easy, and its productivity may surprise you. For more information on hosting an event like this, read Tiffany Long's excellent [10-step guide to hosting a hackathon][6].
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/23/4/open-source-docathon
+
+作者：[Lydie Modé-Malivert][a]
+选题：[lkxed][b]
+译者：[译者ID](https://github.com/译者ID)
+校对：[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
+
+[a]: https://opensource.com/users/lmalivert
+[b]: https://github.com/lkxed/
+[1]: https://opensource.com/article/22/10/docs-as-code
+[2]: https://www.redhat.com/en/topics/api/what-are-application-programming-interfaces?intcmp=7013a000002qLH8AAM
+[3]: https://opensource.com/article/23/3/community-documentation
+[4]: https://opensource.com/article/19/7/what-golden-image
+[5]: https://www.redhat.com/en/resources/build-a-resilient-it-culture-ebook?intcmp=7013a000002qLH8AAM
+[6]: https://opensource.com/downloads/hackathon-guide?intcmp=7013a000002qLH8AAM