Gem warning, page layouts, old pages, general fixes #208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves the warning that occurs when building the webpage using GitHub Actions.
The change includes a transition from using the branch based deployment method towards using the Jekyll plugin for GitHub Actions directly.
This closely followed the best practice suggested on the Jekyll website.
As part of this change, the settings for deployment need to be changed. This needs to be done by an admin and is described here.
Essentially, by going to Settings > Code and automation > Pages, the Build and Deployment source needs to be changed to GitHub Actions. This needs to be done after merging, so that the jekyll workflow can be selected.
Let me know if we should do a meeting for this transition!
Also fixes the 404 page and default layout...