Many of our students start from the beginning and work through the curriculum in order but more tend to cherry pick lessons as needed to fill in the gaps in their knowledge. That's fine too and it's why the whole thing is available at once. The important part about having the path laid out, though, is that it keeps you accountable for your progress -- you know when you're getting off-track because you can see each piece of knowledge in the context of the bigger puzzle. For many, that's what they need to keep them focused.
Although, how are these organized? The colors seem to imply some kind of grouping, but besides "the big 3" at the top, the rest seems to be a random order. Maybe group by alphabet, or front end/back end, frameworks, tools, level of skill required, etc. Finding what I was looking for took a little scrolling, no big deal. I appreciate the resource and I will definitely be using it more.
That being said, I think there's something to exploring those resources on your own. The principal problem I've seen with teaching people to code, especially when confronted with a set track, is that learners start rigorously, taper off, and never finish. I'm curious what The Odin Project's approach to this issue is.