Open captn3m0 opened 5 years ago
If we add a latestReleaseDate
alongside latest
in the build, and use that as the date of the release, it would work?
The issue is in case we add a release a few days late, and the release would show up with a publication date in the past, and feed readers may ignore it?
So Jekyll multi-layout is still an untackled problem: https://issuehunt.io/r/jekyll/jekyll/issues/3041
Pick this if you know a little of Ruby. The intent here is to create a RSS file for each product, similar to how we do it for JSON files. RSS Feeds are easily generated using Jekyll, however the default is to create an RSS feed of all pages, which is not what we want.
Each RSS file should include all the dates known about that product. If there isn't enough information to create a RSS file (such as no dates on /iphone) - use a feed: false
to turn off the RSS for that page.
Keep the page URLs as simple as possible: endoflife.date/feed/php.xml
for eg.
Add a link to the RSS file in the product page as well, as the corresponding link in HTML so that anyone can subscribe to the feed easily.
Since RSS feeds are "notifications", we should provide a 7-day, 30-day, 90-day entry for all items. So if you subscribe to the PHP feed, you should get notified on the following dates:
(And similarly for the remaining PHP versions).
Make sure you read through CONTRIBUTING.md to understand the file structure. Also, please read through the HACKING.md file to setup the project locally. Reading these will help you get onboarded faster and make sure that your PR sees a speedy merge.
And finally, we have a very helpful guide for new contributors during Hacktoberfest as well.
There is a very similar issue for WebCalendar support that you might be interested in: https://github.com/endoflife-date/endoflife.date/issues/59
I someone is interested by this feature an example of a Jekyll Generator is available in #2080.
Assuming you subscribe to the PHP RSS Feed. I would want to get notified on the following scenarios:
RSS Spec allows publication with dates in the future, but it is left to the tool:
It would be better to hide the element till the
date>=today
for that item, in which we case, uncomment it.With that in place, (1) should be doable. But how do we get to (2)?