-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Introduction to Frameworks: Rearrange position in the course #4964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I noticed that this lesson is part of the shared lessons between the NodeJS and Ruby pathways. I don't know much about the Ruby path, but I think the proposed change would not work without disrupting that path. In which case I'm not sure to resolve this without disrupting the other path, or if the other path would also benefit from this change. |
Can you please assign this to me? I am willing to fix it |
I agree with this point. I was originally thinking about raising it when the Node intro section is part of the active revamp milestone, but since it's been raised here, I don't think it'll be any issue at all literally just moving the lesson back to be the first in the Express section (i.e. before Moving the lesson position would mean moving the lesson fetch in website repo to the new position, but that's all that would be needed IIRC. |
I agree, this seems like a good change. As was said in the last comment this is work that will really need to be done in our site repo, so I will move this issue there. @ChuqiaoHuang is this still something you would like to work on given that? |
Yes, I am willing to work on this |
I have already made a pull request according to this issue. |
Checks
Describe your suggestion
Proposed Change:
I think this lesson would be better suited as the first lesson in the Express section, before the
Introduction To Express
Reasoning:
This lesson comes between the
Introduction to the Back End
andIntroduction: What is Nodejs?
lessons.Personally, I think the placement of this lesson feels awkward. We just learned about how a full stack application works, and a little bit about how back ends work, but before we're able to know how a back end works in more detail, we're introduced to frameworks that abstract away how the back end works.
The benefits of abstraction and frameworks kind of fly over the head, as we're yet to even understand or work with a framework-less Nodejs back end yet to know what all is abstracted away.
Not to mention that just after we introduce frameworks, we pretty much forget about their existence until the next section in the course,
Express
.To make an analogy, it feels similar to introducing frameworks like React at the beginning of the Javascript Course, only to switch back to vanilla Javascript immediately after.
Path
Node / JS
Lesson Url
https://www.theodinproject.com/lessons/nodejs-introduction-to-frameworks
(Optional) Discord Name
No response
(Optional) Additional Comments
ginned
The text was updated successfully, but these errors were encountered: