The SILShack class blog - Fall 2013

Holdovers from last time:

Student Backgrounds

Finish bios/intros

A series of questions, with opportunities for story time. Show of hands: How many people have viewed source on a Website?

• a blog?
• used Developer tools to alter a website?
• written HTML?
• written CSS?
• written Markdown?
• a Github account?
• opened/closed an issue or pull request?
• read Python code?
• written Python code?
• read another language?
• written another language?
• used Linux?
• used the command line?
• read software documentation?
• contributed to open source?
• implemented a project or system from scratch?

The answers to all of these questions will be 'yes' at the end of the semester.

In-Class: Get set up on Google Plus

I think most of you are set up and have commented on the intro post. Perfect. * Quesiton I got RE social participation. Concentric circles in wider and wider communities.

In-Class: Get set up on Github

You all should have a Github user name.
* Basic parts of Github: profile, organization, repo, issues, pull requests, milestones. * Michelle's question in-line

Mini-Lecture How the course blog is constructed.

• _config.yml: Where sitewide variables live
• _posts/: Where posts live
• _layouts/: HTML for Jekyll to instert our content into
• *.markdown: Pages for the site

In-Class Exercise: Open your first issue

• Exercise as Milestone
• Example: Virginia had to drop the course
• Example: Jaleesa's typo on the attendance section
• Everyone open an issue "____'s first issue"
• Tag it to the first issue milestone
• look at the milestone

In-Class Exercise: Close your first issue

• Pair up. Comment on the other person's issue and close it.

In-Class Exercise: Edit your Bio

• Fork the repo
• Make a branch called something sane like config
• Change your details in _config.yml
• Describe your changes with a commit message
• Open a Pull Request from your new branch to the silshack master.
• Pair up, review the code, and comment that it looks good.

In-Class Exercise: Write an initial blog post

• Make an issue "______'s first post"
• Fork the repo
• Make a sanely titled branch like firstpost
• Make the file _posts/YYYY-MM-DD-title.md
• Describe your changes in a commit
• add a YAML header (with your _config name as author)
• Write a post, using some features of Github Flavored Markdown
• Open a pull request from your new branch to the silshack master branch

• Pair up, review the code, and comment when it's ready to go.

• Note: As we’ll learn, git is an open source command line version control system. Github.com is the fastest growing git repository on the internet. Th$