i.e. Oswald for titles and Vollkorn for text. Including some markup changes to accomodate them. New approach to aligning article-info to title should work independently of the selected font.
Not worth the effort considering it is not used at all.
* removed background image and as such it's fixed pixel width ** i.e. the layout is now completely dependent on the basic font size and scales accordingly * revamped master template and CSS to allow for nodes with varying lengths instead of truncating everything depending on the background width * increased font size of tag and archive pages * increased overall line height to improve readability * improved CSS to e.g. make use of `last-child` instead of adding `last` classes during static site generation * removed _microblog_ entries from archive as I have more or less stopped using _Twitter_
* e.g. article and tag support data is now fetched through direct _XPath_ template applications ** this required the introduction of a special `resolve` mode to prevent interaction between support and main content resolution ** in most cases arguments had to be wrapped inside helper constants to enable selection of e.g. article support data via the `@handle` attribute using the current elements `@handle` attribute * analogously to the recent changes in _StaticXSLT_ this commit aims to improve the XSLT code style used in generating this static website
* the former also works when CSS is not supported while the latter leads to unseparated tag links
* all datasources are generated as namespace-less XML * the resulting documents have to define the XHTML namespace ** i.e. the article and page contents have to be copied into the XHTML namespace * implemented XHTML copy helper templates * modified page templates accordingly * defined XHTML namespace in the master template
* there is no reason for generating absolute links as the resulting pages will be served on their own domain
* [isso](http://posativ.org/isso/) is a Disqus like commenting system written in Python ** self-hosted i.e. no privacy implications ** lightweight and provides all the features I require for this blog * I thought about implementing a commenting system in InputXSLT but sadly I just don't have the time to think of and implement a reasonable XSLT based solution ** maybe a simple REST service for pushing XML from the client into article-dependend comment directories can be implemented in the future * added basic CSS styling for isso comments simmilar to how they currently look in the old Symphony CMS based blog
* "01_files" contained a single "source" transformation which listed the contents of the "00_content" level ** this was unnecessary as the base "list" transformation already lists the contents of all levels * added new "expression" mode to datasource meta tag processing in the task processing transformation ** this expression modes allows for the evaluation of arbitrary XPath statements *** e.g. a query to the results of "list.xsl" * modified base transformation datasource structures to include the level and meta tree * modified all existing content transformations to query the level-tree instead of the deprecated "source.xml" ** i.e. XPath statements ** the main change is that directories are available as "directory" nodes instead of nodes named by the directory name * these changes where implemented to simplify the architecture and to increase flexibility
* modified all transformations requiring the author name accordingly
* transformations contain one or more "datasource" meta nodes ** these nodes define the required datasources ** up until now it was required to define the whole path to the file to be loaded * the implementation of directory linkage in b942f8e removed the underlying need for providing the source / target prefix ** this commit now updates the generation transformations to match this change *** this simplifies the datasource definition process for the end-user *** additionally it makes the target / source directories easier to maintain * changed cleanage task implementation to remove the whole directory and recreate it from scratch ** otherwise directory linkage and in turn the whole generation failed when the target directory did not exist in the first place * removed task reordering in the process transformation ** tasks are now processed exactly as they were scheduled ** this was changed so that e.g. the "00_content" directory is linked before the first datasource is required
* while articles can be ordered by e.g. date there is no useful order for the pages in a given category ** this is why the order of pages on category overview pages is now random (in each generation)
* wrap text in "xsl:text elements to clean up the output
* 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
* base url is now a local webserver for more realistic testing ** i.e. otherwise the atom feed is not served correctly * article, page, tag and stream pages are now generated as "index.html" inside appropriately named directories ** this is needed for pretty urls that actually work
* 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
* stream transformation is iterated over the paginated article datasource implemented in 854eab6 * stream template contains navigation generation for traversing the article stream
* 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
* dates in lists such as the tag list are displayed in plain ISO formatting ** this way the article titles all start at the same horizontal offset which I find much more visually pleasing * dates on article pages are formatted in the English way instead of in English but formatted as in Germany
* merges the content of the "00_content/meta.xml" file with additional data such as the available tags * simplifies providing a basic datasource to every result transformation * modified master, article and tag page template accordingly
* the master template generates a list of all available tags into the footer ** this currently requires the unaugmented tags datasource to be included into every template making use of the master template
* otherwise it is not easily possible to add additional datasource layers between the content and result generation level * changed meta url appropriately