Document how YAML works for this project

[beparticular]

In design/dev 1:1 this morning, we were talking about YAML vs coding in content changes and we realized we should create some documentation that helps us understand how this process currently works and/or should work.

Using the Activity Overview section (#2372) as an example, we'll see how much the IA and content can be tweaked using YAML vs what would need to be hard coded.

11/03/2021 This will help us understand how we can modify or adjust help text based on type of APD and/or funding stream.

This task is done when...

• [ ] YAML file locations are documented
• [ ] Outline what changes to content can be made in YAML (just text, what styling, etc)
• [ ] Outline how changes are saved and move through dev (snapshots, commits, PRs, etc)
• [ ] Consider if this viable option for future APD types
• [ ] Look for any alternative processes that would save time for both design and dev

[akuas]

Moving acceptance criteria from 4050. Look at how this content is pulled in from YAML (This might need to be its own ticket*) (*Per JL - When we do the content updates, we may need to consider reviewing how we apply the YAML structure so it's consistent across the example boxes (so we can do it piece meal instead of doing an overhaul of all the YAML).