The content of the "integrations" page is confusing

Nobody has claimed this yet.

Link: https://matrix.org/ecosystem/integrations/

From the text on the page:

> Integrations allow you to bring content to and from third party platforms to make your conversations more productive… or more silly. You can see them as bridges, but not for chat.

The list here appears to be for application services or bots that bridge content (but not necessarily messages) from third-party platforms. That's fair, but then why are Hemppa, maubot and opsdroid - bot-building SDKs - on there?

And things like Matrix BarCamp are definitely an *integration*, but it doesn't bridge any content from a third-party platform. All content is generated entirely by Matrix users. And Matrix Registration Bot is definitely matrix-only.

I think the description of this page should be updated to be more generic. Describing integrations as "extensions and added features to your Matrix experience", or similar.

I think it'd be nice to reorganise this page a bit.

* Move the matrix-rss-bridge to the Bridges page (and arguably the matrix-trello-bot as well).
* Have an "Integrations" section for things like matrix-hookshot.
* Have a "Widgets" section for the primarily widget-based stuff like Matrix BarCamp and NeoBoard.
* Have a "Bots" section for primarily chat-based bots like Matrix Registration Bot, matrix-eno-bot and matrix-feeder.
* Move Hemppa, maubot and opsdroid to the ["bot SDKs" page](https://matrix.org/ecosystem/sdks/), and potentially provide a link behind the text "want to build your own integrations? See the list of available Matrix SDKs".

Alternatively these could be broken up into separate pages on the website, rather than all under the "Integrations" page.

Finally, there's a nice list of ready-to-use maubot plugins/bots here, which could help populate this page: https://maubotplugins.mssj.me/

Start with the linked integrations page, then compare the Bridges and SDKs pages and the linked maubot plugins list. Done means the page description and organization of integrations, widgets, bots, bridges, and SDKs are updated according to an agreed structure.

Written by the indexing model from the issue text.