Open nathany opened 9 years ago
upcoming/
is just a placeholder folder and Hugo doesn't serve anything from it. It's probably okay to put your post in content/
while you're writing/viewing it. Then move it to upcoming/
before the pull request.
I'll update the README.
Thanks.
It can be a bit annoying to move back and forth now that I'm revising an upcoming article.
I think draft would work better from my point of view, though I can certainly see how upcoming/ makes it clear what is yet to be published.
It's just easier for us Gopheracademy folks to see/know which articles are yet to be released if they're in upcoming/
. If they're in content/
we'd have to hunt down the drafts and then publish them. I'm not sure which workflow works better.
Yah. I totally understand.
@spf13 any ideas?
I wrote a command to list all the drafts or future posts in hugo. Looks like I didn't commit it yet.
Nevermind. I've committed it, it's in head.
hugo list drafts
Thanks Steve.
Does that satisfy the workflow for GA folks Ahsanul? /cc @bketelsen @erikstmartin
I think that could work. That way we could merge pull requests to publish articles rather than moving files from upcoming/
folder all the time. Though I think upcoming/
still serves a purpose for internal use.
Sounds good. :+1:
I'm not sure if I have another article in me this year, but maybe.
Maybe it would also make sense to make use of future-dated posts (by not using -F
) so that the upcoming posts could be slotted in with the correct dates. It still requires deploying each day though. :shipit:
Any news on moving to a draft-based workflow?
The upcoming/
folder makes it difficult to preview, such as in the recent snafu #108.
I'm going to update the README tonight. Drafts-based workflow is probably for the best.
:+1:
I never figured out how to preview my post while it was in upcoming, so while working I actually stored it in advent-2014/ with
draft = true
in the front matter.Maybe the README could suggest how to preview posts as people are writing them?