[wp-trac] Re: [WordPress Trac] #8976: making "preview changes" more
user-friendly
WordPress Trac
wp-trac at lists.automattic.com
Wed Jan 28 21:24:59 GMT 2009
#8976: making "preview changes" more user-friendly
--------------------------------------+-------------------------------------
Reporter: jdingman | Owner: anonymous
Type: enhancement | Status: new
Priority: normal | Milestone: 2.9
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: dev-feedback needs-patch |
--------------------------------------+-------------------------------------
Comment (by jeremyclarke):
Replying to [comment:6 azaozz]:
> I'm not sure that "Preview Changes" is better than "Preview". What else
can be previewed?
Nothing else can be previewed really but why not be as accurate as
possible? As it is the button just isnt' clear to people. Me, Element and
anyone else who doesn't KNOW what it will do would have to guess, and my
hunch is that many people would assume that the button would just show the
page as it was saved (i.e. that the label is innacurately the same as it
was when the post was a draft). Only if you already know or if you test it
do you know for sure that it will make a temporary save of the post to
show you the preview.
A more pertinent question: What is lost by showing "preview changes"
instead?
>Also "Preview Changes" sounds like the changes would be highlighted in
some way and we already have that in the revisions.
I don't think the highlighting thing is relevant because when they see it
isn't highlighted they won't be confused, they'll just see that there's no
highlighting. Also revisions only show once you save, and don't help
explain what the 'preview' button will do. They are about the past, this
button is about the present.
Making the label 'preview changes' has no negative effect and there is
space for it. The change also won't confuse any existing users because its
just more accurate, no removed information.
> "View Post" button could be added there although it's available in the
"Post saved.." notice too.
The whole point is to make it clear that people don't have to save
published posts before they can see their changes. This needs to be clear
before they save so that they dont' save ugly changes if they dont' have
to.
> Also before the post is edited, both buttons would show exactly the same
content. Sounds more confusing.
I think it's pretty clear that the 'show post' button wouldn't be visible
until you publish the post. The 'preview changes' button would also
obviously need to be 'Preview post' until it is published.
> Another option would be to show the "Preview" button only when the post
is edited or replace the "View Post" with "Preview", but it won't be
available before the first autosave after the content or the title
changes.
I like this idea: after publishing there is one button "view post". AFTER
you have made some changes the 'preview' or 'preview changes' button
appears. THAT SAID: it would be a lot more work that I for one am not
willing to do. The earlier proposed changes would be very very fast to
accomplish.
So, just to summarize what buttons should be visible:
Draft post: [Preview]
Published post: [View Post] [Preview Changes]
--
Ticket URL: <http://trac.wordpress.org/ticket/8976#comment:7>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list