Q1, 2024 — Draft & Publish | Content Editing XP

417

Q1, 2024 — Draft & Publish

planned

Aurélien Georget

Allow users to manage content by having a published and draft content at the same time.

March 15, 2022

Devon Helliwell

We tried the content versioning plugin but it didn't work with related content or unique fields so we are back to waiting for this to be released. Does anyone know if there is an eta?

Steven Dyson

This would be great for my team! I attempted to use the content-versioning-plugin with i18n and Localazy with no success. You could consider reaching out to i18n plugin developers to ensure this feature will work with seamlessly with the other plugins.

Lucas Boilly

Hello, 
You've certainly received a message from me with a link to a prototype. Unfortunately, most of you couldn't access it because we encountered some issues with the tool used, but it's now fixed! Sorry for the inconvenience 🙏
For those who didn't see the first message, this is a prototype for the new iteration of Draft & Publish. Any feedback is welcome!
Here is the link: https://t.maze.co/191919788

Igor Putina

We can't wait for this feature to be out. We're developing our own in the meantime.

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?

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

marked this post as

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.

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?

Gustav Hansen (he/him)

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?

LucaNerlich

Gustav Hansen (he/him): Thanks. It does yes.

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.

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 ?

Gustav Hansen (he/him)

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?

Jan-Niclas Gladbach

Gustav Hansen (he/him): 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.

→