Approval pipeline: drafts, L2 → L1 → admin #31
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: anas/divan#31
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #20. Every change is a draft with its diff; L2 submits to an L1 of that scope; L1 approves or returns with comments; admin publishes or rejects with comments; L1 work goes straight to the admin; admins' own edits publish directly. Queues for L1 and admins; status and comments on each draft; readers see only published versions; audit log. Uses IAM grants.
Content model decided (docs/content-model.md, "Content management model"): the pipeline works on per-entity revisions (version history issue) and covers tags (tags issue), poet intros, books, chapters and sub-chapters as well as works.