This is now an actual repo:
Michael Hulse mhulse
Concentric Sky, Inc.
- Eugene, Oregon
|echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc|
|curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1|
|make install # ok, fine, this step probably takes more than 30 seconds...|
|curl https://www.npmjs.org/install.sh | sh|
|InlineAdmin mixin limiting the selection of related items according to|
|criteria which can depend on the current parent object being edited.|
|A typical use case would be selecting a subset of related items from|
|other inlines, ie. images, to have some relation to other inlines.|
|Use as follows::|
|<meta name="apple-mobile-web-app-capable" content="yes">|
|<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no">|
|<li><a href="http://google.com/">Remote Link (Google)</a></li>|
GitHub Pages "Normal" Setup for User & Organization Pages
Let’s say your GitHub username is “alice”. If you create a GitHub repository named alice.github.com, commit a file named index.html into the master branch, and push it to GitHub, then this file will be automatically published to http://alice.github.com/... The same works for organizations.
Read more here: http://pages.github.com/
However... the downside of this is that anyone that forks this repo won't get it as a GitHub Pages repo when they are working on it... because they have a different GitHub "username" (or "organisation name").
So the trick is to not use a
master branch as the documentation tells you... rather, use a
gh-pages branch, as you would for your other "Project Pages".