Requiring published at date and having a checkbox for published status doesn't make sense

[illegalnumbers]

When I'm creating a blog post I think it doesn't make much sense to have a published at date as well as a checkbox for whether or not it's published. Especially if the published at date is a required date, that was a little annoying. I think it would make more sense to autogenerate that field on initial publication date by clicking the checkmark stating that the draft has been published.

[msevestre]

This is used for future post.

On Sun, Nov 13, 2016, 11:10 PM Ben Nelson notifications@github.com wrote:

When I'm creating a blog post I think it doesn't make much sense to have a
published at date as well as a checkbox for whether or not it's published.
Especially if the published at date is a required date, that was a little
annoying. I think it would make more sense to autogenerate that field on
initial publication date by clicking the checkmark stating that the draft
has been published.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#299, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_jVccYjZlaAfWEJ42jbwpOB36Rhsf5ks5q999KgaJpZM4Kw7-S
.

[illegalnumbers]

Right, but it's required for any post to be created. It's also not obvious that the publishing happens automatically or the time of the publishing (iirc...could be wrong on that) that will occur. It might be a better situation to opt in to that behavior rather than having it by default.