The build process has been broken since deploying to GitHub Pages, blocking work on this. This is most likely because the deployment method chosen for GitHub Pages did not allow the Jekyll source directory to be overridden from the root directory.
Jekyll was also handling sass compilation which was a bit weird considering we have Webpack for that sort of thing.
(Also, docs on the Internet are conflicting and messy and I'm easily confused! :S)
Solution
GitHub Pages also allows us to specify a specific subfolder called docs in the master branch to build from rather than having to rely on a gh-pages branch. See here
Also, give Webpack more asset compilation work.
Tasks
[x] Move Jekyll source files to folder named docs instead of src for easier deployment on GitHub Pages
[x] Handle sass compilation/image loading via Webpack instead of Jekyll
[x] Use GitHub Pages gem for better Jekyll compatibility
Why
The build process has been broken since deploying to GitHub Pages, blocking work on this. This is most likely because the deployment method chosen for GitHub Pages did not allow the Jekyll source directory to be overridden from the root directory.
Jekyll was also handling sass compilation which was a bit weird considering we have Webpack for that sort of thing.
(Also, docs on the Internet are conflicting and messy and I'm easily confused! :S)
Solution
GitHub Pages also allows us to specify a specific subfolder called
docsin the master branch to build from rather than having to rely on a gh-pages branch. See hereAlso, give Webpack more asset compilation work.
Tasks