Basic structure of the new website

[AnshulMalik]

Now that we have the wireframes ready, let's start designing the website.
You can find the wireframes here https://drive.google.com/drive/folders/1XOU2i1IrAlURLidt1i6S2c_M7FdYXupF?usp=sharing

We are thinking of implementing this new website in React as SPA.
If you don't know what is an SPA, then read this.

The PR for this will go to a new branch, called redesign

[lyvwhyr]

/request
I would like to work on this one

I can get the basic setup webpack, css processors etc and add react router for spa for the index page.

[AnshulMalik]

Sure @feralcode we'd love your help

[lyvwhyr]

can you assign to me using the sidebar? I will get this knocked out in the morning going to get some sleep and get on it first thing in the morning.

[AnshulMalik]

I think we can only assign to people who are in the organization, it's assigned to you don't worry :)

[ksandhu16]

can I work on this?

[AnupKumarPanwar]

We would like to have a website where you consume the Github APIs to fetch the data and render them on the website rather than giving links to the GitHub files. For that, a prerequisite is to organise the files in a common way across all the repos so that fetching and parsing is easy. Consider the Algorithms-Explaination repo the explanation part.

[AnshulMalik]

Hi @AnupKumarPanwar. I'd recommend an option which doesn't involve github apis since they are not unlimited. Here is how I think we should implement this,

We save the article/explaination in a markdown file on github on another repository that you mentioned.

Then while making a release of the website, we pull the latest articles repo, may be convert the markdown to html for the website and build and release the new version.
This way we don't need to deal with the github apis and their rate limits.
Please let me know what do you think of this.