Improve drafts & status system

[jonbullock]

Improve drafts & status system.

[mhoennig]

I'm working on this because the current draft system is really unsable. See also issue 652.

My personal requirements:

• draft posts should be rendered with '-draft' added, as it's now, is fine
• but there should be no links from non-draft pages to draft-posts
• also prev/next should never point to draft-posts, maybe except if the page is a draft itself
• draft articles should not count for the tag-counters
• I would like to have a page drafts.html similar to archive.html which contains all drafts
• I want to be able to add password protection to all draft-related pages via .htaccess/.htpasswd

Most of these requirements I've already implemented in my local version, but it's not production ready yet and unit tests need to be improved.

What would be your requirements?

[McNetic]

There should also be a usable way to iterate over published content of [type] (currently, there are only collections of all content of type, which could in theory be filter, but must take into account the possible values of status (draft, published and also published-date). Don't forget to consider the status "published-date" in all of the requirements. It would probably make sense to add a boolean field "published" to the content data model.

[jonbullock]

Happy to receive any pull requests related to the above 👍

[yakoder]

What would be your requirements?

An additional two:

• draft.prefix=[prefix] -- prefix could include paths -- path could be relative to content or begin with slash, a la .gitignore, to be off server root
• render.drafts=[boolean] -- true (default, as it is now) -- false (do not include any drafts in output)