Skip to content

Audit existing CS decks #854

Description

@o-ram

General to-dos

  1. Audit existing decks
  2. Define the purpose of each one
  3. Flag any gaps in decks that need creating

What needs some strategy/thought behind it:
-decks: what do have and what is each one used for
-what could use updates vs what needs archiving vs renaming
-who owns the decks / needs to be consulted

These may get split up into sub-issues as we further scope it out.

Activity

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

Metadata

Metadata

Assignees

Labels

CS Transition PlanningRelated to CS Transition PlanningdocumentationImprovements or additions to documentation

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions