aboutsummaryrefslogtreecommitdiff
path: root/utility/master.xsl
AgeCommit message (Collapse)Author
2014-08-11Implemented page categorization functionalityAdrian Kummerlaender
* 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
2014-08-10Minor improvements to article, stream and master transformationAdrian Kummerlaender
* wrap text in "xsl:text elements to clean up the output
2014-08-10Switched content formatter to kramdownAdrian Kummerlaender
* 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
2014-08-06Improved automatic source code highlightingAdrian Kummerlaender
* 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
2014-08-04Changed base url and url schemeAdrian Kummerlaender
* 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
2014-07-28Implemented basic atom feed transformationAdrian Kummerlaender
* 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
2014-07-27Improved article stream title-text templateAdrian Kummerlaender
* 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)
2014-07-27Implemented article stream generationAdrian Kummerlaender
* stream transformation is iterated over the paginated article datasource implemented in 854eab6 * stream template contains navigation generation for traversing the article stream
2014-07-26Removed unnecessary namespace declarationsAdrian Kummerlaender
* xalan and/or InputXSLT namespace should only be included when they are actually required
2014-07-26Added meta datasourceAdrian Kummerlaender
* 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
2014-07-26Included unaugmented tag datasource into the page footerAdrian Kummerlaender
* 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
2014-07-25Changed master template text elements to EnglishAdrian Kummerlaender
2014-07-25Moved result transformations into "99_result"Adrian Kummerlaender
* otherwise it is not easily possible to add additional datasource layers between the content and result generation level * changed meta url appropriately
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