I understand that there were a few more questions on this subject, and the general consensus was to use your language for managing XML. However, this decision does not entirely correspond to my circumstances.
Firstly, the scope of the project: We want to develop platform-independent e-learning, currently a bunch of HTML pages, but as it grows and develops, it becomes difficult for them to maintain. We already have about 30 modules with 10-30 HTML pages each, and this is constantly growing.
Idea: Have an XML file + Schema preview module, then create some XSLT files that process XML in eLearning modules. XML to HTML via XSLT.
Why: We would like flexibilty to easily reformat the content. I understand that CSS is a viable alternative here, especially to visually alter the appearance, but we may need a little more energy than that and get to the rebuilding of the pages. If we decide to change the page layout or functionality anyway, I assume that changing the "shared" XSLT files will be easier than updating the HTML files.
Depending on some of the βparametersβ, we can display completely different page layouts / structures, above and above what CSS can do. Can XSLT accept QueryString parameters? Not sure.
Now all this should be platform independent and be able to run "autonomously", i.e. without a server that controls HTML, so server technology is out of the question (C #, PHP)
Negative values ββthat I have read so far for XSLT:
- Overhead? Itβs not entirely clear why ... is it the computational power needed to convert to HTML?
- Hard to know
- Best alternatives
Now I would like to know for sure:
- Are there any viable alternatives for this βstand-aloneβ?
- I think about it right.
- Do you have any tips or alternatives.
EDIT: With or without XSL, CSS and jQuery will be a very important part of the solution we are developing. Tidy up (sloppy engraver!)