Replies: 3 comments 3 replies
-
I think re-grouping them under a single hierarchy makes sense (although I'm not sure doing is a pre-requisite to the listed improvements) Overall, I think the content should make it clearer that this is about XSLT and XPath as supported in browsers (since both XSLT and XPath have in the meantime evolved way beyond the browser-supported scope). Should Web/EXSLT be kept around at all? this seems to be specifically about Firefox-supported extensions to XSLT |
Beta Was this translation helpful? Give feedback.
-
I made an inventory: https://docs.google.com/spreadsheets/d/1nwJeXKpyg2lRaQ7dbvh1vnrcCqqxSsg6yTCOlqUwPxA/edit#gid=0 It looks like we should, in addition to the fusion, do:
Of course, we should also: review the articles to make them browser-agnostic (eventually renaming them) and mark what is non-standard with a banner. For page-types, we should create the following specific types:
|
Beta Was this translation helpful? Give feedback.
-
I really like this idea @teoli2003 |
Beta Was this translation helpful? Give feedback.
-
These 4 areas are all about XML manipulations; we should regroup them in one hierarchy and clean them a bit.
XPath is an expression language designed to support the query or transformation of XML documents.
XSLT is a language designed to transform XML documents into other XML documents or formats, such as HTML.
EXSLT is a set of extensions to XSLT.
XML is just a few guides…
Note: there is already an outdated navigation bar in some of these technologies on MDN to link between them:
Regrouping them will allow:
page-type
to these areasAny thought?
If we go forward, I will create an issue with the detailed envisioned structure.
Beta Was this translation helpful? Give feedback.
All reactions