Add support for "miscellaneous" ecosystem project type

[awtj8o81ryywg793]

Description

From time to time, we receive requests to add projects that don’t fit into the pre-existing categories we support, which has limited our ability to list them. We also have projects that were previously listed on the pre-Zola website but are no longer listed because they no longer align with the categories we support.

To address that issue, this pull request adds support for listing projects considered "other".

To see why the term "other" was chosen over "interesting", see: #3539 (comment).

Related issues

Closes #3539.

Role

Member of The Matrix.org Foundation Website & Content Working Group.

Timeline

There is no immediate deadline, but the sooner the better.

Signoff

Please sign off your individual commits.

[cloudflare-workers-and-pages]

Deploying matrix-website with    Cloudflare Pages

Latest commit:	e284f49
Status:	✅  Deploy successful!
Preview URL:	https://34bb08ec.matrix-website.pages.dev
Branch Preview URL:	https://awtj8o81ryywg793-patch-59.matrix-website.pages.dev

View logs

[awtj8o81ryywg793]

I’ve marked this pull request as "open" to signal that, while it isn’t complete, it is nevertheless open for feedback specifically on what data each project should have and how it should be presented visually.

Once that’s done, I can circle back around and update CONTENT.md.

[HarHarLinks]

remember to update https://github.com/matrix-org/matrix.org/blob/main/CONTENT.md#adding-new-projects-to-the-ecosystem also :)

[HarHarLinks]

pending updating the docs this looks mostly good to me. can we launch it with a couple active projects listed instead of a single depressing thirdroom?

[awtj8o81ryywg793]

Quoted from a previous comment:

[...] can we launch it with a couple active projects listed instead of a single depressing thirdroom?

Sure. I know we've discussed this out-of-band before, but what projects do you have in mind? I'd suggest Matrirc (see: #3374 (comment)). See: a5ac162 and 6264458.

[awtj8o81ryywg793]

We should probably support case-insensitivity or normalise the value before checking it.

[HarHarLinks]

https://github.com/Keats/tera/blob/v1/docs/content/docs/_index.md#sort ?

[awtj8o81ryywg793]

Quoted from a previous comment:

https://github.com/Keats/tera/blob/v1/docs/content/docs/_index.md#sort ?

We could do something like:

{% set data = load_data(path="content/ecosystem/miscellaneous/miscellaneous.toml") %}
{% set miscellaneous_projects = data.project %}

{% set projects = miscellaneous_projects | sort(attribute="maturity") %}

Which currently works, in that it places projects whose maturity is either "Obsolete" or "obsolete" at the end, but it will break once we introduce more maturity levels (e.g., Stable, Beta, etc.), as it will place stable projects at the end, for example.

If I’m missing something here, please let me know.

[HarHarLinks]

Is there precedence for a similar case in our codebase? If the approach matches, I'm good with this.

[HarHarLinks]

Is there precedence for a similar case in our codebase? If the approach matches, I'm good with this.