Well, I pushed a cset, that merges all relevant layout and Jekyll code into `/community-news.html` now. This is now the only file to work on.
Yes, I thought of the Wiki extension https://www.mediawiki.org/wiki/Extension:RSS and replacing the news section by the line:
<rss max=3 highlight="GNU Octave news">https://www.gnu.org/software/octave/feed.xml</rss>
Ah okay, I didn't know of that mechanism. I documented it inside `/community-news.html` now.
For Jekyll it is no problem controlling which news (Jekyll jargon: "posts") and how many (currently 3) are displayed. There is a feature called "categories". See for example the post of the current release:
There "categories: news" is currently used for all news. We can define, that less important news, that should definitely not be shown in the GUI, must have "categories: other", or alike. I updated the `/community-news.html` to only consider posts of "categories: news".
Yes, only the "id" naming convention differs between the versions. But there is nothing to worry about. Jekyll produces entirely consistent and valid static HTML5 markup. If that id change affected any links, they would have been updated as well. That is what I like about Jekyll.
I provided an idea of a Makefile for automating deployment, but it will still require you to authenticate with the Savannah server.
|Free forum by Nabble||Edit this page|