Update and expand content style guide

[AmyKort]

To ensure that content is consistent, easy to use and written in plain language across the website, we'll need to develop a style guide.

• Reflect design changes made this PI
• Guidelines for proposing additions to the Guide
• Design approval process for Guide
• Design process for sharing the Guide as we onboard new content managers
• Include guidance to different templates and modules
• Detail responsibility for accuracy and timeliness of different content (ownership)

[jameshupp]

The primary issue I'm seeing with 🔒 the draft guide as it exists so far 🔒 is that it doesn't deal with specific content types or templates. It's broad, which is useful as a baseline for decisions about new things, but less helpful for managing within frameworks we've already established. The guide to reporting examples we put together, conversely, is probably too specific for this. But I'm putting together a couple pieces for this based on that, slimmed down, to see how they read. If it works, we could try to expand the guide further along those lines.

[rhoughfec]

@jameshupp I completely agree. I think when we started we didn't realize how far reaching we would need it to go. Also agree that the reporting examples would be too specific for all the different content on the site.