Create a content strategy for OpenACR projects

[mgifford]

We've got the website, git repos, issue queues & now an editor.

What are we putting up where and why?

I'd say we keep most technical information on GitHub. We should assume a technical user isn't afraid of GitHub.

The website should focus on non-technical users with some knowledge of accessibility. This content will change less often than the GitHub Readme's but should roughly line up (but be less technical and with less accessibility jargon. We can't assume the person here will understand much about accessibility either).

The editor should assume you are a accessibility subject matter expert. You should have any technical knowledge. Anything you need to look up about the process should be within the application. Last thing we want is for people to be afraid of losing their content.

The comparison tool will also need to be written primarily for procurement officers who are neither technical or with much accessibility knowledge.

At some point the editor & the comparison tool may be delivered from the main website, possibly through an iframe.