You may notice that when late 90s/early 2000s sites get posted to HN, there are often a set of comments on how quick-to-load and readable they are.
If I teleported here from the 90s, first thing I'd need to wrap my head around is how HTML and CSS have changed. I'd be learning a responsive framework (or even hand-rolling it, so you know how it works) like bootstrap. And doing a very basic website.
And if html5 & responsive css aren't enough to wrap your head around at once, I'd create a github account, and start with github pages. That'll let you use the static site generator Jekyll. The combination of all three will do pretty much all you need for 90% of the sites out there.
After that, then I'd look at a stack that lets you have some degree of interactivity and persistence in order to build web apps.... But for now, clean responsive websites would be the way forward.
https://github.com/oddbird/susy
Also for static site generators take a look at:
https://middlemanapp.com/ (Ruby) http://gohugo.io/ (Go) https://github.com/getpelican/pelican (Python)
When you need to go beyond static sites and take a look at the web frameworks - Ruby on Rails is the obvious one, but I reckon that Meteor (https://www.meteor.com/) could be a good bet now that it has matured. Might save you a lot of time when compared to RoR for certain tasks.
I'm sure many people will tell you about their negative experiences and how writing these kinds of "tests" are slow or misleading or a waste of time. But I would say that deciding what your software does--even in an abstract and gradual fashion--gives you tremendous freedom in knowing that all the other choices are just implementation details of a larger design. (As the parent says, a "lower level of commitment".)
Many of current batch of tools were developed to meet the needs of engineering teams at scale: e.g. Angular @ Google and React @ Facebook. Their heritage is not "hobbyist programmer" friendly. They are great if the hobby is reading about technology. But many many of those opinions embedded in Django and Rails only become natural once a person is deeply familiar with the culture of their communities.
My advice, do the simplest thing that will work and make something. Pick tools that require a lower level of commitment to an overall architecture as the need arises. Stay out of silos and rabbit holes.
Good luck.