i.e. Overview is now a mostly pure aggregator again. The new commit / blip feature is now maintained in `blip.kummerlaender.eu`.
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.
See 76f8676 @ blog.kummerlaender.eu
Only seems to be a problem on some browsers such as Edge. Nevertheless this patch fixes it for all of them.
The _more_ link symbol is displayed with an ugly blue background in recent versions of Microsoft Edge (see MS issue 11635143).
* navigation now aligns itself properly on smaller screens * increased line height for both the article teasers and commit message list items
* removed _justify_ text alignment for list items
* fixed menu list padding to prevent premature line wrap
* `id` has to contain a valid URL ** i.e. it now contains the same value as `link/@href` * `author` was missing
* added overview commit count parameter * added `key` subdomain link
* article continuation links are injected into the summary paragraph ** changed article summary transformation `02_augment/articles.xsl` accordingly * added CSS styling based on my blog header style
* the first paragraph of the three latest articles of my blog are now displayed on the overview page * feed is fetched via `curl` in `01_raw/article_feed.xsl` ** as with all commit feeds the article feed is processed further in the `02_augment` level ** the count of articles to be displayed is defined in `00_content/meta.xml` as `article_count` * CSS was updated to correctly display the article summary
* project page urls are maintained in `00_content/repositories.xml`
* CommitLog will be used as the new overview page of my [website](http://kummerlaender.eu) * displays the five latest commits and their message ** links to the full feed * I plan to add the latest blog article and a subdomain overview in the future
* I just realized that repository specific commit feeds are already provided by both CGit and GitHub ** i.e. I made the mistake of not checking if my current system already provides the required functionality when I wanted to aggregate my commits and found this to be a use case for StaticXSLT * feeds are fetched via `curl` ** this will be a local request in production ** the messages are still cleaned using `sed` and transformed into _XHTML_ using `peg-markdown` * instead of reading a customized Git log output CommitLog now simply transforms CGit ATOM feeds using identity templates ** this requires ATOM namespace removal which is implemented in `utility/remove_namespace.xsl`
* 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
* feed contains all commits of the respective repository which are included in the timeline view ** i.e. currently up to 20 * this transformation is based on the one used to generate the blog article feed * the goal of this project is to generate various feeds to be included into [my blog](https://github.com/KnairdA/blog.kummerlaender.eu/)
* added `meta.xml` source document defining the mirror urls to be linked to
* added CSS style based on my personal blog ** modified master and stream templates accordingly * added date-time, repository name and commit hash output * removed single-repository log export as it is not the purpose of this application
* 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