Add "showcase" page

[i0bs]

I would like to propose adding a showcase page to the website. This extends an idea that was discussed between moderators of the Discord. I'd love to hear more feedback on this, I think this has good potential for bringing more awareness. Here's a rough list of reasons why:

• You have to use #showcase currently to find communal examples or live projects.
• Some repositories have an edgedb tag, some do not. This makes it hard to find all public examples.
• There isn't a location where non-Discord and non-GitHub users can quickly view what projects exist using the service.

Here's some ideas I have for making this possible:

• We could maybe automate the page to showcase GitHub repositories.
  • Sometimes the edgedb tag is used, this could be referenced.
  • GitHub can intelligently recognize used packages through a package manager file, i.e. requirements.txt, Cargo.toml and etc.
    • Maybe scraping for these would help to give a better list of projects, including those missing the edgedb tag.
    • Client libraries could potentially add a setting for projects to be seen for analytical/non-commercial purposes.
• (Alternative idea suggested by @raddevon) We could find a way to maintain or curate the list.
  • I think most public examples of EdgeDB being used will be posted on GitHub. Maybe we could hand pick some projects that are known to work

[raddevon]

I believe @Sikarii had some work in progress on this. Mentioning so they can also weigh in.

I love the idea, although I'm maybe more intrigued by the idea of an "awesome" repo for compiling projects and resources. By putting it on Github and using the established "awesome" branding, it gives us more discoverability by riding the coattails of that already recognized branding. I think it's relatively common to go to Github and search for "awesome " to find a list of projects related to some new technology you're interested in. It would be cool to get some of that discoverability for free. It would also allow us to list our repo on the meta lists of awesome lists (like https://github.com/sindresorhus/awesome) for further discoverability.

I think @1st1 may have had some concerns about using the "awesome" branding on the repo, but I feel like the discoverability advantages of using that would be fairly significant. We're going to be featured on The Today Show because we launched an awesome repo, but I think it would be significantly more organically discoverable than an "edgedb-showcase" repo or a "Showcase" page on our site.

Having it as a repo is less convenient for people who are on our web site than a list that lives on the site would be, but we already have their attention if they're on our site. An awesome list would make it possible to get the attention of people who aren't surfing the site. Maybe, though, there's an opportunity to automate integration of an awesome list into the web site and serve users would would like to see that on our site and those who want to discover it in the wild.

By making this an open source repo, we imply community involvement in the maintenance and curation of the list too which might take some of that weight off our shoulders.

I'm afraid of the idea of automating the contents of the showcase based on a tag or by trying to recognize ourselves as a project dependency. I feel like we will want to have final say on what is displayed on our site or even showcased in an official "awesome" repo (or something similar). Once people discover it's based on a tag, it's a matter of time before someone leverages that to do something we didn't intend.

[Sikarii]

I do indeed have some work done on a repository in the style of "awesome", although not directly called that right now.
Perhaps we can achieve some kind of a hybrid solution where our list remains in Git (in the form of README.md) and is parsed for a showcase on the website, this way we have a good backend-less way of updating the list (with user submissions) and have greater overall visibility to it.

Regarding automating content; I definitely agree with @raddevon regarding the potential abuse, the list needs to be curated at least to some extent.