feat: content status with related resources

[cwaring]

This PR implements ipfs-inactive/docs#342.

It registers a new global component that can be used in any markdown file, simply add the following line:

<ContentStatus title="**optional**" />

You can also use front matter data to configure the display and add related items.

issueNum: 333 # used to connect to the related issue for the content
related: # nested key, value items rendered as links
  an interesting article: https://ipfs.io
  another interesting article: https://ipfs.io

The interaction logic for the voting mechanism will come in a later PR.

[jessicaschilling]

LGTM 😍

[ericronne]

Cool thx @cwaring!

A couple quick suggestions. Some are global styles, so we can likely address later.

1. Go ahead and bump "Is this important" up to an h3, mea culpa
2. Reduce the spacing below the headings, for better vertical rhythm (see image for rough idea)
3. Make button labels bold
4. Remove the icon that's after the camp link
5. Unlink "Help us improve this page on" so that only "GitHub" is a link
6. Make this ^ "GitHub" link the link color
   

[cwaring]

Thanks @ericronne, I agree but ideally tweaks 2-6 should not be not part of this PR because we need to setup global styles for them to retain consistency and easy of maintenance - otherwise the app will soon get littered with unique pixel values. I would suggest that we address it in the CSS edits branch so it can be become an inherited style.

I'll apply a quick patch in this branch for a visual ref so we can migrate it across later, including the button style etc :)

[ericronne]

Yes i suspected as much. ✊