Proposal to provide content type status and reference implementation status to content type docs

[jhaaaa]

This PR demonstrates a proposal to include a content type status and reference implementation status in content type docs.

Currently, the content type docs do not consistently indicate whether the content type is a standard. In this state, the docs have the potential to mislead devs to think the content types are standards, stable, and more widely adopted than they might be.

• If the content type is a standard, we should indicate this.
  • For example: https://junk-range-possible-git-content-type-statuses-xmtp-labs.vercel.app/docs/content-types/composite
• If the content type is not a standard, has a reference implementation, and has documentation on .org, it means that it is on track to being considered for adoption as a standard through the XIP process. We can indicate this by surfacing a content type status of "Standards-track."
  • For example: https://junk-range-possible-git-content-type-statuses-xmtp-labs.vercel.app/docs/content-types/attachment
  • In this case, the content type is standards-track and has been widely adopted, so its reference implementation can be marked as "Stable."
  • At this time, the author of the content type Idea has the option to create an XIP that will propose that the standards-track content type become a standard content type. The content type remains "standards-track" and the reference implementation remains "Stable."
  • If the reference implementation has not yet been widely adopted and is just starting to circulate and therefore hasn't proven its stability, we can surface a reference implementation status of "Beta": https://junk-range-possible-git-content-type-statuses-xmtp-labs.vercel.app/docs/content-types/reply
• Standards-track content type docs also include an "Open for feedback" callout that gives devs a way to participate in the discussion about the content type.

Surfacing these statuses and callouts in the content type docs and content type repo READMEs can help encourage developers to participate in the content type feedback process. It can also help them understand the stability of the content type they are thinking of adopting.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
junk-range-possible	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 16, 2023 7:04pm

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	50896b9
Status:	✅  Deploy successful!
Preview URL:	https://c1b74f42.website-9re.pages.dev
Branch Preview URL:	https://content-type-statuses.website-9re.pages.dev

View logs

[jhaaaa]

Discussed with @yash-luna and in the interest of driving clarity around content types, I'm going to merge and we can learn and iterate from there.