About this website

It uses a mix of very lotech and hitech web development stuff, for example the navigation menu is rendered through fancy indexing, while this text was written in an opml file, which is dynamicly transformed into html using xslt.

The Opml file was created with my opml outliner script for VIM, which really rocks...

How does it work?

Well this page is rendered through Apache's fancy-indexing mechanism.

This means that the menu you see on the left is the actual folder structure in which this page resides.

Because of this, it's very simple to create a new page, just add a folder/file through ftp/ssh and it will appear automaticly in the website.

When you view a page, a CGI script is started which searches the current folder for a file called 'content.html' and/or 'content.opml'. If a content.html file is found and there's no content.opml file, the html file is shown. If there's only a content.opml file, the CGI script will read it, and apply some xslt templates to render it to html. The script will write the result back to the requesting client, and will also try to write the result to a content.html file (note: this will only work if there is a content.html file present which is writable for the webserver).

The next time a user requests the page, the CGI script will compare the modified times of the content.opml and .html files, and if it's the same, it will return the .html file, and skip the xslt-transform, functioning as a simple more or less automatic caching system.

More about OPML

this is just a testfile, to see if everything works.

at the moment the script has some extra functionality over standard opml, namely the abbility to render url's and files.

 

examples

a text

 

another outline

again some text

blabla

rewretret

 

a link [slashdot.org]

 

same link [slashdot.org]

and again some text

same link [slashdot.org]

long link [slashdot.org]

 

a file

file: README.txt

 

and more

sure




private parts