Hi Jakub,

> The problem with Web components is that they are JavaScript feature. So
> the page that now works without JavaScript will depends on JS to function.

This is fair, but note that my suggestions are all
backwards-comparible-ish, rendering as plain text when Web Components
are not supported / have no JS.

Still, the point taken!

> If you like custom components maybe a better idea would be to create:
>
> XML file and XSLT file that will transform the XML to HTML in The browser. You
> can often see this on RSS feeds. Like on my website:

XSLT is being phased out by Chrome, unfortunately. But yeah, this would
be a nice option otherwise. I mean, XSLT can even select and transform
arbitrary text, which is like a superpower for otherwise
no-text-selectable static HTML!

I think that sticking to plain 3.2+ HTML is the best option for
now. Thanks y’all for convincing me!

Best of love,
--
Artyom Bologov
https://aartaka.me