Website Frontend#802
Conversation
Implementing a frontend for this project using Jekyll and (maybe hopefully) GitHub Pages.
|
The Label Bot has predicted the following:
|
|
(This is my first time working on an open source project so do tell me if I do anything wrong, thanks!) I guess its also nice to add that I'm available to smooth all the rough edges I mentioned (probably through some weeks), but I wanted to put this PR here before I actually go do that as it will take some time and yall might not even be interested in this idea to begin with. |
|
@Henrique-FB i don't have any idea how to view the website. can you share any guide or resource link. |
|
First install Jekyll: https://jekyllrb.com/docs/installation/ (it also needs some dependencies to run, they handle that in this link as well) Open the branch on vscode and run After that is done run After you open it, you should see something like this: If what I said doesn't work I think on this video the dude does it on Windows and this site shows the entire setting up process Hope this works for you. If not we can try something else. |
|
@Henrique-FB Okay i will take a look. |

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
xin the boxes that apply (without "`")Checklist
Put an
xin 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).