This example illustrates an easy way to use XIML based interface with any web application.

In this case we used a just-released Google App Engine to create a data manager and that data is used by the XIML site for display.

see it at http://ximl-demo–pub-alb.appspot.com/

We are continuing our skin creating initiative.

At the moment you can see skins for

flickr photoset:
http://www.ximl.com/site/flickr_api_demo

youtube feed:
http://www.ximl.com/site/youtube_api_demo

Word Press skins:
http://www.ximl.com/site/wp,
http://www.ximl.com/site/wp_skin3

If you would like to see how (very easy) it is to create such skins, have a look at the source code for all this sites:

flickr photoset:
configuration XIML -
http://www.ximl.com/sites/flickr_api_demo/conf.xml

youtube feed:
configuration XIML -
http://www.ximl.com/sites/youtube_api_demo/conf.xml

Word Press skins:
configuration XIML -
http://www.ximl.com/sites/wp/conf.xml,
configuration XIML -
http://www.ximl.com/sites/wp_skin3/conf.xml

Deep linking to internal pages within XIML site is easy to use:
ximl.com/site/{site name}/{page name}
For example:
http://ximl.com/site/ximl_tabs1/tc_ft will go directly to the features page (tc_ft) of site ximl_tabs1.

To link to pages of the main site, use
ximl.com/p/{page name}
For example:
http://ximl.com/p/p_tech_features will go directly to the features page of main site.

To set what page should open on site start, use
<start_page v=”p_tech_about”/> located at /website/config/sys/ in the configuration file.
For example see http://ximl.com/conf.xml


When developing a XIML site, you will normally have many versions of configuration and data files.
The files are backed up in the system.
This files versions represent a history of a site development.
It is possible to see all the development steps for each site.
Site history is available at ximl.com/sitehistory/{site name}.

For example, see http://ximl.com/sitehistory/ximl_tabs1