If you look at the way that travis_ci runs Jekyll, it becomes clear that the ./setup.sh script isn't really needed. That logic can be folded into ./jekyll.sh so that only one script is needed.
This makes the maintenance burden a lot easier.
[ ] change ./jekyll.sh and eliminate ./setup.sh in boilerplate
[ ] edit the boilerplate setup script
[ ] send out a migration notice to the users
[ ] fix the documentation everywhere that references ./setup.sh and ./jekyll.sh
If you look at the way that travis_ci runs Jekyll, it becomes clear that the ./setup.sh script isn't really needed. That logic can be folded into ./jekyll.sh so that only one script is needed.
This makes the maintenance burden a lot easier.
[ ] change ./jekyll.sh and eliminate ./setup.sh in boilerplate
[ ] edit the boilerplate setup script
[ ] send out a migration notice to the users
[ ] fix the documentation everywhere that references ./setup.sh and ./jekyll.sh