The problem WebMap solves

There are a lot of roadmaps on Web 2 and Web 3. They are complex and very lengthy. They look old-fashioned when talking about design and hard to use when talking about user-friendliness. If we talk about the content it seems like they contain everything on this planet i.e. bulk of technologies and stuff. Seeing too much stuff on the roadmap can also reduce the confidence of a beginner to walk on that roadmap.

So we thought of creating something which actually guides us in step by step manner and is also easy to use. And guess what we created WebMap which has a better design and which is more user-friendly. Also unlike other roadmaps, it does not contain every technology but those which are fundamental and which are important to learn. With every topic, we have tried to provide the best resources in form of docs, video links, and a Github repository.

Challenges we ran into

We ran into a few challenges:-

The biggest challenge was to find out the best resources so that users need not waste time looking for resources. It took us almost 6-7 hrs finding resources that are easy to understand and good for learning.

We were trying to implement the logic of marking down a topic that is done and it remains done even if the page is reloaded or closed. But we ran into errors and it took us some time to understand the errors and we were able to solve them.

We were having issues with the front end part i.e. on clicking the front end we were getting back data of backend but we resolved this issue as well.