Proposing use of _drafts

[rivasvict]

Jekyll has a way tom manage all post you may not want to publish yet because it is not ready. The problem is that as I understood this is not such an automatic process like just changing a value on your draft and it is instantly published.

So I propose the usage of this tool.

To be honest I haven't worked with them yet. I am going to test them first and then I will give more information.

http://jekyllrb.com/docs/drafts/

[sadasant]

Hey @RoberVs, check this out.

[schoettler]

Yeah i saw this! was playing with this _draft directory yesterday, i'm looking forward making this process automatic @vctr90

[sadasant]

Ok so _drafts remains a possibility until we find a better way :)

[ghostbar]

Hmm... Using prose.io is the only way I know make this automatic. prose.io is a webui for jekyll sites hosted on GitHub made by the awesome people from developmentseed.

(This does NOT implies making any changes in a regular jekyll deployment, just using the webUI if any individual decides to. Will not affect anyone else)

[rivasvict]

So are you telling me that prose.io has an interface that is able to automatically manage Jekyll's _drafts. I am going to try it tomorrow to figure out how it works

[rivasvict]

I've just tested prose.io and I think it is the best way to manage drafts in Jekyll.
Thanks for thas recommendation.

[sadasant]

Good, then we have a winner!

[ghostbar]

Yes. I yet believe vim is the winner xD But if somebody wants a UI or something that makes it automatic and gives previews then should be using prose.io :)

Glad it worked for you :D

[rivasvict]

I like vim so it is excellent for coding. But what I like about prose is that it is an automatic way of drafting and posting, However, the use of prose will not affect anyone else. :D

[sadasant]

Yes prose is good.

What we have left here is to link prose, it's fairly easy, but let's focus on the rest of the blog first.