I have a project together with several people and we have a README.md
file with a bunch of GitHub Flavored Markdown that is rendered on our GitHub page. We also
Another route to consider is setting up a pre-commit hook which builds the relevant pages. I do this in one of my repositories. You'd probably have to ditch the automatic page generator and just push to the gh-pages
branch yourself, though, as well as doing something fancy to turn your docs into HTML or a Jekyll site as Nathan suggests.
In that repository I push like this to keep gh-pages
identical to master
. There are plenty of other ways to do that, too. This might not be ideal for your situation though (you might not want them to be identical).
Anyway, the reason I had offered a bounty on this question was because I was hoping someone had a better workflow. This method is kind of convoluted and inflexible and it requires everyone to keep their hooks in sync.