Heroku is a great platform to deploy your web apps, in a way that just works for developers. What isnt obvious is you can also deploy static sites too.
As Markdown is now common way for developers to create documentation, why not use Heroku to deploy your markdown driven content site.
The Salesforce developer evangelist team are doing just this, creating workshops written in markdown. The workshops are deployed on Heroku and we collaborate via Github. This is a really effective way to collaborate as we are remote workers and often on our travels.
Markdown is really easy to learn and really easy to read. Its much better to read in its raw form than most Wiki Markup languages. If you have a good editor (Emacs & Emacs Live) then reading and writing markdown is a great experience.
Its also pretty easy to convert Markdown to different formats such as HTML and PDF.
I picked up all the markdown syntax from working with Github readme.md files and from writing markdown in Emacs. SimpleCode.me also has a really good getting started with markdown guide.
Any editor can be used two work on the content for the workshops, this is another beauty of markdown. I recommend Emacs with Emacs Live setup or you are using MacOSX, then Mou gives you live rendering of you content as you type.
To make the markdown render in HTML and PDF similar to the style used on github, a fairly simple css file is added to the project.
As Heroku and Github are both going to be used then the projects are versioned with Git. A git repository is created on Github at the start of a new workshop. A github organisation is used to keep al the projects together. The new Github repository is cloned and development of the content commences.
As its a static site then there is not much need for a .gitignore file, assuming you have a ~/.gitignore_global file for any backup files that your editor creates.
Once the workshop content is good enough to deploy, a new Heroku application is created. A specific build pack is used to tell Heroku how to assemble and deploy the markdown as a web application. This build pack defines how the HTML is generated from the markdown, based on a css file included in the project. The whole app runs on a HTTP server called SimpleHTTPServer, written in Python.
The app is created on Heroku app using the markdown build pack created by James Ward. The command line for this is:
heroku create workshop-name --buildpack https://github.com/jamesward/heroku-buildpack-markdown.git
A procfile is a simple text file that tells Heroku what to do with you application when its ready to run it. For the markdown site we simply start up a simple HTTP server which runs on python (we dont need all the bells and whistles of something like Apache).
web: directive at the front tells heroku to create a process that listens to requests from the Internet. As we are not specifying a port number, it will pick up the default port to listen on from the Heroku environment variables.
web: python -m SimpleHTTPServer $PORT
As soon as you are ready for your markdown content to go live, simply push your local repository up to the Heroku repostiory with the git push command.
If you have more than one remote repository specified in your git configuration, then all you need to do is specify the specific repository to push to. By default the heroku create command adds a remote called heroku.
To check what your heroku repository is called you can use the command:
git remote -v
To push to a remote repository called heroku, use the command:
git push heroku master
It is really easy to create content based on markup. Collaborating on this content is really easy when using Github and deploying this content as a static website is only a git push away with heroku.
Other aspects were are adding to this workshop creation process include:
- create a staging heroku app to allow testing of content once the site has gone live;
- automatically generating a pdf copy of each page every time you deploy a new version.
This work is licensed under a Creative Commons Attribution 4.0 ShareAlike License, including custom images & stylesheets. Permissions beyond the scope of this license may be available at @jr0cket