This is an example project demonstrating how to setup an easy configuration for keeping your README.md automatically synced with a GitHub Pages project page created using one of the great layouts available when using GitHub's Automatic Page Generator.

If you haven't set up a project page for your GitHub repository yet, then you can do so by following the instructions found here. GitHub will provide a great feature and just before you pick your layout it will give you the chance to load in your README.md for your master branch and edit it before using it as the content in the layout. The problem I had with this in my project's is that I wanted to use the README.md from my master branch, but I also wanted it so the project page to stay updated and in sync with the README.md automatically.

• Here is a relative link to a doc file which should work on project page as well.
• Here is another relative link to a doc.
• Check out the GitHub Flavored Markup doc which shows off the markup that will work if using the markup: redcarpet option in _config.yml.

This project contains a bash script which is used in your project as a git hook. Git has support for scripts to hook into and execute when certain actions are taken on a local git repository. If you create a bash script named post-commit and place it in the directory .git/hooks/ within your local repository, it will then be executed after every committ to that repository.

The post-commit script contained in this project is a bash script so you will need bash it in your path. If you are running Git on Windows, this is in bin subdirectory within your Git program files directory. In order to use the post-commit script here you must already have a project page created with one of the layouts using the Automatic Page Generator and have set it up using the following instructions:

• If you already have a gh-pages branch, create a backup in case you botch this setup.

• If you don't already have a gh-pages branch go to your repostory page's Settings tab and use the Automatic Page Generator to create it.

• Change to your local repostory's directory and checkout the gh-pages branch.

• Create a new file called _config.yml this is a file that will tell jekyll how to build our site when it is pushed to GitHub Pages. Put the following lines in the file

  markdown: redcarpet
  path: http://yourusername.github.io/reponame
  

• The above will simply tell jekyll to use the redcarpet style markdown which means it will be parsed in the same way that GitHub does for their repo pages. Also we are creating a global variable for the site called path. This variable will be accessible from site.path.

• Copy the process-rel-links.js file from the docsync directory to your gh-pages javascripts directory.

• Create the directory _layouts within your gh-pages branch if it is not and move index.html to the new _layouts directory.

• Open up index.html and locate the HTML from the rendered markdown in your README.md file. This is usually between between <section> or <article> tags. Delete this text and replace it with the text {{ content }}.

• Before closing index.html, you also need to locate the CSS from your project page theme (should be a file in the stylesheets directory). You need to prefix this and any other assets loaded from your site in this HTML with {{ site.path }}.

  For me this was a line towards the top:

  <link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">
  

  Which needed to be changed to

  <link rel="stylesheet" type="text/css" media="screen" href="{{ site.path }}/stylesheets/stylesheet.css">`
  

• Add the following lines to your index.html file. The first line for jQuery is only needed if jQuery is not already included in your layout's index.html already.

  <script src="//ajax.googleapis.com/ajax/libs/jquery/2.0.0/jquery.min.js"></script>
  <script src="{{site.path}}/javascripts/process-rel-links.js" type="text/javascript"></script>`
  

• Add and commit changes to gh-pages, and switch to master branch. Copy the post-commit script found here in CoryG89/docsync to your local repository's .git/hooks directory.

That's it, now whenever you make a commit to the master branch, the README.md file and all the markdown in the docs directory of your master branch will be synced up with the will automatically be synced to your project page.