xSiteable Frequently Asked Questions !

What is it?

xSiteable is a stand-alone package for site compilation, prototyping, designing, tinkering or / and maintenence.

Which means?

That you install the package, edit your content in simple content text-files, compile it easily, and deploy it where you need it.

So, it is a dynamic thing?

No, it is a compiler. You run it on your machine, and deploy the result when ready, or you install it on your server and have it compile your site at intervals, or use the administration tool to compile pages remotely.

Can it make dynamic stuff?

Yes, you can output any type of files you like, even if HTML is the default. You can produce ASP, PHP, JSP or whatever you like.

What's the license?

BSD license.

What platforms are supported?

As of version 0.8, we've got support for Windows2000/XP/NT/98+ (with binaries), and Linux/Unix/*BSD (source).

What parts of XTM and Topic maps are you using?

At this stage, not as much as one could possibly dream of. :) There are things I want to move into a different space, like FAQ and specification items are now occurrences, but I want these to become topics for better searching and flexibility. And on the same note, some parts of the make-system uses <resourceData> with XML-elements to describe menues and content. This should be outsourced into a data XML file instead.

We now use scope to differentiate between the various roles of an association, making it possible to create any ontology.

There is no validation of the XTM file, so it is assumed that the XTM is correct.

All associations are two- or three-way and grouped.

The structure implying superclass-class relationships is called group-subgroup. We should probably use the same ontology as Omnigator and TM4J so that Topic maps are interchangable.

More freedom against ontologies; the current are too strictly bound to xSiteables purposes.