Identify what frontmatter fields we should support for each content type

[zstix]

Description

There are 6 different content types in the Drupal site (soon to be 7). Each content-type has it's own collection of fields representing metadata for the page. In theory, we could turn each set of fields into a set of frontmatter and have each content-type use it's own template in Gatsby. That said, there may be room for some simplification. For example, some of the content types' fields could simply be content in the markdown file itself.

The purpose of this ticket is to create a proposal for how each content type could be handled in MDX. If we could develop an example MDX file for each demonstrating how a page could look after a migration, that would be helpful. It's possible that (and maybe even ideal if) multiple content types will use the same frontmatter fields and template.

Related Issue(s)

After reviewing the remaining research tasks, we have decided to break the work in #12 down into multiple smaller tickets. This is one of those tickets.

Success Criteria

Create an example MDX file (including frontmatter) for a:

• "basic page"
• "troubleshooting page" (if applicable)
• "agent release note" (if applicable)
• "platform release note" (if applicable)
• "attribute definition" (if applicable)
• "agent API" (if applicable)
• "what's new page" (if applicable)