![]() ![]() ![]() If you are interested in creating a User Page or Project Pages not using the automatic page generator or you don’t have your own. Generating a user page or project pages not using the automatic page generator $ git commit -m "initial commit of project page" Once you are happy with the files, use git add to track all the files you want tracked, use git commit to commit the files and push to GitHub: $ git add. ![]() Next, you can edit the files in your myrepo repository. If you used the automatic page generator, use git init to initialize the git repository, and fetch the files from GitHub: $ cd myrepo You can use the automatic page generator for Project Pages (similar to a User Page) or again use your own. Project Pages are different than a User Page in the sense all the files related to creating the website are kept in a branch called the gh-pages branch (not in the master branch for a User Page). To illustrate the examples below, I will use the name myrepo, but you should change the name from myrepo to whatever is the name of your repository. To create a Project Page, you don’t have to have actually create a user site if you don’t want to, but the URL will still be. $ git commit -m "initial commit of user page"ĭon’t worry if it takes a few minutes for the page to show up because there may be a delay up to ten minutes the first time you push the files to GitHub. Next, you can edit the files in your repository. When you use the automatic page generator for Project Pages, you will check out the gh-pages. Note: we are using git checkout to check out the master branch because this is a User Page. If you used the automatic page generator, use git init to initialize the git repository, and fetch the files from GitHub: $ mkdir All the files in the master branch of this repository are used to publish the website. Once the repository is created on GitHub, you can use the automatic page generator or use your own. To get a User Page, you must create a repository on GitHub named where username is replaced by your GitHub username. Jekyll-Bootstrap works the same way, except you will now have cool themes to pick from for your website!īefore we discuss more about Jekyll, let’s discuss the difference between a User Page and Project Pages. When you use Jekyll you will be installing a set of files in your GitHub repository that tell GitHub to create html files from the markdown files. Jekyll-Bootstrap takes away a lot of the hassle about Jekyll by allowing the user to create blog-aware websites using markdown with themes. Therefore, it is definitely worth taking the time to understand a little bit about Jekyll, but it can be confusing if you are unfamiliar with it. Many blogs are written in Jekyll including every GitHub page. Jekyll is a “a simple blog aware, static site generator” based on files such as Markdown. The main idea of behind both of these repositories is Jekyll discussed next. This tutorial is similar, but uses the Jekyll-Bootstrap repository at () which can include additional themes. The amazing Karl Broman recently added another tutorial specifically for creating GitHub Pages using his simple_site repository at (). The Project Pages are websites which are special repositories that will have the domain name where the name of the repository on GitHub is called myrepo. This User Page is a website that will have the domain name or where username is replaced by your GitHub username. For each registered GitHub account (representing a user or an organization) you can register one User Page, but an unlimited Project pages. The purpose of GitHub Pages is to provide the GitHub user a way to create personal websites for themselves and websites for their projects / repositories. Turn R Markdown files into Markdown files using Knitr in R-Studio and make an online book Write programming books using GitHub and Markdown using GitBook GitHub Pages is a really useful resource provided and hosted by GitHub. My personal favorite tutorial is by Karl Broman called git/github which I highly recommend if you are interested in learning more about git and GitHub. There are so many great reasons to use git and GitHub. ![]()
0 Comments
Leave a Reply. |