At 35, the web is broken, but its inventor hasn't given up hope of fixing it yet
zdnet.com
zdnet.com
It's important to understand the distinctions between a protocol (HTTP/S, TLS, QUIC) and an encoding (XML, HTML) and a governance structure (or lack of it)
It's important to distinguish between what architects think they are designing as the built environment, and what people actually use space for. And that is true in meat space as well as hyper space.
Otherwise importance is personal. They're important to me as a historical bread-crumb trail. They inform.
Most gopher and wais information emerged into web rapidly. The controls behind the gopher and wais information did not emerge into some new nirvana, web was an access method, overwhelmingly read-mostly.
Look in strict literal terms of course it roots in TBL. You can't deny history. The question is what context that lies in. And the context is that to do HTML and HTTP TBL and his related involved people looked at SGML and other things like the Diamond system from BBN (not for a minute do I think that was the progenitor) or Hypercards. They didn't do web in a vacuum.