endoflife.date as Custom Search Engine

[MitchTalmadge]

Most, if not all, modern web browsers support custom search engines. I would like to be able to add endoflife.date as a search engine. For example, I may type eol php and it would immediately bring me to the php page, or it would bring me to a search results page; either is fine.

Example of adding the search engine:

A workaround is to set the search engine to https://endoflife.date/%s so that eol php becomes https://endoflife.date/php. However, this can often result in a 404 page.

Thanks for your consideration.

[captn3m0]

We use lunr.js, and our theme doesn't support a "search results" page

All search results are shown in an auto-complete style interface (there is no search results page).

I think this can be hacked within this project as a custom page, but would be nicer/easier if this is added upstream. cc @mattxwang

[Matheus-RR]

+1 on this. We consume the endoflife.date API programmatically and the slug matching is the biggest friction point for our users too.

The https://endoflife.date/%s workaround breaks because product slugs aren't always intuitive — nodejs not node, amazon-eks not eks, visual-studio-code not vscode. A search/redirect endpoint that handles aliases would solve both the browser search engine use case and API discovery.

Something like GET /search?q=node returning a redirect to /nodejs (or a disambiguation page if ambiguous) would work for custom search engines and be useful for tooling too. The existing /api/all.json endpoint could power a lightweight fuzzy match on the server side.

Practically, even just adding _redirects or alias mappings for common alternative names would solve 90% of the 404 problem without building a full search feature.

[captn3m0]

Umm, we want to have intuitive slugs. endoflife.date/node redirects to /nodejs, and so does /eks. We do not list vscode.

We already use _redirects heavily.

Is this comment AI generated?

[Matheus-RR]

Understood, thank you.

[captn3m0]

Aside: I see you're trying to build releaserun on top of our API. Please provide attribution, and perhaps the release-data repo might be of help: https://github.com/endoflife-date/release-data/ And if you'd like to contribute - PRs are welcome.

[Matheus-RR]

Thanks! We have added attribution to pages which use endoflife.date data. Appreciate the help