OurBigBook tooling is so amazing that we also take care of the HTML publishing for you!
Once a publish target is properly setup, all you have to do is run:and your changes will be published to the default target specified in
git add README.bigb git commit -m 'more content!' ourbigbook --publish
If not specified, e.g. with the the
--publish-targetoption, the default target is to publish to GitHub Pages.
Only changes committed to Git are pushed.
ourbigbookknows how to process get processed and only their outputs are added to the published repo, those file types are:
Every other Git-tracked file is pushed as is.
.bigbfiles are converted to
.scssfiles are converted to
--publishis given, stdin input is not accepted, and so the current directory is built by default, i.e. the following two are equivalent:
./ourbigbook --publish ./ourbigbook --publish .
Publishing only happens if the build has no errors.