Web3 Learning Roadmaps [Old]

Notes for Roadmap

Having Introductory content (setup) and web2 content is important as well for learners who have no prior coding experience.
Prioritize making every content ELI5 (Explain like I’m 5 which basically means explaining content that is understandable to anyone without assumptions of prior knowledge)
- While writing content, ask yourself if the content would need additional explaining.
- Be relatable to everyone. (eg. keccak256 might need explanation but hashing algorithm could be more relatable)
- Avoid dropping advance concepts without building up relevant knowledge. If necessary, link to docs within curriculum that explain concepts.
- Refrain from using buzzwords. Concepts are what we need to learn, we can pick up the slang in other places
The Roadmap needs to have three broad categories at least
- Frontend (HTML, CSS, JS, APIs, etc.)
- Backend (Node, Storage Solutions, etc.)
- Smart Contract Development
The overall roadmap should let a learner doing all three categories combine all the three intuitively
There are two groups of learners that we are focused on at the moment:
- Ones who prefer a structured bottom up approach which includes learning basics and building up on it
- Ones who prefer to get hands-on and learn concepts, tools, etc. as required in the project
- There are various styles of learners such as visual, auditory, etc. and catering to most can be discussed as part of features for the platform. (eg. Having text, videos, accessibility, etc.)
The roadmap for the learning track should keep in mind, both groups of learners
Every broad category of the roadmap can be divided into lessons and projects
- Lessons give an in-depth explanation of concepts along with sample code
- Projects explain each concept being used without assumptions of prior knowledge so learners can hop on projects without going throug
- h the lessons as well. However, explanations in projects would be concise.
- Finding a right balance of theory to be added in the foundation lessons and the projects part. Theory lessons could have 2 - 3 brief paragraphs for a given title. Projects could have a few lines explaining the concept.
- Projects could build up on previous projects. (eg. start with simple wallet connect and end with DEX at the end)
- Two ways links to content
  - Projects can link to our theory lessons for further reading
  - Theory lessons can point links to projects (eg. this theory/ concept is applied in this project). The link would point to the most basic application of concept.