Skip to content

Commit a54a4e8

Browse files
author
Paul Jenkins
committed
Merge pull request #26 from Code52/Master
fixed typo
2 parents d62fc6f + ac63094 commit a54a4e8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2012-01-25-gh-pages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Any GitHub repository with a "gh-pages" branch has a website, usually in the for
1313
What if we wanted a 'root' website (username.github.com) rather than sub-projects? Easy. Create a new repo on GitHub named "yourname.github.com". For Code52, that's [code52.github.com](https://github.com/Code52/code52.github.com/).
1414

1515

16-
There are some neat tricks you can do to make that one of your own domains. If a repo has a CNAME file ([see our example](https://github.com/Code52/code52.github.com/blob/master/CNAME)) GitHub sets the canonical url to the value in that file. That can be done on individual projects, but we've done it on the "root" gh-pages for Code52, so all projects gh-pages appear as code52.org/<projectname>/
16+
There are some neat tricks you can do to make that one of your own domains. If a repo has a CNAME file ([see our example](https://github.com/Code52/code52.github.com/blob/master/CNAME)) GitHub sets the canonical url to the value in that file. That can be done on individual projects, but we've done it on the "root" gh-pages for Code52, so all projects gh-pages appear as code52.org/&lt;projectname&gt;/
1717

1818
##Jekyll
1919
So far we've just been modifying the gh-pages template (you can either create a gh-pages repo manually or click a button and GitHub creates a page from a template, giving you basic project info), but all gh-pages can be processed using [Jekyll](https://github.com/mojombo/jekyll).

0 commit comments

Comments
 (0)