Nemo

> Looking at further, I believe you meant having a completely different releaseCycle with ELS in the name Yes, that was the idea. As it stands, the code does a...

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...

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](https://github.com/endoflife-date/endoflife.date/blob/master/_plugins/create-json-files.rb)....

Hard to do at the moment - unless we're translating all the text as well (which needs a lot more effort), plus not every combination in `site.lang` will be supported...

Happy to look at PRs that try to tackle this, but this is low priority for me, especially if the main usecase is improved links (which we work around by...

Thanks, this is something I've also wanted to improve. Perhaps having a guide with screenshots of a sample edit would help? Something that highlights all the clicks and possible edits?...

It depends - if the release information is available somewhere, we can always scrape it. This attempt targets git/github sources, but as an example - we already scrape GKE version...

I might be wrong but the table at https://access.redhat.com/support/policy/updates/errata#Details differentiates between "Extended Life Phase" (the term we're using here), and "Extended Life Cycle Support Add-On" (the part that actually offers...

> we still need a system ltsDate or similar tag or we need to change `lts: true` to `lts: date` which will show when that related lts became active This...