Introduce the concept of draft content for all resources
- Dominant language
- Elixir
- Stars
- 1.3k
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
Currently only pages and layouts allow users to edit a draft before publishing changes, and soon we'll have preview for pages. That gives the users a workflow to create and edit pages before they are ready for production.
Components and the other resources on the other hand are updated as soon as the changes are saved, which may cause unintended behavior if the content isn't ready to go live yet.
So we could introduce the same concept of draft and publish for the other resources and establish a pattern across all resources.
Contributor guide
Research direction
Start by reviewing how draft and publish currently work for pages and layouts, then compare that workflow with components and the other resources mentioned in the issue. Define the scope and consistent behavior for drafting and publishing across those resources; done means the workflow is established for all applicable resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100