search

decaporg / decap-cms

A Git-based CMS for Static Site Generators
https://decapcms.org
MIT License
17.79k stars 3.03k forks source link

Set default status to "Ready" for editorial workflow #1306

Open Andrewyg opened 6 years ago

Andrewyg commented 6 years ago

- Do you want to request a feature or report a bug? Feature request - What is the current behavior? Currently, after we save the draft for the post in editorial workflow, we'll need to set the status to Ready in order to publish. - What is the expected behavior? You can set the default status after a draft to Ready which meant you can publish directly after you save the draft, or even better after your last edit you can publish it directly without saving a new draft.

tech4him1 commented 6 years ago

@Andrewyg Does the simple workflow meet your needs? It is set to publish directly without saving a draft.

Andrewyg commented 6 years ago

@tech4him1 Nope actually.

So I've been focusing on saving draft at this issue, so let's talk about simple workflow, the simple workflow will publish the post immediately after you save it which meant there is no way to save an unpublished draft.

Then for editorial flow, it can let you save draft, but then every time you need to publish you'll need to save then wait for the site load, then set status to Ready and wait for the site load, last you can publish it. Which makes you wait longer and quite useless when you're working solo. Also, the workflow is useless for collaboration since looks like anyone could change a status.

Last, it looks like you can set a post to Ready then do some more changes and save it without it resetting the status to Draft.

tech4him1 commented 6 years ago

Related to #942. This could definitely be an alternative until drafts for simple workflow are in place.

Andrewyg commented 6 years ago

Well, actually I've opened this issue since @erquhart tells me saving draft without editorial workflow is impossible and he'd ask me to open a issue for setting default status for editorial workflow (see at gitter)

But yeah, it fit what I originally ask on gitter.im

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

searls commented 4 years ago

This is definitely still an issue. The "Set status" dropdown (or that it's required) doesn't add any value to my workflow, which merely requires preview build support

erezrokah commented 4 years ago

Fixing this might be just about reading the initial value from the config here: https://github.com/netlify/netlify-cms/blob/9f219d395803075d9fe363c5366fb9bbf6fe38ae/packages/netlify-cms-core/src/backend.ts#L274

(and verifying it works for the all the different backends)