aboutsummaryrefslogtreecommitdiff
path: root/source/02_data
AgeCommit message (Collapse)Author
2014-07-26Removed unnecessary namespace declarationsAdrian Kummerlaender
* xalan and/or InputXSLT namespace should only be included when they are actually required
2014-07-26Added descending sort by date to article datasourcesAdrian Kummerlaender
2014-07-26Added unaugmented tags datasourceAdrian Kummerlaender
* contains tags and their articles but no further article data * the unaugmented tags datasource is merged with article data on the metadata level
2014-07-25Added root variable to datasource templateAdrian Kummerlaender
* this was done to simplifiy support data queries while resolving the main datasource
2014-07-24Implemented basic article tagging facilityAdrian Kummerlaender
* 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
2014-07-24Added basic article datasource and output transformationsAdrian Kummerlaender
* 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
2014-07-20Split page datasource entry into title and contentAdrian Kummerlaender
* 'h1' node is used as title and any other node as content * modified result page transformation accordingly
2014-07-20Removed unnecessary extension distinction from page datasourceAdrian Kummerlaender
2014-07-20Implemented new "layered" site generation architectureAdrian Kummerlaender
* "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