RFC: Scheduled/Draft Posts; Update page

[denise]

Scheduled/Draft Posts

Now that we've finished the first draft of site search, our next major project is going to be scheduled/draft posts, which are two separate concepts that we've been bundling together since it'll likely be easiest to do them together:

* The ability to save entries midway through writing them, on our servers, as a draft that you can come back to later from any computer;

* The ability to write an entry and schedule it for posting sometime in the future, either once ("post this next Wednesday at 9PM") or recurring ("post this every Monday at noon").

We have specs for both scheduled posts and draft posts in Bugzilla, but we also wanted to throw it open to the crowd for discussion in case anyone has some awesome ideas we haven't thought of:

* What would you want to see a system like this do?

* What would make you want to use it, and what would be the "killer app" for you?

Update Page

Part of this project is also going to involve redesigning the Update page.

We want to make it possible for you to access your scheduled and draft posts at the time of update, in order to work with them, as well as giving us room to add more options in the future. The existing page doesn't have a lot of leeway for us to add new things, and some of the things we've added since we branched from LiveJournal don't integrate very well.

The resulting Update page after the redesign is likely going to be considerably different than what it is right now. (For instance, I'm tentatively thinking about folding in some of the functions of the Edit Journal Entries page, turning the update page into more of a dashboard, where you can access all of your recent posts -- published and unpublished -- along with your publishing schedule, and then edit or reschedule them, or create a new post -- but that's just a very vague idea.) There's also a lot of things we can do for that page, accessibility-wise, to make it easier for people who use assisitive technology.

We don't want to make things worse from a usability standpoint, though, since writing entries is one of the core functions of the site! Mark has done some statistics about which options are most frequently used while posting, which we'll be taking into account, but I also wanted to ask for thoughts:

* The four most-used options at the time of posting, from our data, are: icon, mood, tags, and crossposting. If you consider something else (other than those four) absolutely critical to how you use the update page, what is it?

* What's one major thing you always wanted to change about the current Update page, and why?

* What are the things you've always liked about the current Update page, and why?

We'll use your opinions to come up with the next iteration of the Update page, which will probably go through several revisions until we come up with something that we (and you!) are satisfied with.

Comments

[zvi]

I'd rather we didn't make it easy to post to multiple comms at once. Unique content helps different comms have different identities, and anything that is a barrier to crossposting helps that goal along.

What I think might ease the way on crossposting is if we had an edit as new feature, where you could pull in the text of a posted entry, click edit as new, and then you would be working on a new entry with all of the same text choices made as the old one, which you could then manipulate as you liked, e.g. by changing the community to which it is being posted.

Also, I would like for communities to be able to create templates that would become available to people posting to those communities (not necessarily only members) when someone got to the update?usejournal=

[torachan]

The thing is, multiple communities for everything do exist. Years of having no automatic crosspost on LJ has not had any effect on that, so somehow I doubt that continuing to not have an automatic crosspost option will cut down on the creation of duplicate comms on DW. That's just not how people work.

In addition, some comms do have different purposes, but you still might want to crosspost something that concerns them all. If I write a fic about trans SGA characters and one of them is Teyla, I could post the same fic to a transfic comm, an SGA comm, and a CoC comm and be reaching different audiences.

I would love it if there were no need to crosspost, but there is, so there should be functionality to make it easier.

[jeshyr]

I believe the point is not that leaving it less-trivial to crossspost will make crossposting go away, but that if we make it easier that we'll end up with more crossposts than are absolutely necessary (the end result of that slope would logically be an everything-crossposted morass like Usenet turned into. Which would be ... not good.)

I think the idea of an "edit as new" facility would make what you wanted to do with crossposting fairly easy, while still limiting the ability to simultaneously post your post to every community you're a member of. +1 to that :)

[queenbarwench]

'Edit as new' might be interesting.

What would be really cool, and I don't know that this is the place for this suggestion, is the ability to cross-post across accounts.

F'rinstance, I have a fandom journal and a RL journal (which is safe for my parents to read) but I post everything to my fandom journal. I'd like to, with a single ticky box, be able to x-post selected entries to my RL journal. I think it should be something that comes off my external x-post limit, and could be set up like the external x-posting.