Yes, even if my last post was a bit of a contradiction, some new and interesting ways forward for xSiteable seems to resurface these days. I'm going to have xSiteable split in three distinct projects in the future;

• xSiteable Core : pretty much as the XSLT framework it is now (er, as in the 0.9 series, which will be release "some time soon" ...)
• xSiteable Cache : Various cache machines that will work with xSiteable, creating a fully dynamic CMS system, where if a page gets added or changed the cache will recompile it for you simply by refreshing it through the browser. (Think JSP recompile) The first cache machine offered (as in "out of the box") will be PHP, and Asbjorn has been sniffing at a .Net version, and anyone can contribute their favourite technology if they like.
• xSiteable Content Editor : As it says, a content editor with a web interface, works as a plug-in to Core, and will - together with Cache - create a full CMS system. This module is very similar to the PHP Admin application that was shipped with xSiteable up and including version 0.88.

The idea here is that you add on each module to create a more complex system as needed. If a static page compiler is what you need, then settle with only Core. If you want a dynamic site where you easily can change something, and it is dynamically updated, you add on the Cache. And if you want a remote content editor, chuck the Content Editor on top of the Cache (which already sits on top of Core) to have all the whistles and bells you like. Extensions to this Content Editor is things like multiple users.

The two reasons all this has come up now is that 1) I might have a work-related project that seems to fit the xSiteable bill, and 2) interest in xSiteable from various users have crept up. I'll update here as things move along (it has a current "to the end of the year" scope), but if you have any ideas and such, please let me know.