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.
Proposed changes
Implementing a frontend for this project using Jekyll and (maybe hopefully) GitHub Pages.
Types of changes
What types of changes does your content introduce to this project?
Put an
x
in the boxes that apply (without "`")Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. Don't hesitate to ask if you're unsure about any of them. We're here to help! This simply reminds us of what we will look for before merging your code.Note: If you submit code make sure to test it
Further comments
So, as I specified in #800, having a website frontend would probably be great for some things (and introduce some issues like broken markdown really breaking readability, for example).
I used Jekyll to implement this for two reasons, the first one is that it is natively implemented in Github Pages (and hopefully, if we want at a future date, would allow us to very easily and freely start a website by simply allowing Github Pages to work on this repo.).
The second reason is that it works (sortof) flawlessly with markdown. People can still add stuff to the repo in the exact same way they had before, and Jekyll will by itself convert to HTML, link the specified CSS, and etc (with the addition that any semi-broken markdown will completely destroy the page, as it needs to be very clearly defined or the markdown-to-html part of Jekyll will break).
The Jekyll code itself is super simple, most of the changes implemented here are either
To build the website locally, install jekyll and use
There are a lot of rough edges to smooth out still, I didn't even begin going through all the pages that could be broken, and although I tried I failed miserably at creating a sidebar with the folder structure (for ease of navigation).