Open jamestranovich-noaa opened 2 weeks ago
Curious to get a sense of size/effort of this?
Well, for now this is a placeholder so we can discuss at the Design/Eng cowork meeting tomorrow (October 31st). Hopefully I'll have more detail on scope afterwards.
Oof, we did not meet today. So we'll discuss next week.
@jamestranovich-noaa @kmranjo Did you all meet on this?
No, I didn't think this one was assigned for last sprint, was it? I did raise the workflow question with design since we had collaborated on the original version, so we could probably put together a new one fairly quickly.
We'll revisit this in Dec/Jan
Description
We have removed the requirement to preview a change before publishing, since that was really only for weather stories and we are not using weather stories anymore.
Nonetheless, we may want to implement custom workflows in the future. (Note that for advanced usage, Drupal has a well known
workflow
module).Current Behavior
Currently we are using the default Drupal behavior for publication, which optionally allows you to preview:
You can set the status to
Published
,Draft
, orArchived
.In addition, the sidebar has various settings for metadata attached to the update:
Each subsequent update will create a revision automatically and these can be reverted:
I believe this should be enough for our content type modification needs but in the future we may want to customize this for a per user workflow or publishing experience (for the newer content types).
Future behavior
Questions to discuss/answer (some are contingent on research/design findings):
Acceptance criteria