--drafts doesn't respect published front-matter #1337

Closed
icco opened this Issue Jul 22, 2013 · 9 comments

Comments

Projects
None yet
4 participants
Contributor

icco commented Jul 22, 2013

Seems to me that when you use --drafts, you should also render files that have published: false. It currently does not do this.

Thanks.

Contributor

icco commented Jul 22, 2013

BTW, #469 implies that this is indeed a bug.

Owner

parkr commented Jul 22, 2013

Drafts and unpublished posts are semantically different. I will often write a post and trash it after I realize it's crap but still keep it there with just published: false. I suppose the ideal flow is to move those back to drafts.

published: false was a makeshift drafts feature. Now that we have a proper drafts feature, I suppose it would make the most sense to me to offer a separate flag for this, as an unpublished post seems to be different than a draft.

Contributor

icco commented Jul 22, 2013

Interesting, I don't understand the difference. Your first paragraph is exactly what I do, and I consider those drafts.

Owner

parkr commented Jul 22, 2013

Sorry, that wasn't quite clear. I mean that an unpublished post is a finished piece of writing. I have finished it but it is not yet to be published or it has been yanked from the blog. Nevertheless, it is finished. A draft, on the other hand, is a piece of writing which is unfinished for some reason. It requires further refinement before it can be considered a post. Would you much prefer to use published: false for drafts? I don't see the benefit besides not having to do the one mv command.

Contributor

icco commented Jul 23, 2013

I use published: false for drafts. In your description, I still don't understand the need for differentiating. Basically you have posts in production you want to show and posts you don't. Some people may use the published front matter, and some people may use the _drafts folder, but it has the same effect. Why complicate the command line? Just have one flag to toggle visibility of posts.

Owner

parkr commented Jul 23, 2013

Drafts are hidden for a different reason than unpublished posts in Jekyll v1.x, which is what I'm really driving at. Sorry to be a bit opaque. That is the intended use. The need for differentiation is derived from the differentiation between a revoked post and a draft.

Contributor

icco commented Jul 23, 2013

Yeah, that differentiation makes absolutely no sense to me. Seems arbitrary. But whatever.

A separate flag would work fine for me. I just would like to be able to toggle the posts on.

Owner

parkr commented Jul 23, 2013

Yeah, you're absolutely right - it is arbitrary. But I think it makes sense. Sort of the WordPress model in a way.

@mattr-, what do you think?

Owner

mattr- commented Jul 24, 2013

I'm cool with the idea of a separate flag.

maul-esel added a commit to maul-esel/jekyll that referenced this issue Sep 2, 2013

maul-esel added a commit to maul-esel/jekyll that referenced this issue Oct 24, 2013

maul-esel added a commit to maul-esel/jekyll that referenced this issue Apr 7, 2014

@mattr- mattr- closed this in 91e9ecf Apr 15, 2014

@jekyllbot jekyllbot locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.