In comp.sys.raspberry-pi, Axel Berger   wrote:
[html design in a text editor]
> It has always been and still is the easiest and most efficient way. GUI
> bloat users wouldn't know how to dream about all the automation a good
> editor provides.

I code my web pages from vim, but I also use templates, which provide a
good automation outside of my editor.

> My favourite example is scripting a graphical page, e.g. a map. Agreed,
> it would be faster and easier to place graphic elements using a mouse,
> scripting does take longer. But when done I say "Alright, that's fine
> now. Now do the other 4999 pages exactly the same please" press  and lean back.

No problem. Make it a React page and just JSON to supply the differences
for the other 4999 pages. That's the 2020 way to do it, not necessarily
with React, but possibly some other "SPA" system:

https://en.wikipedia.org/wiki/Single-page_application

Even before "SPA" was an idea, I was writing sites that used separated
template and content, just stitched together on the server side, circa
1999. Nor was the idea new with me.

Elijah
------
then, and now, avoids using javascript as much as possible

--- SoupGate-Win32 v1.05