-
Notifications
You must be signed in to change notification settings - Fork 19
Architecture Workflows
Sam Richard edited this page Aug 16, 2016
·
1 revision
Holmes will have enforceable workflows that determine whether or not something is publish-able.
- Workflows determine if a given content revision is approved to be published
- Defines a user's path when entering data
- Users of given roles can accept or reject current changes
- Last state of workflow is published, all others unpublished
- Define roles to send to next stage of path
- All workflows inherit admin {{workflow}} role to allow users with {{owner}} role to assign admins who can delegate role access
- Inherit dashboard views for users of roles
- Load from included or NPM module
- Can enforce sunrise/sunset
- Flesh out workflows requirements
Working on Punchcard
Org Maintenance
Architecture Planning
These architectural discussions may be out-of-date given the current state of Punchcard.