aboutsummaryrefslogtreecommitdiff
path: root/source/03_merge/timeline.xsl
AgeCommit message (Collapse)Author
2019-04-13Remove newly extracted featuresAdrian Kummerlaender
i.e. Overview is now a mostly pure aggregator again. The new commit / blip feature is now maintained in `blip.kummerlaender.eu`.
2019-04-13Replace commit feed aggregation with manual importAdrian Kummerlaender
This is the starting point for extending _Overview_ to support various types of recent updates (i.e. not just blog articles and commits over a certain message size). While direct fetching and rendering of markdown-formatted Git commit messages is an attractive concept, this new approach should be much more flexible. As a side benefit commit entries can now be edited and expanded compared to their fixed Git reference. e.g. retroactively expanding upon older commits or adding example media that doesn't strictly belong inside the actual commit message.
2015-09-06Adapt commit selection to cater to non-list based commit messagesAdrian Kummerlaender
2015-01-10Tweaked commit selection and added `ConstList` to repositoriesAdrian Kummerlaender
* a commit must now have at least three list nodes to be selected for inclusion into the list of latest commits
2014-10-29Fixed commit timeline sort orderAdrian Kummerlaender
* the commits were only sorted by date and not by time
2014-10-24Added timeline ATOM feed and removed XHTML targetAdrian Kummerlaender
* moved repository feeds to `repository` directory * replaced paginated XHTML timeline target with and ATOM feed ** removed `paginated_timeline.xsl` transformation including the `04_meta` level ** removed CSS and master stylesheets * added title, url and commit count meta data to `meta.xml` * expanded ATOM feed URLs * timeline feed has an upper limit of `commit_count` items ** repository feeds have the same limit because only `commit_count` commits of every repository are fetched in the first place
2014-10-21Added message content based timeline selection criteriaAdrian Kummerlaender
* only commits with equal to or more than two content nodes are included into the timeline ** this is very specific to the way I write commit messages ** it may not be a sensible selection criteria in all circumstances * this was changed with the aim of only including interesting commits in the timeline
2014-10-17Added basic commit timeline aggregator implementationAdrian Kummerlaender
* another application based on StaticXSLT * git is instructed to export XML through a special log format definition * the commit messages are processed as Markdown * currently implemented result views are commits-by-repo and a paginated timeline of all commits in every repository * repositories to be read have to be defined in the `repositories.xml` file in the `00_content` level