Thanks for your reply. Your use case description makes totally sense. I had two different specific use cases where I expected it to be different. I interpreted “draft” more like “release candidate (valid but not published yet)”. e.g. scheduled posts. They should be 100% valid but in unpublished state.
Hope that description makes sense…
Another kind of annoying thing I experienced several times now:
When I remove the draftAndPublish feature for a collection at a later point, the default behavior (and only option) currently is to delete/lose all “drafts”. (Or publish each and every document before removing the feature). That is pretty bad, since draftAndPublish is activated by default. A nice option (feature request) would be an alternative option to keep ALL document no matter what state they were in (draft and published). This would have saved me lots of time and trouble several times already… This is especially true for strapi beginners… And it should be pretty easy to implement.
Besides that I love the draftAndPublish feature!
Keep up the amazing work!