Not a tech stack recommendation, but I'd suggest teaching from putting together HTTP response strings, and build their own abstractions / tools from there, inst

Not a tech stack recommendation, but I'd suggest teaching from putting together HTTP response strings, and build their own abstractions / tools from there, instead of going straight into libraries like express / koa (e.g. i think the middleware architecture hardly makes sense for people who don't know the inner workings of a http server). Same with frontend I think it's better to start from putting together simple html string from the backend, experience why it can be tough for building rich applications, try to build own mini / frail tools, then move to the established frameworks. The gist is: Understand the problem before learning the solution.