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.
As noted in the session abstract, tech comms need GitHub skills because of the popularity of GitHub -- it is reportedly the world's largest open source community, and in addition to public GitHub, companies are rapidly adopting GitHub Enterprise for internal use.
In this workshop, we'll learn how technical communicators can collaborate and contribute in 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 tech comms vary by the type of GitHub project (repository) you are working in, for example:
–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 also an excellent choice for version control of documentation files and management of documentation issues because docs aren't siloed it GitHub. We'll talk about these features and I'll do a demo and an exercise, since version control is GitHub's trickiest feature.
This workshop will include demos and interactive exercises. I will also provide a number of handy GitHub resources.Additional rates apply for this preconference workshop.