This repository has been archived by the owner on Jun 25, 2020. It is now read-only.

Identify documentation requirements #147

Open

alanmoo opened this issue Apr 18, 2016 · 0 comments

Labels

Contributor

alanmoo commented Apr 18, 2016

As a project is built, there's likely a need for some set of documentation. We need to figure out what that is for each project. Some ideas:

Goals of a campaign
Workflow of a technical project (CI, deployment, etc)
Stakeholders

alanmoo added the betterfaster label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.