Add FAIR Guide with Checklists

[egrace479]

• Replaces "Metadata Guide" tab with "FAIR Guide". Includes references for FAIR and Reproducibility, motivates use of checklists.
• Metadata Guide rebranded to Metadata Checklist--a more general guideline for necessary metadata.
  • Renamed the actual file Metadata-checklist.md.
  • Adjusted URLs accordingly and revised the references to it or redirected them to the FAIR-Guide page as appropriate (redirects in docs/index.md and docs/wiki-guide/Digital-products-release-licensing-policy.md , the former had a description rewrite).
• Adds checklists for Code, Data, and Model repositories to follow FAIR principles.
  • Data and Model checklists follow the dataset and model cards, respectively.

[gwtaylor]

Hi @egrace479,
This looks great! I've reviewed each of the modified files in this PR and made some edits as additional commits.

You will see that I added one file, which is a configuration for markdownlint. By default, it uses 2 spaces rather than 4 spaces indent. I like two spaces. However, switching to two space indent inside nested checklists result in them not being indented in the rendered HTML.

This appears to be related to behaviour of the mkDocs renderer issue #545 Python-Markdown issue #3 also issue #451.

Assuming that you are not concerned with the indenting, I have left it as it was (4 spaces) and recorded this in .markdownlint.json so that it won't complain.

If we do want to switch to two spaces (which I believe is more common in Markdown use) we could look at implementing the mdx_truly_sane_lists extension via our mkdocs.yaml file like this.

[egrace479]

Hi @egrace479, This looks great! I've reviewed each of the modified files in this PR and made some edits as additional commits.

...
If we do want to switch to two spaces (which I believe is more common in Markdown use) we could look at implementing the mdx_truly_sane_lists extension via our mkdocs.yaml file like this.

Thank you for the thorough review and your thoughtful additions! Both the Model and Data Checklists are referencing the yaml in their respective HF cards, which require lowercase for licensing (as noted in suggestions). Additionally, I thought adding one more clarifying sentence on what constitutes an issue tracker might be helpful.