Pure CSS, XML, and XSLT

[sjehuda]

Description

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.

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

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

[sjehuda]

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

[gordonwoodhull]

We aren't likely to change our pipeline to use XML and XSLT, as we're quite invested in HTML.

However I think in principle you could create a Quarto custom format that outputs any XML format you desire.

Quarto already supports DocBook output, which may or may not satisfy your requirements.

See e.g. https://stackoverflow.com/questions/73652391/create-custom-xml-output-from-pandoc

[sjehuda]

Gordon.

Thank you for the references.

Yes. I realize that Quarto and other publishing platforms are invested with HTML, because this is what we were influenced to focus on.

Currently, My project Slixfeed (XMPP news service) supports this concept, and once Rivista (XMPP publishing system) would do too, I would inform you.

I think, that harmonizing theming for publishing platform should be one of our main objectives.

Not only would we have less dependencies, and therefore reduce maintenance costs, but we would also be able to have a common resource to share themes, which would be even more beneficial.

Today, the vast majority of themes for "WP" is now obsolete due to arbitrary changes by "WP", and I sense that many people are now informed of the issues of platform specific themes, and practicing Atom Syndication Format in conjunction with XSLT is probably what we want.

While the changes of "WP" are made unfairly, it could be, for other platforms, that some would have to make "breaking changes", and the practice of XML and XSLT (both are standards) would be of an advantage to subdue that issue.

Subsequently, also the maintenance of themes would be reduced.

Hence, I diligently petition projects to utilize Atom and XSLT.

Post script

In addition to all of it, the fact that big organizations try to censor and sabotage XSLT should be an incentive to consider XSLT.

While they may be able to sabotage XSLT on client side, they can not sabotage server-side software neither RSS Reader and other software.

Please see the articles that are attached to the Greasemonkey extension (click the "rescue wheel" icon after you open an Atom/JSON/RSS/Twxtx page).

https://greasyfork.org/en/scripts/465932-newspaper-syndication-feed-reader

[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 Quarto 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