Draft Handling about decap-cms HOT 2 CLOSED

I do not think timed publishing of drafts is necessary for the first iteration on this. Copying what ghost.org supports seems sufficient:

• unpublished posts
  • save draft, publish now, delete post
• published posts
  • update post, unpublish, delete post

Implementing these would make this usable for us.

from decap-cms.

The simplest solution is usually the better one to consider. As you said static site generators typically support in one or two ways for handing drafts; to avoid complexity this handing should be left for them to handle and have netlify abstract on top of this. Although this would "tie draft feature a lot to netlify" it is something that can be controlled by netlify and allow for further abstraction to add support.

A staging and production branch pattern would be a good way to go as well but leaves less control on version handling unless each new draft was a branch of its own(don't want this) and have a method for pulling from specific draft branches to preview changes before a publish is made.

digitalplaywright is spot on with using a pattern of published posts and unpublished.

from decap-cms.