Open twalton83 opened 2 years ago
Some suggestions:
Project ideas:
Serverless/FaaS/Lambdas (this is becoming a hot topic from what I read)
I'm only against this because the goal here is parity and bringing things in house, rather than expansion.
The rest is agreeable to me.
Tatiana Walton
Node Refresh
Summary
The NodeJS course has a majority of its content in the form of a code-along tutorial (Express Library from MDN). There are also some gaps or weaker sections (such as the authentication/authorization sections) and the REST API -> React frontend sections. This course should be refreshed to bring content in house and emphasize view engines less while adding more projects and content that rely on a REST API backend and React frontend. We should not get rid of view engines entirely because of their importance in other stacks.
Motivation
The motivation is to help bring parity between the RoR path and the NodeJS path, and help alleviate common issues seen in the help channels that are rooted in following the MDN code along for the majority of the course. The expected outcome is that learners have a stronger understanding of the MERN stack.
Suggested implementation
Drawbacks
Are there any drawbacks to this proposal? consider the following:
Alternatives
I think the content as it stands right now (not in house) is the alternative.
Additional