WebComponents with XSLT

I’m a sucker for standards. Especially those more theoretical standards: peak theoretical standards era for the web is the era that promised the semantic web; early 2000’s.

Some history

In that time, the first version of this site was built using an XML-based index file, XML files that provided meta data on certain topics and XHTML files that featured the content. With PHP-code to tie requests and responses together, the site was mainly powered by several (big) XSL-Transforms that rendered the pages (it (c|sh)ould’ve been a static site).

Fast forward to today. While WebAssembly is gaining traction, these days the focus is on JavaScript for components. Popularised by frameworks such as React, new elements are defined in JavaScript that can be used in the DOM (the latter is not what React uses btw). The (promoted as) ‘standard’ way to make custom elements is using WebComponents. Yet this effort is driven primarily by Google.

And I’m still closing my ``’s and write `…

Design considerations for murbCMS

:murb:CMS is yet another Content Management System build from scratch by yet another designer. So why do I think this one is different? :murb:CMS is…Note to reader (2010): this year I stopped using murbCMS, although I still sympathize with some of the ideas, maintaining it in PHP consumed too much time and frustration.Standards based (XML, XHTML, XSLT)Light WeightSimple designExtensibleWhat :murb:CMS is not about is webbased editing of documents. Well, it could be, but it will not be my primary target. What :murb:CMS is about is a open flow of information. Connecting seperate files, located anywhere, on basis of their metadata.Currently this idea hasn't been implemented yet. Some problems I still have to work around are:linking external files (can't get it work with the sablotron xslt processor yet)automatic linking based on metadata does not occur yetVisionI believe the web should be a heaven for those in search of information. Some may say it already is, but I believe …