There is a video about all the possible areas in web-development. This guy makes tutorials and I've watched quite a few of them just for the sake of understanding web development better, hope you'll find them useful.

Also, if you don't feel like watching the video and listening to him, here's the mind map he used.

Depends on your specialization/focus in frontend development. What do you want to end up doing or do already and want to improve?

Do you work on UIs for apps, possibly web and mobile apps? It might be useful to pick up React Native, or any UI framework that allows for primitive - yet universal elements for web and mobile.

Do you create frontend modules that require input from the user? Or maybe you just want recyclable and more important, reliable components? Try experimenting with a testing framework to make assertions on your code and ensure it's working.

Do you create a lot of landing pages or microsites? You might want to look into static site generators (SSGs) like Gatsby, NextJS, or even Jekyll/Hugo/etc if you're into non-JS options. SSGs make the creation and optimization of websites much simpler than just writing HTML and CSS from scratch - and gives you performance benefits without having to figure out yet-another-library (Webpack).

Maybe you do a lot of repeated processes (minifying CSS/JS), or want to take advantage of stuff like PostCSS processing. You can get into Gulp, Grunt, or any other task runner.

There's a lot to do! I'd take a look at this chart on Github, it breaks down all the most of the paths for a frontend developer:

source

I'd just focus on getting really good at Javascript, since it's the basis of Node and React. Once you get a grip there, create apps and experiment with different tools, libraries, and frameworks and see what sticks into your workflow.

Hope that helps! 👍

To be frank, after 40 years of programming in one form or another, this whole "Software engineering" thing -- to me -- reeks of marketspeak doubletalk used to put buns in seats at lectures/conferences, make career educators feel relevant, and to let hucksters continue to peddle the same books they've been recycling since the 1990's with a new cover and title on them.

It is a meaningless "soft language" phrase designed to fill out marketing blurbs, introducing zero new concepts, methodologies, or approaches to development that we haven't supposed to have been doing for at least two decades. Whilst the ethical practices of engineering and treating it as engineering should be an essential part of the process, this whole nonsense of a "new wave" of it in front-end development is just taking an existing name, and slapping it in not for improvement, but as a marketing blurb.

Particularly on the web technologies front, since pretty much it's what we're supposed to have been doing since somewhere around the time HTML 4 Strict became viable, aka when we stopped caring about Netscape 4.x or IE 5.0x.

... and the only reason any of the concepts, methodologies, or approaches of this so called "software engineering" can seem like something new to people -- again at least in terms of using web tech -- is the simple fact they never stopped building HTML, CSS, and JavaScript using the outdated, outmoded, 1997 style HTML 3.2 approach of presentational markup, with zero graceful degradation, separation of concerns, semantics, or any other meaningful metric of good practices. See how popular all the garbage frameworks are for proof positive of that.

A situation only further exacerbated by the folks throwing "JavaScript for nothing" at everything, telling users with accessibility needs to sod off and overcomplicating the simplest of tasks.

Sick buzzwords and euphemisms do not substance make.

... and that's the true tell of it, as the ACTUAL engineering concepts of accountability and professionalism are nowhere to be found in what people are now calling "software engineering".

But you should at least learn the jingoistic jargon, since you can bet clients galore are going to start using it in their routine business meetings where they sit around playing BS Bingo.

Even if underneath all the lofty words and new names slapped onto things, nothing has actually changed in terms of getting the job done. End of the day you still end up having to put up with clients who think they can learn about the latest technologies in the pages of Forbes.

Which is akin to taking financial advice from Popular Mechanics. Before you know it you've been scammed by con men like Paul Moller.