| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* stream view is still available from the archive to preserve backwards compatability
* reduce layout / styling differences between kummerlaender.eu and this blog
|
|
Many websites employ the [MathJax](https://www.mathjax.org/) library for dynamically rendering LaTeX math expressions on the client side. I expect to require support for doing just that in the future. But as with syntax highlighting I am of the opinion that this kind of stuff should be performed once during site compilation instead of wasting ressources by forcing each client to do this job for every single page request.
Luckily there is a [MathJax-node](https://github.com/mathjax/MathJax-node) module that allows using the _MathJax_ library on the server side.
This commit adds support for rendering math expressions written in Markdown respectively LaTeX as follows: `$$1 + 1 \neq 0$$` on the server side.
This required the introduction of a new `math_highlighter` helper template in `formatter.xsl` based on the `tex2html` utility provided by _MathJax-node_. This formatter is matched against the (Markdown parser generated) `script` node in `formatter.xsl`'s _embellish_ mode. The HTML rendering of the expression is then embedded in a `p class="math"` node. This explicit labeling allows `master.xsl` to include the `math.css` rules only for pages that actually contain math expressions.
Note that the XHTML rendering utility stylesheet `xhtml.xsl` currently adds a XML comment to each `span` node. This is a workaround to prevent _Xalan_ from collapsing "empty" `span` tag pairs into single nodes which otherwise leads to rendering errors as it is not valid HTML and is interpreted as a wrong tree structure by the browser.
Note that the CSS rules declared in `math.css` are explicitly not part of the MIT licensed part of this repository but where generated by _MathJax_.
As there is currently no _productive_ content making use of math expressions a demo page is available under `page/math_test/`.
|
|
* 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_
|
|
* extracted navigation and tag list style into `buttonlist` class
* navigation is now aligned left and non-overlapping on small screens
|
|
* 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
|
|
* both the CSS and master template markup contained cruft from the previous blog version and its slightly different layout
* removed unnecessary distinction between footer and its _taglist_ as the old footer element is now only a _taglist_
** promoted previous `last_line` to `footer` as it is the actual footer
* unified the different list styles as much as possible
** e.g. introduced new `topline` attribute instead of declaring the title-separator line for each style separately
** removed `taglist` class by declaring its rules directly in the `tags` id
** removed now unnecessary `archivtag` class
** introduced `sparselist` class which enables list such as the one contained the latest microblog entries to have extra padding
* merged `list_tags` helper template into primary master template
** this separation was not only unnecessary but decreased the readability as it provided no real encapsulation
|
|
* eliminated `last_item` list item class by fixing its padding
|
|
* this was done to match the recent extraction of the generic static site generation framework into a separate project
|
|
|
|
* 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
|
|
* modified master transformation accordingly
* fixed small syntax and grammer error in about page content
** missing dot and missing "and"
|
|
* there is no reason for generating absolute links as the resulting pages will be served on their own domain
|
|
|
|
* 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
|
|
* wrap text in "xsl:text elements to clean up the output
|
|
* 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
|
|
* 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
|
|
* atom was choosen in favor of RSS mainly because it is not easily possible to generate the required RSS timestamp in xalan-c (day of the week required)
* modified master template accordingly
|
|
* returns "Start" for the first page instead of "Page 0"
** this corresponds to the navigation
* changed "Start" navigation link in master template
* i.e. the index page is named "0", server config will have to be changed accordingly
** thought about generating it as "index" directly
** while this is possible using the XPath evaluation functionality of the target meta attribute the lack of a if-statement in XPath 1.0 would require a very ugly workaround (e.g. the answer to http://stackoverflow.com/questions/971067/is-there-an-if-then-else-statement-in-xpath)
|
|
* stream transformation is iterated over the paginated article datasource implemented in 854eab6
* stream template contains navigation generation for traversing the article stream
|
|
* xalan and/or InputXSLT namespace should only be included when they are actually required
|
|
* 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
|
|
* "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
|
