<feed xmlns='http://www.w3.org/2005/Atom'>
<title>blog.kummerlaender.eu/source/pages, branch master</title>
<subtitle>Static XSLT based implementation of my blog</subtitle>
<link rel='alternate' type='text/html' href='https://code.kummerlaender.eu/blog.kummerlaender.eu/'/>
<entry>
<title>Implemented new "layered" site generation architecture</title>
<updated>2014-07-20T14:44:30+00:00</updated>
<author>
<name>Adrian Kummerlaender</name>
</author>
<published>2014-07-20T14:44:30+00:00</published>
<link rel='alternate' type='text/html' href='https://code.kummerlaender.eu/blog.kummerlaender.eu/commit/?id=e3b6ddeea3e7fa568f1d9ecd1fbbed4773702fe4'/>
<id>e3b6ddeea3e7fa568f1d9ecd1fbbed4773702fe4</id>
<content type='text'>
* "source" directory contains layers as subdirectories
** ordered by their name
** e.g. layer 0 is "00_content" and contains the content alongside some metadata
* transformations contained within the "source" layers are processed sequentally
* transformations define their requirements in a "meta" variable
** the "meta" variable is interpreted by the core transformation "generate.xsl"
* requirements are currently datasources and target information
** every transformation may have one datasource of type "main"
*** this data source offers e.g. the option to iterate over it
** every transformation may have a arbitrary number of "support" datasources
*** e.g. "meta" is a support datasource
** the target node may provide a fixed target path or a Xpath to be evaluated
* the result of each transformation is written to the appropriate layer of the "result" directory
* this approach to XSLT based static site generation should be quite flexible and offer good expandability
** e.g. adding new datasource options and types
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* "source" directory contains layers as subdirectories
** ordered by their name
** e.g. layer 0 is "00_content" and contains the content alongside some metadata
* transformations contained within the "source" layers are processed sequentally
* transformations define their requirements in a "meta" variable
** the "meta" variable is interpreted by the core transformation "generate.xsl"
* requirements are currently datasources and target information
** every transformation may have one datasource of type "main"
*** this data source offers e.g. the option to iterate over it
** every transformation may have a arbitrary number of "support" datasources
*** e.g. "meta" is a support datasource
** the target node may provide a fixed target path or a Xpath to be evaluated
* the result of each transformation is written to the appropriate layer of the "result" directory
* this approach to XSLT based static site generation should be quite flexible and offer good expandability
** e.g. adding new datasource options and types
</pre>
</div>
</content>
</entry>
<entry>
<title>Initial commit of basic generator structure</title>
<updated>2014-07-14T18:41:42+00:00</updated>
<author>
<name>Adrian Kummerlaender</name>
</author>
<published>2014-07-14T18:41:42+00:00</published>
<link rel='alternate' type='text/html' href='https://code.kummerlaender.eu/blog.kummerlaender.eu/commit/?id=f39407fd3946c5f3aa7883a1f3cc774ad5f7dd8a'/>
<id>f39407fd3946c5f3aa7883a1f3cc774ad5f7dd8a</id>
<content type='text'>
* including example data and current "/home/adrian" layout
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* including example data and current "/home/adrian" layout
</pre>
</div>
</content>
</entry>
</feed>
