392
Q4, 2023 — Draft & Publish
planned
Aurélien Georget
Allow users to manage content by having a published and draft content at the same time.
Yannis Kadiri
Hello everyone, I'm sorry to announce that this new feature would more likely involve a breaking change in v4, resulting in the need for a new major version of Strapi: v5. As we would prefer to make the most of a new major version of Strapi to add more improvements, it has been decided to postpone Draft & Publish v2 for now.
A
Alban
Hello, will this be done this year? Any rough ETA?
marromugi
Will v2 include the feature to send an email to approvers when they update their approval status?
G
Gunter
Hi Guys,
Looking at the screen shots and comments I think this is a really great addition and very useful, however it feels like it is not going quite far enough for the use cases we hit often.
Please correct me if I am wrong, but the UI seems to imply there is a single DRAFT and a single PUBLISHED version - but no real "Versioning" as such - i.e. no roll back, roll forward concepts.
Seeing as it already requires a schema change that is relatively significant, how about taking the next step and put a proper Version History in place?
We'd be very happy to help.
Nice side effect being you can also easily support scheduled publication, as I have seen others request, and it could also enhance the Review Workflow you have planned
Derrick Mehaffy
Gunter: Indeed we are planning to start small and rapidly iterate on the feature once we get "D&P v2" out as the evolved feature will move towards true and total content versioning. We want to try to keep the feature scope smaller to start to judge how users interact and where we need to place focus.
Aurélien Georget
planned
Yannis Kadiri
Hello everyone, I'm sorry to announce that this new feature would more likely involve a breaking change in v4, resulting in the need for a new major version of Strapi: v5. As we would prefer to make the most of a new major version of Strapi to add more improvements, it has been decided to postpone Draft & Publish v2 for now.
L
LucaNerlich
Yannis Kadiri: Thats a shame. How "breaking" would that change be? Would it require another manual database migration?
Andrei Wilkens
Yannis Kadiri: That really is quite sad for us, we were hoping for it :(
I guess when the content-versioning plugin fixes https://github.com/notum-cz/strapi-plugin-content-versioning/issues/12 (they already have a PR open for it)
it will serve as a decent replacement till D&P v2 comes with strapi v5
Doug Osborne
Yannis Kadiri: Bummer. Would this feature get lumped in with the Review Workflow feature (https://feedback.strapi.io/customization/p/reviews-workflow) for v5? Any timing estimate on v5?
g
gu-stav
LucaNerlich: The breaking changes are quite wide-spread.
We'd have to introduce the notion of a document in the database, which might contain several entities with their dimensions (publication state, i18n ...).
This would affect many parts of the app, e.g. lifecycle hooks (should they trigger on the document or the entity?), webhooks, ... but most importantly: the content API, which is currently based on entity IDs. There would be a way to map entity IDs to document IDs, but we've found too many edge-cases to be confident about the change.
Does that answer your question?
L
LucaNerlich
gu-stav: Thanks. It does yes.
B
Brianfbento
Yannis Kadiri: Any ideas when v5 is projected launch? I know dates are hard to give and keep, but I general idea of when would help a lot of teams with planning, or decision making for a CMS.
Yannis Kadiri
Doug Osborne: Review Workflows is what we are working on now. We'd like to release it next quarter.
Brianfbento: No date has been defined for v5 yet but it should not come before the end of next year at least.
J
Jan-Niclas Gladbach
Hey, looking forward to use the feature! Does it include the extended permissions to control the access to drafts by e.g. a guest as stated here https://github.com/strapi/strapi/issues/12309 ?
g
gu-stav
Jan-Niclas Gladbach: In this iteration we won't add any extra permissions. Draft entities will inherit the same set of permissions.
Could you describe your use case a bit, so that we can try to take it into account later?
J
Jan-Niclas Gladbach
gu-stav: We have created the backend for our corporate website using Strapi and currently anyone could access unpublished pages using publicationState:PREVIEW. We would like to prevent this.
g
gu-stav
Hello everyone. I want to give you a quick update as it becomes clearer what we will implement as part of this initiative:
- Editors will be able to save a new draft, after you have published an entity. This means editors can continue to iterate on your content, even if another version of it has been published already
- Editors will be able to save & publish in one action instead of two
- Editors will be able to see the status of an entity in the list and edit-view, as well as for every relation and locale
I've attached some screenshots about our current status. Please keep in mind that something might change if we hit a roadblock.
This initiative is a huge undertaking because we have to re-think the underlying data-structures. This will enable powerful features in the future, such as non-localized relational fields across locales.
Does that work for you? Do you feel like something is missing, that is critical for your use case?
Quentin Le Caignec
gu-stav: Great! How is "updated" determined, does it temporarily show this for recently updated drafts or is it a separate state ?
g
gu-stav
Quentin Le Caignec: "Updated" means that an entity has been published and an update has been saved as draft, but is was not yet published.
B
Brianfbento
gu-stav: This looks great. Exact functionality I would be looking for.
Jorge Pizzati
gu-stav: Exactly what we need! Currently we've had to rely on cache to prevent unwanted changes from going live!
Cami Blanch
Will this replace the Content Versioning plugin that is currently available?
g
gu-stav
Cami Blanch: This initiative won't focus on versioning. However it will lay the foundations to implement versioning in Strapi.
Quentin Le Caignec
An absolutely critical feature that we require on a project, would love to know when this might be planned/in development, to get a rough idea of when it would be released.
g
gu-stav
Quentin Le Caignec: We are currently defining the scope and problems we need to solve and therefore can not give an estimate. We will keep you updated once we have a clearer picture.
Doug Osborne
1 more item of food for thought... it would be great to have "content staging" or "releases" functionality that would allow us to stage changes on multiple pages then publish them simultaneously. Maybe this would be a different feature request, but also depending on how you're handling content versioning, you might be able to create a common version name across multiple pages, be able to simultaneously preview all changes with that version name, and then when ready simultaneously publish all pages with that version. A nice UI that can display these release versions would be sweet. This would help greatly with larger content overhauls on our site.
g
gu-stav
Doug Osborne: Thank you for this feedback. You can follow https://feedback.strapi.io/customization/p/reviews-workflow for progress.
I can not promise we will address staging + simultaneous publishing during that iteration at the moment, but I can assure you it is on our radar and we consider it to be important too.
Load More
→