Add landingpage for removed integrations

[ludeeus]

Proposed change

I'm not 100% sure about this one.
On one hand having something, other than the image below is IMO better than having something that does not look like you still are on our site anymore. On the other hand, this adds another list that will need to be maintained for every integration that is being removed, and once it's out why should we care about old links.

Feel free to close the PR if this is not wanted 👍

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logo's and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase:
• Link to parent pull request in the Brands repository:
• This PR fixes or closes issue:

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

[frenck]

The problem with this approach is that this is throwing a 200 status in the end, thus the result is not removed from Google.

[ludeeus]

For that, we can add 301 to the redirect rule

[frenck]

For that, we can add 301 to the redirect rule

That is probably a better solution, yes.

[frenck]

Just thinking a bit, do we need to tell why it was removed?

As in, we remove integrations for more reasons. The point is, handling the 404 of an integration that was once there. Maybe just a generic page with: "Yo, there was an integration here once, which has been removed from Home Assistant. Possible causes: - unmaintained / no longer working with devices / violating design decisions."-ish page.

[hmmbob]

For that, we can add 301 to the redirect rule

Why not 404? Seems possible to redirect to an error page and throw a 404 - if I look at the docs, no personal experience though

https://docs.netlify.com/routing/redirects/redirect-options/

[ludeeus]

Just thinking a bit, do we need to tell why it was removed?

Good point!
I'll restructure with 301 and make it for generic integration removal

[frenck]

Awesome! 👍