chore: update community generators section

[ruheni]

Changes

This PR removes the Community generators and directs our community members to the ecosystem page and Typeform to submit their packages.

Closes #1868
Closes #4121

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 27, 2023 3:09pm

[github-actions]

This PR changes the following pages (Vercel Preview Deploy links):

Changed Vercel links

• /docs/concepts/components/prisma-schema/generators (currently)

(Note that links will only be valid after Vercel preview deploy succeeded)

[github-actions]

This PR probably requires the following redirects to be added to vercel.json:

• This PR does not change any pages in a way that would require a redirect.

[janpio]

I still think the docs are the better place, and that /ecosystem is not very usable to discover generators.

[ruheni]

I made a few changes: adding back the "Community generators" heading, a short description, and a link out to the Ecosystem page.

I still think the docs are the better place, and that /ecosystem is not very usable to discover generators.

While the docs are the right place, having one page where we aggregate all generators, middleware, client extensions, and other types of packages would be valuable.

• Why do you think it is not very useful to discover generators via the /ecosystem page?
• Is it because we need to talk about it more (internally & externally)?
• How could we make it the default?
• Is this something we could improve with SEO & talking about it on social?

[nikolasburk]

I still think the docs are the better place, and that /ecosystem is not very usable to discover generators.

Agree with this in principle! However, we want to unify the places where we list the community packages so removing them from the docs seemed like the best option.

One idea to improve the situation could be to ask web dev to implement a direct link to the Generators section (with the filter applied) on the ecosystem page. That way, at least people would directly navigate to the relevant packages instead of needing to scroll down and applying a filter when they arrive on the ecosystem page.

How about we ask web dev to create

[ruheni]

How about we ask web dev to create

That’s on their radar. (From a chat with Julie yesterday)