-
Notifications
You must be signed in to change notification settings - Fork 167
Reference, Contributing Checklist (GitHub Method)
Joe Moore edited this page Apr 5, 2022
·
11 revisions
Use this checklist to ensure your contribution process is complete.
- I have created a new GitHub Issue (Story) OR located an existing GitHub Issue in the Content Backlog and requested in a comment that it be assigned to me. (See Content Prewriting and Ideation
- I have kept the Tanzu Developer Center Team in the loop in the
#tanzu-developer-center
Slack channel (VMware Employees Only) or email. You can also use this method to request the Issue be assigned to you. - My content is drafted in accordance with existing style guides and best practices. See Drafting Content
- The front matter (metadata) is filled out completely (e.g. description, topics, tags, author, etc - as appropriate for the content type). See Drafting Content
- My content has been reviewed by my team for technical accuracy. See Editing Content
- My content has been reviewed and edited by a copy editor. See Editing Content
- If applicable, my content has gone through a legal review. See Editing Content
- I have tested my content locally and everything passes. See Testing Content
The following can be done after the initial content PR has been submitted
- I have filled out the Social Media request form (optional) (VMware Employees Only). See Next Steps
- I have created an author page and opened a pull request to get it added. See Next Steps
Congratulations! You are done!
- Start Here
- Prewriting / Ideation
- Setting Up You Environment to Create Content
- Drafting Content
- Editing Content
- Testing Content Locally
- Committing Content to be Published
- Content Next Steps
- Start Here
- Prewriting / Ideation
- Tools you need (hint: it's Google Docs)
- Drafting Content
- Editing Content
- Contributing Content