• Overview
• Contents
• Resources
• Contributing Guidelines
• Code Of Conduct
• License
• Reach Us

30+ Developer Student Clubs across the country have come together to organize "30 Days of Web Development🌐" . It is an initiative for people to learn how to build web applications, irrespective of their current level of expertise.

The main objective behind this program is to provide you with access to top-notch content at zero cost. ✨

We have designed beginner-friendly lessons covering up HTML, CSS, JavaScript, Bootstrap & Firebase 💛. Furthermore, there are quizzes and projects to help you sharpen your basics in a fun and riveting way.

• HTML
• CSS
• Bootstrap
• JavaScript
• Hosting
• Firebase
• Github

We have segment the resources into topics and inside each topic the content is avialable in DAY#.md files. You can use the links below to navigate or use the GitHub navigator.

├── HTML
├ - ├── DAY1.md
├ - ├── DAY2.md
├ - ├── DAY3.md
├ - ├── DAY4.md
├ - ├── DAYOptional.md
├ - └── ReadME.md
├ - └── Html_Quiz
├
├── CSS
├ - ├── DAY1.md
├ - ├── DAY2.md
├ - ├── DAY3.md
├ - ├── DAY4.md
├ - ├── Optional.md
├ - ├── ReadME.md
├ - └── CSS_Quiz
├
├── Bootstrap
├ - ├── DAY1.md
├ - ├── DAY2.md
├ - ├── ReadME.md
├ - └── Bootstrap_Quiz
├
├── JavaScript
├ - ├── DAY1.md
├ - ├── DAY2.md
├ - ├── DAY3.md
├ - ├── DAY4.md
├ - ├── DAY5.md
├ - ├── DAY6.md
├ - ├── ReadME.md
├ - └── Javascript_Quiz
├
├── Github
├ - - └── GITHUB.md
├
├── Hosting
├ - ├── DAY1.md
├ - ├── DAY2.md
├ - └── ReadME.md
├
├── Firebase
├ - ├── DAY1.md
├ - ├── DAY2.md
├ - ├── DAY3.md
├ - ├── DAY4.md
├ - ├── DAY5.md
├ - └── ReadME.md

• Plagiarism is strictly not allowed. Any work that is found to be suspicious of plagiarized work will not be merged.
• Issues will be assigned on a first come, first serve basis. You just have to comment on the issue, asking to be assigned, and it will be done if found fit.
• Preferably, you cannot work on any issue that is not assigned to you.
• In case you want to submit an improvement to an existing algorithm, we prefer that you create an issue, describing in details your improvement. This will help others to analyze your contribution.
• If you have anything else in mind, create an issue and please wait for it to be assigned to you. You can then start working on it and create a PR.
• All PRs must be made from a Branch. Create a separate branch for every Issue you are working upon and once found fit, make a PR. Make sure your code works before submitting it :D