Forms Library documentation update process on the VA Platform Documentation Website

Task Description

Define and document the process for handling documentation update requests (add, remove, modify) to the Forms Library help documentation located in the VA Forms Library Overview section of the VA Platform Documentation website.
Make this a lightweight process for how app team engineers can contribute to this documentation.
Stand up content on the main help page with directions to submit request?
- If you see something missing, write it up in markdown on a ticket and submit the ticket?
- Link checking is important when working with submitted content.
- Could model this after the "If you don’t see what you are looking for..." text on https://depo-platform-documentation.scrollhelp.site/developer-docs/va-forms-library-how-tos.
- Stand up a GitHub template for doc request submission?

How do people notify the team supporting the Forms Library that they have a documentation request?
What does the team supporting the Forms Library do when that request is received?
Are the team members supporting the Forms Library the only people who should make the documentation updates, or should app team members be encouraged to directly update the help docs?
Think about the documentation Robin Garrison recently submitted for the subtask pattern (ticket #544). It isn’t ideal for our engineers to have to add that, but there doesn’t seem like a way to allow non-platform users access to add docs themselves.

[ ] The process for handling documentation update requests (add, remove, modify) to the Forms Library help documentation located in the VA Forms Library Overview section of the VA Platform Documentation website is documented on a Confluence page in the Forms Library Work Stream section of the FLT Confluence space.
[ ] FLT members have reviewed the Confluence page and provided feedback:
- [ ] BJ
- [x] Harshil
- [x] Karen
- [x] Lauren
[ ] All feedback has been addressed.
[ ] Reference to this page has been added to the relevant transition documents (Karen).

Per discussion in the 9/9/22 standup call, we are going with the following plan: