codeforboston / clean-slate-data

MIT License
27 stars 13 forks source link

Documentation that still needs to be created #65

Closed knod closed 4 years ago

knod commented 4 years ago

Documentation to create

When creating a document, link to it in this issue so that we don't duplicate work.

  1. App: general intro (as opposed to design and tech/code notes) (in this folder)
  2. Wiki page: What accounts users need to create and how to get familiar with those services on the devices they will be using
    1. (group) Slack
    2. (group) Github (including some markdown)
    3. (group) Google drive (for now)
    4. (app) Plectica
    5. (app tech) Docassemble
  3. Orientation script
  4. Onboarding script (outlines in meeting checklist page)
  5. Weekly/monthly upkeep that needs to happen outside of meeting
  6. Previous proposals and decisions (as issues)
  7. Template for informal decisions
  8. (app) Style guide
  9. Template for other ~issue types~ general issues (done, unlinkable)
  10. Template for formal proposals (done, unlinkable)
  11. Full meeting checklist ~(how? printed on paper?)~ in wiki

There's also notes about existing documentation that needs to be considered and possibly incorporated. That's probably for another time.

knod commented 4 years ago

Link to a document after creating it.

knod commented 4 years ago

App docs should be made on the google drive.

knod commented 4 years ago

@berit:

@knod:

@caitlincoffey:

knod commented 4 years ago

Each should make issues for each of their items.

knod commented 4 years ago

@jeremylang will review #106, onboarding script.

jeremylang commented 4 years ago

Split off the remaining items into their own issues. Closing this as it no longer has a status of its own and can still be referenced by the other issues.