blog.kummerlaender.eu/source/03_result, branch master Static XSLT based implementation of my blog Moved result transformations into "99_result" 2014-07-25T17:22:36+00:00 Adrian Kummerlaender 2014-07-25T17:22:36+00:00 05f5a1a0bc038451b9ebbed01e18680019280afc * otherwise it is not easily possible to add additional datasource layers between the content and result generation level * changed meta url appropriately 
* otherwise it is not easily possible to add additional datasource layers between the content and result generation level
* changed meta url appropriately
Implemented basic article tagging facility 2014-07-24T18:34:09+00:00 Adrian Kummerlaender 2014-07-24T18:34:09+00:00 776c0031c05c8660fee8d1b06a2371cbb43248f9 * articles are tagged by symlinking them to the appropriate "tag" in the "tags" directory * tags are resolved by the article datasource transformation * added tags for the example articles 
* articles are tagged by symlinking them to the appropriate "tag" in the "tags" directory
* tags are resolved by the article datasource transformation
* added tags for the example articles
Added basic article datasource and output transformations 2014-07-24T14:46:52+00:00 Adrian Kummerlaender 2014-07-24T14:46:52+00:00 305eb17cd2d70c2e922b8997ada86b29329d660e * articles contain the handle and date in their file name ** i.e. it is split using XPath string functions ** usage of the ISO date format provides automatic ordering * added some articles from my blog as example data 
* articles contain the handle and date in their file name
** i.e. it is split using XPath string functions
** usage of the ISO date format provides automatic ordering
* added some articles from my blog as example data
Added recursive traversion of all folders in each level 2014-07-23T15:44:23+00:00 Adrian Kummerlaender 2014-07-23T15:44:23+00:00 76b9348d4ba4c856d888b32f31f1fa7d80e35cbf * enables representing the result folder structure in the source ** e.g. the "page.xsl" transformation is located in "source/pages" and the result is therefore written to "target/pages" ** this enables simplification of target metadata as it is now automatically relative to the level * modified page template accordingly 
* enables representing the result folder structure in the source
** e.g. the "page.xsl" transformation is located in "source/pages" and the result is therefore written to "target/pages"
** this enables simplification of target metadata as it is now automatically relative to the level
* modified page template accordingly
Restructured generation logic into separate templates 2014-07-22T19:04:31+00:00 Adrian Kummerlaender 2014-07-22T19:04:31+00:00 a1df0a45a4fafa9142b0b6b7bc5a633dce0c6ad8 * root template iterates through the levels and calls the "process" template for each stylesheet * the "process" template handles metadata extraction and main datasource resolution ** calls "compile" template for generation preparation * the "compile" template resolves the support datasources, merges the final datasource and resolves the target path using additional helper templates * actual generation of the result is preformed by the "generate" template as before 
* root template iterates through the levels and calls the "process" template for each stylesheet
* the "process" template handles metadata extraction and main datasource resolution
** calls "compile" template for generation preparation
* the "compile" template resolves the support datasources, merges the final datasource and resolves the target path using additional helper templates
* actual generation of the result is preformed by the "generate" template as before
Split page datasource entry into title and content 2014-07-20T18:02:55+00:00 Adrian Kummerlaender 2014-07-20T18:02:55+00:00 6265f7f4be3a54a8a27330918c59ef16da458124 * 'h1' node is used as title and any other node as content * modified result page transformation accordingly 
* 'h1' node is used as title and any other node as content
* modified result page transformation accordingly
Implemented new "layered" site generation architecture 2014-07-20T14:44:30+00:00 Adrian Kummerlaender 2014-07-20T14:44:30+00:00 e3b6ddeea3e7fa568f1d9ecd1fbbed4773702fe4 * "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 
* "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