Media queries should be taught before "Javascript" section.

[roshhi]

Checks

• This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
• I have thoroughly read and understand The Odin Project Contributing Guide
• Would you like to work on this issue?

Describe your suggestion

Right now, media queries come after JavaScript in the curriculum. However, learning media queries earlier would be very beneficial for beginners as students can build solid, responsive foundations and then enhance those projects with JavaScript functionality later in weather app,todo-app and restruant page etc

Path

Node / JS

Lesson Url

Before Javascript section or in Intermediate html-css section.

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

[Bijay-Shre-stha]

@roshhi, media queries have been covered in the Advanced HTML and CSS section under Responsive Design.

[roshhi]

Yeah i know but that's not my point.
They should be taught before Javascript section maybe in intermediate html-csss section so you can make all of your javascript projects fully responsive.
Im telling with experience because i suffered alot in making my JS projects responsive.

[mao-sz]

Converting to a discussion since this is a rather large change that would need a lot more discussion and planning if it was to go through, so is not yet actionable.

While there will always be arguments for placing certain lessons at certain points in the curriculum, actually changing the location of something is often an extremely big change that should only be done if there are significant problems to be solved by that change. Since it's a change that will affect many many learners, and not all learners will find out about the change via a Discord announcement, for example, so may miss the content entirely if it gets moved to before where they currently are.

It makes sense that you'll have struggled with making your JS projects fully responsive before learning about certain things, but I'd like to raise a point for consideration: fully responsive sites (that actually need media queries - they're not needed in many cases of responsiveness) are not the point of the projects in the JS course. The point is learning and practising JS fundamentals. By bringing MQs forward, it could impact how people go through the JS course because they spend more time on stuff that isn't the point of those lessons and projects.

This is all from the perspective of the JS pathway, which has a different course order to the Ruby pathway (where the same JS course kind of serves different purposes in the context of the pathways). In the JS pathway, the JS course is much more for JS fundamentals in general, where people will be a lot less experienced overall. In the Ruby pathway, it comes much later and after the adv. HTML/CSS course, but people will be much more experienced with making web apps by that point, and the JS course is more about diving deeper into JS to enhance what they're already doing. In that context, it makes sense to me that MQs comes before the JS course. But in the context of the JS pathway, it actually makes more sense to me that it comes after. Unless there was a very large restructure of the entire JS pathway, but that isn't something any of the team will rush to do without significant reason.