Publish Individual Locales

[zubricks]

Provide the ability for users to publish one locale at a time e.g. promote only Spanish, German, etc. to prod.

Feature breakdown:

1. Publish button will be extended to include a dropdown selector, this will display all available locales to publish
2. When publishing a single locale, only the data for the selected locale will be updated on the published doc

This is applicable to collections and globals.

Estimated Date of Completion: 8th Dec

[tylandavis]

Design Intent

We'll be updating the button component to allow for a dropdown of actions. Clicking on the main part of the button will publish the full document's changes, while clicking on 'Publish [Locale] only' will only publish changes from that locale's data, and keep other locale's changes in their draft state.

[PP-Tom]

I think publish should publish the current local and the dropdown could say "Publish All", I think that would be a editor experience. The example seems too easy to accidentally publish all.

[Janisvb]

Is there an updated timeline for this feature?

[jhnsml]

Any update here?

[Lismont]

also interested in this feature 👋

[tylandavis]

Hey everyone, we're all deep into getting 3.0 beta out, and should be ready to release in the next week or so. Once that's complete we will be back to working on roadmap features, and this one is definitely one of the top priorities for us.

[Rheaparks]

Hello, any news? I've seen that the 3.0 is still not out…
Is there a plan to put this feature on 2.3? The absence of this feature can be quite blocking…
Thank you!

[felixhagspiel]

@tylandavis would it be possible for me to implement a temporary workaround using the beforeChangeHook until you release v3? I.e. is it possible to tell the backend to just update the currently selected locale? I have not found any info on this in the docs

[PP-Tom]

+1 for this feature, it's really important for a project I have at the moment. Looking for alternative implantation for now, but hitting road blocks.

[johannesspohr]

I had a look at the ongoing implementation.
First, I'm really excited that we're getting this soon, thanks for the work on that!

I tried it for a bit and want to second what @PP-Tom mentioned on the design. If I'm working on a specific locale, the only two use cases I see are publishing the current locale and publishing all locales, but not any other locale than the current one. So my expectation is that the default action is publishing the current locale, and in the dropdown menu there would be an option to publish all locales.
Also, if I understood it correctly, it's not possible at the moment that one locale is in draft state, while another one is published (say an article is available in one locale, but not in another). I guess you could solve that with some hooks magic and an additional field, but to me it seems a bit counterintuitive that publishing one locale also sets another locale to published state without actually publishing the contents.

[ars3nicum]

+1