XML (Atom) and XSLT instead of templating engines

[sjehuda]

Good day.

I suggest to produce all files as XML.

• XML (Atom Syndication Format)
• HTML (Transformed XML with the help of XSLTProcessor)
  This would mean, that the whole site be an API.

This is what I intend to do with a publishing platform which I am working on, and this is what I have experimented with a couple of Python projects of mine, and now I am experimenting with project Rivista.

• https://git.xmpp-it.net/sch/publish-happy
• https://git.xmpp-it.net/sch/Slixfeed
• https://git.xmpp-it.net/sch/Rivista

This means that every platform which is also based on XML can have the same theming compatibility with Quarto.

gemini://woodpeckersnest.space/~schapps/journal/2025-07-03-rivista-to-be-atom-based-publishing-system.gmi

---

For processing XSLT, I advise a non "standard" module, because it appears that the big vendors deliberately sabotage XSLT related technologies and components.

• https://github.com/DesignLiquido/xslt-processorprocessor
• https://github.com/Xcential-Corporation/XSLTjs

Observation

https://openuserjs.org/garage/Why_my_script_doesnt_work_with_Firefox#comment-1810ec600fe

[sjehuda]

Probably a better proposal would be to add upon the existing set of files.

That is to add Atom, Sitemap, and Urlset, in order to make portfolio a machine-readable site.

Please read these references.

https://portal.mozz.us/gemini/woodpeckersnest.space/~schapps/journal/2025-07-29-announcing-ace.gmi

https://portal.mozz.us/gemini/woodpeckersnest.space/~schapps/journal/2025-08-10-an-analyses-of-the-benefits-of-ace.gmi