This is the repository for the AMC Github workshop website.

A repository is a collection of files (web pages, images, code, etc) used for a project. Often it is all the non-secret files in a project -- so everything but passwords or secret keys. (This project doesn't have any secrets so everything is here!)

There are a few ways you can contribute. You will need to be logged in to your Github account to do any of these.

See a problem? Think something could be better? Create an issue!

1. Go to the Issues.
2. Click "New Issue".
3. Write your problem or idea.
4. Click "Submit new issue".

More information about issues:

• Mastering Issues
• Writing Useful Github Issues
• How one team (Wiredcraft) uses issues

Want to fix or add something?

1. "Fork" the repository by clicking "Fork" in the upper right hand corner. This will create a copy of the repository in your Github account.
2. Make changes to your fork. If you are using only Github, edit files or create new files on the Github website and commit your changes to your fork.
3. Create a pull request on the repository that you forked from (the original repository!).
   1. Click "New pull request".
   2. You want to do a pull request between forks (different repositories), so click "compare across forks". The "base fork" is the repository that you want to add changes to; the "head fork" is the one that's yours and contains the changes. Select your fork from the dropdown.
   3. Look at the changes you've made -- the "diff". The left side is the original. The right side is your version. The diff only shows the parts that have changes. Things you've added are in green, things you've deleted are red.
   4. Click the green "Create pull request" button.
   5. Write a description of your changes and why you made them.
   6. Click "Create pull request".

We will review your pull request and, unless your changes are wantonly destructive, merge it into the project! We may need ask questions or make changes first though. You can reply to questions or comments on the pull request page.

• Create a file called "{your name}.md" in the "markdown" directory. For example, I created "libby.md". Then write down your thoughts about this workshop, Allied Media Conference, or life in general! Use Markdown to format your page with headings, links, or lists.
• Correct grammer, or, spelling mistaeks
• Write a better explanation of something or make an explanation clearer
• Add more information or additional links to your favorite resources.
• Correct an explanation that is just plain wrong!
• If you know CSS (Cascading Style Sheets), you can edit the style sheets and make the site look different.
• If you know HTML, you can create or edit HTML files, including the templates in "markdown/templates".
• If you know the programming language Haskell, you can edit the static site generator.

• How to Win Friends and Make Pull Requests on Github
• Of Github and Pull Requests -- a comic and notes about contributing to open source projects by Rachel Nabors
• more

We didn't have time to git into learning git itself. (Feel free to make an issue demanding that hideous pun be removed!!)

As great as Github is, you can't do everything with it. You can't create a new repository or merge conflicting pull requests, among other things. If you are interested in working in open source software and/or learning to code, it is well worth your time to master the git command line tool or a git GUI (graphical user interface).

Here are some tutorials:

• Open Hatch
• Try Git
• more

We encourage you to practice your git skills by working with this repository. Don't worry about breaking things!

This is a Github Pages repository. That means all the files that are stored here are publicly visible on "github.io". You can even download this README.md at http://amc-workshop.github.io/README.md !

But how do the files in "markdown" get turned into HTML? That is not part of Github Pages. But it's not magic, either -- it's code!

If you are curious how it works, you can read more in the README in the site-generator directory. However, that explanation is a little more technical than the rest of this material and assumes you know the basics of how websites work.

• Openhatch
• Outreachy -- Paid internships working on free software
• 10 entry points to tech (for girls, women, and everyone)

• Model View Culture issue on Open Source
• Why Isn't Open Source A Gateway For Coders Of Color?