Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
* XHTML elements "h2" and "h3" are replaced with "h3" and "h4" respectively
** modified all existing contents accordingly
** this was done to avoid the gap between the primary heading and subheadings in the markdown depiction of the contents
* fleshed out the InputXSLT project page with further information
|
|
* basic legal information is provided in English
** further information is provided in German of a separate page
|
|
* _obfuscated_ addresses used "punkt" and "ät" instead of "dot" and "at" to symbolize special characters
* cgit link was missing a closing colon
|
|
|
|
* fixed prettylist CSS to work in both WebKit and Gecko
|
|
* recent changes in InputXSLT revamped "external-text-formatter" into a general "external-command" function
* this changes were implemented to enable e.g. symlinking and copying files from the source to the target
|
|
* this should be the last one, as the remaining articles are not really worth preserving
** at least that is my current assessment
* updated contact page with actual content instead of filler 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
|