GitHub-for-technical-writers-WORKSHOP

Workshop about GitHub focused on content development aspects

Why GitHub?

What are the benefits?

What people use it for?

Who uses it?

The answer is: Everybody, like with Facebook. Except for those geeks that go to GitLab, like Facebook haters go to Google Plus.

What GitHub changed in the IT world?

https://honza.ca/2011/03/7-ways-github-has-changed-the-open-source-world

This post was published exactly when GitHub populatiry started rising. It is still valid. GitHub changed not only developers, but also technical writers lives:

Glossary

GitHub online editing vs. local editing

This workshop is fully based on GitHub functionality to show that Git clients usage is needed only in case of advanced users.

Git is a distributed version control system. In human words: A system that records changes to a file or a set of files over time so that you can recall specific versions later.

No GitHub? Do you use Bitbucket?

Stick to the tool that your team mates use.

Contribution flows

Basic workflow:

  1. Create a repository
  2. Create a ‘feature’ branch from the ‘master’
  3. Make and commit your changes
  4. Open a pull request
  5. Merge the pull request into the ‘master’

Project member:

Project non-member: Fork repo -> Create branch -> Edit -> Commit -> Open pull request

Crowdsourcing

https://kubernetes.io/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/

The edit view looks like this.

Sample contribution that proved that it works: https://github.com/kubernetes-incubator/service-catalog/pull/1878.

Markdown and others

Markdown is a human-readable markup language used to style text on the web

Emoticons: https://gist.github.com/rxaviers/7360908

Other markup languages: https://github.com/github/markup

Ways of documenting projects

GitHub Pages

Free web hosting: https://pages.github.com/

Alternative: