Blog & Events - Date Time Post Scheduling Redesign

[johnnyoffline]

The date/time scheduling a post experience is not awesome.

It needs more awesome.

The time widget sucks.

You can't easily have ALL Day events

You can't have recurring events

You can't clearly back date or future date posts in a way that feels substantial and clear

and it's just in general annoying to use the dates for both Posts and Events.

Make it better.

[rickybanister]

This is what we came up with. The language will clearly spell out what the post is set to do.

For events it will be similar to google calendar. If you click 'all day' it will disable or hide the other fields.

[johnnyoffline]

I don't understand your drawing. This ticket needs more information before it can be executed.

Would you mind expanding on your sketch above, because of the time that has passed between the conversations and this drawing, It's hard to put the pieces together.

Then assign it to Dan(?)

He can get started on the symfony form widget for dates, and pass it on to me for styling / JS.

[rickybanister]

Dan,

1. We need the blog sidebar to display the publish at date if one is set that's not 'publish now' see the drawing above for how it would display. Clicking 'or publish now' would unset the publish at date and make it publish whenever you click the publish button.

2. We need an 'all day' checkbox like gcal that lets you hide the time fields for events. To make an event one day, you just (by default) make the end day the same as the start day, just like google.

[rickybanister]

Included in this should be the new time widget Dan has created. It needs to be styled. Dan, can this be part of your Friday apostrophe stuff on 9.10.10?

[geoffd]

What needs to be done still:

1. We need the blog sidebar to display the publish at date if one is set that's not 'publish now' see the drawing above for how it would display. Clicking 'or publish now' would unset the publish at date and make it publish whenever you click the publish button.

1a. There needs to be a save button when you choose a publish date.

2. We need an 'all day' checkbox like gcal that lets you hide the time fields for events. To make an event one day, you just (by default) make the end day the same as the start day, just like google.

[geoffd]

We noticed a problem with when you set a post in advance. It says the post was published on the day you hit publish, but not the day it is set to go live.

[geoffd]

If you set a post to be published in the future, the Publish button should say "Scheduled" (not publish).

[wjohnald]

Stuff for Wes's list:

-Eliminate onChange() submit event
-Create a time-interval based submit event
-After initial save, all "chunks" appear as text, and they include an edit button -- like slots
-Save button at top.

Did I miss anything?

[wjohnald]

My list is pretty much complete on the event form. I will make the same changes to the blog post form.

[johnnyoffline]

Tom is clobbering this one once and for all.

Here you go

:D

[tboutell]

See [2585]

Blog and events admin completely overhauled. There are two metadata forms, both of which have save buttons: the main metadata form (publication, tags, categories, times) and the title-and-slug form at right (which masquerades as two forms, a slight but useful fib since the title can in fact refresh the slug if the slug has never been saved separately).

Autosave features have been removed in favor of save buttons for these editable zones. The new apostrophe.formUpdate "updating..." message is used to clarify what is happening during an update since there is often no other visual cue. The new publication status menu makes it easier to publish, schedule or switch a post back to being a draft. The JavaScript? code has been greatly simplified. Markup has been clarified.

Time and date validator settings have been corrected. The all-day feature saves correctly and reloads correctly regardless of whether the start day happens to be today.