Getting started with GitHub Pages Github Pages is something as simple as a GitHub service for serving up static HTML from a GitHub repository. It’s the perfect place for project documentation, like Javadoc, and that’s what I’ve been using it for. It can also be used for blogging with Jekyll or even a complete site for your project. Tell me more! GitHub Pages (hence called Pages) can be tied to a project by creating a special branch called gh-pages, or directly to your account by creating a repository called yourname.github.com. Also, saying it only feeds static HTML is like telling only part of the story. Getting started Creating your personal page Pages is really quite easy to use. Important: there’s currently an issue regarding Pages and pushing over http, which means, it just won’t work. Creating a project page Creating the project page is about as easy as creating a personal page, but a little different. Templating using Markdown Create a file named demo.markdown in your repo and add the following content: Rounding it off
GitHub.com flow · @mdo The term GitHub flow refers to how one can develop software with GitHub. It's a process that minimizes friction, enables asynchronous communication (and development), and is decently flexible. For an overview, read Understanding the GitHub Flow on GitHub Guides. Applying the GitHub flow to development of GitHub.com The Website™ builds on that, and tends to go something like this. 1. Issues on the github/github repository are the easiest way to find things to do. It's worth mentioning though that we sometimes jump right into code from a meatspace discussion or from a tweet. Bottom line? 2. At GitHub, almost every new contribution happens in a branch. My branch naming scheme is sometimes serious and relevant, and usually not useful in the slightest. sidebar_hit_areas and today_we_celebrate_our_independence_day are both branch names that I've recently worked on. Great branches really should include accurate names, but most of the time it doesn't matter because they're so short lived. 3. 4.
Get Started With GitHub Pages (Plus Bonus Jekyll) After several failed attempts at getting set up with GitHub Pages, I vowed that if I ever figured out how to do it, I’d write it up. Fortunately, I did eventually figure it out, so here is my write-up. Why I think GitHub Pages is cool Normally when you host stuff on GitHub, you’re just storing your files there. GitHub Pages accepts static HTML but can’t execute languages like PHP, or use a database in the way you’re probably used to, so you’ll need to output static HTML files. The main benefit of GitHub Pages is ease of collaboration. Before you get started If you’ve used GitHub before, already have an account and know the basics like how to set up a repository and clone it to your computer, you’re good to go. I also found this tutorial about GitHub Pages by Thinkful really useful, and it contains details on how to turn an existing repository into a GitHub Pages site. Although this involves a bit of using the command line, it’s minimal, and I’ll guide you through the basics. Make a page <!
GitHub Pages