This repository is a set of slides.

This repository is referenced and used as an example in the reveal-ck wiki at Publishing-Slides.

The master branch contains files that configure and serve as general input to a ruby gem called reveal-ck.

The reveal-ck gem takes this input and generates a set of static HTML files. These files are a presentation when viewed in a browser.

Further-- if you take these static file and commit them to the gh-pages branch, then, through the magic of Github Pages, you'll see the presentation here: http://jedcn.github.io/publishing-reveal-ck-slides

And that's how this repository is a set of slides:

• The source of the slides are on master, and
• The generated result is on gh-pages.

See slides.md for the slide source and http://jedcn.github.io/publishing-reveal-ck-slides for the generated result.

If you're looking to do the same thing, here's what I did:

First-- I created all of my slides initially and commited them on the master branch.

Next, I created and pushed up some placeholder content to Github Pages with the following commands (from these official instructions):

cd /tmp
git clone https://github.com/jedcn/publishing-reveal-ck-slides
cd publishing-reveal-ck-slides
git checkout --orphan gh-pages
git rm -rf .
echo 'Coming Soon' > index.html
git add index.html
git commit -m "Barebones gh-pages commit"
git push origin gh-pages:gh-pages
rm -rf /tmp/publishing-reveal-ck-slides

These commands create a temporary clone in the /tmp/ directory. I had my original clone elsewhere on my computer.

Then I went back to my original clone, made sure slides was in my .gitignore, and ran the following commands:

rm -rf slides
git clone https://github.com/jedcn/publishing-reveal-ck-slides.git --branch gh-pages --single-branch ./slides

bundle exec reveal-ck generate
cd slides
git add .
git commit -m "Files after initial reveal-ck generate"
git push origin gh-pages:gh-pages

And now the slides are available at: http://jedcn.github.io/publishing-reveal-ck-slides