You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@cramforce
This issue is really should be discussion. Before i start working on something specific, i wanted to ask your opinion about it:
On #101 you mentioned that it would be nice to have some sort of visual indication for the draft post on the page.
I do know that the template has a different favicon displayed, when the site is served in devmode, which is rather helpful.
Now that we have basically 3 types of posts (draft, scheduled, published), wonder what would you consider and ideal UI indication for draft and schedule post?
There's two places where we can have visual indication:
The post itself
The collection of posts, which is displayed in the main index page
I was thinking to create a shortcode, which prepends [draft] (for draft posts) or [2029-06-06] (for scheduled posts) before the title of the collection, both on the page and both on the main index page.
What do you think? Does this even worth doing?
The text was updated successfully, but these errors were encountered:
@cramforce
This issue is really should be discussion. Before i start working on something specific, i wanted to ask your opinion about it:
On #101 you mentioned that it would be nice to have some sort of visual indication for the draft post on the page.
I do know that the template has a different favicon displayed, when the site is served in devmode, which is rather helpful.
Now that we have basically 3 types of posts (draft, scheduled, published), wonder what would you consider and ideal UI indication for draft and schedule post?
There's two places where we can have visual indication:
I was thinking to create a shortcode, which prepends
[draft]
(for draft posts) or[2029-06-06]
(for scheduled posts) before the title of the collection, both on the page and both on the main index page.What do you think? Does this even worth doing?
The text was updated successfully, but these errors were encountered: