scottqueen-bixal
commented
2 weeks ago essentially, in all other nodes, we have a draft mode
two options
- make more clear nodes that can be set into draft mode with ui interaction,
for example, life event form should have a radio that toggles between "published" and "draft" before save
- enforce workflow to require approval before publishing
for example, if I save a new revision, it automatically goes into draft mode, and has to receive approval before ability to publish is available, this is similar to basic page workflow
note that life-event node can not be put into workflow, and preference is to use workflows
User / Persona
content editor
Reason / Justification
The dev team and content team will have same role/permission in production later. The life event content is mainly for backend and front end communication. It is also used for building content structure in USAGov site. The life event content cannot be draft mode, which will affect the benefit finder content structure in USAGov site, for example the menu items disappear. We will implement a solution to disable the draft mode of life event content. So content editor cannot save life event content as draft, even getting into life event edit form.
Acceptance Criteria (AC)
Other Notes
No response