I wanted to share a short video that illustrates some ideas for the user
experience improvement of the Translate extension.
The video is available at http://youtu.be/xKfaLyJE4ow?hd=1 (links to
different language-specific versions of the prototypes are available at the
Arun and I are organizing usability testing sessions these weeks. Anybody
can volunteer for participation in the usability tests at
The only requirement is to speak more than one language, but no previous
experience with translation is required.
Feel free to provide any comment on the prototype, or join the testing
I'm new to the list, and the mediawiki world. If this would be
better directed elsewhere, let me know.
I recently came across a skin for Mediawiki called Erudite, which
is based on a Wordpress theme of the same name.
I updated it to the work well with the current Mediawiki version,
fix bugs, and try and ensure everything was general enough that it
should work on any wiki with any extensions. As I say, I'm new to
mediawiki, so my ideas on the best ways of doing things come largely
from a blog post, the mediawiki wiki, and delving into
mediawiki's code for things I wasn't sure about. It's possible I
didn't follow best practises in some places, but I certainly tried
I set up a new wiki demoing the skin (editing and creating accounts
is enabled; try it out,) here:
And the code is all here:
If anybody interested could take a look, and give me feedback, that
would be wonderful.
I'd also ideally love the skin to be taken as one of the standard
skins that is distributed with mediawiki. I think it's very
attractive, and quite different to the other mediawiki themes I
found, so could be a good fit. Might that be possible? How would I
go about pushing that forward?
Thanks, and I look forward to hearing back from folks.
Inspired by the discussions of the design team meetings, I have been
playing around with a few ideas for a simple navigation model for the
mobile that can extend the feature set of tools and options available to
users. It struck me that the article lead, some images and infobox data can
give a very good idea of a topic that is alien to the reader and such a
compact view on the mobile screen has a lot of value.
It got me thinking of the possibility of decomposing any wiki page into
multiple 'views' or layer that can alter the way one views the same page by
selectively rearranging and hiding the content. Possible page layers could
A) Overview: Condensed view of the article optimized for the small touch
screen. It can also contain an index of topics covered that can act as
navigation aid to jump to a section in the Article layer
B) Article: The whole article, just like what you see in the current mobile
C) Gallery: Thumbnails of pictures, videos from the article. Could also
fetch related content from other wikimedia projects
D) Category: Allows you to jump to related topics if you are interested in
E) Discussion: The talk page to discuss
The search and other page functions including language selections go into a
menubar that floats above the article. It would work like the menubar in
Google Now which Pau had demoed. When you scroll down its hidden, as you
scroll up, the menu pops up again, which means that all the functions
including search can be accessed from any part of the page. This also saves
screen space when you are reading and scrolling down, giving you a full
page view of the article with no distractions.
You can see a visual overview of this here:
Just an idea, more discussion with the design team pending.
I'm interested in getting a few interested people together to talk about
possible solutions for viewing diffs (including previewing changes) and
handling edit conflicts for VisualEditor.
We don't need to do anything formal really - if you are particularly
interested in getting involved let me know. If there are a few of us I will
throw a short brainstorming session together and we can go from there.
Just to throw something out there to give you a feel for what little we
have considered in this area: it is possible to utilize the granular
history data we capture for undo/redo purposes to support playback. This
would give the user a time-slider that takes the document from one state to
another, and a play button to animate between these states. This is usually
considered to be a "cool" idea, but we don't know that it's practical or
respectful enough of people's privacy.
I think this is an exciting area of VisualEditor with few restrictions and
almost no existing ideas or plans, which makes it possible for us to come
up with radical solutions and make them a reality.
Continuing yesterday's theme of deciding about fonts for projects in
many languages, I wrote a page about the desired first step in that
The rest of the Localization team supports me on that.
TL;DR: Before writing a big new movement-wide style guide we must
understand and document the different content and UI elements that
need styling in different languages and communities and only after
that start to bikeshed about particular fonts, weights etc.
Comments about that page are welcome.
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
“We're living in pieces,
I want to live in peace.” – T. Moore
Oliver Keyes said:
> Like, if I save a draft, cool. Except it doesn't reappear when I open the
> same page's editing window again.
When I open a page for which I made a draft of a new version,
it shows the list of existing drafts on top of the edit window.
If I click in the link provided, the page is reloaded with my draft inside the
edit box and I can continue updating it before publishing it.
Maybe it was just a bug when you tested?
On Thu, Sep 13, 2012 at 8:31 AM, Dario Taraborelli <
> that's fantastic, is there any plan to support some basic markup/HTML
> parsing in the message - or is it not within the scope of this type of
I asked about this on wikitech. Daniel Friesen's answer:
mw.notify accepts DOM nodes and jQuery objects. So you can add in whatever
> html you want by parsing it into dom. mw.notify also accepts mw.Message
> objects so you can use `mw.notify(mw.message( 'foo' ) );` and it'll be