3 ms·
We use server-side XSLT at work. We use it as a file based CMS. Our XML is an HTML-abstraction and transforms to Bootstrap. Site has ~12000 single pages. While
by donum 10y ago
We use server-side XSLT at work. We use it as a file based CMS. Our XML is an HTML-abstraction and transforms to Bootstrap. Site has ~12000 single pages.
While I love it, I always wonder if others might think I am crazy.
- tannhaeuser 10y agoOn HN (ycombinator and all), perhaps it helps to point out that DSSSL, XSLT's precursor, is Scheme-based ([1]). [1]: https://en.wikipedia.org/wiki/Document_Style_Semantics_and_Specification_Language https://en.wikipedia.org/wiki/Document_Style_Semantics_and_S...
- techdragon 10y agoI don't think your crazy, in fact I've gone looking for such systems in the past while researching static site generators and wanting a more universal solution to let me pull in remote content as xml and json. I would love to hear more about the system you work with.
- donum 10y agoWe're running XSLT 1.0 on Apache Cocoon. Within the abstraction, each of our "Elements" has his own XSL stylesheet containing the whole transformation of it. So for developers, it's easy to navigate the code. All elements are compatible with each other. We've a task running in the background that groups all element into a single XSL stylesheet. Within Apache Cocoon, you can setup a transformation pipeline. The "elements" will be applied in one step, other steps take care of i18n, i10n and "custom pages"/widgets. Our documentation is written in that setup, too. We've also setup automated tests for our ~60 custom written EXSLT functions.