| Age | Commit message (Collapse) | Author |
|---|
|
* e.g. removing the target directory before each regeneration and symlinking CSS files
** this will be extended to include ressource directories and so on
* renamed "formatter.xsl" stylesheet to "helper.xsl" as it now includes various helper templates
* finally checked the main CSS into the VCS
|
|
* expanded "02_data/pages.xsl" transformation to include pages in subfolders
* "03_meta/categories.xsl" transformation generates a categorized view of all pages simmilar to the one provided for tags by "03_meta/tags.xsl"
* "99_result/category/category.xsl" transformation generates category overview pages
* added basic project related pages inside the "projects" category
|
|
* implemented language selection for automatic syntax highlighting
** language selection requires the language to be used to be passed as a class of the code element
** kramdown enables easy definition of this class attribute
* kramdown offers more functionality such as table and class attribute support
* updated all articles accordingly
|
|
* directly pass the executable including its arguments
** the "highlight.sh" proxy script is no longer required
* this was made possible by a recent commit to InputXSLT
|
|
* replaced "pre" node returned by the hightlighting script with an unstyled one
* "pre" style is now declared in css
|
|
* disable indentation in both the page and datasource master stylesheets
** indentation was interfering with correct output of formatted code
* simplified call to formatter helper template
|
|
* i.e. inline code is automatically highlighted using an external syntax highligher
|
|
* the output node is defined in both the master and datasource transformation
** i.e. they do not have to be defined in transformations making use of one of these transformations
|
|
* this is needed for the implementation of a article datasource grouped by year
** this in turn is needed for the archive page template
* modified tags meta transformation and article result transformation accordingly
|
|
* xalan and/or InputXSLT namespace should only be included when they are actually required
|
|
|
|
* contains tags and their articles but no further article data
* the unaugmented tags datasource is merged with article data on the metadata level
|
|
* this was done to simplifiy support data queries while resolving the main datasource
|
|
* 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 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
|
|
* 'h1' node is used as title and any other node as content
* modified result page transformation accordingly
|
|
|
|
* "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
|
