Considering the possible issues of version skew mentioned in #3, I propose using Travis-CI to generate the output contents automatically and push to the desired branch. This could be the gh-pages branch if you want to use GitHub's hosting, or any branch if you set up your hosting machine to poll for pull changes to a specific branch. (Of course, the latter could also perform the pelican rendering itself too, but this gives a degree of public visibility of build success ;-) )
Considering the possible issues of version skew mentioned in #3, I propose using Travis-CI to generate the output contents automatically and push to the desired branch. This could be the gh-pages branch if you want to use GitHub's hosting, or any branch if you set up your hosting machine to poll for pull changes to a specific branch. (Of course, the latter could also perform the pelican rendering itself too, but this gives a degree of public visibility of build success ;-) )