Website Frontend.

[Henrique-FB]

Is your feature request related to a problem? Please describe.
This is not a problem, but, browsing the topics is not as intuitive as it could be, and the simple markdown design can be tiring/boring to keep looking at for a long time. Additionally the entire thing is hard to advertise for people that are very new to this world as they might not be completely confortable with browsing using github.

---

Describe the solution you'd like to add
I've already cloned it and set up a jeckyll folder structure, it transforms all the .md files into html, and uses a simple default css (this css could have a sidebar as well for ease of use for example).
The benefit of using jeckyll is that its easy to convert, keeps content easy to add (just add the content in the same way people are already doing) can be easily built locally and can even be hosted on Github Pages for free extremely easily.

---

Describe alternatives you've considered
Another way of doing this would be to use some other program (or build one from scratch) that turns md into html. Or maybe make a web page load the contents of each .md page with js as you "browse" through the website? Honestly sounds like too much trouble.

---

Additional context
This issue is sort of two fold.
Partly it'd be nice to just be able to build it locally and have a locally run computer-science resource.
The other part of it is the idea of putting it up on github pages so its easy to cite and easier to read/use,

Two things to keep in mind, lots of files in here are pretty broken. Its hard to notice when readinng them through github but there will be some work in cleaning files that have badly written markdown syntax (I found at least 3 pages with some pretty gruesome stuff)

I'm available to both work on this website (I already have it basically completely set up locally), and am also available to try and smooth the rough edges we find while setting everything up.

If you think it's a good idea I'll make a pull request with the changes, jekyll working, and the commands I used to build it locally.

[shhossain]

@Henrique-FB

Thanks for the thoughtful suggestion — your idea looks solid. I'm not entirely sure how it'll turn out in practice, but why not? Go ahead and submit your pull request, and we can take it from there. If you ever have trouble reaching me via GitHub, feel free to send me an email (you can find it on my GitHub profile).

Regarding the markdown issues you mentioned — I appreciate you pointing that out. I’ll definitely look into those. When I first created this repo, I had first contributors in mind, but over time it became harder to review every PR in detail due to my job. Sometimes when I have a bit of time, I just skim through PRs, and if nothing stands out as broken, I merge them — I admit I haven’t reviewed all of them thoroughly.

As for the website idea, I agree — it would definitely help with readability, highlight errors more clearly, and make the project easier to share with newcomers. It could also make the repo more discoverable and approachable for first-time contributors.

Looking forward to seeing your PR!