I really like the idea and general form and the use of an interactive
mockup to gather feedback, so this is just minor impressions and comments.
Because it's such a high-fidelity mockup, I assume you are looking for
visual design feedback as well as functionality. Feel free to ignore that
half if not.
Random feedback not intended to be in order of importance or imply that it
is important or expects a response.
The body text seems large compared to Wikipedia page content normally.
That's a good thing. The rest of the web has headed in that direction,
but it would look more integrated if other parts of the site got less
cluttered and more readable to match.
It's not clear to me why there are so many different font sizes for
elements on the page. A single comment has about 8?
Is mark abusive more important than other tagging or actions that it needs
to be brought out into the box?
Is mark abusive the only action that applies to a single comment rather
than a thread? I suspect I want to be able to tag individual comments and
close and oversight should probably comment based too.
I'd like less clutter. Author meta data, mark abusive could hide. Borders
and header boxes could be more subtle (or go)
I _really_ like the highlight unread and auto mark as read but the current
experimental implementation is not quite right for me. The contrast
between unread and read is very high, so when it suddenly changes it's a
bit alarming. I think it also changes too early. It changes as I start to
read that box and I distracts me or beats me to even starting. I think my
habit is to scroll what I intend to read next to near the top of the screen
so for me the change would be more natural if it faded out a second or two
after that box started to scroll off the top of the screen, or on reload
for pages too small to scroll. At the moment it looks to be tied to entry
at the bottom or rendering and gets marked before I have read it.
I know it's common, but I don't like multiple search boxes on one page. If
there's not a clean way to use the top level box for both sitewide search
and in page search on pages that support it, then I think they should at
least look the same and have the same action button.
I can't see in the test data how it handles very deeply nested reply
indenting?
I assume the final version would resize to fit a range of page widths?
The same pieces of content seem to be being called Messages, Replies and
Responses in different parts of the screen. Or maybe Replies and Responses
are synonyms and Message and Topic are synonyms.
Why does New message get a plus sign but Reply get's neither a new nor a
plus?
Replacing the term "talk page" seems unnecessary. The same purpose with a
new UI could reuse the old name.
I like that it reuses the same style as for unread indicator and Echo
Notifications.
I'd like a way to navigate from the top of the screen to the newest reply.
It looks like it's ordered by most recently updated thread, not by thread
start, so in line with my request for less clutter maybe each "last
updated" timestamp could send you to the comment that refers to.
Keep up the awesome work. I hope you get lots of good feedback, ignore 3/4
of it and come up with a great model
Luke Welling
On Thu, May 9, 2013 at 1:36 AM, Brandon Harris <bharris(a)wikimedia.org>wrote;wrote:
Hello!
I have released a new version of the Flow prototype into the wild.
This will be the version that is discussed during office hours tomorrow.
The URL for the prototype has moved. It is now located at:
http://unicorn.wmflabs.org/flow/
I have also created a page that explains what the prototype is and
how to use it. I will be updating the release notes there from now on and
not posting to this list, so you should watch this page for changes:
http://www.mediawiki.org/wiki/Flow_Portal/lnteractive_Prototype
I'll include the latest release notes, though (mirrored on the
mw.org page):
=== May 9, 2013 ===
* Read posts are now only collapsed in the Feed views
* The "+Topic" button now reads "+New Message"
* Hide the "New message" button when in feed view
* Tag actions no longer work on unsubscribed topics
* Author metadata (edit count, etc.) can now be hidden from a tool in the
sidebar
* Posts by yourself now have a blue border instead of grey (h/t to TheDJ)
* Added in a "mention" example to the Echo flyout.
* Cleaned up the json file for Jimmy Wales' board with regard to post
depths.
* "Reply" buttons changed to mw-ui-constructive (green)
* Changed the green color of unread posts to match the reply button color
(avoid clashing)
* Going to a "Feed" view now removes any tabs. Returning to a board shows
the tabs again.
* Taglist section no longer displays if there are no tags
* In Feed view, topics on own board no longer include your username
* In Feed view, the sort of topics is NOT based on "last update time".
Instead:
** Topics that you are ''subscribed'' to are sorted by last update time;
** Topics that you are ''not'' subscribed to are sorted by create time.
*** This more accurately reflects the behavior when you are subscribed to
a user but not every topic on their board
* Added a new sidebar section, "Back and Forths"
** This gives you a "masquerade" view, so that you can see what the same
topic will look like from the viewpoints of different users.
*** The first is ''your'' view.
*** The second and third are the views of two other participants.
* In Board view, all topics are expanded by default (for easier
fast-scanning)
* Individual posts can be flagged as "abusive". This is the beginnings of
a workflow; actual anti-vandalism functionality will require more work.
* Removed the "Jorm Board" - it was a redundant view
=== May 4, 2013 ===
* Read posts in any thread are collapsed by default, with an indicator to
open all of them up.
** Posts are not collapsed if the thread is collapsed
** Collapse sections is an all-or-nothing deal
** You cannot "re-collapse" read posts. Adding a control to every post is
too heavy
** Collapsing a thread will uncollapse all posts inside of it and remove
the indicator
*** Reopening the thread will expand all posts
* On start up, a modal appears asking you for your user name.
** The form saves it and operates as "that person" from then on.
** This is saved to a cookie, which prevents the modal from opening in the
future
**There is a "clear saved username" link on the side.
* The feed link now treats itself as if it were the "logged in" user and
does some replacing on text to imply that the conversations are happening
with them (and not the original owner of the posts)
---
Brandon Harris, Senior Designer, Wikimedia Foundation
Support Free Knowledge:
http://wikimediafoundation.org/wiki/Donate
_______________________________________________
EE mailing list
EE(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ee