Requirements Gathering for 'Suggest a Guide' Button Link on Toolkits Page

### Dependency
- [ ] When we are ready to prioritize the toolkit again

### Overview
We need to gather requirements for developing how people on the toolkit page can suggest new guides so that we always have a queue of guides to work on and that we are responsive to the community's needs.

### Detail
The `Suggest a Guide` button on the page does not resolve (dev says there is no reference link, since there is no page to link to).

### Action Items
- [ ] Read through the _Suggestion for user experience_ below.
- [ ] Go to the Toolkit page and document (either in comments or in the Google doc provided) the process of searching for information in these sections
- [ ] Guides
- [ ] External Resources
- [ ] Go to the Guide Resources wiki and read about how to suggest a guide.
- [ ] Document (either in comments or in the Google doc provided) the process of creating and/or submitting new guides or resources.
- [ ] Post recommendations for improvement as a comment on this issue
- [ ] Review with Product
- [ ] Add `label: ready for design` so that they can create a mockup of approved recommendation

### Resources/Instructions

#### Preliminary Suggestion for user experience
The 'suggest a guide' buttons could link to a page that
- lays out the process for creating/submitting a guide or documenting access to an external resource.
- has prerequisite information communicating how to do a comprehensive search so that they don't suggest a guide we already have in progress, both on public facing sites and internal sites.

#### Link to
- HfLA website, Toolkit page: https://www.hackforla.org/toolkit/
- HfLA website, About page, executive letter: https://www.hackforla.org/about/#letter
- [Guides Team Wiki, Guide Resources](https://github.com/hackforla/guides/wiki/Guide-Resources)

#### Information to carry over into the design issue
- Notes about Style:
- The link should be made in the style of the about page 'Letter From the ED' section of the About Page.
- That section gets its styling from the executive_letter.yml file, our new page will as well.

#### Information to carry over into the development issue
- [Executive Letter .yml](https://github.com/hackforla/website/blob/f8b7e5c07851a126388beab1122951489112336c/_data/internal/executive_letter.yml)

### Document where assignee is putting their notes
- [Toolkits Page Suggest a Guide UX Research notes](https://docs.google.com/document/d/1FTx860COxSdnDAH5q0aOxT--kzJ437V1bH1SbgosMKI/edit)