Posts Tagged usability

Click Tracking on Edit Toolbar deployed

After many a hearty SQL battle, we finally have click tracking deployed on the wikimedia projects!

Data on button usage

Data on button usage

What’s being tracked?

Which buttons are clicked on the toolbar during editing

What information is being recorded?

The button clicked, the time of the click, total edit count of the user clicking, and edit count for the last 1, 3, 6 months

What information is NOT being recorded?

Individually identifiable information of any sort (eg who exactly clicked what) and anything that would violate our privacy policy in general

Why?

As we revamp the UI, rather than randomly throwing buttons up there we think are pretty (we think they’re all pretty), we thought we’d put buttons up and features that people actually use. Novel, right?

What about the edit history and stuff?

We figure the way a novice editor uses the toolbar is different form a ‘power’ editor, and that there’s probably some gradation in between. Is there? Well, that’s what we hope to find out…

–Nimish

, ,

5 Comments

MediaWiki’s new discussion system in testing on Wikimedia Labs

I’m very excited to announce that LiquidThreads, the next-generation discussion system that I’ve spent the last few months developing for the Wikimedia Foundation, is now in beta testing on liquidthreads.labs.wikimedia.org.

Sample of the LiquidThreads interface

Sample of the LiquidThreads interface

Read the rest of this entry »

, , ,

3 Comments

Babaco Preview

Screenshot of Navigable Table of Contents

Screenshot of Navigable Table of Contents

As brion’s earlier post stated, the new set of usability features (nickname: Babaco)are integrate into the source code but disabled until these features are stable.  New features include, navigable table of contents and content generation dialogues for links, tables, search and replace.  These features are currently staged on the usability prototype environment, and you are welcome to check them out and encouraged to push them hard to find bugs. :-)

We are also hoping to integrate add-media-wizard created by Michael Dale in Babaco. While API to extend the toolbar is being worked on, media import functionality can be played at the usability sandbox environment. Click the “Edit” tab and click an image gallery icon in the toolbar.  You will see a nice media import function there.  Feel free to create an article and import image from Commons using this neat feature.

Browser compatibility matrix for Babaco is found here. As always, share your thoughts and experience through the usability wiki.  Feedback on Babaco goes this discussion page.

- Naoko

,

5 Comments

Squashing the Bugs

Fresh off the whiteboard of the Wikipedia Usability Initiative

Fresh off the whiteboard of the Wikipedia Usability Initiative

Over 40,000 users are now participating in the beta testing of new features for Wikipedia, and other Wikimedia projects. These users have been helping the Wikipedia Usability Initiative to find bugs, of which we are doing our best to squash quickly.

If you are a Firefox 3 user, your experience with the new features has most likely been without issue, but we have found some older browsers such as Internet Explorer 6 to be less stable, especially for projects which use a right-to-left language. After collecting information on browser compatibility and evaluating each browser’s capabilities against the technologies we are using to achieve a better editing experience, we’ve designed a map of which browsers support the new editing tools well enough to ensure a quality user experience, and which do not. Where users’ browsers do not support the new editing tools the old editing tools are provided instead.

While we hope that we can extend support to some of the currently unsupported browsers, we are focusing our efforts on developing a richer browsing and editing experience for users of more modern browsers. Thank you to everyone who has been participated so far in our beta testing process!

– Trevor Parscal (trevor @ wikimedia.org)
Software Developer, Wikimedia Foundation

2 Comments

Improving Wikimedia’s Discussion System

Hi all,

Some of you might have already seen my blog posts about LiquidThreads, Wikimedia’s in-development discussion system.

For those who haven’t, this is a quick primer on what LiquidThreads is, and what it’s going to do for Wikimedia’s communities.

Currently, Wikimedia’s discussion system sucks. Here’s why:

  • It’s not easily usable by the average user. It isn’t obvious how to leave a comment on a talk page, or how to reply to a comment. The indenting we use now is ad-hoc and unsustainable for long discussions.
  • Signatures are done manually and we have to jump on poor unsuspecting newbies who don’t know this (or write bots…)
  • Archiving is done unevenly by bots, which are maintained by users and therefore of very uneven quality. Archives are something of a black hole — they aren’t searchable, easily maintainable or easily accessible. You can’t resurrect an archived discussion easily, nor can you view its history.
  • It’s stored as plain wikitext, which is opaque to any sort of automated process.
  • You can’t move a thread to a different discussion page and preserve its history.
  • There’s no encouragement, mechanism or incentive for quoted, point by point inline replies like we’re all used to with e-mail.
Imagine being a new user and trying to figure out how to add your comment to this.

Imagine being a new user and trying to figure out how to add your comment to this.

Enter LiquidThreads. LiquidThreads is a system that makes MediaWiki’s discussion system behave like a forum or comments thread, while still maintaining the unique refinements that make wikis work. It was originally designed by a Google Summer of Code student, David McCabe, and I’ve been making incremental improvements to make it work for Wikimedia.

Overview of the new LiquidThreads interface

Overview of the new LiquidThreads interface

So, what’s changed?

  • Comments are separated from each other in the wikitext, so there are no more edit conflicts in discussions, and the usability is vastly improved.
  • Instead of indenting, each comment is in its own box, along with its replies. It makes it much easier to follow each post and its replies, and it’s much nicer on the horizontal whitespace. Hopefully, it will be the death of the ‘arbitrary section break’!
  • Each post has its own history page, making it easy to see what’s going on with individual threads without trying to navigate the history of a whole page.
  • It’s easy to move threads between pages, preserving the page history.
  • Discussions  are never ‘archived’. Instead, older discussions fall to the bottom of the page, and eventually they drop off entirely, to hit a new page. If you missed the chance to have your say, just reply to a discussion and it’ll be bumped right up to the top of the page again!
  • Discussions with recent changes are at the top of the page. Discussions that have fallen dormant fall to the bottom. It’s easy to find out what’s happening!
  • You can watch individual threads of a discussion, and even get an email when they’re replied to.
  • It’s easy to link to a discussion, and the links are permanent unless the discussion is deleted. There’s no need to point to an archive or to an old revision ID.

If you’re interested, I’ve put together a test setup for you to play with it.

As always, questions, comments and suggestions are more than welcome, in the comments or elsewhere.

, , ,

8 Comments

First usability release, Acai, is now available.

Screenshot-Editing July 1 Wikipedia

The first usability release, Acai, hit Wikipedia and sister projects this afternoon. The new skin, Vector, and the enhanced toolbar can be turned on from the user preference under “Appearance” and “Editing”. Search result page now has a new layout with less daunting information. Vector is only available for left-to-right languages at a moment due to IE6 incompatibility. However, the enhanced toolbar can be selected from all languages and the new search result page is enabled globally. We could not roll out two features we had planned. First, warning messages for unsaved changes when a user switches away from the edit tab did not work properly thus they are disabled. So please be careful when you switch away from the edit tab. Secondly importing language specific configuration for special characters were not graceful, so we disabled special character function from the toolbar. We are working on the fixes and plan to roll them out as soon as we have stable solutions. The usability project wiki has Vector and the new toolbar as a default, so if you prefer to check them out without changing your preferences it is a good place to visit first. Let us know what you think. We would love to hear from you.

Best,

Naoko

, ,

No Comments

First usability release is coming up soon.

Screenshot of enhanced toolbar

Screenshot of enhanced toolbar

I am happy to announce that the first set of usability improvements is scheduled to be integrated in MediaWiki and will be enabled as one of user preferences in Wikipedia in the first week of July. The nickname for this release is called Acai. The release names will follow the names of tropical fruits in alphabetical order. The description of features are found in this release page. The major improvements are; 1) reorganized tabs which clearly indicates the state of “Read” and “Edit”, 2) enhanced edit toolbar which is expandable based on users’ needs, 3) search result page which hides the clutter and make search results more visible, and etc. We are still combating with IE6 bugs , but come and play with the prototypes and let us know your feedback. On the localization front, we have introduced a set of new texts for localization. If you are a MediaWiki translator, your collaboration on localization is greatly appreciated as always.

Naoko Komura

Wikipedia Usability Initiative

, ,

3 Comments