![]() Enabling different workflows keeps everything organized and on track.Īdditionally, labels can be added to issues, so it’s easy to know at a glance which features an issue is tracking and what it needs from the team. For each launch, we may need to create more than 50 new articles (while a normal day may involve 15 to 20 pull requests and several updates). This is especially lifesaving for launches. These workflows (we use both GitHub Actions workflows and built-in workflows) allow us to accurately capture all that’s needed. This adds complexity for our team when it comes to management.īut GitHub Projects makes the complexity a breeze by enabling different types of workflows. ![]() Additionally, different articles have different internal conditionals, where a single paragraph or even a word may be relevant in some versions but not others. ![]() Some articles are available in all versions, some are -only, while others are GitHub Enterprise Server-only. Workflows for the winĪs you might imagine, Docs articles involve quite a bit of versioning. We use it to track our biweekly work cycles, prioritize and plan work, make work visible across the organization, triage issues, and manage releases. Fortunately, GitHub Projects works beautifully. For such a diverse team working on such an expansive initiative, having a robust project management tool is mandatory. Our 42-person Docs team is fully remote and spans the globe, with members in North America, Australia, Europe, and Africa. ![]() To that end, let’s explore why and how our Docs team uses GitHub Projects to manage their 2,396 open source Docs articles (or 18,545 articles when counting all languages and versions)-which get 900,000+ daily pageviews by 350,000+ daily users. Here at GitHub, we’re committed to helping organizations supercharge productivity and innovation. Whether it’s a student who wants to sign up for an account or a seasoned senior developer who needs to set up GitHub Enterprise Server, Docs meets each person where they are and in the language they speak (and code in, too). If that’s the case, then GitHub Docs are love letters to our 100 million developers who turn to them everyday for help and support. It’s been said that documentation is like a love letter to your future self. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |