up4movement / up4movement.github.io

Homepage for UP4MOVEMENT
https://up4movement.com
0 stars 0 forks source link
fitness personal-trainer

Important info

Helpful link

https://medium.com/@stefanneculai/how-to-build-a-free-static-website-with-jekyll-and-github-pages-707e1cd5ffc3

Workflow (to develop on the site)

  1. Create new branch off of master
  1. Test all local changes by running development -> jekyll serve + look at localhost:4000

  2. When happy, then save all files, commit and push branch to branch with same name on Github

  3. Create pull request between that branch and Master (default)

---- production build -----

NB: The _site folder continuously regenerates itself, but you can try a manual jekyll build command otherwise (do this on a separate branch as there have been unalterable bugs from this command earlier).

  1. npm run deploy (from the branch you finished working on) runs the script that deploys the _site folder to gh-pages branch, which is what the site is running on (must run jekyll build or jekyll serve first to generat _site folder) NB: Haven't had bugs with npm run deploy, but if there are, then the local master branch is working and I can pull from master (the latest changes) and run npm run deploy from there

  2. For some reason, after every deploy to gh-pages, Github usually re-publishes the site to up4movement.github.io, so visiters to the site get 404 errors.