GitHub could be considered a “one-stop-development-shop” because it includes version control, project management, and social features that technical communicators can use to manage and document software projects.
Technical communicators need GitHub skills because of GitHub’s popularity — it is reportedly the world’s largest open source community. In addition to the public GitHub, companies are rapidly adopting GitHub Enterprise for internal use.In this presentation, I’ll show you how technical communicators can collaborate and contribute to GitHub in a variety of ways, including writing content and managing issues; commenting on, reviewing, and merging proposed changes; documenting GitHub projects and managing the wiki community.We’ll discuss how opportunities for technical communicators vary by the type of GitHub project (repository) in which you’re working.
–Public repositories – contribute content and comments
–Corporate public projects – project docs, community management
–Corporate GitHub Enterprise projects (and private repositories) – project docs, issue tracking, project version control
GitHub is a place where docs aren’t siloed, so it’s an excellent choice for documentation version control and managing documentation issues. Since version control is GitHub’s trickiest feature, I’ll do a demo and an exercise. I will also provide a number of handy GitHub resources.
About the presenter
Watson Information Developer
Nicky Bleiel is a Watson Information Developer at IBM. She is a Past President and Associate Fellow of STC. Nicky has over 20 years of experience writing and designing content for software products in the cognitive computing, tech pubs, media sales, industrial automation, simulation, and pharmaceutical industries. She is a popular speaker at many conferences, including the STC Summit, WritersUA, tcworld, ProComm and CIDM; and has been published in STC’s Intercom, tcworld magazine, ISTC Communicator, and more. See nickybleiel.com for a list of her talks and publications.