Xanjax has now morphed into a client side content managment system. The core code size is still only 10K uncompressed!
As you may remember, Xanjax started out just being an XHR/AJAX navigation/history framework. It all came about as a bit of a surprise after I wanted to create programmable menus, which I decided on using JSON for. While I was nutting this out, I had something of an epiphany leading me to a very compact method of processing JSON objects, which in turn led to the CMS template support that Xanjax now offers.
This should be very useful to web designers converting static websites into dynamic ones, and also to organisations needing to host as cheaply as possible because server load is outstripping revenue growth. By processing client side all content associations, or contexts as I call them, the web server only has to serve files, which is very efficient. Client Side CMS should outperform Server Side CMS dramatically on low end servers, and due to a reduction in caching granularity there should be an improvement even on high end servers.
I already have enhanced SEO/Accessibility degradeability working on the templated content, using a supplementary PHP module. This will be available for release very soon, and it simply processes the same JSON format template file. This means you can have SEO readable content with no additional design effort.
Not everyone will be comfortable at first with JSON template files, but I can promise that the efficiency is worth the initial struggle with JSON syntax. You only need a few days to get over the unfamiliarity. I have kept the template keywords as simple as possible consistent with flexibility. Templates can be nested, so there should not be problems with scalability. Look at the commented root.ctx file in the Xanjax sitekit for more information, and for an output example navigate to json contexts (#contexts.xml) in the sitekit.
Many thanks for the post. I appreciate it. You have a very nice site.
finally i find something that i want to know..