Content: Major Topic - Proposed content title

[anavarromartin]

Summary of content

A short summary of the content to be proposed. A few sentences at most.

Summary of audiences

A short summary of the audience. Include:

• Professional area of audience (developer, likely)
• General expertise in their area
• Expertise in the particular topic to be discussed

Level of content

Level of content as it pertains to the topic proposed. Delete those not applicable.

• 101: "Awareness / Exploration"
• 201: "Prototyping / Deploying"
• 301: "Scaling
• Content Series: To include multiple levels of content (Note: Series pieces should either be able to be consumed independently, or very explicit in the title, and with links in the body of the content that they are part of a series)

Contributor Checklist

1. [x] I have added a card to the GitHub Content Backlog and/or moved it to the proper column. See Content Prewriting and Ideation
2. [ ] If contributing via Google Docs: I have added a link to my document to this issue, and set the document's Share settings to "Anyone on the internet with this link can comment".
3. [ ] My content is drafted in accordance with existing style guides and best practices. See Drafting Content
4. [ ] The front matter (metadata) is filled out completely (e.g. description, topics, tags, author, etc - as appropriate for the content type). See Drafting Content
5. [ ] My content has been reviewed by my team for technical accuracy. See Editing Content
6. [ ] My content has beed reviewed and edited by a copy editor. See Editing Content
7. [ ] If applicable: My content has gone through a legal review (VMware Employees Only). See Editing Content
8. [ ] If applicable: I have tested my content locally and everything passes. See Testing Content
9. [ ] Optional: I have filled out the Social Media request form (optional) (VMware Employees Only). See Next Steps
10. [ ] If applicable: I have created an author page and opened a pull request to get it added. See Next Steps

Reviewer Checklist

• [ ] Review if the content is a good fit for the Tanzu Developer Center. See Content Prewriting and Ideation
• [ ] There this GitHub issue has been added to the content backlog project
• [ ] Ensure with the author that the content has been reviewed for technical accuracy.
• [ ] Ensure with the author that the content has been through copy editing.
• [ ] If applicable: Ensure with the author that the content has been through Legal review.
• [ ] Review fit with the Tanzu Developer Center Style Guide and the VMware Style Guide (VMware Employees Only).
• [ ] Ensure the front matter is filled out correctly and completely.
• [ ] If applicable: Review additions to custom_dict.txt.
• [ ] Ensure with the author they have reviewed the staging site for correctness. The reviewer should review this too.
• [ ] If applicable: Review any new Team pages.
• [ ] Optional: Ensure the author has provided copy for Social Media distribution.\
• [ ] If contributing via Google Docs: Send the staging link to the author to review. The reviewer should review this too. Get the final 👍 from the author to push the content public.