Wikimedia Usability Initiative usabilitywiki https://usability.wikimedia.org/wiki/Main_Page MediaWiki 1.42.0-wmf.24 first-letter Media Special Talk User User talk Wikipedia Wikipedia talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Multimedia Multimedia talk TimedText TimedText talk Module Module talk 0 1 9355 9354 2011-01-05T19:35:22Z Guillom 13 shorter wikitext text/x-wiki __NOTOC__ __NOEDITSECTION__ Welcome to the Wikimedia Usability wiki. This wiki served as a knowledge collective and collaboration space for the [[Wikipedia Usability Initiative]] and the [[Multimedia Usability Project]]. It was discontinued in January 2011, as both these grant-funded projects were over. '''Where to go now?''' * You're warmly invited to participate in the '''[[:strategy:List of proposals|product discussions]]''' and express your interest in a certain topic, * For technical details on the implementation of features, please refer to the [[:mw:WMF Projects|MediaWiki website]]. [[Category:Root]] qd84peeokj4vj4m533fgdpll0389i6d 0 3 9213 9204 2010-10-28T11:49:40Z Drorsnir 1545 rvv wikitext text/x-wiki Each prototype wiki is aimed at recreating the user experience of a particular Wikipedia project. To achieve this most of the [[Prototype/Extensions|extensions]] currently installed on each respective Wikipedia project are installed, and some small user interface customizations have been made. == Prototype Sites == {| cellpadding="7" |English | |[http://prototype.wikimedia.org/en.wikipedia.org prototype.wikimedia.org/en.wikipedia.org] |- |Commons | |[http://commons.prototype.wikimedia.org/wiki/Main_Page commons.prototype.wikimedia.org] |- |Arabic |(العربية) |[http://prototype.wikimedia.org/ar.wikipedia.org prototype.wikimedia.org/ar.wikipedia.org] |- |German |(Deutsch) |[http://prototype.wikimedia.org/de.wikipedia.org prototype.wikimedia.org/de.wikipedia.org] |- |Spanish |(Español) |[http://prototype.wikimedia.org/es.wikipedia.org prototype.wikimedia.org/es.wikipedia.org] |- |French |(Français) |[http://prototype.wikimedia.org/fr.wikipedia.org prototype.wikimedia.org/fr.wikipedia.org] |- |Hebrew |(עברית) |[http://prototype.wikimedia.org/he.wikipedia.org prototype.wikimedia.org/he.wikipedia.org] |- |Italian |(Italiano) |[http://prototype.wikimedia.org/it.wikipedia.org prototype.wikimedia.org/it.wikipedia.org] |- |Japanese |(日本語) |[http://prototype.wikimedia.org/ja.wikipedia.org prototype.wikimedia.org/ja.wikipedia.org] |- |Korean |(한국어) |[http://prototype.wikimedia.org/ko.wikipedia.org prototype.wikimedia.org/ko.wikipedia.org] |- |Dutch |(Nederlands) |[http://prototype.wikimedia.org/nl.wikipedia.org prototype.wikimedia.org/nl.wikipedia.org] |- |Polish |(Polski) |[http://prototype.wikimedia.org/pl.wikipedia.org prototype.wikimedia.org/pl.wikipedia.org] |- |Russian |(Русский) |[http://prototype.wikimedia.org/ru.wikipedia.org prototype.wikimedia.org/ru.wikipedia.org] |- |Sinhala |(සිංහල) |[http://prototype.wikimedia.org/si.wikipedia.org prototype.wikimedia.org/si.wikipedia.org] |- |Serbian |(Српски) |[http://prototype.wikimedia.org/sr.wikipedia.org prototype.wikimedia.org/sr.wikipedia.org] |- |Chinese |(中文) |[http://prototype.wikimedia.org/zh.wikipedia.org prototype.wikimedia.org/zh.wikipedia.org] |} == Feedback == Comments should be posted to the [[Talk:Prototype|prototype discussion page]]. Bugs may also be posted there, but ideally they should be reported using the [https://bugzilla.wikimedia.org/enter_bug.cgi Wikimedia Foundation's bug tracking tool] under MediaWiki extensions -> UsabilityInitiative. ==See also== * [[Sandbox]] * [[Demo]] g0vwq4hs8twdxcwbmut1k6nv5mug5lv 0 4 1461 1197 2009-05-21T21:53:34Z Trevor Parscal (WMF) 3 wikitext text/x-wiki == Standard English Wikipedia Extensions == The following list of extensions are installed on the prototype wiki, in reflection of the currently installed extensions on English Wikipedia except those which are beyond the scope or needs of this project. {| width=100% ! width="150" align="left" | Extension ! align="left" | Summary |-- | [[mw:Extension:CategoryTree|CategoryTree]] || Dynamically navigate the category structure |-- | [[mw:Extension:Cite|Cite]] || Adds <nowiki><ref[ name=id]></nowiki> and <nowiki><references/></nowiki> tags, for citations |-- | [[mw:Extension:ConfirmEdit|ConfirmEdit]] || Simple captcha implementation |-- | [[mw:Extension:ExpandTemplates|ExpandTemplates]] || Expands templates, parser functions and variables to show expanded wikitext and preview rendered page |-- | [[mw:Extension:ImageMap|ImageMap]] || Allows client-side clickable image maps using <nowiki><imagemap></nowiki> tag |-- | [[mw:Extension:InputBox|InputBox]] || Allow inclusion of predefined HTML forms |-- | [[mw:Extension:OggHandler|OggHandler]] || Handler for Ogg Theora and Vorbis files, with JavaScript player |-- | [[mw:Extension:ParserFunctions|ParserFunctions]] || Enhance parser with logical functions |-- | [[mw:Extension:Poem|Poem]] || Adds <nowiki><poem></nowiki> tag for poem formatting |-- | [[mw:Extension:SyntaxHighlight|SyntaxHighlight]] || Provides syntax highlighting <nowiki><source></nowiki> using GeSHi Highlighter |-- | [[mw:Extension:WikiHiero|WikiHiero]] || Adds <nowiki><hiero></nowiki> tag to display hieroglyphs |} mi2fbiju2mbf7a2t5mffw1gf94vh0pt 0 5 8548 7197 2010-07-23T18:57:15Z 216.38.133.254 /* Sandbox Sites */ wikitext text/x-wiki <!-- This page should not be used as a sandbox. --> The sandbox wikis provide environments for testing and evaluating experimental and existing extensions. == Sandbox Sites == [[File:Wikipedia Usability Initiative Sandbox Logo.svg|link=|center]] <span style="plainlinks"> {| cellpadding="7" class="wikitable plainlinks" style="width:100%;" !<!-- no box here, honest! --> !Currently testing... !Link !Description |- !&nbsp;1&nbsp; |UI Enhancements |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.1 /sandbox.1]</span> |Staging color scheme and new icons |- !&nbsp;2&nbsp; |MVEmbed |<span style="plainlinks"></span> |This sandbox has been deprecated, use sandbox 9 instead. |- !&nbsp;3&nbsp; |Section edit link redesign, Side-by-side preview |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.3 /sandbox.3]</span> |section edit link, side-by-side AJAX preview, collapsible template staging |- !&nbsp;4&nbsp; |FlaggedRevs, Drafts, AjaxLogin |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.4 /sandbox.4]</span> |Staging an extension that allows users to create and approve drafts of articles, FlaggedRevs integration and AJAX login. |- !&nbsp;5&nbsp; |UI enhancements |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.5 /sandbox.5]</span> |Staging color schemes, new icons, and new tabs |- !&nbsp;6&nbsp; |Template folding and editing |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.6 /sandbox.6]</span> |Primitive prototype. Staging template folding (more to come) |- !&nbsp;7&nbsp; |Collapsible left navigation |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.7 /sandbox.7]</span> |Staging footer cleanup, SimpleSurvey extension |- !&nbsp;8&nbsp; |RTL version of sandbox 6 |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.8 /sandbox.8]</span> |- !&nbsp;9&nbsp; |JS2Support extension sandbox 9 |<span style="plainlinks">[http://prototype.wikimedia.org/sandbox.9 /sandbox.9]</span> |JS2Support as an extension, includes AddMediaWizard, UploadWizard, UsabilityJS2, and TimedMediaHandler Extensions |} </span> All sandboxes are running the same core software and using the same database, but each have a unique configuration and set of extensions, so any edits to one of the sandboxes will render the edit to the other ones as well. == Feedback == Comments should be posted to the [[Talk:Sandbox|sandbox discussion page]]. Bugs should probably not be reported since the software running on these servers is expected to be experimental. == See also == *[[Demo]] *[[Prototype]] dpwtpr7rg4eihlpldtnqamtmz6pr9f3 0 6 8178 5598 2010-06-24T19:48:54Z Shuhari 4 /* Creating your own Selenium RC scripts */ wikitext text/x-wiki == Design == === [http://tango.freedesktop.org/Tango_Desktop_Project Tango Desktop Project] === A project which defines a set of guidelines and resources for the design and naming of icons used in desktop software. The icons are licensed under a [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Attribution Share-Alike license] and examples of the standard icon set can be seen on [http://commons.wikimedia.org/wiki/Tango_icons WikiMedia Commons]. It's perhaps notable that the Tango Desktop Project uses MediaWiki for their own site, perhaps further indicating an alignment of objectives and values. === [http://art.gnome.org Gnome Art] === A set of icons based on the Tango Desktop Project which have been tuned to the needs of the Gnome desktop. Examples can be seen [http://commons.wikimedia.org/wiki/GNOME_Desktop_icons WikiMedia Commons] and also [http://people.freedesktop.org/~jimmac/icons/#git FreeDesktop.org]. === Open Source Design Solutions === ====Wireframes==== * [http://gomockingbird.com Mockingbird] * [http://www.axure.com Axure] Other resources: * [http://www.evolus.vn/Pencil/Home.html Pencil] (Firefox extension) * [http://dub.washington.edu:2007/denim/ DENIM] * [http://wireframes.linowski.ca/ Wireframes Resources blog] * [http://www.clickframes.org/ ClickFrames] * [http://www.fluidia.org/ fluidIA] ====Vector Graphics==== * [http://www.inkscape.org Inkscape] == Requirements management == * [http://requirements.tigris.org/ Requirements on Tigris] * [http://sourceforge.net/projects/osrmt/ Open Source Requirements Management Tool] * a wiki ? == Testing == ==== [http://extensiontesting.wikiation.nl Wikiation extension testing] ==== When software gets bigger, it becomes harder to maintain and support. Testing helps to get to grips with this. This environment's ultimate aim is to provide the best possible testing environment for MediaWiki usage. Both for developers, hosts and for users of the MediaWiki software. Extension testing does help to get a reproducable result of an extension. This does help the user to get a feeling of control. ==== MediaWiki Testing Environment ==== What was originally the "Wikiation Extension Testing Environment" has been forked into the "MediaWiki Testing Environment". It has been forked and the development has been continued. This software is Open Source and is available under the MIT license and is available from the WMF Subversion. Changes since the fork include new documentation including documentation that is delivered with the code. The software for environments is now using information from tables for improved maintainability and for consistent implementation of standards. It is now possible to create multiple instances of an environment in one go. One important departure from the WETE is that we do not only concentrate on extensions. There is also a need to test MediaWiki itself and we have to be open for testing the underlying (LAMP et al) software as well. ==== Interaction testing automation ==== [[File:Selenium architecture diagram.svg|thumb|Selenium architecture diagram]] An automated testing environment for multiple platforms using Selenium IDE, RC, and Grid. QA testers can do step based interaction testing using Selenium IDE, then output them as a Selenium script. The scripts can be run on Selenium RC servers, which will run the tests on different platforms and browsers. The process can be integrated into the development cycle to avoid regressions. See the Selenium architecture diagram for proposed implementation. The idea of using Selenium for testing MediaWiki extensions was started a couple of years ago at Organic Design but was put on the back burner. There may be some useful ideas or code in it though, see [[OrganicDesign:Selenium]] and [[MW:Extension:Selenium]] for more information. Some example tests can be run [http://www.organicdesign.co.nz/wiki/extensions/Selenium/selenium-core/core/TestRunner.html?test=%2Fwiki%2Findex.php%3Ftitle%3DSpecial%3ASelenium%26suite%3DExample+Selenium+test+suite here]. ===== Setting up your environment to use the Selenium servers ===== # Ensure you have Java 1.6 or higher # [http://seleniumhq.org/download/ Download Selenium RC] ===== Testing against the selenium servers ===== After unzipping the RC download: # cd selenium-remote-control-<version> # cd selenium-python-client-driver-<version> # Add the below script as raskin-safari.py # Run the script: #: python raskin-safari.py <source lang=python> from selenium import selenium import unittest, time, re class Untitled(unittest.TestCase): def setUp(self): self.verificationErrors = [] self.selenium = selenium("raskin.usability.wikimedia.org", 4444, "*safari", "http://en.wikipedia.org/") self.selenium.start() def test_untitled(self): sel = self.selenium sel.open("/wiki/Main_Page") sel.wait_for_page_to_load(10000) def tearDown(self): self.selenium.stop() self.assertEqual([], self.verificationErrors) if __name__ == "__main__": unittest.main() </source> ===== Creating your own Selenium RC scripts ===== You can either create your scripts from scratch in selenese, or you can use [http://seleniumhq.org/download/ Selenium IDE] (a firefox plugin) to create the scripts through user interaction. ===== Test Cases ===== [[Resources/QA_Automation#SVN_Commits|A page]] to summarize the automation test scope and cases are being built. Please help to make the test cases comprehensive. 4u3bnm46s7mostjuxxjub9iauucy9ib 0 7 8593 5437 2010-07-29T12:27:45Z Nemo bis 9 cat wikitext text/x-wiki == Metrics == The initial step is to define the metrics which are relevant to the usability of Wikipedia. ===User Demographic Data=== UNU-Merit and Wikimedia Foundation conducted [http://blog.wikimedia.org/2009/04/16/first-preliminary-results-from-unu-merit-survey-of-wikipedia-readers-and-contributors-available/ Wikipedia Global Survey] in October 2008. Among more than 130,000 Wikipedians who participated in the survey, the average age of survey participants was 25.8 years old and half of the respondents were between 18 and 30 years old. Average age of readers was 25.3 years old while contributors was 26.8 years old. Two-thirds of the respondents were male and one-third was female. During the usability study, we observed the difference how the study participants among different age group interacted with editing process of Wikipedia. The objective of the Wikipedia Usability Initiative is to remove the barrier from across all age groups and gender, and it will be insightful to see how the age distribution of users especially for editors change over time. Activity Types The data provided by UNU-Merit shows that 62.55% of Wikipedia users are readers. Occasional contributors account for 24.5% and active contributors account for 9.18%. Although there are many factors and motives for users to contribute, the usability improvement of MediaWiki should help to increase the share of contributors. ===User Behavioral Metrics=== [http://stats.wikimedia.org/EN/Sitemap.htm Wikipedia Statistics] has essential statistical data for the usability metrics. However the data dump of English is yet to be completed from October 2006. Once the data is available, the following metrics will help the usability team to evaluate the usability improvements of the software. It is important to track externalities, such as activity surge in specific topics, activity level of vandalism, activities by bots and etc. *[http://stats.wikimedia.org/EN/TablesWikipediansContributors.htm Contributors] Wikipedians who edited at least 10 times since they arrived. *[http://stats.wikimedia.org/EN/TablesWikipediansNew.htm New Wikipedians] Increase in wikipedians who edited at least 10 times since they arrived. :10 edits seems high entry point to be considered as a new Wikipedian. Having a discussion with Erik Zachte in tracking granular frequency. (e.g. 3, 5 times) *[http://stats.wikimedia.org/EN/TablesWikipediansEditsGt5.htm Active Wikipedians] Wikipedians who contributed 5 times or more in this month. ===Article Metrics=== *[http://stats.wikimedia.org/EN/TablesArticlesTotal.htm Article count] Articles that contain at least one internal link *[http://stats.wikimedia.org/EN/TablesArticlesTotal.htm New articles per day] New articles per day in a given month *[http://stats.wikimedia.org/EN/TablesArticlesEditsPerArticle.htm Edits per article] Mean number of revisions per article *[http://stats.wikimedia.org/EN/TablesArticlesBytesPerArticle.htm Bytes per article] Mean size of article in bytes *[http://stats.wikimedia.org/EN/TablesDatabaseEdits.htm Edits per month] Edits in past month (incl. redirects, incl. unregistered contributors, incl. bots) ===Application Specific Metrics=== :'''Edit''' - As the first usability release (Acai) reorganizes the tabs, it will be good to capture if the click-through-rate of edit tabs go up or not. :'''Edit/Save''' - Usability study showed that some study participant just get lost in within “Edit” mode and never get to “Preview” or “Save” It is critical that we track the save rate. :'''Search''' ::Location - Search location in the new skin “Vector” is moved from above the left navigation bar to right hand corner. The search usage need to be tracked. ::Go vs Search - “Go” takes the inquiry directly to an article, and “Search :'''Toolbar usage''' :'''Left Navigation''' : '''Vector Opt-in rate''' ===Quality of edits=== :: It's not yet clear on how this may be measured yet. Please feel free to [[Talk:Wikipedia_Statistical_Survey#Ideas_for_quantitatively_evaluating_edits_being_made_on_Wikipedia|discuss]] this process with us. == Results == The results may be posted here. Ideally a comparison of the statistics over time will give some indication to the impact that changes to English Wikipedia have caused. === Example formats for results === The following are suggested examples of how collected data might be displayed. ==== Number of users who performed edits each month grouped by number of edits ==== {| cellspacing="0" cellpadding="5" ! width="100" style="border-bottom:solid 1px silver;" | Month ! colspan="4" style="border-bottom:solid 1px silver" | Number of edits in one month |-- ! style="border-right:solid 1px silver;" | ! width="150" align="left" | 1 - 9 ! width="150" align="left" | 10 - 99 ! width="150" align="left" | 100 - 999 ! width="150" align="left" | 1000+ |-- | style="border-right:solid 1px silver;" | January 2009 | # (%) | # (%) | # (%) | # (%) |-- | style="border-right:solid 1px silver;" | February 2009 | # (%) | # (%) | # (%) | # (%) |} [[Category:Statistics]] fjzrzj361owkmizc4wyoyv0u0ds3bfe 0 8 43 2009-02-09T18:16:38Z Trevor Parscal (WMF) 3 moved [[Editor Survey]] to [[Wikipedia Statistical Survey]]:&#32;More focused and specific title wikitext text/x-wiki #REDIRECT [[Wikipedia Statistical Survey]] 3pqwjlxzibp2ywtpzeict6unulajd2b 0 9 58 2009-02-10T19:47:41Z Trevor Parscal (WMF) 3 Created page with 'Which metrics should we consider and why?' wikitext text/x-wiki Which metrics should we consider and why? rdwzsxy80ep0ohca5aqgc4vwe6t6zll 0 11 61 60 2009-02-10T19:51:01Z Shuhari 4 wikitext text/x-wiki * Number of new editors * Number of edits * Characteristic of edits over time ''Reasons to follow..'' 5qjslni6tc3hlmsquz723z37nskag9y 0 12 3322 2452 2009-09-28T19:08:44Z Mephiles602 621 why is there a blockquote? wikitext text/x-wiki __NOTOC__ {{Draft}} {{Internal}} == Overview == There are hundreds of pieces of extension software available for MediaWiki, many of which may provide some improvement in the area of usability. The analysis below focuses on extensions which provide alternative editing interfaces for MediaWiki. Some of the extensions below are beta software while others are currently in deployment with significant use. == Comparison Chart == {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Metric ! width="100" align="left" | [[#wikEd|wikEd]] ! width="100" align="left" | [[#FCKeditor_.28Official.29|FCKeditor]] ! width="100" align="left" | [[#Wikia Wysiwyg|Wikia Wysiwyg]] ! width="100" align="left" | [[#MeanEditor|MeanEditor]] ! width="100" align="left" | [[#Wikiwyg|Wikiwyg]] |- ! colspan="6" | Compatibility |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#Browser Compatibility|Web Browsers]] | style="color:orange" | 5 (42%) [[#Browser Compatibility|&darr;]] | style="color:green" | 12 (100%) [[#Browser Compatibility_2|&darr;]] | style="color:orange" | 4 (33%) [[#Browser Compatibility_3|&darr;]] | style="color:orange" | 4 (33%) [[#Browser Compatibility_4|&darr;]] | style="color:orange" | 5 (42%) [[#Browser Compatibility_5|&darr;]] |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#License Compatibility|Open License]] | style="color:green" | YES [[#License Compatibility|&darr;]] | style="color:green" | YES [[#License Compatibility_2|&darr;]] | style="color:green" | YES [[#License Compatibility_3|&darr;]] | style="color:green" | YES [[#License Compatibility_4|&darr;]] | style="color:green" | YES [[#License Compatibility_5|&darr;]] |- ! colspan="6" | Performance |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#Download Size|Download Size]] | 107KB [[#Download Size|&darr;]] | 399KB [[#Download Size_2|&darr;]] | 132KB [[#Download Size_3|&darr;]] | 120KB [[#Download Size_4|&darr;]] | 87KB [[#Download Size_5|&darr;]] |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#UI Responsiveness|UI Responsiveness]] | style="color:red" | LOW [[#UI Responsiveness|&darr;]] | style="color:orange" | MEDIUM [[#UI Responsiveness_2|&darr;]] | style="color:orange" | MEDIUM [[#UI Responsiveness_3|&darr;]] | style="color:orange" | MEDIUM [[#UI Responsiveness_4|&darr;]] | style="color:green" | HIGH [[#UI Responsiveness_5|&darr;]] |- ! colspan="6" | Quality |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#Completeness|Completeness]] | style="color:orange" | MEDIUM [[#Completeness|&darr;]] | style="color:green" | HIGH [[#Completeness_2|&darr;]] | style="color:orange" | MEDIUM [[#Completeness_3|&darr;]] | style="color:orange" | MEDIUM [[#Completeness_4|&darr;]] | style="color:red" | LOW [[#Completeness_5|&darr;]] |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#User Features|User Features]] | style="color:red" | 0 (0%) [[#User Features|&darr;]] | style="color:orange" | 9 (90%) [[#User Features_2|&darr;]] | style="color:green" | 10 (100%) [[#User Features_3|&darr;]] | style="color:orange" | 7 (70%) [[#User Features_4|&darr;]] | style="color:orange" | 6 (60%) [[#User Features_5|&darr;]] |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#Extendable|Extendable]] | style="color:red" | NO [[#Extendable|&darr;]] | style="color:green" | YES [[#Extendable_2|&darr;]] | style="color:green" | YES [[#Extendable_3|&darr;]] | style="color:green" | YES [[#Extendable_4|&darr;]] | style="color:red" | NO [[#Extendable_5|&darr;]] |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#Themable|Themable]] | style="color:red" | NO [[#Themable|&darr;]] | style="color:green" | YES [[#Themable_2|&darr;]] | style="color:green" | YES [[#Themable_3|&darr;]] | style="color:green" | YES [[#Themable_4|&darr;]] | style="color:red" | NO [[#Themable_5|&darr;]] |- | align="left" | [[Environment_Survey/MediaWiki_Extensions/Criteria#Internationalization.2FLocalization|i18n/L10n]] | style="color:green" | 3 (100%) [[#Internationalization.2FLocalization|&darr;]] | style="color:green" | 3 (100%) [[#Internationalization.2FLocalization_2|&darr;]] | style="color:green" | 3 (100%) [[#Internationalization.2FLocalization_3|&darr;]] | style="color:green" | 3 (100%) [[#Internationalization.2FLocalization_4|&darr;]] | style="color:green" | 3 (100%) [[#Internationalization.2FLocalization_5|&darr;]] |} == Extension Details == === wikEd === [[File:Extension-WikiEd.png|thumb|wikiEd Extension running on English Wikipedia as a Gadget]] Adds syntax highlighting and a large number of tools to the existing MediaWiki editor. The target audience of this extension seems to be advanced users, as it provides a user interface more similar to a programming IDE than a word-processor. '''Notes''' * Dynamic diff and preview * Stable and under active development * Translated/localized for many languages * Supports pasting and conversion from web pages and MS Word * Support by upcoming versions of Opera and MS IE expected ==== Download Size ==== 94 files @ 107KB total ==== Browser Compatibility ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Browser ! align="left" | Version ! width="100" align="left" | Windows ! width="100" align="left" | Linux ! width="100" align="left" | MacOS ! width="100" align="left" | iPhone |- | Firefox | 1.5+ | style="color:green;" | OK | style="color:green;" | OK | style="color:green;" | OK | style="color:silver;" | N/A |-- | Safari | 3.0+ | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Opera | 9.50+ | NOT | NOT | NOT | NOT |-- | Internet Explorer | 5.5+ | NOT | NOT | NOT | NOT |-- | Google Chrome | | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Camino | 1.0+ | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |} ==== License Compatibility ==== This software is under Public Domain. ==== UI Responsiveness ==== * Users on slower internet connections may experience a very disturbing amount of load time as the icon images are synchronously fetched. Our average load time was a few seconds for all icons to appear. The primary issue here is that the images are loading one-after-another and are blocking all other page rendering and user interaction until they are finished. On some browsers this loading occurred once for each article, which depending on use often translated into every time the user navigated to an edit page. * Because of performance issues, the syntax highlighting only occurs when loading the edit box initially, or turning the syntax highlighting off and the on again. Depending on the user's computer and the length of the article, syntax highlighting may take anywhere from a fraction of a second to a few seconds. * Toggling between syntax-highlighted mode and plain wiki-text mode was nearly instant, unless you made a change while in plain wiki-text mode in which case you were subjected to the same syntax-highlighting wait time issue. ==== Completeness ==== Although the intended features of this software seem to be completely implemented and it's currently deployed on Wikipedia as a gadget that users can turn on through user preferences, it's lack of support for most browsers and number of known issues and incompatibilities hint that this software has a long way to go. ==== User Features ==== Although this software provides an extensive set of text manipulation features, none of the common wiki elements are abstracted by a user interface making it in most cases no better than a plain text editor. ==== Extendable ==== Although any JavaScript software naturally lends itself to extendability, there is no functionality for configuring individual components or documented API for developing such components. ==== Themable ==== Although it's possible to change images and CSS style sheets, there's no functionality for configuring individual themes and some style information is embedded within the JavaScript code itself. ==== Internationalization/Localization ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Feature ! align="left" | Support |- | UI L10n | style="color:green;" | OK |- | Alternative Input | style="color:green;" | OK |- | Double-Byte | style="color:green;" | OK |} </blockquote> === FCKeditor (Official) === <blockquote> [[File:Extension-FCKEditor.png|thumb|FCKEditor Extension running on a sandbox]] Provides a fairly robust set of features in a fully WYSIWYG environment and is based on FCKeditor which is an actively maintained in-browser XHTML WYSIWYG editor project. The target audience of this extension seems to be inexperienced users with some form of desktop-publishing experience, as the user interface is extremely similar to Microsoft Word. '''Notes''' * There are various themes for this editor ranging from Microsoft Office clones to custom icon sets. ==== Download Size ==== 32 files @ 399KB total ==== Browser Compatibility ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Browser ! align="left" | Version ! width="100" align="left" | Windows ! width="100" align="left" | Linux ! width="100" align="left" | MacOS ! width="100" align="left" | iPhone |- | Firefox | 1.5+ | style="color:green;" | OK | style="color:green;" | OK | style="color:green;" | OK | style="color:silver;" | N/A |-- | Safari | 3.0+ | style="color:green;" | OK | style="color:silver;" | N/A | style="color:green;" | OK | style="color:green;" | OK |-- | Opera | 9.50+ | style="color:green;" | OK | style="color:green;" | OK | style="color:green;" | OK | style="color:silver;" | N/A |-- | Internet Explorer | 5.5+ | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Google Chrome | | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Camino | 1.0+ | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:green;" | OK | style="color:silver;" | N/A |} ==== License Compatibility ==== This software is under a mix of GPL, LGPL and MPL licenses. ==== UI Responsiveness ==== * Initial loading took a few seconds while additional loads were nearly immediate. A loading message was visible in the text area while the article was loaded and processed. The loading of the article seemed to be the majority of the wait once the editor had been loaded once. * Dialogs which assist the user in inserting tables, images and other elements into the article were fast, but not immediate as they required a new browser window which on many systems introduces a certain amount of overhead and thus wait time. * Switching to wiki-text mode was instant, but switching back to WYSIWYG mode took about a second each time. ==== Completeness ==== Given this software's excellent browser support and extensive list of functioning features, this software seems to have reached a fairly high level of maturity. The stability of the software benefits from a large community of active developers who are empowered by a well structured project management system where they can report bugs and submit patches quickly. This software saw some deployment on some Wikia sites for a brief period of time before they branched, and looks to be in use on many small wikis. ==== User Features ==== ==== Extendable ==== A well documented API exists for adding extra functionality to the FCKeditor and over 100 such plug-ins already exist. ==== Themable ==== There are several skins for FCKeditor which generally aim at replicating the user experience of Microsoft Office products. ==== Internationalization/Localization ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Feature ! align="left" | Support |- | UI L10n | style="color:green;" | OK |- | Alternative Input | style="color:green;" | OK |- | Double-Byte | style="color:green;" | OK |} </blockquote> === Wikia Wysiwyg === <blockquote> [[File:Extension-WikiaWysiwyg.png|thumb|Wikia Wysiwyg Extension running on a sandbox]] Provides a focused set of features which are relevant to Wiki articles in a fully WYSIWYG environment and is based on FCKeditor as it is a branch of the official FCKeditor MediaWiki extension. The target audience of this extension, similar to the official FCKeditor extension, is inexperienced users with desktop-publishing experience, however this extension greatly reduces the number of features available to the user in favor of simplifying the user interface and bringing focus to common wiki article elements. ==== Download Size ==== 41 files @ 132KB total ==== Browser Compatibility ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Browser ! align="left" | Version ! width="100" align="left" | Windows ! width="100" align="left" | Linux ! width="100" align="left" | MacOS ! width="100" align="left" | iPhone |- | Firefox | 1.5+ | style="color:green;" | OK | style="color:green;" | OK | style="color:green;" | OK | style="color:silver;" | N/A |-- | Safari | 3.0+ | style="color:black;" | NOT | style="color:silver;" | N/A | style="color:black;" | NOT | style="color:black;" | NOT |-- | Opera | 9.50+ | style="color:black;" | NOT | style="color:black;" | NOT | style="color:black;" | NOT | style="color:silver;" | N/A |-- | Internet Explorer | 5.5+ | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Google Chrome | | style="color:black;" | NOT | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Camino | 1.0+ | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:black;" | NOT | style="color:silver;" | N/A |} ==== License Compatibility ==== This software is under the GPL license. ==== UI Responsiveness ==== * Although an animated loading graphic was provided to indicate to the user that the page was not ready yet, the loading time was about 8-10 seconds the first time, and 4-5 seconds on additional page loads. * The dialogs which assist users with embedding templates and various kinds of media in the article also provided an immediate visual response to clicking on the button by displaying an animated loading graphic, but would still on average take a few seconds to load. * Dialogs for links were very fast, taking only a fraction of a second to finish loading. * Switching between wiki-text and WYSIWYG mode took anywhere from a few seconds to a fraction of a second depending on whether the content was changed significantly enough to require a trip to the server for parsing or not. ==== Completeness ==== Although based on FCKeditor, this branch has made many concessions in stability and compatibility in the name of quickly implementing various usability oriented design changes and has left the resulting code detached from the FCKeditor development community. That said, this software is being deployed regularly on new Wikia projects and is being actively improved by the Wikia staff. ==== User Features ==== ==== Extendable ==== Although there is no specific documentation available for this branch of the FCKEditor, a few extensions do exist for it which seem to use the same API, indicating this software is similarly extendable. ==== Themable ==== Although the current visual style is a form of an FCKeditor skin, which speaks to the ability to theme this software, changes in the layout of the toolbar prevent this editor from being compatible with other existing FCKeditor skins, and there are currently not any skins in existence for this branch of FCKeditor. ==== Internationalization/Localization ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Feature ! align="left" | Support |- | UI L10n | style="color:green;" | OK |- | Alternative Input | style="color:green;" | OK |- | Double-Byte | style="color:green;" | OK |} </blockquote> === MeanEditor === <blockquote> [[File:Extension-MeanEditor.png|thumb|MeanEditor Extension running on a sandbox]] Provides a hybrid (visual/logical) WYSIWYM approach to editing with basic wiki-oriented features and is based on the WYMEditor project. The target audience of this extension seems to be intermediate users as it's user interface reinforces a separation between model and view which is somewhat of a foreign concept to many inexperienced users, however it may help to illustrate this concept to inexperienced users through it's visual representation of article blocks and sections. * Work being done to integrate a newer version of WYMEditor which is compatible with all browsers * Compatible with MediaWiki 1.15alpha, but requires patch to EditPage.php ==== Download Size ==== 10 files @ 120KB total ==== Browser Compatibility ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Browser ! align="left" | Version ! width="100" align="left" | Windows ! width="100" align="left" | Linux ! width="100" align="left" | MacOS ! width="100" align="left" | iPhone |- | Firefox | 2.0+ | style="color:green;" | OK | style="color:green;" | OK | style="color:green;" | OK | style="color:silver;" | N/A |-- | Safari | 3.1+ | style="color:black;" | NOT | style="color:silver;" | N/A | style="color:black;" | NOT | style="color:black;" | NOT |-- | Opera | 9.50+ | style="color:black;" | NOT | style="color:black;" | NOT | style="color:black;" | NOT | style="color:silver;" | N/A |-- | Internet Explorer | 6+ | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Google Chrome | | style="color:black;" | NOT | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Camino | 1.0+ | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:black;" | NOT | style="color:silver;" | N/A |} ==== License Compatibility ==== This software is under a mix of MIT and GPL licenses. ==== UI Responsiveness ==== * Initial loading time took a few seconds, while additional loads took around a second. The page loading is blocked while the editor initializes which makes for a somewhat disruptive visual experience. * Dialog for embedding images into the article is instant, with an animated effect that shades the editing area while working with the dialog. * Switching between XHTML and WYSIWYM modes is instantaneous. ==== Completeness ==== Although there is active development going on to improve the WYMeditor, which has resulted in browser support similar to FCKeditor and much more stable implementation of existing features, this extension has yet to become compatible with the latest version of WYMeditor leaving it in a somewhat less mature state. This software is still a work-in progress and has never been widely deployed, however there are a few developers who have been continuing to actively improve it. ==== User Features ==== ==== Extendable ==== A briefly documented API exists for adding extra functionality to the WYMeditor, but only 1 such plug-ins already exists. ==== Themable ==== There are a few themes for WYMeditor which all look to be generic styles with icons very typical of rich text editing. ==== Internationalization/Localization ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Feature ! align="left" | Support |- | UI L10n | style="color:green;" | OK |- | Alternative Input | style="color:green;" | OK |- | Double-Byte | style="color:green;" | OK |} </blockquote> === Wikiwyg === <blockquote> [[File:Extension-Wikiwyg.png|thumb|Wikiwyg Extension running on a test page]] Provides a simple WYSIWYG environment for a single section of content directly within the view mode of a page. Admittedly no longer actively supported or worked on, this extension takes a unique approach to the process of editing an article which has been validated in part by other per-section editing approaches like UniWiki's simplified editor. The target audience of this extension seems to be inexperienced users familiar with basic rich text editing like WordPad on Windows or TextEdit on MacOS as it only provides a limited set of formatting tools and enables editing in place. '''Notes''' * Very limited browser support for WYSIWYG and incomplete browser support for markup * "Gracefully" degrades to a plain text editor when incompatible with a browser * Incompatible with current version of MediaWiki ==== Download Size ==== 25 files @ 87KB total ==== Browser Compatibility ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Browser ! align="left" | Version ! width="100" align="left" | Windows ! width="100" align="left" | Linux ! width="100" align="left" | MacOS ! width="100" align="left" | iPhone |- | Firefox | 1.5+ | style="color:green;" | OK | style="color:green;" | OK | style="color:green;" | OK | style="color:silver;" | N/A |-- | Safari | 3.0+ | style="color:black;" | NOT | style="color:silver;" | N/A | style="color:black;" | NOT | style="color:black;" | NOT |-- | Opera | 9.50+ | style="color:black;" | NOT | style="color:black;" | NOT | style="color:black;" | NOT | style="color:silver;" | N/A |-- | Internet Explorer | 6+ | style="color:green;" | OK | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Google Chrome | | style="color:black;" | NOT | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:silver;" | N/A |-- | Camino | 1.0+ | style="color:silver;" | N/A | style="color:silver;" | N/A | style="color:green;" | OK | style="color:silver;" | N/A |} ==== License Compatibility ==== This software is under the LGPL license. ==== UI Responsiveness ==== * Loading is performed asynchronously and invisibly, since the editor is not initially visible * Upon double-clicking within the area of a section of content, the editor appears for that section instantly. * Switching between preview, WYSIWYG and plain wiki-text is virtually instantaneous, however when switching to and from wiki-text the user is confronted with a warning about HTML conversion taking place, blocking the operation until the user decides to continue or not which felt very disruptive. ==== Completeness ==== This extension was abandoned before it reached maturity, leaving many intended features unimplemented and bugs unfixed. ==== User Features ==== ==== Extendable ==== No API exists through which this software can be extended. ==== Themable ==== The visual aspects of this extension are very basic and are not very changeable aside from modifying the small number of images which are used as icons. ==== Internationalization/Localization ==== {| cellpadding="3" border="1" cellspacing="3" |- ! align="left" | Feature ! align="left" | Support |- | UI L10n | style="color:green;" | OK |- | Alternative Input | style="color:green;" | OK |- | Double-Byte | style="color:green;" | OK |} osou9a5wwwc9e0cakyda0xavnw7vcvi 0 13 1569 1568 2009-05-29T17:47:49Z Trevor Parscal (WMF) 3 wikitext text/x-wiki When we got the whiteboard in our office up one of our developers drew our logo at the top with a slogan beneath it. Each morning, the slogan seemed to change. This is a log of the slogans which have appeared on the board over time. [[Image:Whiteboard-Logo.jpg|border|right]] * The early bird gets the edit! - 3/20/2009 * How do I add a reference? - 3/17/2009 * If only I could edit this! - 3/10/2009 * Who is the user? - 3/9/2009 * Where is the cheat sheet? - 3/4/2009 * My mother should never have to learn wiki markup! - 3/3/2009 * Me misses Liquid Threads. - 3/2/2009 * What was it? - 2/27/09 * This was supposed to be fun! - 2/26/2009 * Who deleted my edits? - 2/25/2009 * Diff as in difficult to use? - 2/23/2009 * Edit now, or forever hold your peace - 2/20/2009 * How do I create an article? - 2/19/2009 * Is it "Talk" or "Discussion"? - 2/18/2009 * Wikipedia *is* easy to use ^{[citation needed]} - 2/17/2009 * I can haz moor edits? - 2/13/2009 * How do I upload a photo? - 2/12/2009 * Where's the edit button? - 2/11/2009 * The future is coming soon - 2/10/2009 033nasi9vdio7uaeqhd18jy9r0wb1pr 0 16 6398 3154 2010-04-02T15:07:30Z Amire80 1559 /* Other */ added Interlanguage wikitext text/x-wiki If you would like to nominate a MediaWiki compatible extension for inclusion in our [[Environment Survey]], please feel free to add it below. We also welcome you to explore existing nominations and provide feedback by giving ratings or through the [[Talk:Environment Survey/MediaWiki Extensions/Nomination|discussion page]]. == Resources == * An excellent [[mw:Extension Matrix|comparison]] has already been done on a much broader range of extensions. * [[mw:WYSIWYG_editor|Information]] about varied approaches to editing in a more visual manner. == Nominations == ===Editing=== {| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;" ! width="320" align="left" | Extension ! width="40" align="left" | Example ! width="100" align="left" | License ! align="left" | Summary |-- | [[mw:Extension:FCKeditor (Official)|FCKeditor (Official)]] <ratings:scale category="Extension Survey/Extension Nomination/Editing" title="FCKeditor" /> | [http://mediawiki.fckeditor.net/index.php?title=Sandbox&action=edit] | [[w:GNU General Public License|GPL]] v2 / [[w:GNU Lesser General Public License|LGPL]] v2 / [[w:Mozilla Public License|MPL]] | WYSIWYG editor with markup fallbacks and good cross-browser compatibility. Developed by the official FCKEditor team. |-- | Wikia Wysiwyg <ratings:scale category="Extension Survey/Extension Nomination/Editing" title="WikiaWysiwyg" /> | [http://legobatman.wikia.com/index.php?title=sandbox&action=edit] | No license specified | WYSIWYG editor with markup fallbacks and good cross-browser compatibility. Based on FCKEditor with additional improvements aimed at enhancing usability. |-- | [[mw:Extension:MarkitUp MW|MarkitUp MW]]<ratings:scale category="Extension Survey/Extension Nomination/Editing" title="MarkitUp MW" /> | [http://markitup.jaysalvat.com/examples/wiki/] | [[w:GNU General Public License|GPL]] v2 / [[w:MIT License|MIT]] | Markup editor, similar to existing functionality with good cross-browser compatibility. New and possibly unstable. |-- | [[mw:Extension:Wikiwyg|Wikiwyg]]<ratings:scale category="Extension Survey/Extension Nomination/Editing" title="Wikiwyg" /> | [http://www.wikiwyg.net/demo/] | No license specified | WYSIWYG editor with limited browser compatibility. Seems to be abandoned in favor of the FCKeditor. |-- | [[mw:Category:Uniwiki|Uniwiki]]<ratings:scale category="Extension Survey/Extension Nomination/Editing" title="Uniwiki" /> | [http://www.appropedia.org/index.php?title=Appropedia:Sandbox&action=edit] | [[w:GNU General Public License|GPL]] v2 | Functionality developed by UNESCO to make MediaWiki usable. These tools are based on genuine usability tests. |-- | [[w:User:Cacycle/wikEd|wikEd]]<ratings:scale category="Extension Survey/Extension Nomination/Editing" title="WikiEd" /> | [http://en.wikipedia.org/wiki/Special:Preferences Gadget] on enwiki | Public Domain | Text editor with syntax highlighting, instant diff/preview, find/replace, and MS Word conversion. Widely used, including as gadget on many Wikipedias. Stable and under active development. Translated/localized for many languages. Avoids less user friendly aspects of WYSIWYG. ([[w:User:Cacycle/wikEd_help#WYSIWYG|more]]). |-- | [[mw:Extension:MeanEditor|MeanEditor]]<ratings:scale category="Extension Survey/Extension Nomination/Editing" title="MeanEditor" /> | [http://allievi.sssup.it/jacopo/mwsvn/index.php?title=Sandbox&action=edit] | [[w:GNU General Public License|GPL]] v2 | [[w:WYSIWYM|WYSIWYM]] editor |-- | [[mw:Extension:Semantic Forms|Semantic Forms]] <ratings:scale category="Extension Survey/Extension Nomination/Editing" title="Semantic Forms" /> | [http://hackerspaces.org/w/index.php?title=Hackerspace_Brussels&action=formedit], [http://www.techpresentations.org/w/index.php?title=Wikimania_2009&action=formedit], [http://discoursedb.org/w/index.php?title=Dump_the_electoral_college&action=formedit] | [[w:GNU General Public License|GPL]] | Allows users to add and edit data using forms. It creates dynamic forms based on Form description pages and semantic properties (provided by Semantic MediaWiki) and as a result simply fills out templates with all collected parameters. This is just perfect for infoboxes and such. Features include field auto-completion, standard input types, map interface for coordinate picking, inline file uploads and more. Users include [http://www.wikia.com/ Wikia], [http://www.referata.com/wiki/Main_Page Referata], [http://wiki.creativecommons.org/Main_Page Creative Commons Wiki], [http://wiki.laptop.org/go/The_OLPC_Wiki OLPC Wiki] and [http://www.mediawiki.org/wiki/Semantic_Forms#Sites_that_use_Semantic_Forms more] |-- | [[mw:Extension:TinyMCE_MW|Tiny MCE MW]] <ratings:scale category="Extension Survey/Extension Survey/Extension Nomination/Editing" title="TinyMCE" /> | [http://tinymce.moxiecode.com/examples/full.php] | LGPL (extension and editor) | TinyMCE is not naturally a Wikitext editor. TinyMCE is a javascript WYSIWYG editor. With this extension, you can easily use TinyMCE with Mediawiki and provide users with a toolbar editor they may be more familiar with. The extension is not stable and no longer developed. |-- | Wikizzle <ratings:scale category="Extension Survey/Extension Survey/Extension Nomination/Editing" title="Wikizzle" /> | [http://wikizzle.org] | No license specified | While not providing true WYSIWYG (editing is done directly to wikitext), Wikizzle includes AJAX WYSIWYM editing features similar in purpose to WYSIWYG such as real-time rendering of the article. Runs in Mozilla. |} === Discussion === {| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;" ! width="320" align="left" | Extension ! width="40" align="left" | Example ! width="100" align="left" | License ! align="left" | Summary |-- | [[mw:Extension:LiquidThreads|LiquidThreads]]<ratings:scale category="Extension Survey/Extension Nomination/Disucssion" title="LiquidThreads" /> | [http://wikieducator.org/Talk:LiquidThreads] | GPL v2 | A new discussion page system. Unclear on how existing discussion pages would be converted. Still pending additional code review to determine its suitability for large-scale deployment. |-- | [[mw:Extension:DPLforum|DPLforum]]<ratings:scale category="Extension Survey/Extension Nomination/Disucssion" title="DPLforum" /> |[http://www.undefined.net/w/index.php?title=Talk:DPLforum] [http://www.wikia.com/wiki/Forum:Index] | GPL v2 or later | DPLforum is a heavily-adapted derivation of DynamicPageList 1.12, geared toward displaying forum-style layouts. It is used on many Wikia Wikis. |} === Other === {| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;" ! width="320" align="left" | Extension ! width="40" align="left" | Example ! width="100" align="left" | License ! align="left" | Summary |-- | [[mw:Extension:Semantic MediaWiki|Semantic MediaWiki]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="Semantic MediaWiki" /> | [http://semanticweb.org/index.php?title=San_Diego&action=edit] | GPL | Helps to make explicit relations between concepts expressed as MediaWiki articles. |-- | [[mw:Extension:LilyPond|LilyPond]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="LilyPond" /> | [http://www.cpdl.org/wiki/index.php/Help:How_can_I_add_a_LilyPond_excerpt%3F] | No license specified | This extension adds the option to typeset music directly in the wiki code, using the sintax <lilypond>...</lilypond>. This would be a better way of deal with articles about music than uploading images. Additionally, using <lilymidi>...</lilymidi> it is possible to click on the image to download the midi file. See also: [https://bugzilla.wikimedia.org/show_bug.cgi?id=189 bugzilla:189] and [http://lists.gnu.org/archive/html/lilypond-devel/2009-04/msg00258.html lilypond-devel list] |-- | Add Media Wizard <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Add Media Wizard" /> | - | GPL2 | Tool for adding media to pages or sequences. Includes abstracted remote media import; (currently commons, archive.org, and metavid supported); includes image edit tools. Works with images & video. Staged deployment possible as user Gadget. Uses script loader for localization and performance. Blog post [http://brianna.modernthings.org/article/184/media-handling-on-wikimedia-preview-the-future-part-1 review here] [http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/MetavidWiki/skins/add_media_wizard.js?revision=47525&view=markup code here] |-- | [[w:de:Benutzer:Revvar/VM|Vorlagenmeister]] (Template Master)<ratings:scale category="Extension Survey/Extension Nomination/Other" title="Template Master" /> | [http://de.wikipedia.org/wiki/Spezial:Einstellungen?uselang=en] | GFDL? | Gadget which allows adding/editing of templates through web forms, with help texts and some basic validation, based on an XML description. |-- | [[mw:Extension:Babel|Babel]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="Babel" /> | [http://translatewiki.net/wiki/User:Church_of_emacs/Babel_test_page] | GPL | An extension to have the Babel information ready for use in any wiki. Templates do not scale and are not maintained. |-- | [[mw:Extension:DynamicPageList|DynamicPageList]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="DynamicPageList" /> | [http://semeb.com/dpldemo/index.php?title=Example_1] | GPL | Create dynamic article lists in many ways, most importantly from category intersections. (Would allow a more reasonable, tag-like approach to categories instead of the current bloat.) |-- | [[mw:Extension:BreadCrumbs_(Kimon)|BreadCrumbs]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="BreadCrumbs" /> | - | GNU (?) | Facilitates the navigation of content, making it very easy to go back and also have an idea of the recent pages you've visited. (It really looks better situated at the top of the page, with white background colour). |-- | [[mw:Extension:OpenID|OpenID]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="OpenID" /> | [http://www.sharingbuttons.org/Special:OpenIDLogin] | GNU (?) | Single Signon for websites on the Internet. Saves us from the current password hell. |-- | [[mw:Extension:Labeled Section Transclusion|Labeled Section Transclusion]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="Labeled Section Transclusion" /> | [http://en.wikisource.org/wiki/Wikisource:Labeled_section_transclusion] | No license specified | Allows for the [[mw:Extension:Labeled_Section_Transclusion#Transcluding_visual_headings|transclusion of labeled sections]] (anchors). Not intended for use on mainspace. One potential use is to monitor active threads on noticeboards from the user space. Another use is to group similar templates using sections of only one template. |-- | [[mw:Extension:Drafts|Drafts]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="Drafts" /> | [http://test.wikipedia.org/wiki/Testing_Drafts_Extension] | GPL v2 | Adds the ability to save a draft of an article on the server while editing. Users must be logged in to save drafts, as they are tied to their user account. Drafts are always discarded when they are used to save the article they came from. |- | [[mw:Extension:PSINoTocNum|PSINoTocNum]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="PSINoTocNum" /> | - | No license specified | Adds the ability to suppress irritating automated numbering in tables of contents. |- | [[mw:Extension:MagicNoNumberedHeadings|MagicNoNumberedHeadings]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="MagicNoNumberedHeadings" /> | - | GPL | Adds the ability to suppress irritating automated heading numbers. |- | [[mw:Extension:MagicNumberedHeadings|MagicNumberedHeadings]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="MagicNumberedHeadings" /> | - | GPL | Adds the ability to unconditionally show automated heading numbers. |- | [[mw:Extension:ExtendAnchorTags|ExtendAnchorTags]]<ratings:scale category="Extension Survey/Extension Nomination/Other" title="ExtendAnchorTags" /> | - | No license specified | Allows added class values to be included in anchor tags, to support POSH and microformats. |- | [[mw:Extension:TransformChanges|TransformChanges]] <ratings:scale category="Extension Survey/Extension Nomination/Other" title="TransformChanges" /> | [http://www.organicdesign.co.nz/Special:RecentChanges] | GPL | Changes how recent changes and watchlist pages display lists of information, converting unordered lists to tables and providing CSS classification of output for more control over style customization. |- | [[mw:Extension:Interlanguage|Interlanguage]] <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Interlanguage" /> | [http://testwiki.smolenski.rs/] | GPL | Allows centralized management of interlanguage a.k.a. interwiki links. |} ===Features from Wikia=== {| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;" ! width="320" align="left" | Extension ! width="40" align="left" | Example ! width="100" align="left" | License ! align="left" | Summary |-- | Simpler image upload <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Simpler image upload" /> | [http://www.wikia.com/wiki/Help:Add_Images], [http://images3.wikia.nocookie.net/help/images/8/87/Addimages.png] | GPL | Provides guided image uploading and selection including cross linking to flickr. |-- | More obvious edit buttons <ratings:scale category="Extension Survey/Extension Nomination/Other" title="More obvious edit buttons" /> | [http://images2.wikia.nocookie.net/central/images/c/cc/Sectionedit-header1.jpg], [http://www.wikia.com/wiki/Forum:New_section_edit] | GPL | Increases the visibility of section edit links. |-- | Search suggest <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Search suggest" /> | [http://help.wikia.com/wiki/Help:Search_suggest] | GPL | Provides suggestions for search terms as the user enters text into the search box. |-- | Link suggest <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Link suggest" /> | [http://help.wikia.com/wiki/Help:Link_Suggest] | GPL | Automatically completes internal links as the user types. ([https://svn.wikia-code.com/wikia/trunk/extensions/wikia/LinkSuggest/ code]) |-- | Edit Page Enhancements <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Edit Page Enhancements" /> | [http://help.wikia.com/wiki/Help:Edit_Page_Enhancements], [http://www.wikia.com/wiki/Forum:New_edit_window], [http://images1.wikia.nocookie.net/help/images/f/f5/Edit_Page_Enhancements.png], [http://images2.wikia.nocookie.net/central/images/9/9f/Johncenaeditwindow.jpg] | GPL | Includes wide-screen mode and floating action buttons (such as edit and preview) which are always visible independent of scroll position ([https://svn.wikia-code.com/wikia/trunk/extensions/wikia/EditEnhancements/ code]) |-- | Editing tips <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Editing tips" /> | [http://help.wikia.com/wiki/Help:Edit_Page_Enhancements], [http://images1.wikia.nocookie.net/help/images/f/f5/Edit_Page_Enhancements.png] | GPL | Small help box displayed when editing. The help tips are editable and can be internationalized ([https://svn.wikia-code.com/wikia/trunk/extensions/wikia/EditingTips/ code]) |-- | Ajax login <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Ajax login" /> | - | GPL | Allows logging in without navigating away from the page you are at ([http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/AjaxLogin/ code]) |-- | Social Profile <ratings:scale category="Extension Survey/Extension Nomination/Other" title="Social Profile" /> | [http://halo.wikia.com/wiki/] | GPL | These package of extensions will incorporate a social profile, user board, and basic profile information into MediaWiki. ([http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/SocialProfile/ code]) |} hzlqgq3adcwbp7jzovmta94u8w2nnif 0 19 85 2009-02-13T08:28:13Z GerardM 5 Created page with 'Hoi, at Fosdem we demonstrated a testing environment for MediaWiki and its extensions. It includes an installer. I chatted with Naoko about this. We want to make this software av...' wikitext text/x-wiki Hoi, at Fosdem we demonstrated a testing environment for MediaWiki and its extensions. It includes an installer. I chatted with Naoko about this. We want to make this software available as open source. Sadly for personal reasons we cannot move as quickly as we like. I can get you access.. Please contact me.. Thanks, [[User:GerardM|GerardM]] 08:28, 13 February 2009 (UTC) jmojyo31f8pq1hin26rvjef5l6k3zez 0 21 87 2009-02-13T08:36:13Z GerardM 5 Created page with 'Hoi, I welcome the use of liquid threads. I have little experience with this tool so this is to experiment with this tool. Thanks, ~~~~' wikitext text/x-wiki Hoi, I welcome the use of liquid threads. I have little experience with this tool so this is to experiment with this tool. Thanks, [[User:GerardM|GerardM]] 08:36, 13 February 2009 (UTC) on70ymc5ce1iso3g7kid5kdgo22rxi5 0 25 5020 1590 2009-12-12T23:39:06Z Kozuch 15 moved [[Project Scope]] to [[Wikipedia Usability Initiative/Project Scope]] wikitext text/x-wiki This one-year pilot program is comprised of usability tests and improvements validated by user tests. ==Planning phase (Jan-Mar 09)== *Find office space *[http://wikimediafoundation.org/wiki/Job_openings Hiring] *[[Environment_Survey|Environmental Survey]] ([http://meta.wikimedia.org/wiki/Wikipedia_Usability_Initiative/Environmental_scan previous version]) including reviews of MediaWiki extentions and skins as well as other wiki software *[[Usability_and_Experience_Study]] *Requirement definition ==Phase 1 - Focus on basic editing tasks (Apr-Aug 09) == *Development *Testing (functional, usability, i18n, L10n) *Staging on [[Prototype]] *Community feedback *User testing ==Phase 2 - Focus on simplified editing interface (Sep 09 - Mar 10)== *User testing *Requirement definition *Development *Testing (functional, usability, i18n, L10n) *Staging *Community feedback *User testing idax8o8iy9x7na5t63zi72764vdlexm 0 26 5016 3088 2009-12-12T23:38:36Z Kozuch 15 moved [[FAQ]] to [[Wikipedia Usability Initiative/FAQ]] wikitext text/x-wiki ;'''When will this project begin, and when will it finish?''' The project will begin in January 2009. It will wrap up April 2010. ;'''What is its overall scope?''' The project scope will include the following: * user testing designed to identify the most common barriers to entry for first-time writers, and * a series of improvements to the MediaWiki interface, including improvements to issues identified through user testing and a focus on hiding complex elements of the user interface from people who don't use them. ;'''What is MediaWiki and how was it developed?''' MediaWiki is open source software, managed and maintained by the Wikimedia Foundation, and used by people around the world to write and edit Wikipedia and the other Wikimedia projects. MediaWiki is also used by many thousands of other wiki sites world-wide, including ones run by Novell, Intel, Gartner, nVidia, Linden Lab, and many others. MediaWiki was first developed, by volunteers, in 2002. As of June 2008, 150 volunteers have access to the 'code base,' meaning they can make modifications and provide code improvements to the software. There are several hundred MediaWiki extensions available, and it is continually being improved by both Wikimedia staff and volunteer coders. ;'''What does the Wikimedia Foundation consider to be wrong with the editing interface right now?''' When it was first developed, MediaWiki was considered reasonably user-friendly. At that time, software wasn't as flexible and user-focussed as it is today. It's logical that by today's standards, MediaWiki may not seem to be as streamlined or user-friendly as other software. We have never systematically examined the editing interface to examine what kinds of challenges new contributors face, but we do know of certain common problems. For example, many people have difficulty creating new articles, uploading images, and editing templates, footnotes, and tables. We hope to make improvements in those areas. ;'''Who are the new contributors you are hoping to attract?''' We are hoping to attract new contributors who are just as smart and knowledgeable as the people who have always written for Wikipedia and its sister projects, but who -to date- have been unable or reluctant to participate because of the barriers posed by the interface. There are countless individuals who read Wikipedia and would be great writers/editors, but are daunted by complex wiki syntax. They may not even realize that they can edit Wikipedia. They are the people we are targeting with this project. ;'''How will an increase in participation affect the existing contributors?''' The core Wikimedia contributor community is made up of people who are very smart and well-versed in the technical aspects of the web. That will probably never change, and we don't want it to change. However, we do want to expand that community to include people who are less tech-centric, as well as demographic groups which are currently underrepresented, such as women and older people. ;'''What is the nature of the interface improvements that will be made in this project?''' In phase 1 (until late summer 2009), we will focus on reducing or eliminating common, simple barriers to entry. A possible example would be, "making the edit button more visible." These will be identified through systematic user testing, but also by surveying existing research. In phase 2 (until early 2010), we will shift our attention to identifying complex pieces of "wiki code" (the formatting language used to write Wikipedia articles) and making them less visible to first-time contributors and/or helping them achieve the respective functionality (such as adding tables) more easily. ;'''When can we expect to see the first changes to the Wikipedia interface?''' We hope to demonstrate a first series of improvements by mid-2009, with production deployment following shortly thereafter. ;'''How can the Wikimedia volunteer community be involved in this project?''' The project will be open and participatory throughout. Every major report will be publicly shared, and all code will be developed through our existing, public version control system. Volunteer developers and testers will be encouraged to contribute throughout the process. ;'''Are the positions created for this project just temporary?''' We will allocate at least two existing, budgeted developer positions to this project, and additional hires will be employed for the duration of the grant. ;'''Why don't these funds count towards your overall fundraising goals?''' The majority of the funding for this project will go towards costs not included in our 2008-09 budget. While we anticipate that the project will offset some of our operating costs, we also want to retain flexibility to reallocate funding inside the project budget as required. ;'''Are you going to localize these changes in all the languages of Wikipedia and the other projects?''' All code will be ready for localisation. ;'''Are you going to be looking at the entire editing/contribution process or just the software?''' This project focuses on technical solutions, but the user testing will aim to capture problems experienced throughout the editing process. :''<small>Source: [[foundation:Stanton Grant Q&A|Stanton Grant Q&A]]</small>'' p8zgprby77bdatt7u4p33ab63xkjydl 0 27 5018 1170 2009-12-12T23:38:46Z Kozuch 15 moved [[Links]] to [[Wikipedia Usability Initiative/Links]] wikitext text/x-wiki == Usability == * [http://meta.wikimedia.org/wiki/Usability_group Usability group] * [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Usability Wikipedia-EN:WikiProject_Usability] * [http://de.wikipedia.org/wiki/Wikipedia:WikiProjekt_Benutzerfreundlichkeit German Wikipedia Usability WikiProject] ** [http://de.wikipedia.org/wiki/Wikipedia:WikiProjekt_Benutzerfreundlichkeit/Test_Februar_2006 German Wikipedia Usability test February 2006] * [http://de.wikipedia.org/wiki/Wikipedia:BIENE German usability project for handicapped people] * ''Strengthening and unifying the visual identity of Wikimedia projects: a step towards maturity'', [[user:guillom|Guillaume Paumier]] & [[user:elian|Elisabeth Bauer]], Wikimania 2007 ([http://wikimania2007.wikimedia.org/wiki/File:GPaumier-Visualidentity-WM2007-proceedings.pdf proceedings], [http://wikimania2007.wikimedia.org/wiki/File:GPaumier-Visualidentity-WM2007.pdf presentation]) ** [http://de.wikipedia.org/wiki/Benutzer:Skinbastler de:Benutzer:Skinbastler], related to the presentation above * Personal lists of Wikipedia usability issues: ** [http://en.wikipedia.org/wiki/User:AxelBoldt/Wikipedia_usability_problems en:User:AxelBoldt/Wikipedia usability problems] ** [http://en.wikipedia.org/wiki/User:M/Wikipedia_usability_problems en:User:M/Wikipedia usability problems] *[http://wikimediafoundation.org/wiki/Press_releases/Wikipedia_to_become_more_user-friendly_for_new_volunteer_writers wmf:Press releases/Wikipedia to become more user-friendly for new volunteer writers] *[http://blog.wikimedia.org/2008/12/03/improved-usability-in-our-future/ Improved usability in our future] *[http://blog.wikimedia.org/2009/01/21/a-note-on-the-wikipedia-usability-initiative/ A note on the Wikipedia Usability Initiative] == Accessibility == * [http://en.wikipedia.org/wiki/Wikipedia:Accessibility Wikipedia-EN:Accessibility] (part of the [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style English Wikipedia's Manual of Style]) * [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Accessibility Wikipedia-EN:WikiProject_Accessibility] * [http://browsershots.org/ Browser shots]<br> * W3C: [http://jigsaw.w3.org/css-validator/ css], [http://validator.w3.org/ html], [http://validator.w3.org/checklink links]<br> * [http://toolserver.org/~dispenser/view/Checklinks Checklinks]<br> * [http://www.accesible.com.ar/examinator/ eXaminator]<br> 6ezwz35j2s3aizsjjnqjq6w3t67qscz 0 29 101 2009-02-13T21:16:58Z GerardM 5 Created page with 'Not all browsers are equally able to show extended Latin characters. When browsers are assessed for their ability to support MediaWiki extensions, this aspect is certainly as imp...' wikitext text/x-wiki Not all browsers are equally able to show extended Latin characters. When browsers are assessed for their ability to support MediaWiki extensions, this aspect is certainly as important. Thanks, [[User:GerardM|GerardM]] 21:16, 13 February 2009 (UTC) o6gix7hf19vtectag3xyvvma71gtsaw 0 32 139 104 2009-02-15T13:49:01Z Siebrand 17 editing a comment of another user wikitext text/x-wiki Given that the Babel extension relies on MediaWiki for its distribution, it is a much easier to support then templates. Thanks, [[User:GerardM|GerardM]] 21:20, 13 February 2009 (UTC)<!-- editing a comment of another user --> hcyfurhrjga5f56o1efcf02tdbpwm8e 0 35 118 117 2009-02-15T00:49:02Z GerardM 5 wikitext text/x-wiki I [http://ultimategerardm.blogspot.com/2009/02/usabilitywikimediaorg.html blogged] about LQT .. Thanks, [[User:GerardM|GerardM]] 00:47, 15 February 2009 (UTC) bl5kgcqitccueycjfppivpm0tkw6frx 0 39 140 122 2009-02-15T13:49:56Z Siebrand 17 wikitext text/x-wiki I'm going to play on your talk page, Gerard. '''[[User:Cbrown1023|<span style="color:green">Cbrown1023</span>]]''' '''<small>[[User talk:Cbrown1023|<span style="color:#002bb8">talk</span>]]</small>''' 02:30, 15 February 2009 (UTC)<!-- will ordering change on edit? --> lcnu0euatnkhwz1y976lno1s8ugqf19 0 40 123 2009-02-15T07:11:18Z GerardM 5 Created page with 'This deserves an reply .. ~~~~' wikitext text/x-wiki This deserves an reply .. [[User:GerardM|GerardM]] 07:11, 15 February 2009 (UTC) c2jqatncv1mfwoennrvlbt5h2zkzq5b 0 41 124 2009-02-15T08:30:20Z Waldyrious 24 Created page with 'Just read you post... trying out the Liquid Threads too :) --~~~~' wikitext text/x-wiki Just read you post... trying out the Liquid Threads too :) --[[User:Waldir|Waldir]] 08:30, 15 February 2009 (UTC) l5kigwik3i51t9poxgueccdwaq9txsx 0 42 125 2009-02-15T08:32:14Z Waldyrious 24 Created page with 'Hum, strange. Since the reply above was at the same level as Cbrown1023's, and since it was written later, I think it whould display below it, don't you agree?' wikitext text/x-wiki Hum, strange. Since the reply above was at the same level as Cbrown1023's, and since it was written later, I think it whould display below it, don't you agree? ms0qdtvv9ewqevntvwyd6l2sml4zput 0 44 127 2009-02-15T09:16:59Z 77.182.137.153 Created page with 'It seams that a old Version of LQT is used. The Recent changes page can not be opened. Please update' wikitext text/x-wiki It seams that a old Version of LQT is used. The Recent changes page can not be opened. Please update jntcabqwtwrkigj7avfklv4vl151s4k 0 53 149 148 2009-02-15T19:04:00Z 71.224.11.211 re wikitext text/x-wiki it does! okay... now it doesn't because your post has more things... weird nytueysqqu95pxk27pjc359pwvylxkf 0 57 162 2009-02-15T21:17:37Z Waldyrious 24 Created page with 'It didn't even when my post had no replies... at least for me.' wikitext text/x-wiki It didn't even when my post had no replies... at least for me. ecwaiusd1husmu4vbfnqdgxwz1fekbj 0 58 163 2009-02-16T00:59:13Z John Broughton~usabilitywiki 33 Some considerations when doing sampling. wikitext text/x-wiki Some things that might be considered in doing the survey: *There are two types of editors: ''registered'' and ''anonymous''. Edits by the latter are recorded as IP addresses. Some IP addresses belong to multiple people (for example, a couple of years ago, a single IP that represented an ''entire country'' - because that's the way the ISP had set it up - was temporarily blocked by a Wikipedia administrator); some are dynamic. Any survey ought to be distinguish between the two types of editors. (And yes, a few long-time editors do use only an IP address, though this is quite rare.) *While the Wikipedia database contains all edits (with the possible exception of oversighted edits), when an article is deleted, that edit no longer is visible via the Special:Contributions page. It's not clear that this makes that much difference, population-wise (when sampling), but since more than a thousand articles are deleted every day, and since the majority of these (I'm fairly sure) were created by new editors, it's possible that there are a lot o cases where what looks like (say) an editor's second edit is really his/her twelfth, if (for example) he/she did ten edits in one or two new articles that was/were speedily deleted. [[User:John Broughton|John Broughton]] 00:59, 16 February 2009 (UTC) *You definitely need to make sure that bots aren't in the sample; they often have very high edit counts, but since they aren't actually ''human beings'', they are irrelevant to the quality of the user interface. More problematical is editors who use specialized tools, typically for vandal fighting or doing mass cleanup of typographical or other common errors. These tools (Twinkle, Huggle, WikiCleaner, etc.) have their own user interface. (Such edits usually do contain a link to the tool that was used.) [[User:John Broughton|John Broughton]] 00:59, 16 February 2009 (UTC) 9ym4bv590fsr786be5fkuou0v2uww60 0 59 164 2009-02-16T01:00:38Z John Broughton~usabilitywiki 33 Comments elsewhere, please wikitext text/x-wiki I'd prefer comments at [[wikipedia:User talk:John Broughton]]. [[User:John Broughton|John Broughton]] 01:00, 16 February 2009 (UTC) qffb37mhvkmbkgyc9ug26gsotlu1szk 0 62 168 2009-02-16T08:12:17Z Angela 34 Created page with 'Here are some of the usability improvements that Wikia has been working on. They're all available under the GPL at wikia-code.com. * Static edit bar moves the confusing text out ...' wikitext text/x-wiki Here are some of the usability improvements that Wikia has been working on. They're all available under the GPL at wikia-code.com. * Static edit bar moves the confusing text out of view and puts the save button always in sight to prevent people typing their text and then not knowing they need to do something to save it. ([http://www.wikia.com/wiki/Image:Johncenaeditwindow.jpg screenshot]) * More obvious edit buttons as many people still don't realise they can edit. ([http://legobatman.wikia.com/wiki/Lego_Batman:_The_Video_Game View this] logged out for an example of more prominent section edit buttons. ([http://www.wikia.com/wiki/Image:Sectionedit-header1.jpg screenshot]) * Simpler image upload, flickr importer (could easily be turned into a Wikimedia Commons importer). [http://help.wikia.com/wiki/Help:Add_Images Help page], [http://help.wikia.com/wiki/Image:Addimages.png screenshot] * Search suggest and link suggest - these features need rewriting to be less DB intensive. With link suggest, you start typing <nowiki>[[So and it will display [[Some link]]</nowiki> to complete the link for you, using existing page titles on that wiki. ([http://help.wikia.com/wiki/Help:Link_Suggest help page]) *Edit Page Enhancements include widescreen mode and help tips in the sidebar. Of course, the tips are editable and internationalizable. ([http://help.wikia.com/wiki/Help:Edit_Page_Enhancements Help page]) :[[User:Angela|Angela]] 08:12, 16 February 2009 (UTC) 4m6edxagxfbnoqcxy7yddtg2afcqf41 0 69 182 2009-02-17T15:57:40Z VIGNERON~usabilitywiki 39 translations? wikitext text/x-wiki This site will be only in English? Or are some translations planned? I can help a little for French. Cdlt, [[User:VIGNERON|V<span style="font-size:75%">IGNERON</span>]] * [[User Talk:VIGNERON|^discut.]] 15:57, 17 February 2009 (UTC) 39tibefysfcqxhisnrv9l5kvogq0m4o 10 77 8653 3921 2010-07-29T13:31:13Z Nemo bis 9 cat wikitext text/x-wiki <!--<div style="font-size:85%; margin:0; padding:.25em .5em; border:1px solid #cccccc; background:#f9f9f9" id="main-page-langbar"> Select language: [[Main Page|In English]] &bull; [[Etusivu|suomeksi]] </div><br>--> <div style=" float:right; border:solid 1px #9accf6; background:#f1f9ff; padding:1em; padding-top:0.5em; padding-bottom:0.5em; font-size:1.2em; width:20em; color:black; margin-bottom: 1.5em; margin-left: 1.5em; "> '''Participate in the Initiative''' {| style="background-color: #f1f9ff" cellpadding="5" |- | [[File:Dialog-information_on.svg|45px]] | Check out our '''[[Prototype|prototype sites]]''' and provide '''[[Talk:Prototype|feedback]]''' to help us prepare for deployment. |- | [[File:Emblem-star.svg|45px]] | We need '''[[Your Opinion]]''' on changes that might affect you. |- | [[File:Dialog-apply.svg|45px]] | Help us complete our '''[[Releases/Babaco/Compatibility Matrix|browser compatibility testing]]'''. |} </div><noinclude> [[Category:navigational templates]]</noinclude> rmm13l54xsyuqvp3xxovv3oc17hzy08 0 79 996 868 2009-03-30T19:19:50Z IAlex 6 double redirect wikitext text/x-wiki #redirect [[Environment Survey/MediaWiki Extensions/Nomination]] ij8lzvwix9t1308qiqyyy8nv5bkyb80 6 85 1567 235 2009-05-29T17:46:24Z Trevor Parscal (WMF) 3 moved [[File:WUI-Whiteboard.jpg]] to [[File:Whiteboard-Logo.jpg]]:&#32;More specific name wikitext text/x-wiki Logo on the whiteboard of the Wikipedia Usability Initiative where the [[Slogans|slogan of the day]] is written. 7hh5rt00ywam5a7h5mj2iwhfvu9y1m8 6 112 1554 398 2009-05-29T17:19:29Z Trevor Parscal (WMF) 3 moved [[File:FCKEditor.png]] to [[File:Extension-FCKEditor.png]]:&#32;More specific file naming wikitext text/x-wiki Screenshot of FCKEditor. lv2fk95jms9p3gp0amle41ifwoeefr6 6 113 1553 399 2009-05-29T17:19:09Z Trevor Parscal (WMF) 3 moved [[File:MeanEditor.png]] to [[File:Extension-MeanEditor.png]]:&#32;More specific file naming wikitext text/x-wiki Screenshot of MeanEditor. 0640quuddwvsipwr7hf5up9t1mbkyr8 6 114 1552 400 2009-05-29T17:18:55Z Trevor Parscal (WMF) 3 moved [[File:WikiEd.png]] to [[File:Extension-WikiEd.png]]:&#32;More specific file naming wikitext text/x-wiki Screenshot of WikiEd. 1zege0hpn5tkpmk5mczeuigtveil2ey 6 115 1551 401 2009-05-29T17:18:39Z Trevor Parscal (WMF) 3 moved [[File:Wikiwyg.png]] to [[File:Extension-Wikiwyg.png]]:&#32;More specific file naming wikitext text/x-wiki Screenshot of Wikiwyg. 2kof8c22kkzae6i62kvepsubgs6d7oq 0 116 416 2009-03-18T00:18:04Z Shuhari 4 mission statement wikitext text/x-wiki '''''Research barriers, Inspire participation, Enable collaboration, and Empower people.''''' pkybkh2jt9bq6huppdkcjge4iq93w91 0 117 655 633 2009-03-24T13:39:38Z Snigbrook 129 [[HAGGER?????]] moved to [[Goals]] over redirect: revert wikitext text/x-wiki Team Goals: # Identify barriers # Analyze # Design + Develop solutions # Evaluate #*technical functionality, performance, browser compatibility, and i18n/L10n #*user acceptance and ease of use # Deploy # Measure 7440pju9psjjpf5pjwipr3ty1am1nl3 0 120 9365 869 2011-08-22T12:16:05Z Ruslik0 224 fixing dr wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Results]] 8dj3pzgr2a5o8tfs8t8ii43xvv0ffyv 6 122 1550 470 2009-05-29T17:18:21Z Trevor Parscal (WMF) 3 moved [[File:WikiaWysiwyg.png]] to [[File:Extension-WikiaWysiwyg.png]]:&#32;More specific file naming wikitext text/x-wiki Screenshot of Wikia's wysiwyg editor. cn9lzq3wt9dhq3djxicnfqdfc8kltfi 10 124 3568 1024 2009-10-15T18:28:04Z Guillom 13 adding alt wikitext text/x-wiki <div style="border:solid 1px orange;border-left-width:10px;background-color:#FFDDAA;padding:5px;margin-bottom:5px;" class="noprint"> {| width="100%" style="background-color:#FFDDAA;" cellpadding="5" | width="50" align="center" | [[File:Imbox_draft.png|left|Draft]] | '''This is a Draft''' Although this document may have useful content, it should not be considered final. Please take this into consideration when discussing this page. |}</div> l72mttldvg7mdn4zjbmnyuq31jgbvdb 0 126 6679 6678 2010-04-27T12:17:01Z Gaeser 1817 Undo revision 6678 by [[Special:Contributions/204.108.230.103|204.108.230.103]] ([[User talk:204.108.230.103|talk]]) wikitext text/x-wiki The objective of our Environment Survey is to learn about what work has already been done in the area of improving the usability of MediaWiki and other similar software platforms. We hope to use this knowledge in compliment with the results of formal usability testing to develop effective solutions. We will be looking at existing approaches to enhancing usability through existing MediaWiki software such as extensions and skins as well as identifying interesting features in other wiki software. == Nomination == {| | valign="top" nowrap="nowrap" width="20%" | * [[Environment_Survey/MediaWiki_Extensions/Nomination|MediaWiki Extensions]] * [[Environment_Survey/MediaWiki_Skins/Nomination|MediaWiki Skins]] * [[Environment_Survey/Other_Wiki_Software/Nomination|Other Wiki Software]] | valign="top" style="padding:5px;padding-left:20px;" | To help in locating solutions which are of interest to this project, we invite anyone to nominate existing solutions for analysis and consideration. Please understand that the ratings on these pages are of interest to us, but should not be seen as a contest. Also, any features, designs or actual code that any of these nominations provide which we find useful to our project and are under a free license may be looked at for use in future solutions, however we are not necessarily looking at these nominations as drop-in solutions. |} == Criteria == {| | valign="top" nowrap="nowrap" width="20%" | * [[Environment_Survey/MediaWiki_Extensions/Criteria|MediaWiki Extensions]] * [[Environment_Survey/MediaWiki_Skins/Criteria|MediaWiki Skins]] * [[Environment_Survey/Other_Wiki_Software/Criteria|Other Wiki Software]] | valign="top" style="padding:5px;padding-left:20px;" | In an effort to capture the technical and qualitative differences between solutions, we have developed a criteria by which each solution is evaluated against. |} == Results == {| | valign="top" nowrap="nowrap" width="20%" | * [[Environment_Survey/MediaWiki_Extensions/Results|MediaWiki Extensions]] * [[Environment_Survey/MediaWiki_Skins/Results|MediaWiki Skins]] * [[Environment_Survey/Other_Wiki_Software/Results|Other Wiki Software]] | valign="top" style="padding:5px;padding-left:20px;" | Although our results are considered internal documents, we want to let everyone see the progress we are making, and invite them to discuss the content of the survey on the appropriate discussion pages. |} tb99seyi99inpjcujhk5imigakqbu2g 0 128 9366 494 2011-08-22T12:16:57Z Ruslik0 224 fixing dr wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Results]] 8dj3pzgr2a5o8tfs8t8ii43xvv0ffyv 0 129 995 496 2009-03-30T19:18:58Z IAlex 6 double redirect wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Nomination]] t9npwa0ep3lvwltezig0u234gedjv0y 0 130 997 498 2009-03-30T19:20:21Z IAlex 6 double redirect wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Nomination]] t9npwa0ep3lvwltezig0u234gedjv0y 0 131 9367 500 2011-08-22T12:17:55Z Ruslik0 224 fixing dr wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Results]] 8dj3pzgr2a5o8tfs8t8ii43xvv0ffyv 0 136 511 2009-03-20T18:50:00Z Trevor Parscal (WMF) 3 [[Environment Survey/MediaWiki Extensions/Extension Nomination]] moved to [[Environment Survey/MediaWiki Extensions/Nomination]]:&#32;Less redundant title wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Nomination]] t9npwa0ep3lvwltezig0u234gedjv0y 0 138 516 2009-03-20T18:52:03Z Trevor Parscal (WMF) 3 [[Environment Survey/MediaWiki Extensions/Editing]] moved to [[Environment Survey/MediaWiki Extensions/Results]]:&#32;Clearer title wikitext text/x-wiki #REDIRECT [[Environment Survey/MediaWiki Extensions/Results]] 8dj3pzgr2a5o8tfs8t8ii43xvv0ffyv 0 140 1455 1433 2009-05-18T21:53:04Z 86.9.123.100 /* User Features */ stabile->stable wikitext text/x-wiki {{Draft}} {{Internal}} == Browser Compatibility == '''Rationale''' Wikipedia and other Wikimedia projects are accessed using a wide range of platforms and browsers. '''Evaluation''' Full support for a specific browser on a specific platform gives 1 point, partial support gives 0.5 points and no support gives 0 points. Maximum number of points in the scope of this survey is 12. == License Compatibility == '''Rationale''' MediaWiki is under the GPLv2 open source license and any software contributions need to be under similar or compatible license. '''Evaluation''' A license compatible with integration into GPLv2 software is required to pass. == Download Size == '''Rationale''' Conserving bandwidth is important not only for our own servers but also for users who are connected to the internet via low-bandwidth connections, making less information needed to be transmitted mutually beneficial. '''Evaluation''' The total number of kilobytes of information including JavaScript, CSS, HTML, and images above what is already present through MediaWiki. == UI Responsiveness == '''Rationale''' The ability of the editor to respond to user actions quickly is an important factor in usability and user adoption. '''Evaluation''' This category will be evaluated using a low, medium, high rating. Factors include: * Are there page refreshes that the user has to wait for between certain actions? * Is Ajax used to make the user experience more fluid, and if so, is the performance crisp and responsive? * Is there a lag when the editor is loading? * Is there a lag when edits are saved? == Completeness == '''Rationale''' MediaWiki extensions are in various states of the development lifecycle. If an extension is in use in multiple instances or has had some releases that have allowed it to be more stabile and mature, then it will require less time and effort to make it ready for wider use. '''Evaluation''' This category will be evaluated using a low, medium, high rating. Factors include: * Is a stabile version of the extension available? * Has the extension been successfully deployed on one or more sites with significant traffic? * Is there active development on the extension? * Is there an active community of developers working on improving the functionality or stability? == User Features == '''Rationale''' A MediaWiki article contains a wide range of elements, i.e. images, text, links, tables, templates, video, etc... An editor that provides a WYSIWYG interface to add as many of these element types as possible is preferred. '''Evaluation''' In its existing stable version, how many of the standard MediaWiki element types can a user add or modify via a graphical interface? This category will be rated based on support for handling the following elements. 1 point is given for providing a way to add and manipulate the element with a graphical user interface, 1/2 point is given for providing a read-only visualization of the element. * Headings * Internal Links * External Links * Inline formatting (bold, italic, etc.) * Section formatting (paragraph, preformatted, blockquote, etc.) * Lists and indentation * Tables * Templates * Images * Video == Extendable == '''Rationale''' It's expected that additional features will be added in the future, making the prior existence of an expendable architecture valuable. '''Evaluation''' If the software has a modular architecture which lends itself to adding or removing features without having to make significant modifications to the core software. == Themable == '''Rationale''' Integration into MediaWiki's theme system would ideally require modification of isolated user interface resources and not core software. '''Evaluation''' If user interface resources isolated from the core software. == Internationalization/Localization == '''Rationale''' Given MediaWiki's use in over 250 different languages, the software needs to be compatible with different languages. '''Evaluation''' This category will be evaluated by the software's support for specific features. * Does the software provide a way to localize user-interface messages such as icon tool-tips and selective text labels? * Does the software support alternative text input? * Does the software support double-byte text? t9hd3yhbydgczgm71ecfs74iuvsrpq7 0 141 2039 1454 2009-07-15T14:27:55Z 199.200.10.1 that's my site. The "content" is creative commons, but not the design. wikitext text/x-wiki If you would like to nominate a MediaWiki compatible skin for inclusion in our [[Environment Survey]], please feel free to add it below. We also welcome you to explore existing nominations and provide feedback by giving ratings or through the [[Talk:Environment Survey/MediaWiki Skins/Nomination|discussion page]]. == Resources == * There's a large collection of skins for MediaWiki which widely range in quality and practicality at [http://www.mediawikiskins.com mediawikiskins.com] == Nominations == {| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;" ! width="320" align="left" | Skin ! width="40" align="left" | Example ! width="100" align="left" | License ! align="left" | Summary |-- | Cavendish (MozillaWiki) <ratings:scale category="Extension Survey/Skin Nomination" title="MozillaWiki" /> | [http://wiki.mozilla.org/Main_Page] | GPL [https://wiki.mozilla.org/skins/cavendish/main.css] | Very clean centered fixed width layout. |-- | OpenOffice <ratings:scale category="Extension Survey/Skin Nomination" title="OpenOffice" /> | [http://www.mediawikiskins.com/ads_item.php?id=79] | Unknown | ... |-- | WikiGoes <ratings:scale category="Extension Survey/Skin Nomination" title="WikiGoes" /> | [http://www.mediawikiskins.com/ads_item.php?id=77] | Unknown | ... |-- | openSUSE <ratings:scale category="Extension Survey/Skin Nomination" title="openSUSE" /> | [http://www.mediawikiskins.com/ads_item.php?id=38] | Unknown | ... |-- | Tango <ratings:scale category="Extension Survey/Skin Nomination" title="Tango" /> | [http://www.mediawikiskins.com/ads_item.php?id=23] [http://tango.freedesktop.org/] | Unknown | ... |-- | wikiHow <ratings:scale category="Extension Survey/Skin Nomination" title="wikiHow" /> | [http://www.mediawikiskins.com/ads_item.php?id=22] [http://www.wikihow.com] | Unknown | ... |-- | RoundedSassyBig <ratings:scale category="Extension Survey/Skin Nomination" title="RoundedSassyBig" /> | [http://www.mediawikiskins.com/ads_item.php?id=21] | Unknown | ... |-- | Clean <ratings:scale category="Extension Survey/Skin Nomination" title="Clean" /> | [http://mediawiki2u.com/2008/05/clean-mediawiki-template/] | Unknown | ... |-- | Modern <ratings:scale category="Extension Survey/Skin Nomination" title="Modern" /> | [http://usability.wikimedia.org/wiki/Main_Page?useskin=modern] | GPL | Skin readily available in MediaWiki. Attempts to be slicker than MonoBook. |-- | Azure <ratings:scale category="Extension Survey/Skin Nomination" title="TMBW" /> | [http://tmbw.net/wiki/Main_Page] | Proprietary | Clean but colorful fixed-width layout. More prominent navigation tabs, some of which use JavaScript. |-- | AboutUs <ratings:scale category="Extension Survey/Skin Nomination" title="AboutUs" /> | [http://www.aboutus.org/] | Unknown (probably not reusable) | One of the more innovative skins, with many new user interaction mechanisms. Somewhat chaotic though. Note that the site is almost entirely Ruby On Rails currently, and is no longer technically MediaWiki. |-- |Creative Commons <ratings:scale category="Extension Survey/Skin Nomination" title="CreativeCommons" /> |[http://wiki.creativecommons.org/Main_Page] |Unsure, but likely to be free for obvious reasons |Not super creative, but is clean and meshes well with the non-wiki site. |-- |Wordpress Codex <ratings:scale category="Extension Survey/Skin Nomination" title="WordpressCodex" /> |[http://codex.wordpress.org] |Unknown |... |-- |AdobeLabs <ratings:scale category="Extension Survey/Skin Nomination" title="AdobeLabs" /> |[http://labs.adobe.com/wiki/index.php/Main_Page] |Unknown |... |-- |OrganicDesign <ratings:scale category="Extension Survey/Skin Nomination" title="OrganicDesign" /> |[http://organicdesign.co.nz/Special:RecentChanges] |Unknown |Rounded corners. Economically use of space &ndash; wiki logo is moved next to to the right of the page title and the user menu is moved to where the Monobook logo would have been. Registered users have the opinion to upload a "user photo". |-- |WikiGender <ratings:scale category="Extension Survey/Skin Nomination" title="WikiGender" /> |[http://www.wikigender.org/index.php/New_Home] |Unknown |Improved navigation, especially in menus and search box. Fixed width choice hampers readability. |} 9ks7dkyqrvmqfppqm9sgd73dm9ys231 0 143 600 599 2009-03-23T23:09:22Z Trevor Parscal (WMF) 3 Unprotected "[[Environment Survey/MediaWiki Skins/Criteria]]": Using notices and assuming good faith wikitext text/x-wiki {{Draft}} {{Internal}} hgl87fazrtwc7l5huff9cpr329kwd9r 0 144 1138 602 2009-04-16T17:29:52Z Arash Boostani 109 wikitext text/x-wiki == [http://wiki.mozilla.org/Main_Page Cavendish (MozillaWiki)] == * Visually appealing tabs * Search field appears in the top right section of the screen, which is common on many sites * Left toolbar styled in soothing colors and larger text * Logo, tabs, and search are all integrated into a single page header * Centered layout == [http://wiki.services.openoffice.org/wiki/Main_Page OpenOffice] == * Left toolbar section titles are highlighted clearly * Search field appears in the top right section of the screen, which is common on many sites * "Go" button next to the search field removed, leaving only the "Search" button * Logo, tabs, and search are all integrated into a single page header * Fixed width, centered layout == [http://www.livingwild.org/wiki/Main_Page WikiGoes] == * Search field appears in the top right section of the screen, which is common on many sites * Tabs are highlighted well * Fixed width layout * Article content is clearly separated from surrounding layout == [http://tango.freedesktop.org/Tango_Desktop_Project Tango] == * Table of contents is right aligned == [http://www.wikihow.com/Main-Page wikiHow] == * Section headers and "edit" links are visually linked together * Visually appealing tabs * Search field appears in the top right section of the screen, which is common on many sites * Left toolbar section titles are highlighted clearly == [http://mediawiki2u.com/2008/05/clean-mediawiki-template/ Clean] == * Tabs are replaced by buttons that match the section edit links * Section headers and "edit" links are visually linked together * Search field appears in the top right section of the screen, which is common on many sites == [http://tmbw.net/wiki/Thunderbird_(Demo) Azure] == * Centered layout * Edit links are more styled and more visible * Save and Preview buttons are centered and styled to be more visible mnnvpy9jxpe5p7dzysekfhvo085msi0 0 146 1472 1453 2009-05-24T04:07:10Z Michaeldsuarez 120 Fixed interwiki links to Wikipedia. wikitext text/x-wiki If you would like to nominate a piece of Wiki software other than MediaWiki for inclusion in our [[Environment Survey]], please feel free to add it below. We also welcome you to explore existing nominations and provide feedback by giving ratings or through the [[Talk:Environment_Survey/Other Wiki Software/Nomination|discussion page]]. ==Resources== * An excellent comparison has already been done on a much broader range of software on [[w:Comparison_of_wiki_software|Wikipedia]] == Nominations == {| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA;" ! width="320" align="left" | Name ! width="40" align="left" | Example ! width="100" align="left" | License ! align="left" | Summary |-- | MindTouch Deki <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="MindTouch Deki" /> | [http://www.mindtouch.com/Products] | GPL, LGPL (and some closed-source features in paid versions) | Uses XML as an internal data format for articles. |-- | HDWiki <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="HDWiki" /> | [http://www.hudong.com/wiki/Jimmy+Wales example article] [http://www.hudong.com/editsectionauth/Jimmy+Wales/5 edit page] | Open Source (specific license unknown) | Chinese wiki platform used by popular wiki encyclopedia [[w:Hudong|Hudong]] ([http://www.hudong.com/]). Developed because of (perceived) shortcomings in MediaWiki. Said to be open source, but unsure. |- | Wetpaint <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="Wetpaint" /> | [http://www.wetpaint.com] | ... | A community of wikis. |-- | Confluence <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="Confluence" /> | [http://www.atlassian.com/software/confluence] | ... | ... |-- | WikiDot <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="WikiDot" /> | [http://www.wikidot.com] [http://www.calchamber.com/Headlines/Pages/BusinessParticipationVitalasStateStartsGreenChemistryWikiSite.aspx] | ... | ... |-- | TikiWiki <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="TikiWiki" /> | ... | ... | ... |-- | DokuWiki <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="DokuWiki" /> | http://wiki.pangea.org | GPL | ... |-- | PBwiki <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="PBwiki" /> | [http://pbwiki.com/content/viewdemobusiness] | Commercial | ... |-- | Wagn <ratings:scale category="Extension Survey/Other Wiki Software Nomination" title="Wagn" /> | [http://wagn.org] | Open Source | ... |} k2j67b3xh9bzuqt1ycvcd9k58vi14u7 0 147 1113 1108 2009-04-14T20:56:18Z Trevor Parscal (WMF) 3 /* Features of Interest */ wikitext text/x-wiki {{Draft}} {{Internal}} == Features of Interest == '''Rationale''' Only some of the features will be of interest to the Wikipedia project, as many pieces of wiki software were not designed to be used an an encyclopedia. '''Evaluation''' Each feature of interest will be reviewed in comparison to the way that Wikipedia currently already handles or does not yet handle such functionality. fy8n2z57ps6ptcspuiq5bl1rbivhxrh 0 148 1149 1148 2009-04-17T06:58:58Z Pjetter 172 Undo revision 1148 by [[Special:Contributions/Pjetter|Pjetter]] ([[User talk:Pjetter|Talk]]) Put on talk page wikitext text/x-wiki __NOTOC__ {{Draft}} {{Internal}} == Overview == There are many software solutions for creating a wiki, allowing anyone to edit the content. Many of these solutions have features which improve the usability of interacting with a wiki. The following list provides information about various software solutions. Some of these solutions are open-source software packages, some even based on MediaWiki, which anyone can setup on their own, while others are either commercial software packages or online services. == Other Wiki Software Details == === Deki === <blockquote> MindTouch Deki is an open source enterprise collaboration and community platform that enables users to connect and remix enterprise systems, social tools and web services. It started on the Mediawiki platform, but has been modified and enhanced significantly. ==== Features of Interest ==== * WYSIWYG editing interface * Simplified page layouts * Editing toolbar follows you as you scroll the page up and down * Wizard interfaces for image upload, video embedding, link insertion, and templates * Table of contents is placed and out of the way to the right </blockquote> === Wikia === <blockquote> Wikia is a community destination supporting the creation and development of wiki communities on any topic people are passionate about. It operates on the Mediawiki platform. ==== Features of Interest ==== * Simplified image uploader * More obvious edit button * Automatic text completion when typing links * Includes widescreen mode when editing * Includes static edit bar that moves the confusing text out of view and puts the save button always in sight to prevent people typing their text and then not knowing they need to do something to save it. * Small help box displayed when editing. * WYSIWYG editor </blockquote> === Knol === <blockquote> Google's Knol project is a site that hosts many articles written about various subjects. The authors can take credit for their writing, provide credentials, and elicit reviews and comments. Users can provide feedback, comments, and related information. So the Knol project is a platform for sharing information, with multiple cues that help users evaluate the quality and veracity of information. ==== Features of Interest ==== * WYSIWYG editing interface * Editing toolbar is very simple and stays at the top of the page when you scroll up and down * Wizard interfaces for image upload, document embedding, videos, etc... * Alternate mode that allows power users to edit HTML directly * Provides the ability to select from a list of standard text styles </blockquote> === WikiHow === <blockquote> wikiHow is a collaboration to build and share the world's largest, highest quality how-to manual. It is built on the Mediawiki platform. ==== Features of Interest ==== * Tabs at the top of the page are much more user-friendly and clear * Default editing mode provides a different field for each section * Advanced users are given the option to go to the Advanced Editing mode * Discussion pages provide a field to add a new comment, rather than the current method that asks the user to edit the page. * The desired document structure is made very clear to the user, with very little ability to stray from that structure </blockquote> === Wetpaint === <blockquote> Wetpaint allows users to create websites that mix the features of wikis, blogs, forums and social networks into a rich, user-generated community based around their topics of interest. ==== Features of Interest ==== * The WYSIWYG editor floats above the page and is movable </blockquote> 05bwt9zylw4nq7dlcd62ltc9z10gk6e 10 149 8660 614 2010-07-29T13:33:39Z Nemo bis 9 cat wikitext text/x-wiki To help in locating {{{1}}} which are of interest to this project, we invite anyone to nominate existing {{{1}}} for analysis and consideration. Please understand that the ratings on these pages are of interest to us, but should not be seen as a contest. Also, any features, designs or actual code that any of these nominations provide which we find useful to our project and are under a free license may be looked at for use in future solutions, however we are not necessarily looking at these nominations as drop-in solutions.<noinclude> [[Category:Templates]]</noinclude> hsr6bu2bj46qi17k9ymt4mofhvz8q9i 8 150 3565 560 2009-10-15T18:20:55Z Guillom 13 ** multimediahub-url|multimediahub wikitext text/x-wiki * navigation ** mainpage|mainpage-description ** multimediahub-url|multimediahub ** recentchanges-url|recentchanges ** randompage-url|randompage * SEARCH * TOOLBOX * LANGUAGES hfbg93rlv96g5ao0cfbk83gul1fie4l 6 153 588 584 2009-03-23T22:27:31Z Trevor Parscal (WMF) 3 [[File:Under Contruction Icon.png]] moved to [[File:Imbox draft.png]] wikitext text/x-wiki Icon representing a person performing construction work. hpkkyz7m565a7o48kyh9m5cckp7wqxw 6 154 589 2009-03-23T22:27:31Z Trevor Parscal (WMF) 3 [[File:Under Contruction Icon.png]] moved to [[File:Imbox draft.png]] wikitext text/x-wiki #REDIRECT [[File:Imbox draft.png]] 5e88juz7nsqw5pg65tltqtfdo5yn2c1 6 155 591 2009-03-23T22:28:59Z Trevor Parscal (WMF) 3 Icon indicating important information. wikitext text/x-wiki Icon indicating important information. 2prm1rv4tv7r5qsvkk0xpr956r2of88 6 156 592 2009-03-23T22:29:30Z Trevor Parscal (WMF) 3 Icon indicating important notice. wikitext text/x-wiki Icon indicating important notice. bzprcnsqudic6yvtssxr17veipwr34m 10 157 8630 8380 2010-07-29T13:18:24Z Nemo bis 9 cat wikitext text/x-wiki <div style="border:solid 1px #1e90ff;border-left-width:10px;background-color:#fbfbfb;padding:5px;margin-bottom:5px;" class="noprint"> {| width="100%" style="background-color:#fbfbfb;" cellpadding="5" | width="50" align="center" | [[File:Imbox_notice.png|Internal document]] | '''This is an internal document''' While making small fixes to this page like fixing typos and dead-links is encouraged, any changes which significantly modify the information of this page should be suggested on the discussion page instead, as this is an internal document. |}</div> <includeonly>[[Category:Internal documents]]</includeonly><noinclude> [[Category:Templates]]</noinclude> 6e18xtdalhfea57g7567kpeh0jz79b7 4 292 8400 1142 2010-07-09T22:33:47Z Avicennasis 1641 fix. wikitext text/x-wiki #REDIRECT [[w:Wikipedia:Administrators]] 6rr2zybxfwum0p7r45fipkckdb3olr6 4 294 9362 1144 2011-08-22T11:40:48Z Ruslik0 224 a fix wikitext text/x-wiki #REDIRECT [[w:Wikipedia:Copyrights]] 047hexsdnlzl4ciyrgwsgz7wz4mnmu0 4 296 7365 1146 2010-06-03T14:17:17Z Trần Nguyễn Minh Huy 1655 Redirected page to [[w:Wikipedia:Bureaucrats]] wikitext text/x-wiki #REDIRECT [[w:Wikipedia:Bureaucrats]] 6uo1eulvnn0ucpkzz4o87u07ditklfv 6 311 1548 1211 2009-05-29T17:15:00Z Trevor Parscal (WMF) 3 moved [[File:Design-EditToolbar.pdf]] to [[File:Design-EditToolbar-1.pdf]]:&#32;Different approaches need numbers wikitext text/x-wiki Initial mock-up of revised edit toolbar. Designed by Trevor Parscal. gmgocfz00y0t1z97g1ro0jeavhpv3t7 6 312 9370 1210 2011-08-22T12:20:48Z Ruslik0 224 fixing dr wikitext text/x-wiki #REDIRECT [[File:Design-EditToolbar-1.pdf]] eoc2rgld0ks6ncweys67zi1dmd19p7e 6 313 1543 1275 2009-05-29T17:12:33Z Trevor Parscal (WMF) 3 moved [[File:Design-NavigationTabs.pdf]] to [[File:Design-NavigationTabs-1.pdf]]:&#32;Different approaches need numbers wikitext text/x-wiki Initial mock-up of revised navigation tabs. Designed by Trevor Parscal. thrwsnuqi84tczrrq0kq79qjryh7vj7 6 314 1547 1213 2009-05-29T17:14:41Z Trevor Parscal (WMF) 3 moved [[File:Design-SearchResults.pdf]] to [[File:Design-SearchResults-1.pdf]]:&#32;Different approaches need numbers wikitext text/x-wiki Initial mock-up of revised search results. Designed by Trevor Parscal. 68ms1cx86nkvgixjn9tulp7gcesyrc2 0 315 1578 1220 2009-06-01T20:22:44Z M~usabilitywiki 219 redirect to the study wikitext text/x-wiki #REDIRECT [[Usability and Experience Study]] 6x2xlavlzjqkx0g6b7uy1rzh4q6flkx 0 316 10279 8816 2019-03-14T17:58:44Z Krinkle 709 wikitext text/x-wiki The Wikimedia Usability Initiative Team partnered with [http://www.boltpeters.com Bolt Peters], a San Francisco, California, user experience consulting firm, to conduct both in-person lab and remote interviews and studies of the general Wikipedia experience, with focus on the editing experience, process, and its successes and failures. The study consisted of 15 one-on-one interviews, each lasting between 45 and 60 minutes. 10 of these interviews were conducted in person at a lab facility and 5 were conducted remotely from the Wikipedia Usability Office. The interviews were conducted in late March 2009 in San Francisco, CA. The primary research goals were to: * identify obstacles that novice users encounter in editing a Wikipedia article&mdash;including, but not limited to&mdash;adding personal content, fixing a typo, adding a reference, and contributing to discussion pages * identify obstacles in creating a new article * evaluate the self-sufficiency and legibility of help materials and documents found on Wikipedia.org * evaluate how novice users interact with templates * discover user experience patterns and issues that have not been previously identified. == Methodology == === Target Audience === The target audience of the Usability Study was limited to regular Wikipedia readers who are willing to contribute their knowledge to the site, but have expressed reservations about doing so. The team aimed to select a majority (~80%) of users that had not edited but were willing to, and a minority (10%) of users that had not edited and weren't willing to and (10%) of users that were novice but not new editors, with less than 5 contributions. We preferred potential subjects whose ''primary'' reasons for not contributing seemed to be due to the technical complexity of the interface of MediaWiki and markup, but understand that fear of article deletion, unwillingness to have work edited by others, lack of confidence in 'expertise', not being willing or used to collaborating, and philosophical differences are all also big inhibitors to Wikipedia readers' contribution. According to a multilingual survey of Wikipedia readers conducted by the Wikimedia Foundation and UNU-Merit, 74.6% of Wikipedians are male, and 24.7% are female. The average age of Wikipedians (aged 10&ndash;85) is 25.1 years old (the average male Wikipedian is 25.6 and the average female Wikipedian is 23.7. Since the team's goals are aimed at reducing common barriers for Wikipedia readers to become editors, and there are over 300 million unique Wikimedia visitors, the majority of which are English Wikipedia readers, we set out to keep our gender (M/F) breakdown equal and our gender spread across ages (Under 18, 19&ndash;34, 35&ndash;44, 45&ndash;54, 55&ndash;64, 65+), so that our research would give us insight into the entire spectrum of potential new editors. Our desired participant profiles: {| class="wikitable" style="text-align:center;" |- ! Participant No. ! Has not edited, but is willing to ! Has not edited, doesn't see themselves editing ! Has made < 25 contributions ! Male ! Female ! Under 18 ! 19&ndash;34 ! 35&ndash;54 ! 55+ ! Uses WP everyday ! Uses WP > Once a week ! Uses WP Once every few weeks |- | 01 || X || || || || X || X || || || || X || || |- | 02 || X || || || X || || || X || || || || X || |- | 03 || X || || || || X || || X || || || X || || |- | 04 || X || || || X || || || X || || || || X || |- | 05 || X || || || || X || || || X || || X || || |- | 06 || X || || || X || || || || X || || || X || |- | 07 || X || || || || X || || || || X || X || || |- | 08 || || X || || X || || || || || X || || X || |- | 09 || || || X || || X || || X || X || || || X || X |- | 10 || || || X || X || || || || X || X || || X || X |- | 11 || X || || || || X || X || || || || X || || |- | 12 || X || || || X || || || X || || || || X || |- | 13 || X || || || || X || || || X || || X || || |- | 14 || X || || || X || || || || || X || || X || |- | 15 || || || X || || X || X || X || X || X || X || X || |} === Lab Testing === [[File:Research-Photo-LabTesting.jpg|thumb|right|400px|Set up at Fleischman]] The Lab testing was conducted at the [http://www.ffrsf.com/ Fleischman Field Research] facilities, located in San Francisco, California. Participants, limited to those within driving distance, were brought into a room with the Research Interviewer, and a Mac or PC, based on their stated preference. Behind a two way mirror, Wikimedia Usability Researchers could view the interviewer and participant interacting, hear the interview audio, view the participants entire screen and computer interactions, and see their faces and expressions, in real time as the interview was being conducted. These videos (both the screen and the participant) were also captured under a Creative Commons License and can be viewed in the section labeled "Full Interview Videos". <br clear="all"> === Remote Testing === [[File:Research-Photo-RemoteTesting.jpg|thumb|right|400px|Set up at Wikimedia Annex]] The Remote Testing was conducted at the Wikimedia Usability + Wikia office. Participants were recruited live, and called for interview within 1hr of the completion of their survey response. They completed the script in their native environment. Using [http://www.techsmith.com/uservue.asp UserVue], a remote screen sharing application, the B|P interviewer, the Wikipedia Usability Team, and other observers could view the participant's screen in real time, and hear the complete audio via telephone and speakers. The audio interview along with the screen capture videos were recorded and are available here under a Creative Commons license (see "FullInterview Videos below.") <br clear="all"> === Lab Testing and/VS Remote Testing === We decided to do a combination. * Users from outside the San Francisco area * In person&mdash;see more <br> [http://boltpeters.com/articles/versus.html B|Ps Lab Vs. Remote Comparison] === Recruiting === We recruited over 2,500 San Francisco residents for the in person testing. A banner/alert was placed and displayed at the top of every 1 in 100 Wikipedia pages for the duration of 8 hours. When users viewed our message by clicking, they were forwarded to B|P ethnio recruiting system where we asked them a series of questions. Specifically, users were asked about what they were doing on Wikipedia, how often they used Wikipedia, if they had ever contributed to Wikipedia (and in what manner), their age, gender, location, and availability. Based on these criteria, the 2,500 users who responded to our survey were filtered down to 500 viable subjects based on their answers to these questions. The team, along with B|P, partnered with Davis Recruiting to contact, filter, and screen these 500 participants based on their Wikipedia contribution history, Wikipedia usage patterns, their given reasons for not contributing, and their talkativeness and openness to discuss their thoughts and actions. From 2,500 users, we ended up with 10 study participants and 3&ndash;5 waitlisted participants. <div style="float:left">[[File:Research-Recruitment-Screener.png|thumb|400px| Screenshot of Ethnio recruit survey]]</div> <div style="float:left">[[File:Research-Recruitment-Invite.png|thumb|400px| Screenshot of Ethnio screener invitation]]</div> <div style="float:left">[[File:Research-Recruitment-Thanks.png|thumb|400px| Screenshot of Survey Gratitude]]</div> <div style="clear:both"></div> === Study Participants === ==== Lab Testing ==== {| class="wikitable" |- ! Participant No. ! Age ! Gender ! Wikipedia Editing History ! Wikipedia Usage ! Occupation ! Other Info ! Location |- | 01 "Suzanne" | 50 (45&ndash;54) | Female | Has not contributed, but is willing to. Has account. | Every day | Paralegal. | Was checking a reference. | San Francisco, CA |- | 02 "Grace" | 24 (18&ndash;34) | Female | Has not contributed, but is willing to. | Every day | Medical Student. | Was looking up diseases. | San Francisco, CA |- | 03 "Tito" | 21 (18&ndash;34) | Male | Has not contributed, but is willing to. | Every day | College Student and Video Producer. | Was researching corporate videos. | San Francisco, CA |- | 04 "Dan" | 41 (35&ndash;44) | Male | Has not contributed, but is willing to. Has account. | Every day | Programmer | Was reading about DVI and HDMI interface info. | San Francisco, CA |- | 05 "Seamus" | 43 (35&ndash;44) | Male | Has not contributed, but is willing to. | More than once a week | Controller for a non-profit | Was researching for a presentation. | San Francisco, CA |- | 06 "Saurab" | 28 (18&ndash;34) | Male | Has not contributed, but is willing to. Has account. | More than once a week | Retail Software Developer | Was reading about supply chain processes. | San Francisco, CA |- | 07 "Gene" | 64 (55&ndash;64) | Male | Has not contributed, and is NOT willing to. | Every day | Retired Public Transit worker | Researching. | San Francisco, CA |- | 08 "Claudia" | 64 (55&ndash;64) | Female | Had edited fewer than 5 entries. Has account. | Every day | Database administrator | Looking up Frank Loesser | San Francisco, CA |- | 09 "Galen" | 24 (18&ndash;34) | Female | Has not contributed, but is willing to. | More than once a week | Costumer | Was finding out about Americans of German descent. | Oakland, CA |- | 10 "Nikki" | 16 (Under 18) | Female | Has not contributed to Wikipedia, but has to other Wikis. | Every day | High School Student | Was looking up a TV Series. | San Francisco, CA |} ==== Remote Testing ==== {| class="wikitable" |- ! Participant No. ! Age ! Gender ! Wikipedia Editing History ! Wikipedia Usage ! Tech Savvy ! Other Info ! Location |- | 01 "Lisa" | (55&ndash;64) | Female | Has not edited, but is willing to | More than once a week | 2: Uses computer to access internet and email apps. | Research | Eureka, CA |- | 02 "Shaun" | (18&ndash;24) | Male | Has not edited, but is willing to. | Every day | 3: uploads and downloads files from internet and devices | Research | Rexburg, ID |- | 03 "Jerry" | (25&ndash;34) | Male | Has not edited, but is willing to. | Every day | 2: Uses computer to access internet and email apps. | Reading about the history of New York | New York, NY |- | 04 "Bryan" | (25&ndash;34) | Male | Has not edited, but is willing to. | More than once a week | 3: uploads and downloads files from internet and devices | Researching psychology concepts | Apex, North Carolina |- | 05 "Carrie" | (18&ndash;24) | Female | Has edited fewer than 25 entries | Every day | 3: uploads and downloads files from internet and devices | Looking up information | Bayside, NY |} === Scripting === The moderator script was drafted by the Wikipedia Usability Team, B|P, and the Wikimedia Foundation, and an almost identical script was used for the lab subjects and the remote subjects, the discrepancies being entirely related to the difference in set up. The script aimed to see how users would attempt to and feel about a collection of tasks or objectives that first time and early Wikipedians frequently encounter in their editing process including, but not limited to: * Finding and using the various modes of editing ("edit this page" vs. section edits) * Adding personal content or information to an existing article * Looking at Discussion Pages * Adding comment/thread to a discussion page. * Adding or using content from an external source (website, paper, etc) * Adding a reference to content * Adding an external link to a list or section of links * Editing an article that uses a template * Navigating through template syntax to edit an infobox. * Formatting content (Headers, bold, italics, linking, tables) * Creating a new article * Fixing a typo * Finding and using help <br> Though the script was generally task based, the questions were open ended and left room for interpretation, encouraging subjects to not try to complete the tasks in any "correct" way, but rather to go about them naturally, if they had felt the motivation to do so on their own. Open-ended interview questions including "How did you find that process? What did you like or dislike about it?" regularly follow every "task". The script was piloted on two internal members of the Wikimedia Foundation&mdash;one regular editor, and one newbie editor&mdash;prior to the lab and remote testing. *View the complete Moderator Script [[Moderator Script | here]] *View B|P's explanation of Moderation Techniques [http://boltpeters.com/articles/moderating.html here] == Summary of results == The primary goals of our study were to examine the ease of use of the Wikipedia editing interface, focusing on both cognitive and UI obstacles to editing and factors that could potentially increase users' editing of articles. We focused on editing tasks, but along the way learned about much more than the specific tasks and the editing experience. While the team observed no patterns or distinctions based on gender alone seen during the study, we observed patterns amongst the different age groups. Younger users (Under 18&ndash;34) tended to have less inhibition to make smaller changes to Wikipedia than older users (45+), and in doing so also tended to learn more by example and employ a trial and error method to making changes. When the trials of these younger users did not reach success, they were also more resilient in recovering from those errors. Older users tended to give up more readily, feared they might "break" things, and often sought instructions from the "they" behind Wikipedia. =====''People Love Wikipedia (and get there easily)''===== <span style="color: gray"> ''"I use Wikipedia all the time. Usually it’s the most information in the easiest spot to access. It always looks very well put together it boggles my mind how many people can contribute and it (still) looks like an encyclopedia."'' -- Galen, 24, Costume Designer</span> <span style="color: gray"> ''"I like Wikipedia because it's plain text and nothing flashes" '' -- Claudia, 64, Database Administrator </span> If there was one thing that was consistent and unanimous across our study participants, it was the assessment that Wikipedia is an incredibly valuable information resource whose accessibility is unparalleled. Aside from its value as a reference, a time and lifesaver, and an up to the minute news resource, participants also praised its simplicity, coherence, and breadth. They find that the quality and quantity of information they find there is outstanding, trustworthy, and their go-to reference when they have a question or need more information about a topic, even one that they themselves might have quite a bit of expertise on. Users also tend to click on Wikipedia articles if they see them as part of the results list when they search for a topic/subject, because they trust the content and are familiar with Wikipedia. An extra thanks to Google, for showcasing just how referenced Wikipedia articles are&mdash;consistently making their links one of the top hits&mdash;our users count on that! <span style="color: gray"> ''"I usually use a Wikipedia shortcut on my computer"'' -- Suzanne, 50, Paralegal </span> <span style="color: gray"> ''"It's usually [one of] the first hit[s] on Google"'' -- Grace, 24, Medical Student </span> <span style="color: gray"> ''"I don't usually go to the Wikipedia front page."'' -- Dan, 41, Programmer </span> By and large, participants explained that they accessed Wikipedia articles through a top search hit from Google. Other methods of entry were through browser search plugins, shortcuts, and referring articles. When asked to head to Wikipedia, many participants stated or explained that they had never been to the front page before. =====''Wiki Syntax is not that hard to ignore (in small doses)''===== <span style="color: gray"> ''"So now I learned how to edit. It was okay, just like editing, I do it every day…. Things like my personal profile on an internet dating site."'' -- Gene, 64, Retired Public Transit Worker </span> <span style="color: gray"> ''"Pretty cool, easier than I thought, I just have to get used to it."'' -- Lisa </span> Users' word processing skills translated to the task of editing text in Wikipedia so that all the users we spoke to, including the technically uninitiated, were able to identify and make changes to the content text (as opposed to the wiki markup syntax) on Wikipedia. The changes users were able to make included correcting typos and grammar, adding words and sentences, copying and pasting, and formatting text (with bold and italics). The ease of editing around wiki markup drastically decreased as the complexity of the article increased&mdash;most notably when articles started with large infoboxes, templates, and other syntax-heavy elements. =====''The "right" way Vs. The "wrong" way''===== <span style="color: gray"> "''What I did was a hack, I'm not actually using the sit''e" -- Claudia, 64, Database Administrator </span> <span style="color: gray"> ''"Rather than making a mess, I'd rather take some time to figure out how to do it right"'' -- Dan, 41, Programmer </span> All of our participants are Wikipedia readers, but had little or no experience with editing. Generally the editing process was not a warm and welcoming one. Before subjects even hit the ‘edit’ or ‘edit this page’ buttons, they voiced concerns about the rules, proper etiquette, formatting, and were naturally conscientious of and inhibited by maintaining the community expectations. When a few of them attempted to find answers to their questions about rules and etiquette, they were overwhelmed with the amount of information and documentation they encountered. The most commonly expressed concerns were around who was allowed to edit what, who reviewed the edits, and what level of privileges were given to which users. Users also expressed concern and hesitation about editing without doing extensive research and feeling confident in their ability (put somewhat on the spot) to add relevant and accurate information. Not knowing what they could or should add/edit is a large barrier to at least some users' willingness to edit. Another major concern that participants expressed was the need to cite and validate their information. More often than not, our subjects did not know when they were expected to add a reference, felt an impulse to add a reference anyway, and faltered on the right way to do that, which included determining where in the article (or which section) was appropriate, the correct formatting, and the appropriate syntax when the references were autogenerated. In cases such as these references (as well as html links, internal links, and lists) many users copied and pasted text from examples from within the same article in order to make their edits appear the way they wanted them to&mdash;namely to appear like others on the page. While this worked fine for most simple, basic edits, users felt that this was a ‘hack’ and they weren’t doing it in the ‘right way’. The final observed example where participants struggled with the right and wrong way to do things was when they received conflicting messages. One user whose edits were immediately reverted after they saved was flustered and concluded that edits must go through a review process and assumed they'd 'show up in a few days.' Additionally, when viewing discussion pages participants felt quite confident about what type of content and discussion was appropriate, until they encountered the most noticeable text on the page stating "this is not a forum," after which the doubts started to roll in. =====''Feeling Stupid''===== <span style="color: gray"> ''"[I felt] kind of stupid."'' -- 24, Galen, Costumer </span> Every user in this study struggled to get a basic grasp of the editing interface. Despite users’ overall excitement about Wikipedia, their willingness to spend up to an hour on the site, and varying levels of computer expertise, they largely failed to make edits correctly without repeated attempts and efforts. Users regularly commented that they had ‘no idea’ or ‘no clue’ what they were looking at, or what they were doing. While they actually were able to edit simple text, users were not at all confident that they were succeeding during the process. As users edited, they mentioned that they thought they were looking at html or some variation of html, and they all admitted that they weren’t familiar with it, or knew very little. They commonly used descriptors such as ‘computer stuff’, ‘technical stuff’, ‘programming language’, ‘syntax’, etc.; in other words, something that is ‘not for me’, but for someone who has been trained in this professionally. Many users described their ideal or expected interface as something more like facebook.com, myspace.com, or a blog- an intuitive GUI that hides the code. This led to intimidation in editing anything, ‘in case I mess it up’. Users were not confident that they were doing the right thing until they had previewed the page and seen that their changes were displayed in the way they expected. Users also did not find the toolbars too helpful- though nearly all of them hovered over the toolbar icons to read the pop-ups, the only icon they recognized and used consistently was Bold. * Expertise * Level of comfort * Lack of consistency * Conflicting messages * 10 ways to do 1 thing =====''Feeling Overwhelmed''===== <span style="color: gray"> ''"There sure is a lot of stuff to read"'' -- Dan, 41, Programmer </span> <span style="color: gray"> ''"This is where I'd give up"'' -- Claudia, 64, Database Administrator </span> <span style="color: gray"> ''"I'm sure there is help out there, but I am too lazy to read that."'' -- Tito, 21, Student and Video Producer </span> <span style="color: gray"> ''"What's to stop you from just putting in anything?"'' -- Suzanne, 50, Paralegal </span> <span style="color: gray"> ''"But it's on the internet and people will read it and believe it's true."'' -- Grace, 24, Medical Student </span> There were a variety of things that left our participants feeling overwhelmed, but articles that started with infoboxes, thick wiki syntax, help docs, and any attempts to find concise answers on rules or guidelines left participants feeling lost. Some explained "If [I] can't read it in five seconds, you've lost me," while others exclaimed "It may take a whole night to do this", and another spent the majority of their time with us searching and digging, explaining "If I really wanted to put it on there, I'd find a way to do it." While their thresholds varied, the results were strikingly similar&mdash;lots of information, not a lot of guidance; more questions, fewer answers. =====''What I see Vs. What I get''===== <span style="color: gray"> ''"I'm more of a visual person."'' -- Galen, 24, Costumer </span> <span style="color: gray"> ''"I couldn’t really understand the format, I didn’t know what it was saying. I would just go to the stuff that’s readable. It looks kinda like a website, lingo stuff."'' -- Tito, 21, Student and Video Producer </span> <span style="color: gray"> ''"In many websites, you kind of see the screen just the way you see it in the article, Here it looks like they converted it into plain text. I think what I’ll have to do is open another Wikipedia, so I can compare the views. In blogs, it’s easier to add stuff- you don’t go into the programming mode. This html version- its much easier to edit a blog."'' -- Saurab, 28, Retail Software Developer </span> Once within the editing environment, most subjects commented on the illegibility of the hybrid Wiki syntax and article content&mdash;the more complex the article, the more exaggerated the response. When users made it past their initial reactions, navigating around the syntax to perform basic word processing tasks (correcting a typo, inserting a block of text, bold and italics formatting) proved less problematic than finding a particular section, adding references, using tables, creating and naming links. But not even our youngest and most computer savvy participants accomplished these tasks with ease. Aside from feeling confused by the “code”, “computer lingo”, and “html”, subjects could not correlate what they were seeing within the edit box to what they saw on the article page. We saw the vast majority of participants perform the same behavior as they began to edit&mdash;most subjects opened a separate browser window to view the static article as they were making their changes and used preview and save before they had finished their work to monitor their editing progress and results. * Expectations * Blogs * Word Processor * Previewing and Saving * Lingo/Html/Lingo =====''What I do Vs. What I get''===== <span style="color: gray">''"They should have instructions for what you want to do, but it's really not there."'' -- Suzanne, 50, Paralegal</span> <span style="color: gray">''"Can't something auto correct my links [to internal pages]?"'' -- Grace, 21, Medical Student</span> <span style="color: gray">''"Let someone else do it (waves hands)" -- Claudia"''</span> A significant number of our participants, noticeably female, tended to have expectations around actions and processes that could happen without being explicitly requested. These users expressed expectations for help of the right variety being presented to them at the right time, automated clean up and formatting of edits ('I hope that someone will come after and fix it'), and the existence of an editing or reviewing staff, mysteriously called "they" (there is no such person or persons!). * Expectations: automation and "they" * Instructions =====''Exploring (learning by example) and Receiving Instructions (learning from Help Docs)''===== <span style="color: gray"> ''"I don't know by looking at it [here], but by looking at other examples."'' -- Grace, 24, Costumer </span> <span style="color: gray"> ''"I like to learn by example because you don't have to digest a whole lot of irrelevant stuff."'' -- Dan, 41, Programmer </span> <span style="color: gray"> ''"I want to see instructions for the "edit this page."'' -- Suzanne, 50 Paralegal </span> When participants were asked to perform a task or format a particular sentence, rather than consulting help, they chose to look within that section or article for another example of a similarly formatted word or sentence. This proved to the be the most effective learning tool for uninitiated editors. Copying and pasting from another example relieved some of their concerns about the "right" or "wrong" way to do things and the illiteracy of wiki markup. It also helped in associated what they were seeing in the edit box with what they were typing (or here, copying) within the edit window&mdash;"I don't know by looking at it, but by looking at the other ones." Aside from learning by example, most participants successfully learned by trial and error. Previewing and saving after the most minor of changes to verify the result with the expectation (i.e. correctness) was commonplace. Many participants started off with baby steps&mdash;"I'm just going to try and type sort of what I see, just as a test" on an article, and notably not in the sandbox. This method seemed to lower barriers to editing and thresholds to learning&mdash;"I can guess on how to do things based on what's already in the page." =====''Sticklers for Details''===== <span style="color: gray"> ''"I would correct people's grammar errors, subject verb agreement"'' -- Gene, 64, Retired Public Transit worker </span> At the conclusion of our interviews, we asked all of our participants what might encourage them to contribute more to Wikipedia or in what ways they felt they would contribute. Many mentioned that fixing typos and grammatical errors would be one of the actions they'd be most likely to do. In fact without prompting, some users started to do this on their own in the course of completing other tasks. Participants of all of the age groups did this, but those that explicitly mentioned it tended to be older (44+). =====''References''===== <span style="color: gray"> ''"Should[n't] I cite the text that I inserted from Creative Commons."'' -- Nikki, 16, High School Student </span> <span style="color: gray"> ''"I'm aware that copying directly from another source is discouraged and that references are needed... I don't want to put in incorrect information, that's one of the main reasons I don't go changing stuff."'' -- Saurab, 28, Retail Software Developer </span> <span style="color: gray"> ''"How will people know it's genuine information"''-- Dan, 41, Programmer, who spent the majority of our session going to great lengths to verify the validity of his edit. </span> Without any prompting, the majority (one less than the entirety) of our participants expressed the desire or obligation to cite their sources, provide references, or validate the information they were adding or editing on Wikipedia. That desire, however, rarely resulted in a successful citation. Subjects struggled to differentiate between a reference, an internal link, and an external link. In fact, only one subject used the "shortcut" for an internal link in lieu of using the full html address for the forwarded article. Whether in the course of attempting to create a reference or while accomplishing another editing task, many users hovered over each of the toolbar icons in search of a solution. If/when users found the "reference" button (at the far right!), most could not digest the syntax that was placed at their cursor and questioned where the super script, footnote number, and text belonged and would end up. In the few cases in which the subject was adding a reference to an article where these references were auto generated, the users were completely dumbfounded. =====''Creating a New Article''===== The task that nearly every user failed at was creating a new page. Participants passed over the pointer to create a new article within search results, did not associated red links with yet-to-be-created pages, and could find no obvious button or action in the Wikipedia navigation. Several users, while scanning the pages to try to figure out how to create a new article, saw ‘create a book’ on the left, and thought maybe they should ‘add wiki page’ in order to create a new article. The wording ‘create’ likely points them towards that link, as there is no other mention of ‘create’ on the page. The few users that managed to create a new article commented on the lack of formatting or templating guidelines and expressed surprise that the starting point was a completely blank slate. =====''Where do I edit?''===== Users often missed the ‘edit’ buttons next to each section, clicking on ‘edit this page’ all the way at the top. This often got them lost if they were editing a particularly long article, as they weren’t easily able to find the section they wanted to edit. Several users also clicked on the wrong ‘edit’ button next to the sections, thinking that the ‘edit’ button below the section referred to the section above. Users who got used to editing single sections (instead of the whole page) expected to be able to edit the first section, as well as the template box at the top, separately from the whole page. =====''Clutter''===== Repeatedly, users missed messaging displayed on the pages. The amount of information and the number of ‘boxes’ on each page may have distracted users from the most important/relevant messages. Some users also missed the ‘save’ button because they got confused by the double scroll bars on the edit page. The message under the ‘Discussion’ section for various articles was confusing to some users, especially when they read ‘this is not a forum’, which seemed to contradict their thoughts about what a ‘discussion’ page would include. =====''Help needs some help''===== <span style="color: gray"> ''"I have no idea how to do that, maybe there is a how to?......Help should be on the top right. It's always there."'' -- Claudia, 64, Database Administrator </span> <span style="color: gray"> ''"There should be instructions here. It's not immediately clear."'' -- Suzanne, 50, Paralegal </span> While most participants said they probably wouldn’t go there on their own, once they were prompted to explore the Help section, most users did not find the section very helpful, if they even found it. The amount of information is overwhelming to users, and users sometimes got lost trying to find the one set of instructions they needed in order to complete their task. The cheat sheet was the only item in the help section that led to a subjects successful edit. Copying and pasting from other examples within the article or from another article was more often the help users sought. Additionally, we never saw the same click path through help twice, even when participants were looking for the same information. Users looking for the same information ended up in any number of final destinations (including the "Simple English Wikipedia" when one user was particularly challenged and was looking for a 'simple' answer), the majority of the time without answers. Help proved to be neither intuitive or consistent. ===== '' Inhibitors to Editing'' ===== Most users said they had ‘thought about’ editing Wikipedia, but never done it because of laziness or lack of time. The few who had edited had made only minor changes to sentences (fixing typos or grammar, etc.) Users mentioned as they tried to edit that they would need ‘more time’ to learn how to do what it was they were attempting, because they didn’t understand Wiki-markup, and it wasn’t immediately obvious what they needed to do. Users also expressed concern that the content they were adding was ‘correct’&mdash;in terms of content appropriateness, accuracy, and formatting. =====''ETC''===== *When using Wikipedia's own search, users rarely saw the "did you mean" results that were close approximations of their search terms, thus having to search again. In two cases, users left Wikipedia's search and used Google instead. *Some users missed the ‘spam-blocker’ code that they had to put in because it appeared above or below the fold of the page they ended up on after they tried to save. *Most users thought the ‘history’ section of the articles would be useful, but only for articles that they had a particular interest in or were editing themselves. However, some users were confused by what ‘prev’, ‘cur’, or ‘hist’ meant. *While most users did not actually try to upload images, the few who did were confused as to how to do it, and how exactly the process worked. === Highlight Videos=== * [http://commons.wikimedia.org/wiki/File:WMFUsability_highlights_explain.ogv Explain the Editing Process to Me] * [http://commons.wikimedia.org/wiki/File:UX_lookslike.ogv I Can’t Tell What This Really Looks Like] * [http://commons.wikimedia.org/wiki/File:Wiki_feel_stupid_v2.ogv Editing Wikipedia Makes Me Feel Stupid] === Full Interview Videos === [[Category:Usability studies]] kbkau13p9rqyfrntjrue16ytw7ujwb8 6 319 1562 1458 2009-05-29T17:38:13Z Trevor Parscal (WMF) 3 moved [[File:LabTest00.jpg]] to [[File:Research-Photo-LabTesting.jpg]]:&#32;More specific name wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 320 4522 4521 2009-11-13T00:24:14Z Parul Vora~usabilitywiki 185 Undo revision 4521 by [[Special:Contributions/Parul Vora|Parul Vora]] ([[User talk:Parul Vora|Talk]]) wikitext text/x-wiki __NOTOC__ {{Internal}} These designs are either preliminary mock-ups of prototypes which may be built or screenshots of prototypes which have been built but are still under development. Some of the ideas in these mock-ups are creative and experimental, while others are more practical and proven approaches. == Skin == ==== Motivation ==== * Improve visibility of common navigation elements and reduce visibility of less common ones * Decrease clutter throughout * Increase visibility of search box ==== Approach 1 ==== <!-- This design was created by Trevor Parscal on May 28th 2009 --> [[File:Design-Skin-1.pdf|thumb|200px|page=1]] * Reduce unneeded boxes and lines * Spread out items in cluttered areas * Move search box to the top-right * Separate tabs into namespaces, views and actions (in a drop down) '''Summary''' Vector is a new skin which uses a similar layout to MonoBook but reduces the superfluous use of lines and boxes. In practice this skin also reduces the download size of skin related information to 50% of the size of MonoBook, and requires a fraction of the CSS code. <div style="clear:both"></div> == Navigation Tabs == ==== Motivation ==== * Improve communication of where user is and where they can go * Increase visibility of alternative views of information, especially editing * Decrease clutter in head of page ==== Approach 1 ==== <!-- This design was created by Trevor Parscal on May 24th 2009 --> [[File:Design-NavigationTabs-1.pdf|thumb|200px|page=2]] * Display navigation in a more structured way using sections, views and actions * Proportion visibility of elements to frequency of use and increase overall size * Visually differentiate sections, views and actions * Collapse less commonly used elements into on-mouse-over drop-down menus '''Summary''' This design is superseded by the Vector skin, but laid the initial groundwork for tab reorganization. The downside to this design was the movement of tabs which occurred when switching namespaces, while the upside was it's clearer representation of structure between what tabs were namespaces, views, and actions. <div style="clear:both"></div> == Edit Toolbar == ==== Motivation ==== * Improve ease of interpretation of icons * Balance visibility of commands with frequency of use * Provide access to contextual help resources ==== Approach 1 ==== <!-- This design was created by Trevor Parscal on May 23rd 2009 --> [[File:Design-EditToolbar-1.pdf|thumb|200px|page=2]] * Implementation of the icons from the [http://tango.freedesktop.org/Tango_Desktop_Project Tango Desktop Project] * Removed many advanced commands (may reintroduce them in an advanced mode) * Added connection to help panel * Merged some commands into content generation wizard launching points '''Summary''' By reducing the number of icons down to only the most commonly (and successfully) used ones as per our user research study, the toolbar now requires less attention to comprehend its capabilities. Selective text labels help to explain less identifiable icons, and formatting types are grouped into a unified drop-down menu. This design requires the presence of content generation dialogs to provide additional interaction when inserting media and links. <div style="clear:both"></div> ==== Approach 2 ==== <!-- This design was created by Parul Vora on May 28th 2009 --> [[File:Design-EditToolbar-2.pdf|thumb|130px|page=1]] * Showed basic and common commands in top section of toolbar * Added expandable toolbars where more advanced commands and help reside '''Summary''' By adding an expandable/collapsible secondary toolbar area the primary toolbar can be simplified while still providing access to additional items. This design is more transition-friendly as it provides a way to improve the layout of the toolbar without modifying the functionality of the actual buttons. The icons represented in this mockup are for illustration purposes only and will be replaced with duo-tone (full color on mouseover) versions of icons from or based on the Tango Desktop Project. <div style="clear:both"></div> == Search Results == ==== Motivation ==== * Improve users' comprehension of results * Align with users' expectations for results format * Improve navigation through results ==== Approach 1 ==== <!-- This design was created by Trevor Parscal on May 22nd 2009 --> [[File:Design-SearchResults-1.pdf|thumb|200px|page=2]] * Increased visibility of titles of results * Implemented icons from the Tango Desktop Project for paging navigation * Reduced visibility of infrequently needed information * Visually structured search page to meet users' expectations '''Summary''' By analyzing the user experience of popular internet search engines many common and useful features have been identified which present solutions to issues found while researching user interaction with search results. One key feature of this design is that it keeps as many of the search results as visible as possible. Other elements such as a list of common search configurations provide quick access to different search results using the same search terms. Overall, reducing clutter and visually encapsulating ancillary information contributes to improving the visibility of the search results. <div style="clear:both"></div> == Section Edit Links == ==== Motivation ==== * Increase clarity of what content relates to the edit link * Improve visibility of section edit links ==== Approach 1 ==== <!-- This design was created by Arash Boostani on May 15th 2009 --> [[File:Design-SectionEditLinks-1.jpg|thumb|200px]] * Provide a visual indication of what will be editable when the user mouses over the section edit links '''Summary''' Our research showed that many of the times which people did find the section edit link, they incorrectly connected the link with the content above it rather than below. By highlighting the affected content when the user mouses over the section edit link, the user is presented with an illustration of which portion of content relates to the link. This approach has technical limitations however, as the current approach to parsing text does not encapsulate sections or even structure the resulting HTML code reliably in relation to the section outline. An example of a case in which this approach breaks is when a div tag is opened in one section and closed in another - which is valid and common on Main Page articles but would break the section highlighting functionality. <div style="clear:both"></div> ==== Approach 2 ==== <!-- This design was created by Trevor Parscal on May 28th 2009 --> [[File:Design-SectionEditLinks-2.pdf|thumb|200px|page=2]] * Move section edit link next to section title * Show edit icon next to links By moving the edit links over to be directly next to the titles it's more obvious which section they relate to. Additionally, the icon helps to increase the visibility of the links, helping resolve the issue of users not finding them at all, which we identified in many cases during testing. In some Wikipedia projects, custom JavaScript code is being used to transform the page in a way that results in section edit links directly following the title, however this design takes it a step further with the removal of the brackets and addition of the icon and would ideally be achieved by modifying the actual output of the parser. <div style="clear:both"></div> == Layout (Cleaning up the Clutter) == ====Motivation==== * Organize and group links, messages intuitively * Consolidate redundant links, messages * Remove duplicate links and messages where applicable * Collapse information that tends visually overwhelm (templates use, hidden categories) ==== Approach ==== <!-- This design was created by Parul Vora on May 28th 2009 --> [[File:Design-Vacuum-1.jpg|thumb|130px]] <div style="clear:both"></div> == Overview == * Slides from an internal overview of acai design mockups. [[File:Design-Overview.pdf|thumb|130px|page=1]] bjety0y886xvmt6r1cs772ia9ki6af2 6 321 1563 1459 2009-05-29T17:38:35Z Trevor Parscal (WMF) 3 moved [[File:RemoteTest00.jpg]] to [[File:Research-Photo-RemoteTesting.jpg]] wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 322 1558 1285 2009-05-29T17:35:46Z Trevor Parscal (WMF) 3 moved [[File:Invite.png]] to [[File:Research-Recruitment-Invite.png]]:&#32;More specific name wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 323 1561 1286 2009-05-29T17:37:07Z Trevor Parscal (WMF) 3 moved [[File:Screener.png]] to [[File:Research-Recruitment-Screener.png]]:&#32;More specific name wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 324 1560 1288 2009-05-29T17:36:48Z Trevor Parscal (WMF) 3 moved [[File:Thanks.png]] to [[File:Research-Recruitment-Thanks.png]] wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 325 9238 9236 2010-11-01T20:57:02Z Hoo man 2104 Reverted edits by [[Special:Contributions/67.188.95.21|67.188.95.21]] ([[User talk:67.188.95.21|talk]]) to last revision by [[User:120.22.64.204|120.22.64.204]] wikitext text/x-wiki === Introduction and Setup === * Thank you for coming in. * Complete Consent forms - Creative Commons Licensing - we will be recording both your screen through screen-sharing and your face through that camera, and our audio conversation. These recordings are going to be posted on the internet and available for those interested in this research to view at least part of them. If you sign here, you are agreeing that's ok. * We're collecting feedback on Wikipedia. Basicallly I'll ask you some questions and then watch you use the webiste. * This will take about 45 min - 1 hr. === Explanation of Moderator and Participant Roles === * Your job is really easy, you just have to be yourself and act as you naturally would. I did not design this website, and I don’t actually work directly for Wikipedia, I’m just collecting feedback. As you interact with the site, please be honest with your positive and negative thoughts. There’s no right or wrong answers, and nothing you say will hurt my feelings. * You are not being tested, the Wikipedia pages are being tested. === Background Questions === * Tell us a little about yourself * What was it you were doing on Wikipedia when you filled out the survey a few weeks ago? * You said you come to Wikipedia XXX often. What are you usually looking up/doing? How has your experience been in the past? * (Non-editors) You mentioned that you haven’t edited Wikipedia before, but you’d be willing to. What are the reasons that you haven’t in the past? Can you tell me what you know now about the process of editing? * (Editors) You mentioned that you have contributed to Wikipedia before. Please tell us about those experiences. * Can you tell me what you know now about the process of editing? * (Optional) Have you ever uploaded an image to any of Wikimedia's resources? Would you be interested in uploading images to your entry? What kinds of things would you be interested in uploading? For what kinds of articles? === Think Aloud === * Next I’d like to have you go on Wikipedia to do a couple of tasks. * There’s one thing that I would like you to do differently. Please think aloud as you use the web site today. For example, if you are reading something read it out loud and feel free to say anything that comes to your mind as you read - for example that’s interesting or what in the world are they talking about? Also, talk out loud while you’re doing a task, so I can understand what you are thinking and doing. (e.g.: Now I’m going to try to use the search engine) And, if you get to a point where you would naturally stop working, let me know. * I’ll let you decide your task is complete, whether you find what you are looking for or not. Just tell me when you’re finished. Were going to be focusing on navigating through the website and making changes to Wikipedia entries. For the tasks that we’re going to do, we will be previewing your changes but for most of the time we won’t be permanently saving your changes (note: we will walk them through that if necessary) * Do you have any questions before we continue? Okay, let’s go to the Wikipedia website. * Login === Tasks === ==== Adding Personal Content ==== *What were you doing when you filled out the survey for this phone interview? Go ahead and continue doing that, or walk me through how you were doing that… * We want you to navigate to a Wikipedia entry that's of personal interest to you, you can remain on this page, or alternatively go to the entry for your: Hometown; Favorite sports team, movie, singer, actor; Last meal you had/book you read; College or University you attended. As you do this, remember to say everything you’re doing out loud. * If you wanted to add a sentence or paragraph of info to this page, how would you do that? Go ahead and show me. (pre-fab sentence to give user if they don’t know what to add: Free knowledge for everyone on the planet.) (if necessary, show them how to preview and cancel their changes instead of saving them here, and continue to do this throughout as needed, as we don't want to save any harmful changes!) * Is that something you think you might do? Why/why not? What other types of things might you want to edit? Why? (fix typo, add section, add reference, add comment on discussion page, etc.) * How did you feel about that process? How was that process? * What do you think about the way this is all laid out (the text, the navigation, and the other elements on the edit page)? How’s the information on this page? What information would you expect to be there? What information do you actually see there? Why do you think this information is here? ==== Discussion Pages ==== * Please go to the discussion page for this article. Have you ever read, used or contributed to a discussion page for a Wikipedia article? (if yes) Please tell me about that. ''Time Permitting'' * If you wanted to add a question or comment to the last section/thread on this discussion page, how would you go about doing that? Please go ahead and do that. (pre-fab sentence if the user doesn't know what to add, if they even get there: “Is it ok if I make and remove minor unharmful edits as a study participant?” * Now let’s pretend you saved your changes to this discussion page and wanted to get rid of those changes. How would you go about doing that? * Probe about history: What do you think the history is all about? What do you think that’s used for? Have you used it in the past/how would you use it? Have you had any unique experiences with the history pages? Please explain. * (If user doesn’t mention, ask about categories) Did you see the ‘category’ box at the bottom? Any idea what the ‘categories’ are? How would you use those? Have you used them in the past? Do you have any unique experiences with them? Please explain. ==== Adding External Content ==== * (If current need be) Let’s go ahead and go to another entry on Wikipedia. You can choose whatever is interesting to you. Alternatively: Hometown; Favorite sports team, movie, singer, actor; Last meal you had/book you read; College or University you attended. *Let’s say you wanted to add some information here from another source: say a document on your computer or in this case, another website? (Let user choose if there's something they would like to add. Help them come up with examples. If they can't come up with anything else, direct them to the http://www.creativecommons.com) * How would you go about doing that? Is that something you would do? Why/why not? How was that process? ==== Using References and External Links and lists ==== * (if user doesn't mention References) Did you see the section about references? Would you add a reference from your text to the XX site? Why/why not? Go ahead and show me how you would do that. * (if user doesn’t mention External Links) Did you see the section about external links? Would you also add the CC site to the external links? Why/why not? Go ahead and show me how you would do that. ** Note: if there is not a 'References' of 'External Links' on the Wikipedia entry that the user is viewing, direct them to the entry for “The Cathedral and the Bazaar” ''Time Permitting'' * Let's say you wanted to link to another Wikipedia article from within this article (called internal linking). How would you go about doing that? Is that something you would do? Why or why not? How was that process? ==== Editing an article that uses a template ==== * Let’s go ahead and take a look at the Wikipedia page on San Francisco, CA. * If you wanted to edit just the 'Transportation' section here, how would you go about doing that? * If you wanted to add a new section here, how would you go about doing that? ==== Adding Formatted Content ==== * Transportation section (hand user printed instructions): ** Create a new section, call it “Bridges” ** Include this text under the section heading: ** Golden Gate '''Bridge''' ** San Francisco – Oakland Bay '''Bridge''' ** Save your changes ** Then, above this text at the top of the section, please add the following: ** ''See also'': Golden Gate Bridge ** and link 'Golden Gate Bridge' to the Wikipedia entry on the Golden Gate Bridge. * (Make sure they know to make ‘bridge’ bold and 'See also' italicized) * How was that experience? ==== Navigating and editing within templates ==== * Let’s say you moved to San Francisco and wanted to change the population field to be one greater. How would you do that? (Point out where this information is on the actual entry if necessary). * Let’s say you wanted to add San Francisco's motto to the page. How would you do that? * How do you feel about all that? What do you think about all the stuff that’s on this (edit) page? ==== Creating a new article ==== * If you wanted to create a new article, how would you go about doing that? (if you can’t think of anything, create a new article for a made up historical figure named ‘Bartelby Sanchez’ or ‘Sidney Rapunzel’ or ‘Lucy McVrices’). * (if they can’t do it) Do you see anything here that might help you figure out how to do it? Why don’t you take a look at the help pages. How do you feel about the info the help pages give you? Did you find what you were looking for? ==== Creating a Header and a Table ==== * hand user printed instructions for new page: * Create a new section for this article with the header “Biographic Information”. ** In the body of the page under the section header, create a table with the following information in it: {| class="wikitable" |- | Age | Birthplace | Favorite Band |- | Your age | Your birthplace | Your favorite band |} === Final Questions === * What might encourage or increase your participation to Wikipedia? * Follow up on questions above === Summarizing Likes and Dislikes=== * Is there anything that you would want to see changed/done differently on the Wikipedia website? Particularly related to the tasks you completed today? If so explain. * Any other likes or dislikes that you’d like to mention? * Anything else you’d like to share with me or ask me? * Would it be okay for us to contact you if we have any follow up questions or information? === Follow up === * Well [participant name] that does it for us. Here’s your $75 Amazon gift certificate. Again, thanks so much for coming in and talking to us- it’s really useful for our research! [[Category:Usability studies]] fdbwi78t42adutwbhei1efm75cymvox 0 326 1367 2009-04-30T17:36:49Z Parul Vora~usabilitywiki 185 moved [[UX and Usability Study]] to [[Usability and Experience Study]] wikitext text/x-wiki #REDIRECT [[Usability and Experience Study]] 6x2xlavlzjqkx0g6b7uy1rzh4q6flkx 6 334 1417 1416 2009-05-13T18:04:12Z RobH 194 Protected "[[File:Wiki.png]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 341 1546 1507 2009-05-29T17:13:54Z Trevor Parscal (WMF) 3 moved [[File:Design-Skin.pdf]] to [[File:Design-Skin-1.pdf]]:&#32;Different approaches need numbers wikitext text/x-wiki Screenshots of prototype for new skin. Designed by Trevor Parscal and Parul Vora. e57hbtc3fw1erlpsudbmjciyjyici0x 6 343 1545 1510 2009-05-29T17:13:35Z Trevor Parscal (WMF) 3 moved [[File:Design-SectionEditLinks.jpg]] to [[File:Design-SectionEditLinks-1.jpg]]:&#32;Different approaches need numbers wikitext text/x-wiki Screenshot of initial prototype for section highlighting on mouseover of section edit link. Designed by Arash Boostani. j50rsfve7z3w456xghkputcix5f0yrk 6 344 1582 1515 2009-06-02T17:12:56Z Trevor Parscal (WMF) 3 uploaded a new version of "[[File:Design-EditToolbar-2.pdf]]":&#32;Resolution was too high @ 300dpi, now it's 72dpi. wikitext text/x-wiki Mockup of the second revision of the new toolbar. Designed by Parul Vora. 0xkn1qnpgufuipgg2agytf4mtz2k15g 6 345 1519 2009-05-28T23:33:09Z Trevor Parscal (WMF) 3 Mockup of second revision of section edit link changes. Designed by Trevor Parscal. wikitext text/x-wiki Mockup of second revision of section edit link changes. Designed by Trevor Parscal. j1z2z9jxtc2cnw7mkps4za8g5ugs3fe 6 347 1570 2009-05-29T17:52:14Z Church of emacs 18 moved without redirect -> no traces of image left except in unlinked log wikitext text/x-wiki #Redirect [[File:Design-EditToolbar-1.pdf]] lyqjaysfk5b6x9mt9ap91u7db8dpvn8 6 348 1584 1581 2009-06-02T17:30:20Z Trevor Parscal (WMF) 3 uploaded a new version of "[[File:Design-Overview.pdf]]":&#32;Flattened pages. wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 349 1587 2009-06-02T17:48:40Z Trevor Parscal (WMF) 3 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 351 1613 2009-06-09T13:33:23Z Eneas 66 My own creation based on the mockup of the usability team wikitext text/x-wiki My own creation based on the mockup of the usability team tkdpddty6cvvkyvwmzhfo6f3fq12vrz 6 352 1617 2009-06-09T19:47:45Z Eneas 66 My own creation based on the mockup of the usability team wikitext text/x-wiki My own creation based on the mockup of the usability team tkdpddty6cvvkyvwmzhfo6f3fq12vrz 6 353 1619 2009-06-09T21:27:24Z Eneas 66 My own creation based on a screenshot of the new vector skin wikitext text/x-wiki My own creation based on a screenshot of the new vector skin oh2zqeic9w0fsjucv8z3pwondkl7k9o 6 354 1629 2009-06-10T19:10:55Z Eneas 66 My own creation based on a screenshot of the new vector skin wikitext text/x-wiki My own creation based on a screenshot of the new vector skin oh2zqeic9w0fsjucv8z3pwondkl7k9o 6 361 1657 2009-06-16T21:30:27Z Trevor Parscal (WMF) 3 Screenshot of MediaWiki with the improvements set forth in the Acai release. wikitext text/x-wiki Screenshot of MediaWiki with the improvements set forth in the Acai release. 1tv4cfapqx1l9na4k1z27n5o7euhg8h 0 362 8893 8625 2010-09-16T18:44:22Z Arbitrarily0 2472 adjusted category listing wikitext text/x-wiki ''Wikipedia Usability Initiative team is planning on coordinating four releases with the core MediaWiki development team from July 2009 till March 2010. Each release is named after the names of tropical fruits in alphabetical order.'' == [[Releases/Acai|Acai]] == [[File:Release-Acai-01.png|thumb|300px]] This release is currently deployed as a user preference on all [[w:Wikimedia_projects#Wikimedia_projects|Wikimedia Project sites]]. '''Targeted features...''' * Tab reorganization * Edit toolbar improvements * Relocated search box * Improved search interface * General aesthetic improvements * Opt-in/Opt-out switch and survey For more information, see the [[Releases/Acai|Acai Release]] page. To help with ongoing browser compatibility testing see the [[Releases/Acai/Compatibility_Matrix|Acai Compatibility Matrix]]. <div style="clear:both"></div> == [[Releases/Babaco|Babaco]] == [[File:Babaco_link_dialog_example.jpg|thumb|300px]] This release is currently in development and staged on [[Prototype|prototype wikis]]. The main features of this release are: * Navigable Table of Contents * Dialogues for; ** Links ** Tables ** Find and Replace For more information, see the [[Releases/Babaco|Babaco Release]] page. To help with ongoing browser compatibility testing see the [[Releases/Babaco/Compatibility_Matrix|Babaco Compatibility Matrix]]. <div style="clear:both"></div> == [[Releases/Default Switch|Default Switch]] == == Citron == * [[Citron Designs]] * [[Citron Phase I|Phase 1 feature set]] for Citron The main features of this release are: * Folding of tables and templates * In-line preview * Refinements of dialogues * Support add-media-wizard from the toolbar and more Work in progress can be previewed in the [[Prototype|prototypes]]. Citron [[Releases/Citron/Compatibility Matrix|Browser compatability matrix]] [[Category:Releases| ]] g6lcj1e2a8zpf5rqkjbscfdod4tbufr 0 363 10260 5985 2017-02-21T03:45:10Z Krinkle 709 prettytable=>wikitable wikitext text/x-wiki __NOTOC__ == Browser Compatibility Matrix for Features in Acai == You may also be interested in the [[Releases/Babaco/Compatibility_Matrix|compatibility matrix]] for features in Babaco. {|class="wikitable" !rowspan="2"|Browser&nbsp;⇨<br/>Feature&nbsp;⇩ !colspan="4"|Internet Explorer !colspan="3"|Firefox !colspan="3"|Chrome !colspan="3"|Safari !colspan="3"|Opera |- !width="30"|5.5 !width="30"|6 !width="30"|7 !width="30"|8 !width="30"|1 !width="30"|2 !width="30"|3 !width="30"|B !width="30"|1 !width="30"|2 !width="30"|3 !width="30"|4 !width="30"|iP !width="30"|9 !width="30"|9.5 !width="30"|10 |- !rowspan="2"|Distribution |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:14.5%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:21.3%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:5.2%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:2.9%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:44.3%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.2%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:4.6%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.8%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:1.9%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |- |align="center"|<small>0.1%</small> |align="center"|<small>14.5%</small> |align="center"|<small>21.3%</small> |align="center"|<small>5.2%</small> |align="center"|<small>0.1%</small> |align="center"|<small>2.9%</small> |align="center"|<small>44.3%</small> |align="center"|<small>0.2%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |align="center"|<small>4.6%</small> |align="center"|<small>0.8%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |align="center"|<small>1.9%</small> |align="center"|<small>0.1%</small> |- !Toolbar |style="color:blue"|<!-- IE-5.5 -->XF |style="color:blue"|<!-- IE-6 -->XF |style="color:purple"|<!-- IE-7 -->RXF |style="color:green"|<!-- IE-8 -->P |style="color:green"|<!-- FF-1 -->P |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- C-B -->P |<!-- C-1 --> |style="color:green"|<!-- C-2 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-iP -->P |style="color:green"|<!-- O-9 -->P |style="color:green"|<!-- O-9.5 -->P |style="color:green"|<!-- O-10 -->P |- !Navigation |style="color:green"|<!-- IE-5.5 -->P |style="color:green"|<!-- IE-6 -->P |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |style="color:green"|<!-- FF-1 -->P |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- C-B -->P |<!-- C-1 --> |style="color:green"|<!-- C-2 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-iP -->P |style="color:green"|<!-- O-9 -->P |style="color:green"|<!-- O-9.5 -->P |style="color:green"|<!-- O-10 -->P |- !Search |style="color:green"|<!-- IE-5.5 -->P |style="color:green"|<!-- IE-6 -->P |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |style="color:green"|<!-- FF-1 -->P |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- C-B -->P |<!-- C-1 --> |style="color:green"|<!-- C-2 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-iP -->P |style="color:green"|<!-- O-9 -->P |style="color:green"|<!-- O-9.5 -->P |style="color:green"|<!-- O-10 -->P |- !Preferences |style="color:green"|<!-- IE-5.5 -->P |style="color:green"|<!-- IE-6 -->P |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |style="color:green"|<!-- FF-1 -->P |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- C-B -->P |<!-- C-1 --> |style="color:green"|<!-- C-2 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-iP -->P |style="color:green"|<!-- O-9 -->P |style="color:green"|<!-- O-9.5 -->P |style="color:green"|<!-- O-10 -->P |} Estimated browser distribution based on information from w3schools.com as of May 2009 [http://www.w3schools.com/browsers/browsers_stats.asp] {|class="wikitable" !Mark !Description |- |style="color:green"|P |Pass: Renders and functions properly |- |style="color:red"|F |Fail: Does not render or function properly |- |style="color:blue"|XF |Expected Fail: Does not render or function properly, but is not expected to due to expected browser limitations |- |style="color:orange"|RF |RTL Fail: Renders and functions properly in left-to-right mode, but not in right-to-left (as seen on our [http://prototype.wikimedia.org/ar.wikipedia.org Arabic prototype]) |- |style="color:purple"|RXF |RTL Expected Fail: Does not render or function properly in right-to-left mode, but is not expected to due to expected browser limitations |} == How can I help? == We need more people to follow our [[#Testing Procedure|testing procedure]] and report back to us on their experiences. Uploading screenshots and adding information to the [[Talk:Releases/Acai/Compatibility Matrix|discussion page]] is a great way to help us out! == Testing Procedure == * Login to prototype.wikimedia.org [http://prototype.wikimedia.org/en.wikipedia.org/Main_Page] [[File:Releases-Acai-Testing-Navigation.png|thumb|300px]] '''Navigation''' * Verify the all elements in the head area are rendering properly * Verify the tabs are functioning properly (highlighting when current) * Verify the drop-down on the right of the View History tab is rendering properly <div style="clear:both"></div> [[File:Releases-Acai-Testing-Toolbar.png|thumb|300px]] '''Toolbar''' * Visit featured article [http://prototype.wikimedia.org/en.wikipedia.org/Manchester_Small-Scale_Experimental_Machine] * Click edit [http://prototype.wikimedia.org/en-wp/index.php?title=Manchester_Small-Scale_Experimental_Machine&action=edit] * Verify the toolbar is rendering properly * Verify the sections of the toolbar function properly * Verify clicking of buttons on the toolbar functions properly <div style="clear:both"></div> [[File:Releases-Acai-Testing-Search.png|thumb|300px]] '''Search''' * Enter "small" in the search box at the top right and click search [http://prototype.wikimedia.org/en-wp/index.php?title=Special%3ASearch&search=small&fulltext=Search] * Verify each of the search profiles are rendering properly * Verify the advanced search controls are rendering properly <div style="clear:both"></div> [[File:Releases-Acai-Testing-Preferences.png|thumb|300px]] '''Preferences''' * Click preferences [http://prototype.wikimedia.org/en.wikipedia.org/Special:Preferences] * Verify the tabs of the preferences are rendering properly <div style="clear:both"></div> gzir43h59fbte220gmdydyq19z9clen 6 364 1667 2009-06-17T06:28:32Z Eneas 66 Screenshot of IE6 wikitext text/x-wiki Screenshot of IE6 cbrnp25ov8o7km5m5y1sthwg2rasp90 6 366 1692 1677 2009-06-17T23:00:24Z Trevor Parscal (WMF) 3 moved [[File:Releases-Acai-Testing-Tabs.png]] to [[File:Releases-Acai-Testing-Navigation.png]] wikitext text/x-wiki Screenshot of how Vector's tabs should look. 177h7fhrcg6aun3h8ik0laaavwbau22 6 367 1701 1678 2009-06-18T17:34:46Z Trevor Parscal (WMF) 3 uploaded a new version of &quot;[[File:Releases-Acai-Testing-Preferences.png]]&quot;: Adjusted to reflect bug fix. wikitext text/x-wiki Screenshot of how Vector's preferences should look. gonxzyy3pnzmt9gom4x9qh6iljjlbt5 6 368 1679 2009-06-17T19:46:23Z Trevor Parscal (WMF) 3 Screenshot of how Acai's search should look. wikitext text/x-wiki Screenshot of how Acai's search should look. r4gkes27thtq9i8nr7lnaslh1l3frki 6 369 1680 2009-06-17T19:46:51Z Trevor Parscal (WMF) 3 Screenshot of how Acai's toolbar should look. wikitext text/x-wiki Screenshot of how Acai's toolbar should look. ohg2vo4e6vumgs69n8rh54anpnpdycx 0 377 8626 5955 2010-07-29T13:15:46Z Nemo bis 9 cat wikitext text/x-wiki [[File:Release-Acai-01.png|thumb|400px]] [[File:Acai-berry.jpg|thumb|right|Acai berries]] The first release—named Acai—has been deployed to Wikipedia and all Wikimedia sister projects as a user preference since July 1 2009. The following features have been targeted. You can try it out by clicking "Try Beta" link on the top of every page. * '''Tab reorganization''' :The new interface called Vector provides clear indication of the state of “read” and “edit” whether you are in an article or an discussion page. * '''Edit toolbar improvements''' :Action-grouped expandable toolbar hides infrequently used tool icons. Users can expand the toolbar based. Power users can expand the toolbar to access specialized tools. Special characters and help references (cheat sheet) are built into the toolbar for easy access. Special characters are displayed based on the configuration of each language site. Toolbar icons are redesigned by reusing Tango and Gnome icons. * '''Improved search interface''' :Search result page is often the entry point to articles. The visibility of relevant results are increased by removing the clutter. * '''General aesthetic improvements''' :Some aesthetic improvements have been applied for visual enhancements and redundant information has been removed. *'''Opt-in/Opt-out switch and survey''' :As the features above are deployed as one of the user preferences, Opt-in/Opt-out page allows logged in users to turn on and off multiple preferences for the usability initiative at the same time. Users are asked to participate in a quick short survey when they opt-out. :<small>''This feature was enabled in beta form on 7 August 2009.''</small> [[Category:Releases]] s14ghgrb446cbrjg4c12tfbm7i90n2j 10 387 8665 8586 2010-07-29T13:34:35Z Nemo bis 9 cat wikitext text/x-wiki [[Image:Redirectltr.png|#REDIRECT ]]<span class="redirectText" id="softredirect">[[:{{{1}}}|{{{2|{{{1}}}}}}]]</span><br /><span style="font-size:85%; padding-left:52px;">This page is a [[:w:en:Wikipedia:Soft redirect|soft redirect]].</span><noinclude> [[Category:Templates]]</noinclude> qs59u9v679ls80e3gngxmtyyfggkksu 0 395 8888 7384 2010-09-14T20:34:37Z 79.84.176.164 wikitext text/x-wiki {{box |Tell us your opinion on |[[Opinion Dialogs|...the new insert dialogs]] |[[File:Glade-3.svg|45px]] |[[Toolbar|...the current toolbar]] |[[File:Preferences-desktop-font.svg|45px]] |[[Opinion Colors|...the prototype colorscheme]] |[[File:graphics.svg|45px]] |[[Opinion Edit Messages|...edit messages]] |[[File:groupchat.svg|45px]] }} We are continually researching, designing, and developing a variety of features to improve the usability of the entire family of Wikimedia and MediaWiki projects. Along the way, we frequently find ourselves asking "how does the community feel about that?" or "would our community support that or reject that?" So we thought we'd ask!! Though we cannot do this for every feature or detail of our project, here is the (ever growing) list of things we'd love to hear your point of view on: *[[Opinion_Icons | Format Icons]]<br> *[[Opinion_Watch | Watch and Unwatch]] *[[Opinion_Colors | Color Scheme]] *[[Opinion_Edit Messages | Edit Messages]] *[[Opinion_Left Navigation | Left Navigation]] *[[Opinion_Dialogs|Insert Dialogs]] *[[Opinion:_Language Links|Language Links]] <!-- == Usability problems == On the French Wiktionary, the Acai beta conflicts with the site's heavily customised MediaWiki:Edittools. How does one enrich the Special Characters toolbox? There's a whole bunch of language-specific entries that need to be moved from MediaWiki:Edittools to that menu. Also, the MediaWiki:Edittools display is no longer collapsible (and is truncated to boot!) once Acai is active, which makes it nearly unusable. [[User:Urhixidur|Urhixidur]] 15:52, 7 August 2009 (UTC) == Problems in hindi wikipedia== In hindi wikipedia we have added [http://hi.wikipedia.org/wiki/%E0%A4%AE%E0%A5%80%E0%A4%A1%E0%A4%BF%E0%A4%AF%E0%A4%BE%E0%A4%B5%E0%A4%BF%E0%A4%95%E0%A4%BF:Translit.js translit.js] to transliterate english (roman) charecters to hindi(devnagari) charecters. Translit.js works in editer window ,search bar and in many more fields but it dosent seem to be working with new Acai beta theme . Kindly help --[http://hi.wikipedia.org/wiki/%E0%A4%B8%E0%A4%A6%E0%A4%B8%E0%A5%8D%E0%A4%AF:Sumit_sinha sumit sinha] == The older sidebar was better == The older sidebar that came with one of the first releases of Vector is better than the current one in my opinion. It needed a few tweaks to make it more understandable, but the new sidebar that replaced has links that are too close together and it doesn't fit well with the rest of the Vector design. --[[User:Cmelbye|Cmelbye]] 22:51, 8 August 2009 (UTC) --> bedqgux8qzdexi9wyf7lqrjtautfmcf 0 396 1918 2009-07-08T22:06:16Z Parul Vora~usabilitywiki 185 moved [[Designs]] to [[Acai Designs]]: don't want to put babaco designs on the same page - it'll get way too long! wikitext text/x-wiki #REDIRECT [[Acai Designs]] megb3b53vskrvnh357l01hxz049b0v1 0 398 6681 6680 2010-04-27T12:18:09Z Gaeser 1817 Reverted edits by [[Special:Contributions/204.108.230.103|204.108.230.103]] ([[User talk:204.108.230.103|talk]]) to last revision by [[User:Mephiles602|Mephiles602]] wikitext text/x-wiki __NOTOC__ {{Internal}} [[File:Babaco.jpg|thumb|right]] We welcome your constructive feedback. Please use the [[Talk: Babaco_Designs | Discussion]] page for all of your comments. <div style="clear:both"></div> == Tabbed Navigation == <!-- This design was created by Juxn on July 13th 2009 --> [[File:090713 babaco tabs.pdf|thumb|200px|page=1]] === Motivation === * Introducing tabs that can be used within content generation dialogues and a right column. * The active tab should be a part of the page. * Emphasizing special functionality of tabs --> For example: The Edit link is unique and very important. It's different from a link in the left nav (like "Help" or "Mainpage") so it should look different. * Achieve consistent design === Approach === * Real tabs (not open at the top). * Rounded corners * Gentle gradient background * Blue background indicates a link * Gray background (="empty tab") and red link indicates a not existing page == Layout == [[File:babco_layout.pdf|thumb|200px|page=1]] === Motivation === * Take advantage of horizontal screen real estate without sacrificing readability page/article contents * Create space for contextual editing tools on edit pages only * Design layout of right navigation bar for possible inclusion in all Wiki pages. * Achieve a more predictable layout * Improve readability of article content without alienating any particular browser/screen configuration of our users === Approach === * Fixed width left and right columns * Elastic content column * Accommodates users with smaller (800X600) screens and is ideal for our users average screen size * Right column only exists on edit pages. == Color Scheme == [[File:colorScheme.pdf|thumb|200px|page=1]] === Motivation === * Add more visual cues for page navigation, points of interaction, action, selection, etc. * Carefully use color for emphasis of page, tabular, and organizational structure. === Approach === * Maintain historical consistency with wiki colors - blue for links, red for yet-to-be-started pages, yellow for selection - in a unified color palette. * Maintain sitewide consistency with colors across different pages. * Use more readable and differentiable colors. I.e. the dk. gray tested by many online newspaper sites. Use highlight, selected, dynamic, or static cue colors when appropriate. * Introduce color only as needed to solve specific navigation issues. == Toolbar Upgrades: Icons == <!-- This design was created by Juxn on July 12th 2009 --> [[File:090712 babaco toolbar.pdf|thumb|200px|page=1|GNOME icons]] === Motivation === * Improve comprehensibility * Achieve consistent design === Approach === * Adapting Gnome-Icons * Monochrome and simple in color treatment * Gentle shiny "button" style === Resources === *Learn how to make a "Bold" or "Italics" icon for your language [[Babaco Designs/Icon Localization|here]]. == Toolbar Upgrades: Button Interaction == [[File:button_interaction.pdf|thumb|200px|page=1]] === Motivation === * The current toolbar has a singular mode of interaction * We want the buttons to reinforce selection: This reinforces the user's sense of it being "click able" and their mouse selection. * We want it to reflect state: If my cursor is in a section that is already bold, it would be beneficial to have the toolbar/buttons convey this. === Approach === * Add mouse over behavior to toolbar buttons to improve interaction and experience. * Explore the possibilities of the syntax highlighting/development necessary to enable the toolbar with 2-way interaction. * If possible, add "selected" look and behavior to toolbar buttons. == Toolbar Upgrades: Dialogs == === Motivation === * Make it as easy to add links, images, references as it is to add and format text. * Allow users to create and insert these without needing to know wiki syntax * Create an intermediate between rich-text and wiki syntax for special insertions: links, references, media, tables [[File:contentGeneration.pdf|thumb|200px|page=1]] === Approach 1 === * Create dialogs that can be used for insertion, but that can also be used for editing those links, references, etc. * Be as smart and give as much feedback to the user when creating/inserting these elements * Achieve consistency of interaction across all dialogs. <div style="clear:both"></div> [[File:Wireframe-Babaco-Dialogs.pdf|thumb|200px|page=1]] === Approach 2 === * Unified UI for internal and external links using software to guess the intention of the user, but still allow the user to force the link to be internal or external * Give feedback for internal links as to whether the link is to an existing page or not * Greatly simplify the options for tables * Provide a preview of what the table will look like <div style="clear:both"></div> [[File:Ideas for tabledialog.pdf|thumb|200px|page=1]] ===Insert table dialog=== Please visit [http://prototype.wikimedia.org/s-3/index.php?title=Main_Page&action=edit Sandbox3] to test the dialogs. We are not sure about the preview * Because it does not reflect the table dimensions * It reflects tableborder, sortable table amd header row only * People might want to edit this preview-table, which is not possible. Therefor the preview should be named "Example" and should look not editable. (See mockup #1 - #2) * Maybe it is a wiser decision not to show this preview/example at all. (See mockup #4) == Editing Interface Improvements == [[File:Wireframe-Babaco-WikiEditor.pdf|thumb|200px]] === Motivation === * Users got lost while previewing * Users did not consistently locate and make use of the terms of contribution, edit summary, minor edit and watch controls * Users with different sized screens may wish to adjust the size of the table of contents or even hide it completely * Many users were not fully aware of the effects of clicking save (you've now changed Wikipedia!) === Approach === * Make preview a mode of the editing interface activated with a set of tabs * Only show terms of contribution, edit summary, minor edit and watch controls when a user clicks the publish button using a modal dialog. * Add hide and show control for the table of contents as well as drag-and-resize grips on the left side of the table of contents and a grip icon at the bottom. <div style="clear:both"></div> == Table of Contents + Help == [[File:contents.pdf|thumb|200px|page=1]] === Motivation === * Allow users to navigate the editing of the article as they do the article itself. * Give users a sense of where they are (or rather, their cursor is) in the structure of the article. * Possibly provide help in this right column real estate as well. === Approach === * Dynamically laid out table of contents. * Jumps to section on click * Scrollable. * Highlights current section. <div style="clear:both"></div> = Beyond Babaco = Some early designs looking forward past the Babaco Release. == Left Navigation == == Full Screen Edit Mode == [[File:fullScreen.pdf|thumb|200px|page=1]] ==== Motivations ==== * More screen real estate for editing tools and help * A more "defined" editing process and space * Simplifying the editing experience by removing less useful links and navigation. ==== Approach ==== * Use left and right columns for non-toolbar editing tools * Keep main sitewide navigation * Remove less relevant sitewide links == Messages == [[File:messages.pdf|thumb|200px|page=1]] ==== Motivation ==== * Prevent messages on discussion pages (as well as article pages) from overwhelming users and distracting from the content. * Prevent messages from taking a full screen of real estate - obscuring content. * Give users control for how they view, show, hide messages. ==== Approach ==== * Make messages collapsible * Provide toggle to show and hide messages * User right column for messages on article pages? * Ranking system for message type? == Discussion == ==== Motivation ==== * Users were not able to easily identify the timeline of discussions * Users had trouble knowing where to contribute to the discussion * Users often did not know how to, that they should, or simply forgot to add a signature * Processes like Featured content and deletion candidates must have complex templates and be managed manually ==== Approach 1 ==== [[File:Design-LiquidThreads-1.png|thumb|200px]] * Made posting isolated, as opposed to editing entire discussion * Enforced structure of discussion to represent threading and order * Posts are always signed automatically * Enable users to watch only their discussion * Set default parameters and structure automatically * See also [[strategy:Proposal:Stop using wikis for tasks for which wikis are not suitable]] <div style="clear:both"></div> ==== Approach 2 ==== [[File:Wireframe-LiquidThreads-1.pdf|thumb|200px]] * Integration of reply and internal link views into the post they are in relation to * Avoid obscuring information with the toolbar <div style="clear:both"></div> qeled1guwhqa06kq0nxllddq1w20unb 6 399 1928 2009-07-09T08:25:28Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 400 1929 2009-07-09T08:43:35Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 401 1930 2009-07-09T08:43:46Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 402 1931 2009-07-09T09:02:06Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 403 1932 2009-07-09T09:08:12Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 404 1933 2009-07-09T09:09:23Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 405 1934 2009-07-09T09:10:33Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 406 7059 6570 2010-05-17T16:56:34Z 82.74.192.60 /* Comments */ ++ wikitext text/x-wiki __NEWSECTIONLINK__ *<big>To discuss the Vector skin or anything else go to [[Talk:Prototype]].</big> *<big>To discuss the current Toolbar go to [[Toolbar]].</big> For the Babaco Design we consider to create new icons for the toolbar: * to have more comprehensible icons (for bold and italic for example) * to have icons that will be in a line with the website design So at the moment there are 3 questions where we need your opinion about, but feel free to say anything about icons on this page. ==Bold and italic== '''1.''' [[File:Icons a a.jpg]] * In Acai we used the GNOME Icons. * This is not bound to a specific language. "a" just represents any letter. '''2.''' [[File:Icons b i.jpg]] * These letters make more sense ("b"=bold "i"=italic) * This might not be comprehensible for non english speakers. * Or maybe it is being used so much that it is kind of universal. What do you think? Are there any people from non english speaking countries? ===Comments=== (Please post your comments here) I feel strongly that names of cities and countries should be used in their original languages (in other countries) (e.g., Deutschland, not Germany nor Allemagne nor Germania nor Alemanha; France, not Frankreich nor Francia; España, not Spain nor Espagne nor Spagna; Napoli, not Naples nor Neapel; Venezia, not Venice nor Venedig nor Veneza). Icons instead should be "universal" : we should not use "B" (for "bold") and "I" (for "italic") in English; nor, in French, "g" (for "Gras") and "i" (for "Italique"); nor, in German, "F" (for "Fett") and "K" (for "Kursivschrift"); nor, in Italian, "g" (for "grassetto") and "c" (for "corsivo"). That leaves us with Wikipedia's "universal" icon as explained: * In Acai we used the GNOME Icons. * This is not bound to a specific language. "a" just represents any letter. We need this icon to be simple and logical: as an artist, I feel that the italic "a" is pretty nice and clear, but I really do not like the design of the bold "a"... especially because it looks more like an "Inline effect" or "outline", than "bold". Improving the "a"s icon is easy enough. [[User: Siamodiversi]] 15 September 2009. 2009.09.15 Note that for the classic toolbar, we use B and I icons for bold/italic. Some months ago we introduced localized variants of them (and some others), which you can under skins/common. It's easier not to maintain more icon variants, of course... ;) --[[User:Brion VIBBER|Brion VIBBER]] 04:22, 10 July 2009 (UTC) I ve been talking to two chinese students today. They said that even though they know '''b''' and ''i'' from chinese-software they didn't know the meaning b="bold" and i="italic". So they said that it makes no difference if the letters are '''b''' and ''i'' or '''a''' and ''a'', since the letter actually are '''bold''' and ''italic''. Than I asked a french student, who didn't know b=bold and i=italic and was very confused about the icons. He said he would prefere '''a''' and ''a''. Than I asked two german students, they knew the meaning of b and i, even though the letters '''f''' and ''k'' are used in german. Nevertheless all of them said, that the current '''a''' and ''a'' icons are confusing, because both letters are in different typefaces. It should rather be the same typeface in bold and italic.--[[User:Juxn|Juxn]] 07:54, 10 July 2009 (UTC) The best thing would be to have different letter for each language. German: '''F''' and ''K'', English: '''B''' and ''I'' and so on. People find what they are used to and don't get confused. I'm not used to the icons that are currently used and had to think about their meanings. As Brion mentioned above localized variants are alredy possible. -[[User:Eneas|Eneas]] 11:46, 10 July 2009 (UTC) :By the way, I'm missing the signature button on discussion pages. Couldn't you add this icon because it's used quite often? -[[User:Eneas|Eneas]] 11:46, 10 July 2009 (UTC) : I will..--[[User:Juxn|Juxn]] 13:17, 10 July 2009 (UTC) ::In Swedish software '''F''' (Fet) and ''k'' (kursiv) is commonly used. [[User:Ainali|Ainali]] 21:00, 27 January 2010 (UTC) In Italian-localized Office programs the bold icon is almost always a '''g''' (for "grassetto", shortcut CTRL-G), while the italic icon used to be localized as a ''C'' (for "corsivo") but is now a capital ''<tt>I</tt>'' (even the shortcut is CTRL-I). I guess any letter will be fine, as long as it is clearly recognizable as being bold or italic. I think an uppercase ''<tt>I</tt>'' (in a serif font) would be more recognizable than ''i''. Also, in my (very humble) opinion, if the keyboard shortcuts are not localized, neither should be the icons. --[[User:Arcturus4669|Arcturus4669]] 15:01, 12 July 2009 (UTC) A general study: *About the Italic icon: The idea of using I for ''Italic'' is probably more because the letter "I" can be shown diagonally better than any other letter. Text editors use the Times new roman font for displaying this because the capital I has two horizontal lines which display the diagonal line (when in italic) better. *About the Bold icon: The main problem here is that the current Bold icon when compared to the italicized one doesn't look that much thicker. *About the relation between "B" and "I": The advantage of the two letters together is that they show each others function better. Through the "I" thinness the "B" thickness is more obvious. And through the "B" horizontal line the "I" diagonal line is more obvious. *Conclusion:Using the Times New Roman font with the capital letters I and B would be the best practice and the most usability advantage.---[[User:Diaa abdelmoneim|Diaa abdelmoneim]] 12:33, 14 July 2009 (UTC) From the silhouettes of the original set is better and should be incorporated into the new icons. The font should also emphasis the differences between bold, italic, and oblique ("slanting", often mistaken for true italics). Consider looking through serif fonts where this difference is better established, instead of bubble letters. [[User:Dispenser|Dispenser]] 13:28, 15 July 2009 (UTC) :most Hebrew speakers know the meaning of '''b''' and ''i'', but I prefer "a" for both. that way you can see the difference. [[Special:Contributions/93.173.230.238|93.173.230.238]] 10:23, 23 July 2009 (UTC) ::Hi, I'm from Italy and I think the icons with B and I are comprehensible. IMHO it would be better to put the letters B for the bold and I for the italic, both in capital letters. --[[Special:Contributions/151.64.105.230|151.64.105.230]] 20:07, 30 July 2009 (UTC) PS: great work, I'd love to edit wikipedia with this skin! Do we know what multilingual applications like OpenOffice do here? [[User:Mike.lifeguard|Mike.lifeguard]] 16:07, 6 August 2009 (UTC) :Microsoft Office uses Times New Roman capital letters taken from the localized names (F and D in Hungarian). --[[User:Tgr|Tgr]] 07:09, 7 August 2009 (UTC) If we want shortcuts (I don't think so - browsers use different modifier keys than document editors anyway, so it wouldn't be much help), then the two letters must be different and it's best to stick with I and B to avoid language-dependent conflicts with other shortcuts and with browser functions. Otherwise, localized letters would be far more preferable. --[[User:Tgr|Tgr]] 07:09, 7 August 2009 (UTC) How about make these icons convertible? I mean we can represent them as "'''B'''" and "''I''" in English Wikipedia, but also can represent them as "'''粗'''" and "''斜''" in Chinese Wikipedia. --[[User:PhiLiP|PhiLiP]] 19:50, 8 August 2009 (UTC) :"'''粗'''" and "''斜''" look strange to me --[[User:Liangent|Liangent]] 17:45, 10 August 2009 (UTC) :I'm from non-english speaking area, and I'm in favour of b and i. These 2 icons "stolen" from GNOME project are strange, old-lookng and confusing. Either b or i (or language specific - you can easily change letter in text editor - if icons are made in SVG) either use Oxygen icons from KDE project. --[[Special:Contributions/95.176.164.40|95.176.164.40]] 17:29, 14 August 2009 (UTC) ''''B'''' and '''I''' seems standard in most word processing software, which is what users will be familiar with, and has the benefit of being immediately recognisable (although I agree with the above points re. localisation). I find the typography of the current icons somewhat confusing, however, and would suggest using the more familiar plain (i.e. non-outlined) upper case characters instead of the proposed design. -- [[User:Philoscoffee|Philoscoffee]] 07:45, 24 August 2009 (UTC) :In Hungarian the translations of Microsoft Office use '''F''' ("félkövér") and ''D'' ("dőlt") and <u>A</u> (for underlined, "aláhúzott"), so B and I is not universally understood as representing 'bold' and 'italic' (although some versions (maybe most) of Office and other applications still use the shortcuts CRTL+b and CRTL+i). --[[User:Bdamokos|Bdamokos]] 17:03, 16 September 2009 (UTC) Both versions are far from ideal. The first set uses really strange letter shapes, which unneccessarily clutter the design. The second should use a serif font for the "i", in order to better emphasize the italic stylie. -- [[User:JovanCormac|JovanCormac]] 11:20, 5 October 2009 (UTC) : I don't care much whether it's going to be <big>'''B'''</big> and <big>''I''</big> or <big>'''a'''</big> and <big>''a''</big>. However I do strongly suggest NOT to make the B/I language specific as the usability somehow decided to do. Nowhere else have I ever seen that before and I doubt anyone would understand it. There's nothing wrong with the monobook-toolbar content wise. The icons were understood especially the bold/italics. Don't make new issues, there's enough to solve already. [[Special:Contributions/82.74.192.60|82.74.192.60]] 16:56, 17 May 2010 (UTC) ==Link icon== We will have only one icon for both internal and external link (which will open a dialogue to create and specify the link). So the icon should work as a general link icon. '''1.''' [[File:Linkicon externallinkforeverything.jpg]] We could use this icon, which is being used for external links. I like the icon itself, it's clear, simple and easy to recognize. Though the current meaning (external link) could be conflicting. '''2.''' [[File:Linkicon chain.JPG]] Or the typical chain-icon, which noone really understands, but erveryone is used to. '''3.''' [[File:Linkicon handcursor 1.png]] Handcursor and link. This shows a link concretly. This way it's quite intuitive and comprehensible. I am not sure how this matches the other (more abstract) icons. '''4.''' [[File:Linkicon handcursor 2.png]] Is "Link" a universal expression? Or do we need to support something like "abc"? What do you think? Do you have other ideas? ===Comments=== (Please post your comments here) I've always found the chain-link icons used in some editors rather unobvious. I might prefer a little bit of blue text with a hand cursor over it -- something which actually visible shows what a link looks like. --[[User:Brion VIBBER|Brion VIBBER]] 04:27, 10 July 2009 (UTC) As well as in the other sections: Please use icons where everybody is used to. I think standard icon sets can be found in MS Office and also Open Office. Please use these icons (or similar ones) because nearly everybody is used to them. -- [[User:Eneas|Eneas]] 11:50, 10 July 2009 (UTC) : We will definitely base all icons on established icon sets. (like MS Office, Open Office, Tango,..) But certain functions in our toolbar a pretty special. (see signature for example).--[[User:Juxn|Juxn]] 14:35, 10 July 2009 (UTC) +1 on the "blue text" icon, I find it natural. As for the "chain" icon in Office programs, I bet most novice users have no clue about what it does. Some time ago, I made a quick one for [http://allievi.sssup.it/jacopo/mwsvn/index.php?title=Sandbox&action=edit my experimental editor]. The hand cursor looks like a good idea. : A side note: how does the merged button work? What kind of link will the interface create if the user presses the button with no text selected? Autodetection is ok as long as there is some text selected. We definitely do not want to lose the hint that the "http://" prefix is required and that the link text can be specified. --[[User:Arcturus4669|Arcturus4669]] 14:50, 12 July 2009 (UTC) I see what you mean and I like it too. But unfortunatly we can't do it like this [http://allievi.sssup.it/jacopo/mwsvn/index.php?title=Sandbox&action=edit my experimental editor] because we don't support underlined links by default - and only blue "ab" would not be comprehensible imo. Therfor it might be a good idea to add the hand cursor (as Brion said) - though we only have 24x24px which is not enough to display blue text + a hand cursor. I am not a fan of it, but it looks like we are going for the chain. --[[User:Juxn|Juxn]] I've [[Talk:Prototype#Thoughts_from_Dispenser|commented]] about the unintuitive nature of the chain and have always needed to explain the "chain link" pun. I like Brion's suggest you could crop part of the hand and it will still be recognizable, but I worry since in MS Luna theme they use it as a hover effect. And what's with the black and white icon, I though we moved from the color hover effect to a saturation effect. [[User:Dispenser|Dispenser]] 13:28, 15 July 2009 (UTC) Blue "abc" with hand looks great; see if we can get that fitting in with the Tango icon theme style. --[[User:Brion VIBBER|Brion VIBBER]] 14:40, 16 July 2009 (UTC) Make the bold, italic, and link icons consistent, so that it's clear that they all do something to the same thing: text. The third icon is best, abc sounds like a dictionary, while "link" is recognizably a [[word]], as most wiki links are, even if it's foreign. How does it look with the underline? For the bold italic, perhaps an icon with thee I and B in the foreground (like the hand cursor), with '''bold''' and ''itali'' in the background (like "link"). External links should probably add that ugly little arrow - or perhaps http should be in place of 'link'. How does link look underlined? [[User:M|M]] 22:23, 20 July 2009 (UTC) Using the hand icon corresponding to what the user sees when interacting with the result makes a lot of sense here. [[User:Mike.lifeguard|Mike.lifeguard]] 16:08, 6 August 2009 (UTC) I'm not sure I would recognize the hand + blue text to be a link icon, even if it is logical afterwards. Convention usually beats logic. I would go with the standard chain (or globe-and-chain) most other editors use. --[[User:Tgr|Tgr]] 07:08, 7 August 2009 (UTC) :Though it might be more recognizable if it would be underlined and in a deeper blue (monobook uses <span style="color:#002BB8">#002BB8</span>, google <span style="color:#0000CC">#0000CC</span> or <span style="color:#2200CC">#2200CC</span>, firefox default is <span style="color:#0000EE">#0000EE</span>). --[[User:Tgr|Tgr]] *I vote for 1 - had I been only told about the choices, I would have stuck with the Office-style chain (link) icon as it is so widely used (if not always understood!) but having seen 1 I think it's most impressive and a break with tradition based on a really understandable icon might be acceptable.[[User:Bedales94|Bedales94]] 00:23, 8 August 2009 (UTC) *I like 4. Option 1 really confuse someone like me. --[[User:PhiLiP|PhiLiP]] 19:55, 8 August 2009 (UTC) *I like option 1 for external links, considering a similar icon is in use after external links. (Can we get that exact icon? Or change it?) I'm still ambivalent about internal links...keep brainstorming. [[User:HereToHelp|HereToHelp]] 02:52, 10 August 2009 (UTC) '''Re: #1''': This one clearly says to me "undock" or "maximise". I would expect this button would either spawn a new browser window dedicated to editing that article, or would expand the editing area. '''Re: #2''': If no one understand this icon, why would we use it? Why mimic a software suite for numbers alone? What, for that matter, is wrong with the blue wikilink <nowiki>[[ ]]</nowiki>? Won't this be immediately obvious to anyone who is editing an article with any Wikilinks? From what I see here, '''I can only support #4'''. ''We will have only one icon for both internal and external link (which will open a dialogue to create and specify the link).'' What? No! No no no no no! D: I use that to quickly Wikilink articles. Why in the world would I want to lose that ability? Double-click a word, click the Wikilink button. Why not have a disambiguating generic-link button and an intuitive blue wikilink button? - [[User:BalthCat]] [[Special:Contributions/142.167.84.28|142.167.84.28]] 07:23, 11 August 2009 (UTC) *I asked a friend to examine some icons and he thought that the square with an arrow was fullscreen. So yeah, it's out. [[User:HereToHelp|HereToHelp]] 02:51, 23 August 2009 (UTC) I think that the pointing hand icon is along the right lines, but 'abc' suggests spelling or dictionary lookup and may be confusing. Instead of trying to represent the link itself in the icon, why not symbolise what it points to; i.e. a page? This fits in better with users' thought processes when adding links and would allow the use of the same pointing hand symbol along with a page (or pages) behind it for internal links and a globe behind it for external (i.e. web) links. The chain icon is OK, but the current design is unclear and would work better if two or more links of the chain were fully visible, perhaps in a diagonal top-left to bottom-right orientation. (I'd avoid the use of words like 'link' in icons altogether as it detracts from the icon's visual immediacy and presents localisation difficulties.) -- [[User:Philoscoffee|Philoscoffee]] 07:45, 24 August 2009 (UTC) :Although I like the idea of a handcursor I think it is out if we want to stick with the gnome guidelines, that say: [http://developer.gnome.org/projects/gup/hig/1.0/icons.html "Do not include body parts in the icon. "]--[[User:Juxn|Juxn]] 11:24, 28 August 2009 (UTC) ::Whilst I think this guideline is a good general rule of thumb, here the hand cursor is not being used so much for its significance as a body part (pointing, pressing, clicking, etc.), but rather as a visual symbol of the action of navigating a link. This is consistent with the graphical cursor used by most (all?) browsers to highlight and navigate links and so will be familiar to users irrespective of culture, background etc. (which seems to be the main objection about the use of body parts in icons). -- [[User:Philoscoffee|Philoscoffee]] 10:45, 5 September 2009 (UTC) ==Signature icon== # [[File:Icontest signature 3.png]] The old icon in a new style. # [[File:Icontest signature 4.png]] Same idea, with the word "Sign". # [[File:Icontest signature 1.png]] Since the signature is used for signing discussion contributions a speechbobble might be a good icon. # [[File:Icontest signature 2.png]] Since the signature stands for a user we could use this user-symbol. # [[File:Icontest signature 5.png]] A fingerprint. Does not really work in that small size imo. # [[File:Icontest signature 6.png]] A pencil that draws a signature. ===Signature Icon II=== So here are some variations of the pencil with a line that looks more like a handwritten signature. {| |i. ||[[File: 0716 signicon 2.png]] |- |ii. ||[[File: 0716 signicon 3.png]] |- |iii. ||[[File: 0716 signicon 1.png]] |- |iv. ||[[File: 0716 signicon 4.png]] |} What do you think? Which icon is comprehensible? Other ideas? ===Comments=== *Each of the signature items II is better than the other ones. *I personally think 1 and 2 are intuitive. Although number 2 has a nice feel for English wiki's, it is hard to localize for over 260 languages. [[User:Shuhari|Shuhari]] 19:43, 13 July 2009 (UTC) *Please remember that pencil icon is planned to be used for a section edit icon in the future. So if possible, we want to reserve that image concept and not give it up for signature. (By the way, as we don't display signature icon for the article page, it is not intuitive for a user to sign for the comment.) [[User:Shuhari|Shuhari]] 17:04, 14 July 2009 (UTC) *I vote for 2. It's a clear signing icon that shows an actual signature. I'd also propose making the Signature itself in a different color instead of gray like dark blue or black, the colors that are used in signatures.--[[User:Diaa abdelmoneim|Diaa abdelmoneim]] 17:25, 14 July 2009 (UTC) * The idea of signing is uncommon, 2 is certainly better than one that we been using all along. Alternative suggestion? On old documents you sign where there is an X____. Others use colored labels <span style="background:red;border:1px solid black;">&emsp;&emsp;&emsp;</span>. You typically sign with a pen (I think outlook uses for digital signatures). Some people sign with a rubber-stamp. Painters sign in the bottom right corner of paintings. May just add a pen to number 2 or do something like this [http://www.elock.com/newsimg/pen_sign.jpg]. By the way should this in the talk space to actually allow people to use the sign icon? [[User:Dispenser|Dispenser]] 13:28, 15 July 2009 (UTC) * Yes, X___ is pretty universal, I think. Adding that (in a slightly different shade) to the first 1 or 2 would be good. The word "sign" is unrecognizable, so it doesn't quite matter. The old one, plus the X___ would probably be cleanest. [[User:M|M]] 22:27, 20 July 2009 (UTC) * I wouldn't immediately recognize any of these, but the first two are at least not misleading. 3 and 4 look like instant messaging icons, and the pen is a general "edit" symbol. A signature with and underline (like [http://commons.wikimedia.org/wiki/File:Louis-xiv-signature.jpg this]) might be more recognizable. If you go with the pen, a quill or a fountain pen might be better. --[[User:Tgr|Tgr]] 07:23, 7 August 2009 (UTC) *I vote for 1 (with 2 a close 2nd, although I tend to think the use of a word here takes away from it being an icon (even though this is a little contradictory of my views on the B/I debate for Bold/Italic icons))[[User:Bedales94|Bedales94]] 00:19, 8 August 2009 (UTC) *I think that 1 will be familiar to the veterans, although 2 may provide a subtle clue to English speakers. I never understood the need for the user icon by the account links; we might remove it entirely, certainly not enshrine it further.[[User:HereToHelp|HereToHelp]] 03:04, 10 August 2009 (UTC) **Is is possible to make a signature look like four tildes? [[User:HereToHelp|HereToHelp]] 19:18, 12 August 2009 (UTC) ***Surely that would only help people who already know that you need to use four tildes to insert a signature - and the type of people who most need the icons are those who do not know precisely this information. We aren't considering making the icon for bold three apostrophes! ;-)[[User:Bedales94|Bedales94]] 20:38, 16 August 2009 (UTC) *I think we should consider a more easily distinguishable finger-print. That, or perhaps a pencil drawing tildes? I think my issue with the scribbles is that it is either hard to localise, or might look like gibberish to another language speaker anyway. Is that a signature? A poorly done graphing icon? An invitation to have fun with bezier curves? Meanwhile, if the finger-print is indeed universal, that one symbolises imprinting your "irrefutable" identity on the post. (I think in Malaysia and Korea, at least, it is customary to purchase a stamp rather than sign?) - [[User:BalthCat|BalthCat]] 07:57, 11 August 2009 (UTC) *How about the signature text itself, instead of or as well as an icon? That should make the button’s purpose clearer, by removing the need to understand that a ‘signature’ icon refers to author identification. — [[Special:Contributions/82.36.30.34|82.36.30.34]] 02:22, 23 August 2009 (UTC) **That is a fantastic idea. There should also be a link next to it that takes the user to the preference page where he or she can edit the signature. -- [[Special:Contributions/77.1.28.154|77.1.28.154]] 10:21, 23 November 2009 (UTC) ==HereToHelp's mockup set== [[File:Usability icons.png|thumb|400px|Even if you don't like the icons, you can see the benefit of a consistent look. Try to guess which button does what.]] Hi! I think that this is becoming a little more complicated than it needs to be. I agree that links and signatures are difficult, but it should be entirely possible to have different icons, and different organizations of special characters, on different wikis. Therefore, if we take a few anglo-centric shortcuts, a fairly complete system emerges. I also think that we should be as simple as possible: the globe and chain, or even plus and minus for text size, can be illustrated more simply by literally showing the result, accompanies by a few handy letters and words. But even if you don't like the icons, I think that it is important to have a consistent feel to these icons, as I have tried to do. What do you think? [[User:HereToHelp|HereToHelp]] 17:32, 14 August 2009 (UTC) :A little late, but I like the consistency. It should be more consistent, however, in grouping; bold, italics, strike, small, big, sub and sup should be grouped together, as they are style commands. I don't know what the rectangle and the last one are supposed to mean, though... --[[Special:Contributions/86.9.119.235|86.9.119.235]] 19:02, 16 September 2009 (UTC) ::Yes, the grouping was tentative. The rectangle is an image; the arrow is a redirect. I'll do another draft; thanks for your encouragement! [[:en:User:HereToHelp|HereToHelp]] ([[:en:User talk:HereToHelp|talk]]) 20:14, 16 September 2009 (UTC) :::How about now? I really like them this time. [[:en:User:HereToHelp|HereToHelp]] ([[:en:User talk:HereToHelp|talk]]) 21:56, 16 September 2009 (UTC) HI and thank you very much for your ideas! It is a nice approach to show the result as an icon, I totally agree, that this can be much more intuitiv. But very often this works only for experienced users. For example: your reference-icon, no-wiki-sytnax-icon, redirect-icon are not comprehensible for someone who doesn't know wiki-syntax. It is very important to us to create icons that can be understood by new users. (Actually I think, that experienced users don't use the toolbar that much anyway.) I like your link-icons, but I think we can't do it like that, since we don't use underlined links in WP. But this is very close to my layout no3 and no4 (see above). Further we decided to use the GNOME Icon set as much as we can and add new Icons in that style if we need them. So basically the icons in babaco will stay the same (like in acai). We will only implement these new, improved icons: link, signature, table, indent, b and i (for engl). --[[User:Juxn|Juxn]] 13:56, 19 September 2009 (UTC) :Why should experienced editors be penalized when newcomers don't use the buttons anyway? I intended for the second row to be hidden, as it corresponds to advanced, rarely-used functionality. (How often do you create a table from scratch?) I think that anyone who is going to add a reference will have read enough of Wikipedia to know what it looks like in an article. I agree that the links may be a work in progress, but I think they work at least as well the globe and chain (which, if you aren't familiar with them from other programs, are not intuitive at all). And I think that the style - one color, thick lines, distinct shapes - is superior the GNOME. When did we decide, from on high, that we were doing GNOME? We are not GNOME, we are Wikimedia, and we have different needs and styles. [[:en:User:HereToHelp|HereToHelp]] ([[:en:User talk:HereToHelp|talk]]) 00:32, 21 September 2009 (UTC) ::I agree with you on that one. Sticking to GNOME just because "we should" is nonsense. As long as the GNOME style is good enough, we might as well use it, but where it isn't, we should do better. In fact, we'd probably be well advised to stick as close to ''Windows and Office'' style-wise as possible, since that is what 95% of people use every day. It isn't free software, so what? I'm not proposing to sell Wikipedia to Microsoft, just that we emulate the Office style, which is well-designed and, what's most important, familiar. -- [[User:JovanCormac|JovanCormac]] 11:27, 5 October 2009 (UTC) The "image" icon is really bad IMO. I don't think anybody associates an '''empty''' rectangly with a picture. -- [[User:JovanCormac|JovanCormac]] 11:27, 5 October 2009 (UTC) :Okay, but I can't think of a generic image that wouldn't be distracting, and I don't want to use more than one color. [[:en:User:HereToHelp|HereToHelp]] ([[:en:User talk:HereToHelp|talk]]) 01:10, 6 October 2009 (UTC) ::(Bump!) HereToHelp, how about adding a tree in that image icon? A black tree, I mean. [[Special:Contributions/220.137.58.80|220.137.58.80]] 13:35, 20 April 2010 (UTC) == Why not let icons be optional ? == I am not sure if there are some technical constraints that make impossible to keep icons optional. Isn't each wiki's logo optional ? (Wiktionary's logo is different from Wikipedia's logo, and the English "Wikipedia" name is not the latin language's "Vicipaedia" : compare [[:la:File:Wiki.png]] with [[:en:File:Wiki.png]]) If each logo can be kept optional, why not keep icons optional too ? Should we not let the wiki communities choose (and perhaps even design) their own icons ? It sounds strange that a matter as specific as the design of an icon should be decided at [http://blog.wikimedia.org/2009/07/17/lets-tango/ the top Wikimedia Foundation level]. [[User:Teofilo|Teofilo]] 13:34, 17 August 2009 (UTC) :I disagree. The icons should be consistent on all wikis to ensure the most minimal amount of confusion. --[[User:Mephiles602|Mephiles602]] 16:10, 17 August 2009 (UTC) ::I think there needs to be ''stylistic'' consistency (see my mock-up above), but individual wikis can, say, change some icons for a different language. (They should also be able to re-order them, as per right-to-left compatibility.) As for no icons at all, I'm not really sure. [[User:HereToHelp|HereToHelp]] 01:44, 18 August 2009 (UTC) ::Although I did not read every details, https://bugzilla.wikimedia.org/show_bug.cgi?id=20125 seems to imply that you can change the icons on your local wiki, using the local javascript there. Must be something like [[Mediawiki:Common.js]]... So I think it is a waste of time to discus this icon issue at at the global level. Any kind of standard looking set of icons will do, for default values. Detailed discussions should take place locally, on each wiki. On the other hand, '''a detailed instruction manual on how you can change icons on your local wiki''' should be provided when the new açai is no longer a beta test and becomes a standard product. [[User:Teofilo|Teofilo]] 04:17, 18 August 2009 (UTC) ts5lfwu0fe7653b0h4iwzlv4qply87m 6 408 1964 2009-07-10T14:18:29Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 409 1965 2009-07-10T14:18:44Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 410 1966 2009-07-10T14:18:54Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 411 1967 2009-07-10T14:19:04Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 412 1968 2009-07-10T14:19:15Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 413 1969 2009-07-10T14:19:25Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 417 2005 1992 2009-07-13T20:19:09Z Juxn~usabilitywiki 176 uploaded a new version of &quot;[[File:090712 babaco toolbar.pdf]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 418 2772 1998 2009-08-14T18:38:17Z Trevor Parscal (WMF) 3 uploaded a new version of &quot;[[File:090713 babaco tabs.pdf]]&quot;: Cropped it down and corrected the DPI. wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 419 2001 2009-07-13T19:57:09Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 420 2002 2009-07-13T19:57:25Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 4 422 9330 9329 2010-12-21T13:32:12Z Hydriz 2170 wikitext text/x-wiki The Wikipedia Usability Initiative is realized by a grant from the U.S.-based Stanton Foundation. The goal of this initiative is to measurably increase the usability of Wikipedia for new contributors by improving the underlying software on the basis of user behavioral studies, thereby reducing barriers to public participation. With an initial focus on English Wikipedia, eventually this research and development will be implemented across all languages and possibly to other [[:en:Wikimedia projects#Wikimedia projects|Wikimedia projects]]. qdg5zjjc6wvm6gfprayrrt8xpjj3ou3 0 424 8984 8915 2010-10-11T13:57:04Z Chatul 2523 /* Adding character attributes for symbols */ new section wikitext text/x-wiki __NEWSECTIONLINK__ *<big>To discuss the current Icons go to [[Opinion Icons]].</big> *<big>To discuss the Vector skin or anything else go to [[Talk:Prototype]].</big> == Userfriendliness in Editing is Key == Hello, I never edited wikipedia but I installed a wikimedia wiki to assess it as a note taking tool and collaborative work at work and at home. I came to the conclusion, which seems to be shared even by some among you to a certain extent, that wikimedia due to its lack of userfriendliness could not be used professionnally in the current state because editing required a significant knowledge of html (or its wikimedia subset) which can not be considered as largely widespread or be part of what some has named digital literacy. It thus required learning it, and of course if we want wikimedia to be used by anyone even for taking notes, this is learning something not related to their main business and they may not have time for that. This is why, even though I was enthused by its collaborative capability I felt it was impossible to ask people at my job to edit a wiki like they would do for a word processor document, it is already not easy to ask people to take time to document what they do, with the current userfriendliness of wikimedia, and the additionnal time required to edit, they would have drop out documenting. To be shared widely, I think wikimedia editing should be made as simple as word processors (which use is definitely part of digital literacy) and also featurewise rich enough. I think among the mandatory userfriendliness features it should be possible simply to : * choose the color of the text * choose the font * choose the size * introduce the possibility to outline with several colors * offer the possibility of foot notes * offer the possibility of comments all that in a simple maneer (agnostic to html) I don't know if all that is already included in the scope of your project but I think it is very important for people using widely wikimedia in their home or professionnal projects and therefore be sufficiently familiar with the edition possibilities that they feel no obstacle to one day editing wikipedia when they feel they can contribute. When I saw the news of this initiative I welcomed it very much, please make it really user friendly this is key (think of the market share taken by the iphone even with a very late release date compared to other phones, it mainly amounts to its user friendliness and ease of use... think about it). I read that important amount of money was dedicated to this excellent initiative. I think this is annother reason to reach for a real ease of use in order to maximize the impact of this investment and also because in general this kind of opportunity does not come twice. We support you in this well inspired initiative it is an opportunity to make the needed and decisive difference ! :Hoi, the key thing with every new application is that you appreciate what the application is about. Given that MediaWiki, the name of the software, is intended for collaborative editing, you have to look at what it is that you need as such. Several of the comments that you make are a bit bewildering. It is ok that you have to learn about what it is that the software does, MediaWiki is not a text processor, expecting all the attributes of a modern text processor may give the impression that it is a text processor. :It is possible to have different text sizes et al in Wikipedia. However it is not used that often because you are looking for a consistent look and feel. The point, MediaWiki is used professionally and teaching what is special about the software is important. This usability initiative should make many things more intuitive but it should not take away the notion that this is not text processing. Thanks, [[User:GerardM|GerardM]] 11:45, 15 June 2009 (UTC) == Still more suggestions on the edit-button bar == Hi, After playing some more with the prototype, a few more ideas occurred to me. * The Help ("cheatsheet") dropdown menu is great, but again you left off the discursive list (; and :). Perhaps you should at least mention indentation with the colon, since it's so common on Wikimedia projects? Practically every section of every Talk page has them on the English Wikipedia. * Again under the Help menu, I notice that you don't include ALT text in your example of a Figure caption. I understand that that's simpler for newcomers, but it's disappointing that we don't encourage accessibility for the visually impaired. * The Heading dropdown menu is likewise great, except that Level 1 shouldn't be listed, since it messes up the Table of Contents (see [[:en:User:Proteins/MoS_Nightmare]] for an illustration). The levels might be more intuitive for newcomers if the dropdown menu showed the levels more as they might appear in the article, e.g., with larger bolder fonts for the higher levels. (See the "What you get" column of the "Headings" section of the Help dropdown menu.) Bonus points: you should never allow the user to add a heading level that is more than one level lower than the present level, e.g., you shouldn't allow the user to add a H4 heading in the middle of an H2 section. That's a barrier to accessibility for the visually impaired and a major headache for the Manual of Style. * I would demote the boldface and italics edit buttons to the "Formatting" dropdown menu. That seems like the most natural grouping. For another thing, these two typefaces are not used that often in Wikipedia articles. Boldface is usually used once per article, in repeating the article title in the first sentence of the lead. Unless the article is being created from scratch, that sentence has usually been written already; therefore, most editors in most situations will never need the boldface button. The most common use of italics is in the inline citations (journal names), which are handled already by the citation templates. Thus, it's relatively rare that editors need to introduce italics. * Perhaps also under Formatting, you might add something for striking out text? That's also common practice on Wikipedia; for example, at FAC, one strikes objections as they are met by the nominator of the article. * Again, I would promote the "Headings" dropdown menu to the first (leftmost) position on the edit-button bar. I would discourage the use of external links by putting that one last. Lists seem less important than references (at least on Wikipedia) so you might put the three types of lists under the "Insert" dropdown menu. Hoping these new suggestions are helpful, [[User:Proteins|Proteins]] 18:27, 24 June 2009 (UTC) == Problem with the headings and lists == When you select the text <code>== Foo ==</code> and then select level three from the headings dropdown, you get <code>===== Foo =====</code> instead of the expected <code>=== Foo ===</code>. The effect of the list buttons on multi-line selections is also not what one would expect. --[[User:Tgr|Tgr]] 08:00, 26 June 2009 (UTC) == Treatment of "Headings" in editbox buttons == Thanks for making those changes, but I'm not sure that "Advanced" is descriptive enough? My main suggestion, though, is to promote the Headings dropdown menu to the main line, say next to the add image button. Also, as suggested above, you should remove the Level 1 option, or at least add safeguards. [[User:Proteins|Proteins]] 15:58, 27 June 2009 (UTC) == Footer and alerts == div#foot with license and copyright info looks much better with monobook skin. See http://www.picamatic.com/show/2009/06/27/08/39/4149639_1280x275.png for real MediaWiki site. Also, EditWarning alerts (like any other javascript alert) are very annoying and should not be used by default. --[[Special:Contributions/85.141.235.251|85.141.235.251]] 16:50, 27 June 2009 (UTC) == EditWarning should be quiet after undo == The EditWarning extension is great -- warning that if you leave, your changes will be lost. However, the following use case should be fixed: # Edit a page # Type an "X" # Type ctrl-Z to undo # Click any link to leave the edit page Currently, EditWarning will pop up an alert. It should not, because nothing has changed. (Probably you are just keeping a "dirty" bit that indicates whether the edit box has been touched.) The simplest way to do this, in addition to your "dirty" bit, is to store the original wikitext when editing begins, and compare it to the current wikitext when the user tries to leave (window.onbeforeunload). I've been doing this in my own EditWarning-type extension and it works great, even for large pages. This is a small change, but if you suppress these unnecessary warnings, that is definitely good '''usability'''! --[[Special:Contributions/4.79.245.132|4.79.245.132]] 20:38, 30 June 2009 (UTC) ::I think this is an overhead, and there were no big benefit when this function would be implemented. How often do you think user do the described action above. For me too seldom. --[[Special:Contributions/129.27.129.83|129.27.129.83]] 10:21, 1 July 2009 (UTC) :::This has been fixed; EditWarning now only warns if the contents of the edit box are different from the initial contents. --[[User:Catrope|Catrope]] 17:40, 9 August 2009 (UTC) == LaTeX next to Special Characters == Hi, <br/> like the Special Characters Menu, there should be a similar menu for Math/LaTeX markup as used by [http://www.mediawiki.org/wiki/Manual:Enable_TeX texvc] and [http://www.mediawiki.org/wiki/Extension:Blahtex BlahTex]. The supported LaTeX commands should be grouped by their use ("greek symbols", "arrows", "integrals", etc.). See [[:en:Help:Displaying a formula|Help:Displaying a formula]] for a reference of commands. &mdash; [[User:MovGP0|MovGP0]] 21:43, 30 June 2009 (UTC) :This would be very useful. If it is not possible, please bring at least the "math button" again... in math texts, usually there are more math tags than paragraphs (!) It is bad idea to type < m a t h > every time! [[Special:Contributions/143.107.45.43|143.107.45.43]] 12:33, 15 September 2009 (UTC) Even better implement something like this extension that no longer seems to be supported (tried on V1.15.x Mediawiki) but had a good user-friendly approach: http://www.mediawiki.org/wiki/Extension:TeX_Editor ==More suggestions for the edit page== At my suggestion, [[:en:User:Cacycle]] recently added a feature to wikEd which you might consider here. The feature collapses references and long templates into placeholders, which reveal their contents when clicked (my original idea) or onmouseover (Cacycle's implementation). I also suggested tables, although wikEd doesn't do that as yet. The advantages of this approach are several. First, references and templates such as infoboxes/navboxes are unfamiliar in syntax and usually stretch over many lines, sometimes even filling the visible edit box. This is particularly grievous at the beginning of the article, where long infoboxes are common and where most newcomers will first try to edit. By collapsing each of these long elements into a small labelled placeholder, you make the text ''far'' more readable, much closer to the article as read. In effect, this approach distinguishes between simple wiki-markup (links, section headings, italics) and complex wiki-markup (references, templates, tables). The simple markup is a much smaller "perturbation" of the normal article and much easier to learn. You might consider other innovations of wikEd for usability as well, such as its icons, its color coding, its find/replace mechanisms, its automated fixing routines, etc.. It's well-liked by many of Wikipedia's most productive editors. I've listed a few more ideas for wikEd on [[:en:User talk:Cacycle/wikEd]], which you might also consider. [[User:Proteins|Proteins]] 01:02, 2 July 2009 (UTC) PS. A third warning, please listen: Including "level 1" in the Heading dropdown menu is an invitation to disaster on a massive scale. If this new skin succeeds in recruiting thousands of beginning editors to Wikipedia, as we all hope, they will naturally choose level 1 for their first heading, right? I hope you know that '''level-1 headings are never appropriate on the English Wikipedia''', and I suspect most other languages and Wikimedia projects. Even if you ignore all my other suggestions here and above, please pay attention to this one. :The usability team is listening. Great point about level 1 heading is not appropriate for Wikipedia. How about external MediaWiki users though? We may need to find a way to customize for Wikipedia and MW project wikis. <br />P.S. Will check out content folding of wikiEd. Thanks for the pointer. --[[User:Shuhari|Shuhari]] 06:39, 2 July 2009 (UTC) ::Level 1 headings translate to h1 tags, which are normally only used to denote the title of the article. It is unlikely that many external MediaWiki sites would like to use multiple h1 tags, so IMO level 1 should be left out by default. If it is possible to customize the toolbar, the minority of wikis using L1 tags should be the ones to do that. --[[User:Tgr|Tgr]] 20:51, 4 July 2009 (UTC) ==Line breaks== For complex (multiline) inserts like ''gallery'' or ''table'' implicit line breaks can help to recognize easily what has been inserted with one click. After all manually inserted galeries or tables markup seldom flow inline with other text. [[User:Erik Zachte|Erik Zachte]] 03:39, 2 July 2009 (UTC) <nowiki> The following candy bars have a good taste to price ratio. <gallery> File:Example.jpg|Caption1 File:Example.jpg|Caption2 </gallery>Of these the following also have a high tooth decay factor. {| class="wikitable" border="1" |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |}Consume at own risk. </nowiki> Better <nowiki> The following candy bars have a good taste to price ratio. <gallery> File:Example.jpg|Caption1 File:Example.jpg|Caption2 </gallery> Of these the following also have a high tooth decay factor. {| class="wikitable" border="1" |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |} Consume at own risk. </nowiki> :A simple yet powerful way to increase intuitiveness. --[[User:Shuhari|Shuhari]] 06:44, 2 July 2009 (UTC) ::Fixed, should now work on prototype wikis. Fix not tested on IE yet. --[[User:Catrope|Catrope]] 16:22, 10 August 2009 (UTC) == Undo and redo == Could u please create an undo and redo button in the edit box? It works automatically on Firefox with ctrl-z and ctrl-y but most novice users don't know the shortcuts. Thank you.--[[User:Diaa abdelmoneim|Diaa abdelmoneim]] 10:24, 2 July 2009 (UTC) == Most block level elements should add a new line == I'll try to explain by example. Suppose I'm writing some text... <pre> Type, type and want to make next text bold '''click''' (Seems OK). And now I'm typing some more text and want to make a list... Go to a new line * OK. And now... click to go to next item?* wrong - same line </pre> Further more if I'm inside a line (not at the end) that has a list character, clicking on the list button should make the list disappear (this is would be similar to how it works office editors). But this could be a little tricky so another button for adding new list item should be added to avoid confusion. <pre> OK. Now I want to insert a table... Well this won't work:{| class="wikitable" border="1" |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |} </pre> BTW. I have this experimental table adder which you might use (I think I won't be able to finish this soon). It's not much but I guess it's better then just pushing the code straight away to the editing area (there is a simple, light editor that adds/removes new columns and rows and inserts code after finishing). I'm almost sure it worked in all modern browsers + IE 6, but it was quite a long time since I worked on it so I won't give my head on it. Some comments are in Polish so if you have a problem figuring something out just let me know. Anyway the code is here: [http://nux.w.of.pl/download/wiki/wp_ted_0.0.2.zip wp_ted_0.0.2.zip] a general class used for JS-pop messages (not in a new window): [http://nux.w.of.pl/download/wiki/sftJSmsg_0.0.5.zip]. The script adds a button above the textarea. Obviously it wasn't tested on new Vector skin (it was made for monobook), but I think it will work for it too. --[[User:Nux|Nux]] 22:18, 2 July 2009 (UTC) == A few thoughts on the enhanced edit toolbar == First off, thanks for all the effort as it is looking quite nice. A few thoughts... is it possible to reverse the "internal" and "external" links buttons, as per the standard tools? (While it is only a minor inconvenience remembering the order, I don't see an actual need to swap them - and having the external link button first might just inspire people to ''add'' them!) Thoughts? --[[User:Ckatz|Ckatz]] 02:50, 3 July 2009 (UTC) == Signature help == On the enhanced edit toolbar -> Help -> Discussion, it would be useful to add a simple example like [[w:Wikipedia:Talk_pages#Example:]], or you'll see things like [http://www.frontieredigitali.net/index.php?title=Discussione:Libert%C3%A0_di_copia_e_di_accesso_privati_alle_opere_finanziate_con_soldi_pubblici&oldid=11458 this]. Thanks, [[User:Nemo bis|Nemo]] 07:26, 30 July 2009 (UTC) P.s.: Very odd not to have the sign button here on namespace 0. == Custom buttons and icons == Hi. So I'm trying to figure out how too add custom icons. So far I figured out that I have to do it onload and I can use label (instead of labelMsg) to use text (not read it from MediaWiki). But the problem is I cannot add new icons - as seems they have to be in <tt>.../extensions/UsabilityInitiative/EditToolbar/images/</tt>, which is not very useful for custom buttons. So is there a way to add an icon under a specific address e.g. [http://commons.wikimedia.org/w/thumb.php?f=Format-text-strikethrough.svg&width=22px this one]? I would also like to run a specific js-action (function) instead of defining some action (something like onclick="wp_sk.run()"). Regards, [[User:Nux|Nux]] 18:53, 3 August 2009 (UTC). :Maybe you can browse to the top directory by ../../.. etc.--[[User:Liangent|Liangent]] 11:07, 11 August 2009 (UTC) :: Might work for some, but thumb generating only works for SVG and only for local files. The rest needs different domain... I'm waiting for [https://bugzilla.wikimedia.org/show_bug.cgi?id=20125 bug 20125] to be resolved, and in the mean time I'm currently using [http://pl.wikipedia.org/w/index.php?title=Wikipedysta:Nux/nuxedtoolkit.js&uselang=en my script] for adding buttons. --[[User:Nux|Nux]] 20:44, 11 August 2009 (UTC) ::: You can use [[Special:FilePath]] --[[User:Liangent|Liangent]] 05:20, 14 August 2009 (UTC) :::: I now the path, but there is no way to use it. --[[User:Nux|Nux]] 18:52, 25 September 2009 (UTC) == Headings in edit window == Under the advanced drop down, there's an option to specify headings. The headings start at one and end at five. I see two problems with that. The first, HTML lets you go to a sixth level heading (although articles rarely go beyond the fourth). The second, Heading 1 is generally reserved for the title of the document, not for sections; for editors unaware of this, we might see some header problems in terms of the English Wikipedia's WP:LAYOUT. [[User:ChyranandChloe|ChyranandChloe]] 04:46, 4 August 2009 (UTC) :Header 1 has been removed. --[[User:Catrope|Catrope]] 18:29, 9 August 2009 (UTC) == Customizing the toolbar == The old toolbar made it (relatively) easy to add new buttons using user/site JS with the <var>mwCustomEditButtons</var> JS global variable. Will the new toolbar have anything like that? I'd like to rewrite my script - [[w:en:User:Mr.Z-man/refToolbar]] to use the new toolbar, but there's no easy way to do it, and the HTML of the toolbar seems to be changing in an incompatible way with the next release. [[User:Mr.Z-man|Mr.Z-man]] 23:35, 5 August 2009 (UTC) :Could some kind of default citing script be added, either something like Mr. Z-man's or like [[w:en:User:Odie5533/SnipManager]]. Having a default method of citing sources would make it much easier for anonymous and new editors.[[User:Smallman12q|Smallman12q]] 00:29, 7 August 2009 (UTC) ::Someone has reported it to MediaZilla. See [[MediaZilla:20125]]. --[[User:PhiLiP|PhiLiP]] 20:33, 8 August 2009 (UTC) :Kind of found a way to do it, I did a google search and found this: http://en.wikisource.org/wiki/User:Alex_brollo/vector.js?match=pl :I just kind of modified his code, but the bottom part of the code seems to be of no use for me as it doesn't seem to display under my current settings. It's so hard to find info on customizing the toolbar and vector it seems! While i'm here I should also ask, is there a way to make the toolbar "advanced" section load on default without the user clicking it first? and why is there no signature button on this toolbar? Weird!--[[User:Bluesoju|Bluesoju]] 10:39, 15 June 2010 (UTC) == Vietnamese characters == Although the new toolbar features a "Latin" section in the Special Characters pane, it lacks most of the characters required for typing in Vietnamese. The Vietnamese Wikipedia has used the <code><nowiki><charinsert></nowiki></code> extension inside [[:vi:MediaWiki:Edittools|MediaWiki:Edittools]] to provide access to these characters, for those without access to an IME. (We also provide a JavaScript-based IME, but browser support varies, so the character palette is still necessary.) Would it be possible to add a separate section for Vietnamese (similar to the "IPA" section)? It would only be necessary on Vietnamese-language wikis. Here's the full list of characters: :À Á Ả à Ạ :a à á ả ã ạ : Ầ Ấ Ẩ Ẫ Ậ :â ầ ấ ẩ ẫ ậ :Ă Ằ Ắ Ẳ Ẵ Ặ :ă ằ ắ ẳ ẵ ặ :Đ đ ₫ :E È É Ẻ Ẽ Ẹ :e è é ẻ ẽ ẹ :Ê Ề Ế Ể Ễ Ệ :ê ề ế ể ễ ệ :I Ì Í Ỉ Ĩ Ị :i ì í ỉ ĩ ị :O Ò Ó Ỏ Õ Ọ :o ò ó ỏ õ ọ :Ô Ồ Ố Ổ Ỗ Ộ :ô ồ ố ổ ỗ ộ :Ơ Ờ Ớ Ở Ỡ Ợ :ơ ờ ớ ở ỡ ợ :U Ù Ú Ủ Ũ Ụ :u ù ú ủ ũ ụ :Ư Ừ Ứ Ử Ữ Ự :ư ừ ứ ử ữ ự :Y Ỳ Ý Ỷ Ỹ Ỵ :y ỳ ý ỷ ỹ ỵ &nbsp;&ndash;&nbsp;[[User:Mxn|Minh Nguyễn]] <small>([[User talk:Mxn|talk]], [[Special:Contributions/Mxn|contribs]])</small> 05:43, 7 August 2009 (UTC) :I've added the entire 1E00-1EFF Unicode range as a separate "Latin extended" set. All of the characters mentioned above should be in either Latin or Latin extended. --[[Special:Contributions/83.119.125.27|83.119.125.27]] 21:31, 9 August 2009 (UTC) ::While that's nice, it's not really useful for anyone, because the characters users are looking for will be buried in a list of other languages' characters. It would be very nice to have a set of system messages that define custom character palettes, similar to the way gadgets can be defined using [[MediaWiki:Gadgets-definition]] and friends. &ndash;&nbsp;[[User:Mxn|Minh Nguyễn]] <small>([[User talk:Mxn|talk]], [[Special:Contributions/Mxn|contribs]])</small> 07:10, 3 October 2009 (UTC) ===...and just about any other set of characters=== I'm noticing that some Cyrillic letters are missing (for example È è Ѝ ѝ). This new interactive toolbar should be easily modified on all the individual projects when it gets deployed, right? Will it be possible to create and customize new subsets of characters on, for example, an advanced wiki-markup set. And will MediaWiki:Edittools be obsolete after this toolbar? --[[User:Brainmachine|Brainmachine]] 11:30, 7 August 2009 (UTC) :Yes, the special characters section will be customizable; projects can add, remove and alter buttons and sections as they wish. And yes, MediaWiki:Edittools will hopefully be obsolete when the toolbar has matured. --[[Special:Contributions/83.119.125.27|83.119.125.27]] 19:50, 9 August 2009 (UTC) ===…and hebrew [[w:niqqud|niqqud]] and [[w:cantillation|cantillation]]=== <span title="niqqud"> '''niqqud''': <span title="qamats"><span style="font-size:160%"> <charinsert>ָ</charinsert></span>◌</span> · <span title="patah"><span style="font-size:160%"> <charinsert>ַ</charinsert></span>◌</span> · <span title="tsere"><span style="font-size:160%"> <charinsert>ֵ</charinsert></span>◌</span> · <span title="segol"><span style="font-size:160%"> <charinsert>ֶ</charinsert></span>◌</span> · <span title="hiriq"><span style="font-size:160%"> <charinsert>ִ</charinsert></span>◌</span> · <span title="holam"><span style="font-size:160%"> <charinsert>ֹ</charinsert></span>◌</span> · <span title="qubuts"><span style="font-size:160%"> <charinsert>ֻ</charinsert></span>◌</span> · <span title="sheva"><span style="font-size:160%"> <charinsert>ְ</charinsert></span>◌</span> · <span title="hatef qamats"><span style="font-size:160%"> <charinsert>ֳ</charinsert></span>◌</span> · <span title="hatef patah"><span style="font-size:160%"> <charinsert>ֲ</charinsert></span>◌</span> · <span title="hatef segol"><span style="font-size:160%"> <charinsert>ֱ</charinsert></span>◌</span> ··· </span> <span title="cantillation"> '''cantillation:''' <span title="dagesh"><span style="font-size:160%"> <charinsert>ּ</charinsert></span>◌</span> · <span title="shin dot"><span style="font-size:160%"> <charinsert>ׁ</charinsert></span>◌</span> · <span title="sin dot"><span style="font-size:160%"> <charinsert>ׂ</charinsert></span>◌</span> · <span title="rafe"><span style="font-size:160%"> <charinsert>ֿ</charinsert></span>◌</span> · <span title="meteg"><span style="font-size:160%"> <charinsert>ֽ</charinsert></span>◌</span> ··· etc. </span> --[[User:Joystick|Joystick]] 13:43, 7 August 2009 (UTC) :Thanks. We had these and a lot of other Hebrew characters lying around, but we didn't know about the ◌ trick yet. I've added a bunch of Hebrew chars with ◌s to the toolbar. --[[Special:Contributions/83.119.125.27|83.119.125.27]] 21:31, 9 August 2009 (UTC) ==Special characters on Search page== I suggest you also take into account the special characters in the search box. More or less as in the picture below: [[File:Usability.search.png|600px]] --[[User:Joystick|Joystick]] 14:21, 7 August 2009 (UTC) ==Possible increase in icon spacing on Toolbar== I have not had the opportunity to view the toolbar in anything other than IE8, but I find the icons a little close together - just a tiny bit more space (laterally) would give them a more pleasing look. I am not suggesting wasting lots of screen real-estate, and am aware that on small screens they may will run into difficulties, but a tiny tweak would help (perhaps even 2 pixels per icon)[[User:Bedales94|Bedales94]] 00:27, 8 August 2009 (UTC) :They are '''already''' wasting too much space. This indicates that there needs to be more than one mode for the toolbar. I will suggest so below. - [[User:BalthCat|BalthCat]] 07:27, 11 August 2009 (UTC) == "Script is too slow" error message == With Firefox, when using the new beta on edit pages. See screenshot below : [[File:Prototype test on Commons 004 script is too slow.jpg|500px|Screenshot]] [[User:Teofilo|Teofilo]] 05:26, 8 August 2009 (UTC) :Translation: ''A script on this page may be busy or not responding. You can end it now or wait to see if it finishes.'' [[User:HereToHelp|HereToHelp]] 02:28, 10 August 2009 (UTC) :: While they may be not your primary target audience, keep in mind that a huge percentage of the internet users are using 10 years old, or older, personal computers, with little memory and small and slow hard disks, some even with likewise old operating systems. Internet connections may be slow and expensive. Having tried all these new JavaScripts on such dangling a system (with excellent internet connections, though) I tend to say that they are likely too slow to be useful except for owners of rather new hardware, that many third world users will likely not get until its again 10+ years old, and completely useless for us. --[[User:Purodha|Purodha]] 10:40, 12 August 2009 (UTC) ::: Also when I see on [[Releases/Acai/Compatibility_Matrix]] that the new prototype is supposed to be compatible with Internet Explorer 6 makes me a bit skeptical. Perhaps the new prototype is compatible with Internet Explorer 6 on a brand new smart and fast computer, but I guess that most of the people who use Internet Explorer 6 now are people with an old slow computer for which Internet Explorer 7 or 8 are not available. So in fact the so-called "browser compatibility" remains a fiction as long as you do not conduct "older computer compatibility testing". [[User:Teofilo|Teofilo]] 09:19, 16 August 2009 (UTC) == LanguageConverter markups == I'd like to advise some language converter markups. Which are widely used by some wikis like Chinese Wikipedia. Here is a complete list of these markups: # '''All text convert(add rules into conversion table) but hide parsed result'''<p>Input: <code><nowiki>-{H|zh-cn:zh-cn content; zh-tw:zh-tw content;}-; '''zh-tw content'''</nowiki></code><p>Output (zh-cn): ; '''zh-cn content'''<p>Output (zh-tw): ; '''zh-tw content''' # '''All text convert(add rules into conversion table) and display parsed result'''<p>Input: <code><nowiki>-{A|zh-cn:zh-cn content; zh-tw:zh-tw content;}-; '''zh-tw content'''</nowiki></code><p>Output (zh-cn): zh-cn content; '''zh-cn content'''<p>Output (zh-tw): zh-tw content; '''zh-tw content''' # '''Single convert'''<p>Input: <code><nowiki>-{zh-cn:zh-cn content; zh-tw:zh-tw content;}-; '''zh-tw content'''</nowiki></code><p>Output (zh-cn): zh-cn content; '''zh-tw content'''<p>Output (zh-tw): zh-tw content; '''zh-tw content''' # '''Title convert'''<p>Input: <code>-{T|zh-cn:zh-cn title; zh-tw:zh-tw title;}-</code><p>Output: Use the specified title to replace the original page title # '''Raw content'''<p>Input: <code>-{R|zh-cn:raw content; zh-tw:raw content;}-</code><p>Output: zh-cn:raw content; zh-tw:raw content; # '''Remove rules from conversion table'''<p>Input: <code><nowiki>-{H|zh-cn:zh-cn content; zh-tw:zh-tw content;}-'''zh-tw content; -{-|zh-cn:zh-cn content; zh-tw:zh-tw content;}-zh-tw content'''</nowiki></code><p>Output (zh-cn): '''zh-cn content; zh-tw content'''<p>Output (zh-tw): '''zh-tw content; zh-tw content''' # '''Discriptions'''<p>Input: <code>-{D|zh-cn:zh-cn content;zh-tw:zh-tw content}-</code><p>Output: Chinese (China): zh-cn content; Chinese (Taiwan): zh-tw content; *--[[User:PhiLiP|PhiLiP]] 20:27, 8 August 2009 (UTC) :Maybe only on wikis with Language Converter enabled? Or use php-generated javascript? --[[User:Liangent|Liangent]] 17:44, 10 August 2009 (UTC) == ''Most Used Special Characters'' Section Needed, Everything Else Awesome :) == The Special Characters in the edit toolbar are the only nuisance I can see in the German prototype. The problem is: there is no section with the most used special characters like there is currently at the bottom of the German WP edit pages. Just please add a section "mostly used" ("meistgenutzt") with the already established selection of most often needed secial characters: ''<nowiki> Ä ä Ö ö ß Ü ü • „“ ’ ‚‘ “” ‘’ «» ‹› »« ›‹ – • + − · × ÷ ≈ ≠ ± ≤ ≥ ² ³ ½ † # * ‰ § € ¢ £ ¥ $ ¿ ¡ ∞ ‣ • 〈〉 … → ↔ • &nbsp; [[]] | {{}} ~~~~ • ° ′ ″</nowiki>'' The same should be done for the other language versions, repectively. Other than that, the Prototype is simply awesome :). The edit toolbar symbols are just in the right order, the header with the search bar is much better, the short syntax help is simply wonderful and the new look/stylsheet looks gorgeous :) :). Also great is that the basic functionality still works with Javascript comepletely disabled :). Many of the [[Babaco Designs|Babaco proposals]] are awesome as well :). It's great to see that WP is continually improving usability and accessibility and flow of reading and editing and searching articles :). –[[Special:Contributions/91.14.197.76|91.14.197.76]] 14:34, 9 August 2009 (UTC) :The problem is that "most used" differs per wiki. On dewiki, ÄäÖöÜü would indeed be among the most used ones, but the folks on frwiki don't care about Umläute and want to see ÀàÁáÂâÇçÈèÉéÊê... instead. For this reason, it's best that such "most used" sections be added through local customization. --[[User:Catrope|Catrope]] 18:32, 9 August 2009 (UTC) ::Perhaps "selected" or "recommended" would be a better term. [[User:HereToHelp|HereToHelp]] 02:40, 10 August 2009 (UTC) ::Catrope, Yeah, exaclty such local lists of mostly used special characters, like they already exist e.g. in the German WP, I was referring to (yes, that "91.14.197.76" was me before I got me a handy unified login account today, really useful thing, that :D :) :)). As I said already, other than that I love the beta and I really do appreciate your usability initiative and the thought and passion you all put behind it :). Just want to contribute my two cents :D :).--[[User:Sternenmeer|Sternenmeer]] 14:35, 29 August 2009 (UTC) == Advanced editing functionality == (Discalimer: these ideas might be a little early in the process.) I think that the collapsible toolbar has great potential to make the default interface very simple while being extremely versatile and powerful. Someone mentioned wikiEd above and I think that we can excerpt some of its more commonly useful features for the main interface. Color coding, for example, promises to make the editing window more comprehensible to neophytes and veterans alike. I'd also like to see some way to hide references in the editing window, since in well-sourced articles they can make it very difficult to work with the flow of the text. Speaking of which, refTools is another handy gadget that could be integrated into the default editing space. And as for hiding, the list of pages transcended onto the current page is rather cumbersome. This should be hidden, or removed outright (it would improve load speeds and lessen server load). Does anyone think these are good ideas? [[User:HereToHelp|HereToHelp]] 02:39, 10 August 2009 (UTC) == Wasted space == The edit bar is enormous, like a child's editbar. The icons much larger than I need them to be. I thought perhaps that this change was because my laptop is not a 20" monitor, like is more and more the standard, but then the Advanced tab opens a new bloated line below rather than utilising the four inches to the right of "Help". It's bloated and ugly as far as I'm concerned. I'm against this sort of screen-creep. Someone above even said the icons need to be spaced out more. So this signals to me that more than one theme of editbar should be standard, as I cannot even conceive of how it needs /more/ space. I also don't want the toolbar to baby me. I know what ^ and V and + and - mean beside a font. (Also, there is some suggestion that chosing from the Heading drop box will change the toolbar row, rather than insert the heading code.) - [[User:BalthCat|BalthCat]] 07:36, 11 August 2009 (UTC) ==Lady Aleena's list of missing buttons== [[Talk:Prototype#Missing_wiki_markup]] :To which I add: strike - [[User:BalthCat|BalthCat]] 08:24, 11 August 2009 (UTC) ::I suggest strike, too. (Big is imho unnecessary) --[[User:Purodha|Purodha]] 11:43, 12 August 2009 (UTC) == Backup? == What about a button that stores a copy of a page elsewhere for you to work with. For example, it could copy to /User:BalthCat/Backups/Article Title, and then include the author data at the very end of the backup? Not sure if that is "safe" considering license issues, but it's an interesting idea. Saves the cut/paste/create/save/etc. - [[User:BalthCat|BalthCat]] 08:27, 11 August 2009 (UTC) : I suggest using the [[:mw:Extension:Draft|Draft Extension]] for this purpose, and deploy it on each wmf wiki. I tested it locally, and found it saving some 2/3 of of all page versions, which is quite some disk space, backup file size, etc. when projected to Wikipedia; plus nicely giving me a secure feeling that I may not loose much on the next power loss. --[[User:Purodha|Purodha]] 10:55, 12 August 2009 (UTC) == Position of "insert" button list == [[File:Edit toolbar J8C1.png|thumb|right|Sreenshot, cropped, with marker]] There are some buttons which, when the "advanced" edit toolbar view is selected, should be shown following the "insert" label, and not be positioned at the same places as without this selection. Maybe, the move should be in the opposite direction, i.e. both the label, and the additional buttons behind it could be placed where the unlabelled buttons are in non-"advanced" view. I suggest to add labels to all groups, including the two ones remaining in the screen shot shown here, when "advanced" view is selected. --[[User:Purodha|Purodha]] 11:44, 12 August 2009 (UTC) == Special character lists == I suggest adding two (sticky) buttons formatting the lists of special characters: # adjust block height so as to exactly accomodate all special character buttons and not waste space (i.e. shrink or expand verically as needed) # where applicable, arrange buttons in a keyboard-like fashion. E.g. for Cyrillic characters, I am faster finding the right ones when they are presented resembling a keyboard, like Macintosh has it, than in the order in which they are pesently presented. --[[User:Purodha|Purodha]] 11:10, 12 August 2009 (UTC) == "Wrapping" buttons == I use the "signature" button most, and self-made quoting buttons like "" «» „“ „” ¡! ¿? &lt;code>&lt;/code>, etc., second most. Note that, typographical correct quotes are extremely rarely found on computer keyboards. As a consequence, many use "'s, and there is a considerable amount of editing owed to correcting quotes, and dashes. --[[User:Purodha|Purodha]] 11:10, 12 August 2009 (UTC) == Colons in Edittoolbar labels == [[File:Edit toolbar J8C1.png|thumb|right|Sreenshot, cropped, with colons following labels]] There are some labels in the new edit toolbar that imho should be followed by colons, at least when translated ;-) see screenshot. Maybe, it is a matter of style, and colons are not needed in English. I admit that the colon-less style looks appealing to me. --[[User:Purodha|Purodha]] 11:10, 12 August 2009 (UTC)--[[User:Purodha|Purodha]] 11:42, 12 August 2009 (UTC) == Can I opt out ? == Because of what I said above ([[#"Script_is_too_slow" error message]]), I would like to opt out. I have successfully set the appearance option to "monobook" in [[Special:Preferences]]. However, I don't see how I can remove the new toolbar and instead use the older more simple toolbar here on http://usability.wikimedia.org . [[User:Teofilo|Teofilo]] 09:07, 16 August 2009 (UTC) :You can't do that on this particular website, but on all other project wikis, you can do so by pressing the "Leave Beta" button. --[[User:Mephiles602|Mephiles602]] 16:12, 17 August 2009 (UTC) ::Hello, ::Well, not exactly "all other project wikis". http://strategy.wikimedia.org has no "leave Beta" button. My question concerns not only the present but also the future, after açai is no longer a "beta test", but has become a standard product : when that happens, the "leave beta" link will be removed, won't it ? :: ::In the "edit" section of [[Special:Preferences]], I am left with no other choice than enabling or disabling "edit toolbar" (which means here or on http://strategy.wikimedia.org , enabling açai or disabling açai). Why not create another line in the "edit" section of [[Special:Preferences]] with "enable old and simple edit toolbar" ? [[User:Teofilo|Teofilo]] 04:01, 18 August 2009 (UTC) :::I am sorry that you cannot switch back to old and simple edit toolbar. We are looking into a way to provide preference for it. Bug [https://bugzilla.wikimedia.org/show_bug.cgi?id=20361 20361] [[User:Shuhari|Shuhari]] 06:46, 23 August 2009 (UTC) :::: You can get rid of the toolbar entirely. Edit your Vector.css (My Preferences / Appearance / Custom CSS) and add this :::::.wikiEditor-ui-toolbar {display: none;} :::: Make sure you follow the directions about refreshing the browser cache after you save the CSS file. Unfortunately, you can't restore the old toolbar other than by leaving the beta. Ideally they would have used a different class-name for the new toolbar with the default for it being display:none. Then you could switch to the old or new toolbar as desired. [[User:Marc Kupper|Marc Kupper]] 00:32, 21 September 2009 (UTC) == Toolbar causes Firefox to lose changes in editbox during back/forward == I am used to walking through browsing history using back/forward when editing (e.g. to check the current article state), which (at least in Firefox) is usually not a problem, since the form contents is kept. However, when the advanced toolbar is enabled, Firefox loses the editbox contents and every time restores it to the original state, losing all my changes. I know this is not a bug on UsabilityExtension’s part, but in Firefox, but this behavior is a showstopper for me nonetheless; the advanced toolbar had to go. (OK, as an experienced editor, I almost did not use the toolbar anyway…) For the more technically inclined: the problem seems to be triggered by wrapping the textarea to some divs (using jQuery’s wrap, which clones it in the process), ''and'' adding an input above it (in this case, the SELECT for Heading). I commented about the problem at https://bugzilla.mozilla.org/show_bug.cgi?id=209292#c22 Maybe if the toolbar did not use the SELECT… --[[User:Mormegil|Mormegil]] 15:22, 20 August 2009 (UTC) : It seems the toolbar has been tweaked so there is no SELECT anymore! Perfect, I can use it once again now! --[[User:Mormegil|Mormegil]] 11:28, 9 September 2009 (UTC) == Comparing entries in different languages == I would suggest adding a notation for entries in different languages, e.g., wordcount, categories, completeness, stubness etc. == Template tab == As mentioned [[Talk:Prototype#I_want_a_better_damn_template_system|here]], it would be VERY nice if we godt such a template tab. The tab should be customizable, so that wikis could enter their templates. I dont know if that could be possible, but i hope so! --[[:da:Bruger:Masz|Masz]] 16:07, 8 September 2009 (UTC) :Definitely! It took me ages (as a not welcomed newbie) to find the WP page listing possible templates! What I want: A structure drop-down menu containing frequently used templates, plus a link somewhere to [[:en:WP:TEMP]] page for more information. [[User:Nageh|Nageh]] 20:15, 6 February 2010 (UTC) == Is this skin designed for rtl (right to left) languages? == I change my language to pesrsian (fa/ فارسی) but it seems skin is not designed for right to left languages. (sidebar doesn't go to right,etc) :Use the Prototype wiki to find the answer to your question. --[[User:Mephiles602|Mephiles602]] 15:36, 1 October 2009 (UTC) == Integrating the Wikisaurus project in the editbox == I had the proposition to integrate the Wikisaurus project (http://en.wiktionary.org/wiki/Wiktionary:Wikisaurus) that i seem is really interesting in the editbox of Wikipedia, it could be by a button or function to turn it on off, for some people it is a very useful application, because its saves them time to write an article, also OpenOffice has this function, and brandnew Google Wave also implements this function, why not using a existing project?? --[[User:Subcomandante84|Subcomandante84]]11:50, 13 October 2009 (UTC) I would also do the proposal to create a new Logo for the project, Thesaurus has a Dinosaurus, so i just thinked about a Dinosaurus in the form of a W and found the Pterosaurus, the logo is just a dummy for the moment, but anyone can feel free to modify or redesign it. [[File:Wikisaurus-proposal.svg]] --[[User:Subcomandante84|Subcomandante84]]19:51, 20 October 2009 (UTC) == Add a word counter to the editbox == I would also propose to add a word counter to the editbox and display the number of words written in the article beneath it, so articles could also been classified by the number ofs it words, articles with 3000 words, articles with 5000 words, and so on... --[[User:Subcomandante84|Subcomandante84]]14:19, 27 October 2009 (UTC) == A site similar to "Get satisfaction site" from Mozilla == I found the site "Get satisfaction" from Mozilla http://getsatisfaction.com/mozilla/topics, and i found that a really good example for how you could improve suggestion scheme, it is very simple, has a nice front end, and the ideas are voted by the community so the best idea is integrated. I found that a really interesting project which is thinking in the same direction then Wikipedia is thinking, to evolute the web, and make a product for the customer and for the community --[[User:Subcomandante84|Subcomandante84]]18:22, 27 October 2009 (UTC) == Make the top bar and the menu always visible == It is a bit unhandy to scroll upwards every time you want to see the bar. Perhaps it would be better to get the article into an iframe or something like that so we have a scrollbar on the right of it and always see the controls. Or the menu and the top bar could be initially hidden and show up only when the mouse pointer gets over them, but this would create big problems with console browsers like Links. : better: change css for #panel to positon:fixed [[Special:Contributions/84.114.177.169|84.114.177.169]] 04:18, 20 November 2009 (UTC) == Paste issue == While I applaud the WMF usability initiative, can they please give us a feature to paste formatted text as unformatted? It's incredibly frustrating to try to copy from another source into the article text box and find that it's carried over formatting. Certainly this is getting in the way of me clearing the admin backlog on certain areas. - [[User:Tbsdy lives|Tbsdy lives]] 03:03, 5 February 2010 (UTC) :Agreed. I often make piped links the old-school way, by copying the article name into the edit window. Now I wind up with something like big and ugly (although once you save the source code loses the formatting). Still very annoying; there's no reason to (manually) format the text of source code. [[:en:User:HereToHelp|HereToHelp]] ([[:en:User talk:HereToHelp|talk]]) 19:19, 6 February 2010 (UTC) :The usability tech team is working on several issues introduced by the release on February 4th. One of the issues is experimental features kept turned on even if you leave the beta. [https://bugzilla.wikimedia.org/show_bug.cgi?id=22402 Bug 22402] We should have a fix in place soon, but until then you can restore your old toolbar by going into preferences and disable experimental features under "Editing" tab. [[User:Shuhari|Shuhari]] 19:28, 6 February 2010 (UTC) The issue of not being able to opt-out from the beta completely has been resolved. <s>[https://bugzilla.wikimedia.org/show_bug.cgi?id=22402 Bug 22402]</s> [[User:Shuhari|Shuhari]] 20:39, 6 February 2010 (UTC) == Inserting wikicode into the textarea (iframe) == I've written a script which inputs text into the textarea. How would this most cleanly be done with the new iframe? Is there a good API? By the way - the normal accesskey and tabindex for the textarea don't work. [[User:Skalman|Skalman]] 22:39, 6 February 2010 (UTC) :Same problem here. My script looks for the textarea and helps me editing the text. How to do the same with the iframe? Besides, I don't understand why the textarea is replaced with an iframe? Currently I don't see any advantage or benefit. On the other side, the behaviour of the iframe is very different from the textarea. This makes it hard to use and not very "useable". For example, it's not possible to set the text cursor to the end of the text by clicking in the free region below the last line. Selecting text is also very different (try to double click and hold the mouse button to select multiple words, it does not work, at least in Opera). A lot of other problems. So, what's the point? Please tell me if this is'nt the right place to ask such questions. --[[User:TMg|TMg]] 21:14, 11 February 2010 (UTC) :It seems [[Talk:Prototype#iframe instead of textarea|Talk:Prototype]] is the right place to discuss this. --[[User:TMg|TMg]] 22:07, 11 February 2010 (UTC) == Localizable character palettes == Someone responded to my [[#Vietnamese characters|request for Vietnamese characters]] by adding a "Latin extended" category to the "Special characters" pane. But what we really need is a way for localizers (at Translatewiki, for instance) or individual wikis to specify a custom category. Currently the pane is very inconvenient for Vietnamese users, because Vietnamese characters are arbitrarily split between two different categories (three if you count the đồng sign). I realize this arrangement is based on Unicode, but for a Vietnamese speaker, "Á" and "Ả" are each a vowel with a tone mark&nbsp;– they belong next to each other. &ndash;&nbsp;[[User:Mxn|Minh Nguyễn]] <small>([[User talk:Mxn|talk]], [[Special:Contributions/Mxn|contribs]])</small> 07:08, 7 February 2010 (UTC) : One solution would be to create a list for every single language, rather than a list only for different character sets. This would, of course, be quite long... I wonder whether it would be possible to create a personal "favourites" section in the character pane? This might be a solution to the length issue, although it would mean that each Vietamese user would have to create the same personal list. [[User:Witty lama|Witty lama]] 02:11, 8 February 2010 (UTC) ::It doesn't necessarily have to be a ''personal'' list, just a ''localizable'' one. So each MediaWiki locale would be responsible for a system message like [[MediaWiki:Wikieditor-toolbar-characters-definition]]. It would have a format much like [[:en:MediaWiki:Gadgets-definition]]: an unordered list with each item representing a locale-specific category. Each item would have the category name, a vertical bar, and the name of the system message containing the characters for that category. It would look like this: :::<code>*Tiếng Việt|wikieditor-toolbar-characters-vietnamese</code> ::And [[MediaWiki:Wikieditor-toolbar-characters-vietnamese]] would contain a space-delimited list of characters: :::<code>À à Á á Ả ả à ã Ạ ạ  â Ầ ầ Ấ ấ Ẩ ẩ Ẫ ẫ Ậ ậ Ă ă Ằ ằ Ắ ắ Ẳ ẳ Ẵ ẵ Ặ ặ Đ đ ₫ È è É é Ẻ ẻ Ẽ ẽ Ẹ ẹ Ê ê Ề ề Ế ế Ể ể Ễ ễ Ệ ệ Ì ì Í í Ỉ ỉ Ĩ ĩ Ị ị Ò ò Ó ó Ỏ ỏ Õ õ Ọ ọ Ô ô Ồ ồ Ố ố Ổ ổ Ỗ ỗ Ộ ộ Ơ ơ Ờ ờ Ớ ơ Ở ở Ỡ ỡ Ợ ợ Ù ù Ú ú Ủ ủ Ũ ũ Ụ ụ Ư ư Ừ ừ Ứ ứ Ử ử Ữ ữ Ự ự Ỳ ỳ Ý ý Ỷ ỷ Ỹ ỹ Ỵ ỵ</code> ::The locale-specific categories would be placed at the top of the category list. [[MediaWiki:Wikieditor-toolbar-characters-definition]] would be blank by default, so locales (like English) wouldn't be required to create their own categories. ::&nbsp;&ndash;&nbsp;[[User:Mxn|Minh Nguyễn]] <small>([[User talk:Mxn|talk]], [[Special:Contributions/Mxn|contribs]])</small> 07:09, 8 February 2010 (UTC) ==Malayalam transliteration Script == Hi, I am from Malayalam Wikipedia ([[:ml:]]), we are having a transliteration script to type Malayalam using English keyboard. But this script get disabled in Enhanced Toolbar and editbox. Please provide a way to include this kind of scripts to Beta. --[[User:Praveenp|Praveenp]] 17:41, 11 February 2010 (UTC) :Can you link to this script? --[[Special:Contributions/83.119.125.27|83.119.125.27]] 17:17, 18 February 2010 (UTC) Sure, [[Toolbar/Malayalam transliteration Script]] (extracted from [[:ml:Mediawiki:Common.js]]). This script is limited to some pre defined text areas. Once we added a script which can work on every text areas. But it got some problems with internet explorer. So we reverted that. Both scripts given in the above mentioned page. If possible add these scripts to enhanced toolbar.--[[User:Praveenp|Praveenp]] 12:30, 18 March 2010 (UTC) == Missing feature == I use the new babaco toolbar and I've noticized that the acai "search and replace" feature it has been removed. It has been dicussed before removing or is a "surprise"? I think it's very helpful form my contributions in "wikify" pagese. Regards. == Just a brief feedback about vector costumization == I just added the first personal button into my Vector it.source skin, boldly manipulating my vector.js file, and I'm very happy and perfectly satisfied. It was impossible to work into it.source under Vector without my own buttons! Pathoshild's Regex Framework works too. The most encouraging point: I am really a deep js-ignorant. :-) --[[User:Alex brollo|Alex brollo]] 15:08, 15 April 2010 (UTC) :Could you post a link or something? It would be helpful for others. Also how do I add one of the seperator bars? And hell how do I add the search and replace on my toolbar for my own wiki? ==Reporting user's suggestion== [[Ticket:2010060310036186]] would like to suggest a "hide column" link to hide the left toolbar when not needed. [[User:Elitre]] [[Special:Contributions/95.247.20.31|95.247.20.31]] 19:30, 4 June 2010 (UTC) == No toolbar on Wikipedia == I don't have anytoolbar anymore on Wikipedia (FR at least; probably EN too). I do have the toolbar when logged out, but I don't when I am logged in. Where should I start investigating?--[[User:David Latapie|David Latapie]] 07:53, 10 June 2010 (UTC) == More Klicks - definitely worse than before. == My most used toolbar button is "insert wikilink". It was changed from a one-klick to a two-klick operation. Very bad, since it also forces an additional cursor movement. Time needed is quadrupled. I hate it. --[[User:Purodha|Purodha]] 11:58, 31 August 2010 (UTC) == Lost Buttons - a huge usability drawback == Among the toolbar buttons, that I use quite often, are "''change selection into'' <code>#REDIRECT[<nowiki />[...]]</code>" and "''insert the local typographical pair of quote characters around selection''". I have added them to the toolbar with personal JavaScript. With the advent of the "enhancements" of the Unsability Initiative, they became unavailable and thus unusable. Very bad. My hope had been, to get these two as standard buttons. My hope had been to even receive some more usability built into them: * ''change selection into'' <code>#REDIRECT[<nowiki />[...]]</code>, and delete eveything outside the selection, * ''insert local typographical pair of quotes around selection, ''and remove any kinds of quotes at both edges inside selection, which I had not been able to program myself yet. Greetings --[[User:Purodha|Purodha]] 12:16, 31 August 2010 (UTC) == Major problem at Wikisource == There is at least one major problem at Wikisource: [http://en.wikisource.org/wiki/Wikisource:User_experience_feedback]. [[User:Innotata|Innotata]] 22:15, 1 September 2010 (UTC) == Focus lost with new toolbar == There is a difference when using the new advanced toolbar and comparing with the old one: When editing a page, I usually start typing in the edit box before the toolbar loads completely. Before, I had no problem: I would type and the toolbar would eventually load, and once it did, nothing was disturbed. With the new toolbar, I tend to do the same: while the toolbar loads (it's usually the last thing to finish loading), I am already typing in the text area but as soons as it finishes loading, the focus on the edit area is lost. Some of my keystrokes are lost and I have to take the mouse to click on the edit area and recover focus. It would be great if this could be ammended. Right now, I disabled the new toolbar to avoid this effect. Thanks, [[User:Malafaya|Malafaya]] 13:59, 20 September 2010 (UTC) == Adding character attributes for symbols == Templates generally require that certain special characters, e.g., '''=''', be encoded if they are not to be interpreted as delimiters, e.g. <nowiki>{{tlx|rp|page=666}}</nowiki> must be encoded as <nowiki>{{tlx|rp|page&amp;#061;666}}</nowiki> in order to render as {{tlx|rp|page&#061;666}}. This would be asier if the toolbar included something similar to Special characters -> Symbols that included the basic ASCII symbols and that inserted character entities instead of the actual characters. [[User:Chatul|Chatul]] 13:57, 11 October 2010 (UTC) 33qfkrq2affixz66bg2xa27fbt0i7oe 0 425 2646 2465 2009-08-11T21:56:02Z Microchip08 216 wikitext text/x-wiki {{box|Editbox discussion|Feel free to add your opinions on the new edit box.|[[File:Dialog-information.svg|45px]]|To discuss the current icons, go [[Opinion Icons|here]]. To discuss the Vector skin, or anything else, go [[Talk:Prototype|Prototype]]|[[File:Edit-undo.svg|45px]]}} == Userfriendliness in Editing is Key == Hello, I never edited wikipedia but I installed a wikimedia wiki to assess it as a note taking tool and collaborative work at work and at home. I came to the conclusion, which seems to be shared even by some among you to a certain extent, that wikimedia due to its lack of userfriendliness could not be used professionnally in the current state because editing required a significant knowledge of html (or its wikimedia subset) which can not be considered as largely widespread or be part of what some has named digital literacy. It thus required learning it, and of course if we want wikimedia to be used by anyone even for taking notes, this is learning something not related to their main business and they may not have time for that. This is why, even though I was enthused by its collaborative capability I felt it was impossible to ask people at my job to edit a wiki like they would do for a word processor document, it is already not easy to ask people to take time to document what they do, with the current userfriendliness of wikimedia, and the additionnal time required to edit, they would have drop out documenting. To be shared widely, I think wikimedia editing should be made as simple as word processors (which use is definitely part of digital literacy) and also featurewise rich enough. I think among the mandatory userfriendliness features it should be possible simply to : * choose the color of the text * choose the font * choose the size * introduce the possibility to outline with several colors * offer the possibility of foot notes * offer the possibility of comments all that in a simple maneer (agnostic to html) I don't know if all that is already included in the scope of your project but I think it is very important for people using widely wikimedia in their home or professionnal projects and therefore be sufficiently familiar with the edition possibilities that they feel no obstacle to one day editing wikipedia when they feel they can contribute. When I saw the news of this initiative I welcomed it very much, please make it really user friendly this is key (think of the market share taken by the iphone even with a very late release date compared to other phones, it mainly amounts to its user friendliness and ease of use... think about it). I read that important amount of money was dedicated to this excellent initiative. I think this is annother reason to reach for a real ease of use in order to maximize the impact of this investment and also because in general this kind of opportunity does not come twice. We support you in this well inspired initiative it is an opportunity to make the needed and decisive difference ! :Hoi, the key thing with every new application is that you appreciate what the application is about. Given that MediaWiki, the name of the software, is intended for collaborative editing, you have to look at what it is that you need as such. Several of the comments that you make are a bit bewildering. It is ok that you have to learn about what it is that the software does, MediaWiki is not a text processor, expecting all the attributes of a modern text processor may give the impression that it is a text processor. :It is possible to have different text sizes et al in Wikipedia. However it is not used that often because you are looking for a consistent look and feel. The point, MediaWiki is used professionally and teaching what is special about the software is important. This usability initiative should make many things more intuitive but it should not take away the notion that this is not text processing. Thanks, [[User:GerardM|GerardM]] 11:45, 15 June 2009 (UTC) == Still more suggestions on the edit-button bar == Hi, After playing some more with the prototype, a few more ideas occurred to me. * The Help ("cheatsheet") dropdown menu is great, but again you left off the discursive list (; and :). Perhaps you should at least mention indentation with the colon, since it's so common on Wikimedia projects? Practically every section of every Talk page has them on the English Wikipedia. * Again under the Help menu, I notice that you don't include ALT text in your example of a Figure caption. I understand that that's simpler for newcomers, but it's disappointing that we don't encourage accessibility for the visually impaired. * The Heading dropdown menu is likewise great, except that Level 1 shouldn't be listed, since it messes up the Table of Contents (see [[:en:User:Proteins/MoS_Nightmare]] for an illustration). The levels might be more intuitive for newcomers if the dropdown menu showed the levels more as they might appear in the article, e.g., with larger bolder fonts for the higher levels. (See the "What you get" column of the "Headings" section of the Help dropdown menu.) Bonus points: you should never allow the user to add a heading level that is more than one level lower than the present level, e.g., you shouldn't allow the user to add a H4 heading in the middle of an H2 section. That's a barrier to accessibility for the visually impaired and a major headache for the Manual of Style. * I would demote the boldface and italics edit buttons to the "Formatting" dropdown menu. That seems like the most natural grouping. For another thing, these two typefaces are not used that often in Wikipedia articles. Boldface is usually used once per article, in repeating the article title in the first sentence of the lead. Unless the article is being created from scratch, that sentence has usually been written already; therefore, most editors in most situations will never need the boldface button. The most common use of italics is in the inline citations (journal names), which are handled already by the citation templates. Thus, it's relatively rare that editors need to introduce italics. * Perhaps also under Formatting, you might add something for striking out text? That's also common practice on Wikipedia; for example, at FAC, one strikes objections as they are met by the nominator of the article. * Again, I would promote the "Headings" dropdown menu to the first (leftmost) position on the edit-button bar. I would discourage the use of external links by putting that one last. Lists seem less important than references (at least on Wikipedia) so you might put the three types of lists under the "Insert" dropdown menu. Hoping these new suggestions are helpful, [[User:Proteins|Proteins]] 18:27, 24 June 2009 (UTC) == Problem with the headings and lists == When you select the text <code>== Foo ==</code> and then select level three from the headings dropdown, you get <code>===== Foo =====</code> instead of the expected <code>=== Foo ===</code>. The effect of the list buttons on multi-line selections is also not what one would expect. --[[User:Tgr|Tgr]] 08:00, 26 June 2009 (UTC) == Treatment of "Headings" in editbox buttons == Thanks for making those changes, but I'm not sure that "Advanced" is descriptive enough? My main suggestion, though, is to promote the Headings dropdown menu to the main line, say next to the add image button. Also, as suggested above, you should remove the Level 1 option, or at least add safeguards. [[User:Proteins|Proteins]] 15:58, 27 June 2009 (UTC) == Footer and alerts == div#foot with license and copyright info looks much better with monobook skin. See http://www.picamatic.com/show/2009/06/27/08/39/4149639_1280x275.png for real MediaWiki site. Also, EditWarning alerts (like any other javascript alert) are very annoying and should not be used by default. --[[Special:Contributions/85.141.235.251|85.141.235.251]] 16:50, 27 June 2009 (UTC) == EditWarning should be quiet after undo == The EditWarning extension is great -- warning that if you leave, your changes will be lost. However, the following use case should be fixed: # Edit a page # Type an "X" # Type ctrl-Z to undo # Click any link to leave the edit page Currently, EditWarning will pop up an alert. It should not, because nothing has changed. (Probably you are just keeping a "dirty" bit that indicates whether the edit box has been touched.) The simplest way to do this, in addition to your "dirty" bit, is to store the original wikitext when editing begins, and compare it to the current wikitext when the user tries to leave (window.onbeforeunload). I've been doing this in my own EditWarning-type extension and it works great, even for large pages. This is a small change, but if you suppress these unnecessary warnings, that is definitely good '''usability'''! --[[Special:Contributions/4.79.245.132|4.79.245.132]] 20:38, 30 June 2009 (UTC) ::I think this is an overhead, and there were no big benefit when this function would be implemented. How often do you think user do the described action above. For me too seldom. --[[Special:Contributions/129.27.129.83|129.27.129.83]] 10:21, 1 July 2009 (UTC) == LaTeX next to Special Characters == Hi, <br/> like the Special Characters Menu, there should be a similar menu for Math/LaTeX markup as used by [http://www.mediawiki.org/wiki/Manual:Enable_TeX texvc] and [http://www.mediawiki.org/wiki/Extension:Blahtex BlahTex]. The supported LaTeX commands should be grouped by their use ("greek symbols", "arrows", "integrals", etc.). See [[:en:Help:Displaying a formula|Help:Displaying a formula]] for a reference of commands. &mdash; [[User:MovGP0|MovGP0]] 21:43, 30 June 2009 (UTC) ==More suggestions for the edit page== At my suggestion, [[:en:User:Cacycle]] recently added a feature to wikEd which you might consider here. The feature collapses references and long templates into placeholders, which reveal their contents when clicked (my original idea) or onmouseover (Cacycle's implementation). I also suggested tables, although wikEd doesn't do that as yet. The advantages of this approach are several. First, references and templates such as infoboxes/navboxes are unfamiliar in syntax and usually stretch over many lines, sometimes even filling the visible edit box. This is particularly grievous at the beginning of the article, where long infoboxes are common and where most newcomers will first try to edit. By collapsing each of these long elements into a small labelled placeholder, you make the text ''far'' more readable, much closer to the article as read. In effect, this approach distinguishes between simple wiki-markup (links, section headings, italics) and complex wiki-markup (references, templates, tables). The simple markup is a much smaller "perturbation" of the normal article and much easier to learn. You might consider other innovations of wikEd for usability as well, such as its icons, its color coding, its find/replace mechanisms, its automated fixing routines, etc.. It's well-liked by many of Wikipedia's most productive editors. I've listed a few more ideas for wikEd on [[:en:User talk:Cacycle/wikEd]], which you might also consider. [[User:Proteins|Proteins]] 01:02, 2 July 2009 (UTC) PS. A third warning, please listen: Including "level 1" in the Heading dropdown menu is an invitation to disaster on a massive scale. If this new skin succeeds in recruiting thousands of beginning editors to Wikipedia, as we all hope, they will naturally choose level 1 for their first heading, right? I hope you know that '''level-1 headings are never appropriate on the English Wikipedia''', and I suspect most other languages and Wikimedia projects. Even if you ignore all my other suggestions here and above, please pay attention to this one. :The usability team is listening. Great point about level 1 heading is not appropriate for Wikipedia. How about external MediaWiki users though? We may need to find a way to customize for Wikipedia and MW project wikis. <br />P.S. Will check out content folding of wikiEd. Thanks for the pointer. --[[User:Shuhari|Shuhari]] 06:39, 2 July 2009 (UTC) ::Level 1 headings translate to h1 tags, which are normally only used to denote the title of the article. It is unlikely that many external MediaWiki sites would like to use multiple h1 tags, so IMO level 1 should be left out by default. If it is possible to customize the toolbar, the minority of wikis using L1 tags should be the ones to do that. --[[User:Tgr|Tgr]] 20:51, 4 July 2009 (UTC) ==Line breaks== For complex (multiline) inserts like ''gallery'' or ''table'' implicit line breaks can help to recognize easily what has been inserted with one click. After all manually inserted galeries or tables markup seldom flow inline with other text. [[User:Erik Zachte|Erik Zachte]] 03:39, 2 July 2009 (UTC) <nowiki> The following candy bars have a good taste to price ratio. <gallery> File:Example.jpg|Caption1 File:Example.jpg|Caption2 </gallery>Of these the following also have a high tooth decay factor. {| class="wikitable" border="1" |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |}Consume at own risk. </nowiki> Better <nowiki> The following candy bars have a good taste to price ratio. <gallery> File:Example.jpg|Caption1 File:Example.jpg|Caption2 </gallery> Of these the following also have a high tooth decay factor. {| class="wikitable" border="1" |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |} Consume at own risk. </nowiki> :A simple yet powerful way to increase intuitiveness. --[[User:Shuhari|Shuhari]] 06:44, 2 July 2009 (UTC) == Undo and redo == Could u please create an undo and redo button in the edit box? It works automatically on Firefox with ctrl-z and ctrl-y but most novice users don't know the shortcuts. Thank you.--[[User:Diaa abdelmoneim|Diaa abdelmoneim]] 10:24, 2 July 2009 (UTC) I second this. Any editor should have an undo / redo function. There is no acceptable reason not to have this. Thanks == Most block level elements should add a new line == I'll try to explain by example. Suppose I'm writing some text... <pre> Type, type and want to make next text bold '''click''' (Seems OK). And now I'm typing some more text and want to make a list... Go to a new line * OK. And now... click to go to next item?* wrong - same line </pre> Further more if I'm inside a line (not at the end) that has a list character, clicking on the list button should make the list disappear (this is would be similar to how it works office editors). But this could be a little tricky so another button for adding new list item should be added to avoid confusion. <pre> OK. Now I want to insert a table... Well this won't work:{| class="wikitable" border="1" |- ! header 1 ! header 2 ! header 3 |- | row 1, cell 1 | row 1, cell 2 | row 1, cell 3 |- | row 2, cell 1 | row 2, cell 2 | row 2, cell 3 |} </pre> BTW. I have this experimental table adder which you might use (I think I won't be able to finish this soon). It's not much but I guess it's better then just pushing the code straight away to the editing area (there is a simple, light editor that adds/removes new columns and rows and inserts code after finishing). I'm almost sure it worked in all modern browsers + IE 6, but it was quite a long time since I worked on it so I won't give my head on it. Some comments are in Polish so if you have a problem figuring something out just let me know. Anyway the code is here: [http://nux.w.of.pl/download/wiki/wp_ted_0.0.2.zip wp_ted_0.0.2.zip] a general class used for JS-pop messages (not in a new window): [http://nux.w.of.pl/download/wiki/sftJSmsg_0.0.5.zip]. The script adds a button above the textarea. Obviously it wasn't tested on new Vector skin (it was made for monobook), but I think it will work for it too. --[[User:Nux|Nux]] 22:18, 2 July 2009 (UTC) == A few thoughts on the enhanced edit toolbar == First off, thanks for all the effort as it is looking quite nice. A few thoughts... is it possible to reverse the "internal" and "external" links buttons, as per the standard tools? (While it is only a minor inconvenience remembering the order, I don't see an actual need to swap them - and having the external link button first might just inspire people to ''add'' them!) Thoughts? --[[User:Ckatz|Ckatz]] 02:50, 3 July 2009 (UTC) == Off the rails, and half way down the embankment== while I do like the new additions and modifications to the box, I think you are not on the right track. We use mediawiki at work, and have more than 1000 articles in place. However, I find it very difficult introducing new users (GenY,Z) to authoring articles. They just don't get it. They think the editing is clunky and old fashioned. GenY are really looking for a wysiwyg editor, not a text editor. Text editing is fine for sms, but for nice looking easy to read articles, folks want a slick editor. MS-Word, OpenOffice Writer are good examples. If this initiative is to succeed, it must create a wysiwyg editor. Perhaps an alternative is to provide good bi-directional connectivity to openoffice writer? Folks can then simply '''Edit''' as they do today, but instead of the editbox, the article/section will be sent directly to openoffice? Please take this is the positive manner in which it is offered. --[[User:Paul Kennedy|Paul Kennedy]] 01:04, 5 August 2009 (UTC) 25m483svids07henntpojmvuvfnbkti 0 426 2031 2009-07-14T22:42:06Z Nihiltres 78 Plausible redirect… wikitext text/x-wiki #REDIRECT [[Releases/Acai]] 85viv5awy6l8k6i7cfm76a55wekq8f3 6 428 2034 2009-07-15T00:51:54Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 429 2043 2041 2009-07-15T23:03:25Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:Button interaction.pdf]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 430 2135 2045 2009-07-28T21:29:27Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:ContentGeneration.pdf]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 431 2047 2009-07-16T09:11:13Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 432 2048 2009-07-16T09:16:51Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 433 2049 2009-07-16T09:17:05Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 434 2050 2009-07-16T09:17:18Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 435 2051 2009-07-16T09:17:32Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 436 2052 2009-07-16T09:18:10Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 439 9162 9160 2010-10-26T19:15:54Z 80.98.104.125 Undo revision 9160 by [[Special:Contributions/137.89.211.34|137.89.211.34]] ([[User talk:137.89.211.34|talk]]) wikitext text/x-wiki List of alphabets to include in the Special characters section in the edit toolbar: * Latin (basic, no diacritics) * Latin diacritics (Western European languages) * Latin diacritics (Eastern European languages) * Cyrillic * Greek * Arabic * IPA * Hebrew * Chinese * Japanese * <strike>Scary wiki stuff</strike> * more? f3e03okmft9pw7m2b2c6c4b47w6rqz6 6 443 2103 2009-07-21T23:52:03Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 447 2121 2119 2009-07-25T20:02:35Z Eneas 66 uploaded a new version of &quot;[[File:Babaco-Mockup.png]]&quot;: cosmetic changes wikitext text/x-wiki My own creation, based on a screenshot of a mock-up of the usability team. fohr8iklbgp9cbn9ej34mwiw1d4cq6d 6 449 2137 2009-07-28T22:03:40Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 450 2141 2009-07-28T22:53:05Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 451 2150 2009-07-28T23:10:56Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 452 4068 3171 2009-11-04T13:30:10Z 83.119.125.27 update wikitext text/x-wiki [[File:Wikipedia Usability Initiative Logo.png|right|100px|link=]] Take a look at the things we are currently working on. [[Talk:Prototype|Don't forget to give us feedback!]] <span class="plainlinks"> * [http://prototype.wikimedia.org/sandbox.3/Main_Page New design for section edit links] * A preliminary implementation of [http://prototype.wikimedia.org/sandbox.3/Main_Page side-by-side preview] * New [http://prototype.wikimedia.org/sandbox.1/Main_Page color] [http://prototype.wikimedia.org/sandbox.5/Main_Page schemes] for the Vector skin * A [http://prototype.wikimedia.org/s-4/index.php?title=Main_Page&action=edit Save draft button] on the edit form, allowing users to save draft versions of articles :''See also: [[Sandbox]]'' c4m5eo4rswsqiyu33xc6eue5qxcdryz 0 453 9252 9211 2010-11-02T13:03:01Z 77.64.170.2 undo last edit wikitext text/x-wiki {{Internal}} The Usability Initiative conducted its Usability, Experience, and Progress Study in early October 2009 in San Francisco, CA. Interviews were conducted on October 14th and 15th.<br /> __TOC__ The Project Team partnered with [http://boltpeters.com/ Bolt Peters], a local user experience consulting firm, and [http://www.davisresearch.com/ Davis Research], a California based Recruiting firm (who we highly recommend), both of who we worked with in our [[Usability_and_Experience_Study | previous study]] in March. We conducted 8 in-person interviews focusing on the editing experience, process, and its successes and failures, particularly focused on evaluating the changes the Initiative implemented in it's first two releases ([[Releases/Acai|Acai]] and [[Releases/Babaco| Babaco]]). We also explored novice user experiences, use, and interaction with templates, syntax and other complex formatted content. <br /> == Call for Proposals == We reached out to both local and North America based UX + Usability firms with a call for [[Usability,_Experience,_and_Progress_Study/CFP | Proposals]]. == Goals == The primary research goals were to: * Validate the changes implemented by the Usability Initiative; changes made to the editing process that were intended to improve editing experience and reduce interface barriers to participation. Those changes include features bundled into our Acai and Babaco Releases. * Of those changes, specifically look at site-wide navigation and skinning, the new toolbar, the content generation dialogues, and the new table of contents (edit page navigation). * Identify and evaluate patterns of reactions and obstacles that novice users encounter in editing Wikipedia with respect to 'templates' and 'Infoboxes'. * Continue to identify barriers that Wikipedia readers-but-not-contributors encounter in performing basic tasks associated with editing a Wikipedia article (adding personal content, fixing a typo, adding a reference, contributing to a discussion page, navigating and modifying the history). * Continue to discover user experience patterns and issues that have not previously been identified. == Methodology == === Target Audience === The primary goal of this study was to evaluate changes made since the original study. We therefore took a similar approach to recruiting our study participants. In the future, we may even consider bringing back some previous subject. As with the previous study, the target audience of this study was limited to regular Wikipedia readers who are willing to contribute their knowledge to the site, but have expressed reservations about doing so. The team aimed to select a majority (~80%) of users that had not edited but were willing to, and a minority (20%) of users that were novice but not new editors, with fewer than 5 contributions. We preferred potential subjects whose ''primary'' reasons for not contributing seemed to be due to the technical complexity of the interface of MediaWiki and markup, but understand that fear of article deletion, unwillingness to have work edited by others, lack of confidence in 'expertise', not being willing or used to collaborating, and philosophical differences are all also big inhibitors to Wikipedia readers' contribution. {| class="wikitable" style="text-align:center;" |- ! Participant No. ! Has not edited, but is willing to ! Has made < 25 contributions ! Male ! Female ! Under 20 ! 21&ndash;30 ! 31&ndash;40 ! 40+ ! Uses WP every day ! Uses WP > Once a week |- | 01 || X || || || X ||X || || || || X || |- | 02 || X || || X || || || || X || || X || |- | 03 || X || || || X || || || || X || X || |- | 04 || || X || X || || || X || || || X || |- | 05 || X || || || X || X || || || || ||X |- | 06 || X || || X || || || || X || || ||X |- | 07 || X || || || X || || || || X || || X |- | 08 || || X || X || || || X || || || || X |} === Recruiting === Using [http://www.ethniodev.com/ Ethnio], we recruited over 1181 San Francisco residents for the in person testing. A banner/alert was placed and displayed at the top of every 1 in 1000 Wikipedia pages for the duration of 96 hours. This led Wikipedia readers to a short welcome message and survey (shown below). Based on our criteria (see above, Target Audience), the 1181 users who responded to our survey were filtered down to 486 viable subjects. Our team partnered with [http://www.davisresearch.com Davis Recruiting] (who we can't say enough good things about). Davis recruiting contacted and phone screened these participants based on further discussion, explanation, and criteria as well as based on their age, gender, occupation and other demographics. Davis Recruiting also screens for talkativeness and openness in discussing thoughts and actions. From Davis we received our 8 study participants with 3 wait-listed/back up candidates. <div style="float:left">[[File:Research-Recruitment-ScreenerII.png|thumb|400px| Screenshot of Ethnio recruit survey]]</div> <div style="float:left">[[File:Research-Recruitment-InviteII.png|thumb|400px| Screenshot of Ethnio screener invitation]]</div> <div style="float:left">[[File:Research-Recruitment-ThanksII.png|thumb|400px| Screenshot of Survey Gratitude]]</div> <div style="clear:both"></div> === Lab Testing === This time around, because of our prior experience with remote testing, smaller subject numbers, and desire to conduct future studies (read: funds), we conducted all of our interviews in person. We returned to the [http://www.ffrsf.com/ Fleischman Field Research] facilities, located in San Francisco, California. Participants, limited to those within driving distance, were brought into a room with the Research Interviewer, and a Mac or PC laptop, based on their stated preference. Behind a two way mirror, Wikimedia Usability Researchers could view the interviewer and participant interacting, hear the interview audio, view the participants entire screen and computer interactions, and see their faces and expressions, in real time as the interview was being conducted. These videos (both the screen and the participant) were also captured under a Creative Commons License and can be viewed in the section labeled "Full Interview Videos". === Study Participants === {| class="wikitable" |- ! Participant No. ! Age ! Gender ! Wikipedia Editing History ! Wikipedia Usage ! Occupation ! Other Info ! Location |- | 01 "Judy" | 46 | Female | Has made one edit (on public transportation) | Every day | Architect | | San Francisco, CA |- | 02 "Mark" | 33 | Male | Has not contributed, but is willing to. | Every day | Environmental Consulting | | San Francisco, CA |- | 03 "Alexandra" | 23 | Female | Has not contributed, but is willing to. | Everyday | College Student and Video Producer. | Was researching corporate videos. | Oakland, CA |- | 04 "Angelique" | 33 | Female | Has not contributed, but is willing to. | More than once a week | Executive Director of Non-Profit | | San Francisco, CA |- | 05 "Cheryle" | 32 | Female | Has not contributed, but is willing to. | More than once a week | Homemaker | | San Francisco, CA |- | 06 "Stephen" | 53 | Male | Has made an edit | Everyday | Freelance Writer | | Santa Rosa, CA |- | 07 "Jack" | 23 | Male | Has not contributed, but is willing. | Every day | Quality Control @ Biotech | | El Cerrito, CA |- | 08 "Terrence" | 21 | Male | Has not contributed but is willing to | Every day | Student | | West Oakland, CA |} === Scripting === The moderator script was drafted closely match the script from our original study, drafted collaboratively by the Wikipedia Usability Team, B|P, and the Wikimedia Foundation. The script originally aimed to see how users would attempt to and feel about a collection of tasks or objectives that first time and early Wikipedians frequently encounter in their editing process including, but not limited to: finding various modes of editing, adding personal content, looking at discussion pages, creating a new article, finding and using help, navigating an article with templates, and adding a reference, external link, formatting. In this second round study, we focused on the same tasks, but particularly observed the use (or lack of use) of the tools and changes the team has implemented. The changes include, but are not limited to: a "cleaned up" and less cluttered skin, updated search and searchbox location, an entirely new toolbar including updated toolbar buttons, actions, and dialogues, tabbed site-wide navigation, edit box navigation, and integrated help. Click [[UXII Moderator Script|here]] for the full script. == Summary of Results == ====='''No Searching for Search'''===== Despite a fairly drastic relocation of the search box, none of the 8 users stumbled when trying to use it. In fact, one user actually used the box successfully, and then later was taken aback to realize it was in a different place than he was used to. The new position takes advantage of user expectations from across the web, aligning Wikipedia with many other major websites. The improved search algorithm was a marked improvement from our last study where we saw users give up and use Google to navigate to the Wikipedia page they were searching for. ====='''Easier Navigation'''===== <span style="color: gray">''“It was easy, and I wouldn’t have thought it would be that easy.”''</span> <br /> All of the 8 users successfully found the Edit tab with a minimum of hunting when they were asked to begin editing. There were no open questions about page types or page actions, but 3 users "misused" the edit tab from within and edit or preview process. ====='''Decreased Intimidation'''===== <span style="color: gray"> ''“Before there were a lot of tools, and I liked that they were all spread out in front of you, but this actually makes a lot of sense. I had to muddle my way through the older system, but this one seemed fine.” ''“Websites don't have common sense, but programmers do.”'' </span> One notable observation from the previous study in this series was the degree of trepidation users expressed after reaching the editing interface. This time, although they persisted in referring to wikitext as code, they were much more willing to dive in and start editing. We primarily credit the significantly cleaner overall look of the page and the more modern toolbar, which has been tremendously simplified and de-geeked. ====='''Toolbar: Visibility'''===== <span style="color: gray">''“Links are so easy to screw up. I’m not sure if we've correctly typed the link markup. Ah, there are these buttons...”'' <br /> ''“I'm trying to see what the code looks like for these other links. I guess these double brackets will make it search for that. ... Ah, the link button. So I guess this is what I was looking for earlier.”'' </span> While the toolbar provided some much- needed help to users who were lost in “code”, we found that the #1 problem was simply getting users to notice it. 7 of the 8 users were inclined to try to find something in the existing text that seemed close to the end result they wanted, and copy/paste it. It’s likely that the coloring (very pale gray) as well as the positioning (middle of a very busy page) contribute to this stealth toolbar effect, but it’s also possible that users simply don’t understand the “show me” nature of the different tools. Make the tools/toolbar stand out. ''See our prototypes to address this issue [http://prototype.wikimedia.org/sandbox.5/Main_Page here]''. ====='''Toolbar: Links'''===== <span style="color: gray">''“Uh-oh, I think I may have made the wrong kind of link before. I'll go to the preview window to see if this is a link. It would have been nice to just edit it in the preview.”''<br /> </span> Of the dialog boxes that have been implemented, the one that most consistently resulted in errors or confusion was the link insertion dialog; in fact, 6 of 8 users initially made some error in using it. The most common error was failure to notice the two top tabs for internal and external links. Not having seen these, users quite happily worked toward creating their link without any worries about the nature of the link. This behavior demonstrates that the distinction is a purely technical one. Unify wiki/external link tabs in the link dialog box. Since the single button on the toolbar indicates one tool, and most users did not differentiate the type of link they were making, and missed the tabs altogether, eliminate the two tabs in the link dialog. ''See our current prototypes addressing this issue [http://usability.wikimedia.org/w/index.php?title=File:Wireframe-Babaco-Dialogs.pdf&page=1 here]''. ====='''Toolbar: Tables'''===== <span style="color: gray"> ''“Table, I’m not sure what that is. I'm going to save it and then see, because this preview is too confusing.”'' ''“This is basically the programming for the table. I don't see where to add the information. ... It came out wrong, not what I was expecting, but what I do see is a table with historical figures, so I'll go into the editor and look at that. ... If I hadn't looked at the other table, I wouldn't have known how to do this." '' ''“Okay, I just got a bunch of code instead of a table.”'' </span> The insertion of tables proved to be one of the most problematic tasks, tripping up 4 of 8 users, even after they discovered and began to use the toolbar. The dialog box seemed straightforward enough, but once the wikitext was inserted, confusion set in. Users were not sure which part of the text to actually edit, with some interpreting the “sample text” (Row 1, cell 1) as labels, and attempting to insert table contents between the markup dividers. Confusion was exacerbated when users flipped to the article view (either in preview mode or by publishing), and couldn’t find anything resembling the table they were expecting. Bar none, they were looking for a table with grid lines and a background color. ====='''Toolbar: Etc'''===== The icons for “Bold” and “Italic” font break the web- and application-standard convention of using the letters B and I, resulting in widespread disorientation among users. Even those who correctly guessed their purpose were not confident they had guessed correctly, and had to hover or click to confirm their assumption. The term “Advanced” is a misnomer, implying that the functionality contained within will be primarily of interest to advanced users. In reality, the tools extracted to this area of the toolbar are simply less commonly used. The term “advanced” in this context can be a barrier to exploration, preventing some novices from ever discovering the tools tucked away there. The “Embedded File” tool proved to be one of the least easily understood tools of this study. Users generally avoided it, finding that even the sample text, when inserted, provided no additional insight. ====='''Navigable Table of Contents'''===== <span style="color: gray"> ''“This is different, it's got these hot-links [the table of contents]. That's nice."'' ''“On the right, this would take me to the live article.”'' </span> Less than half of our users recognized the table of contents for what it is, with most users not seeming to notice it at all. Those who did notice it tended to think it would bring them to that section of the live article. When a heading is clicked in the table of contents, the article text is not correctly aligned within the editing window, sometimes being off by as much as several paragraphs. ''See our current mockups addressing these issues [http://usability.wikimedia.org/w/index.php?title=File:Wireframe-Babaco-WikiEditor.pdf&page=1 here]''. ====='''Templates'''===== <span style="color: gray"> ''“I’m completely intimidated by that.”'' ''“It took me a minute to figure it out, but now I know that it’s all laid out in computer editing lingo, so that it creates a box.”'' ''“That’s a whole lot of html that makes my eyes dance all over the screen."'' </span> While the changes made as part of Babaco have significantly reduced the intimidation factor of editing ordinary pages, this finding did not hold when users encountered the more complicated template code. Users were confident using scrolling and the right-hand links to find the item they wanted to change in a single-column page, but introducing a second column flummoxed them. Their behavior returned to the uncertainty and unwillingness to make changes that we have seen in earlier releases. Some participants were also uncertain about the language—terms like “transcluded” are new to most users and add to the intimidation factor. Make it clearer that users are in a template that requires “advanced” or “special” markup. ====='''Previewing'''===== <span style="color: gray"> ''“I'd want to go back to the read page and look at it without all the code, to figure out where I want to put my part.”''<br /> ''“I was expecting it to be more like a Word doc.”''<br /> ''“I might go to word, and make the paragraph there first. It's easier to spellcheck and look at it without all the links and stuff.”''<br /> </span> Only 2 of our 8 users realized that in preview mode, the editing window was still on the page, just pushed to the bottom, and 1 of them didn’t realize it for quite a long time. ====='''Saving'''===== <span style="color: gray">''“Save puts it in some place on the wiki server where I can get in and edit it, but it’s not published.”''</span> We’ve all had it drilled into us - “Save your work!” All 8 of our 8 users displayed a desire to somehow do this before proceeding to a different page of any sort, and most assumed that “Save Page” was the correct way to do this - often even performing this as a preliminary step before previewing their changes. == Study I and Study II== The study confirmed for us that our changes are progressing in the right direction - towards greater ease of use for novice users. The majority of such users we interviewed in this study showed less intimidation, completed tasks faster and with greater ease (and sometimes even with pleasure!), and employed the tools and features we have implemented without instruction and with success. The users did, however, illustrate many imperfections with those tools (i.e. the separation between internal and external links in the link dialog box) along with a bug or two ;). But it should please us and you to know that we are convinced these tools are worth modifying and updating - we will continue to tweak and develop the new toolbar, the dialogs that accompany them, in-situ help, the Vector skin, navigation across the site and from and edit page, Search, and on. That being said, our study illustrated how much work is still left to be done. Our script focused on tasks that allowed us to focus on a user's ability to find and employ the tools we have deployed (in the interests of evaluating our work), but our interviews brought to the surface the myriad issues that continue to create barriers for new users. We again saw users struggle to get their questions answered (at least the ones that couldn't be solved with our toolbar cheat sheet), suffer from never ending link options (we call them "rabbit holes"), adopt makeshift preview and save processes, become overwhelmed with textual instructions, messages, and warning, and within the course of a one hour study - having their first edits reverting without dialogue or explanation. Though we cannot address all of these issues within the time, resources, and scope of our project and grant, we hope the issues brought to the surface will be addresses with future work, other Foundation projects, new grants, and community members and volunteers. The solicited feedback and interviews, and your unsolicited feedback on this page and project wiki continue to help us do what we do better. == Full Interview Videos == [http://bpluv.com/wikipedia/wiki_er2_user1_compressed.mov User 1]<br /> [http://bpluv.com/wikipedia/wiki_er2_user2_v2.mp4 User 2]<br /> [http://bpluv.com/wikipedia/wiki_er2_user3_v1.mp4 User 3]<br /> [http://bpluv.com/wikipedia/wiki_er2_user4_compressed.mov User 4]<br /> [http://bpluv.com/wikipedia/wiki_er2_user5_v1.mp4 User 5]<br /> [http://bpluv.com/wikipedia/wiki_er2_user6_v1.mp4 User 6]<br /> [http://bpluv.com/wikipedia/wiki_er2_user7_compressed.mov User 7]<br /> [http://bpluv.com/wikipedia/wiki_er2_user8_compressed.mov User 8]<br /> [http://usability.wikimedia.org/wiki/File:Uxii_search.ogv User 2 Search Clip]<br/> <div style="float:left">[[File:Cheryle_props.ogv | thumb | left | 400px | Our eventual goal for all Wikipedia Users]]</div><br/> <div style="clear:both"></div> == Accounts == Please note that we created user accounts to isolate the work or changes made by a test subject. These accounts were: Usability X (for X = 1, 2,....8). == Notes == The team's rough notes from the interviews are [[Usability, Experience, and Progress Study/Notes|here]]. [[Category:Usability studies]] ilv8igzqfzbyi73j6wytw9e77ojk8aj 0 454 8608 4960 2010-07-29T12:57:19Z Nemo bis 9 cat wikitext text/x-wiki Hello! We are looking to conduct a Usability/User Experience Study in San Francisco, CA in late September and are looking for help! Deadline for Submission: August 20th, 2009. ==Who we are== We are the Wikipedia Usability Initiative. Our work is supported by a grant from the U.S.-based Stanton Foundation. This grant has enabled our one year pilot project to measurably increase the usability of Wikipedia for new contributors by improving the underlying software on the basis of user studies, thereby reducing barriers to public participation. We believe that by lowering the technical barriers to participation subject-matter experts are more likely to add their knowledge to new and existing articles, resulting in a higher quality encyclopedia. With an initial focus on English Wikipedia, eventually this research and development will be implemented across all languages and possibly to other WikiMedia projects. [http://www.wikipedia.org Wikipedia], for those of you that don't know, is a web-based encyclopedia containing more than 11 million articles in 265 languages. The English language Wikipedia is the most comprehensive edition and contains more than 2.6 million articles. According to comScore, 274 million people visited Wikipedia in September 2008, making it the 4th most popular website world-wide. According to the Wikimedia Foundation's own statistics, more than 10 billion Wikipedia pages are viewed every month. The Usability Team is a special project of the Wikimedia Foundation. The [http://www.wikimediafoundation.org Wikimedia Foundation] is an audited, 501(c)(3) non-profit charitable organization based in San Francisco, California. It is dedicated to making free knowledge available to everyone on the planet by empowering a global network of volunteers to collaboratively develop educational resources. ==Our research== As outlined in our grant proposal, our research is focused on reducing the barriers for contribution to English Wikipedia and the other Wikimedia projects. We conducted an initial exploratory [http://usability.wikimedia.org/wiki/Usability_and_Experience_Study Usability Study] in March, 2009 with [http://boltpeters.com/ Bolt Peters]. As we are working on solving problems discovered we are looking to both validate our improvements and inform our future design and development. In the first phase of this project encompassing two [http://usability.wikimedia.org/wiki/Releases releases], we have been designing and developing changes to the user interface that help authors perform basic editing tasks including, but not limited to, a new skin, an enhanced toolbar, content wizards and dialogs, and new editing tools to help in navigating content and help materials. In the upcoming phase of our project, we will be focusing on the core components of the editing process - particularly complex formatting in wiki syntax and the use of templates. Our goals are to both "hide" this complex formatting language to provide easier access to the article body content, and also to provide users with an editing interface to these complicated structures. ==What we're looking for (or How you can help)== We are looking for UX and Usability firms, researchers, and enthusiasts to help us to evaluate the changes we have made to the existing softward and inform our future work on complex content and templates. Generally we are looking to: * recruit appropriate target groups that serve both of our interests * have 10-20 participants, at least half of which we will be able to interview in person in San Francisco, CA. the other half of which are *not* located in San Francisco - preferably globally. * conduct in-person and remote interviews of tasks and open ended questions with video and audio of the participant, moderator, and computer screen. * analyze and synthesize all of the information from the interviews into actionable recommendations, user profiles, age and gender trends, etc. * share video highlights and the full interview audio + video with our community online. ==Getting in touch== If you or your company is available to help, please email us at [mailto:usability-study@wikimedia.org usability-study@wikimedia.org]. Let us know how you can help or with a proposal and we will get back to you. Thanks! DEADLINE: August 20th, 2009 [[Category:Usability studies]] 9vo1rnhufzb57zfxx7qhkihcxf464m9 0 456 8616 2921 2010-07-29T13:02:45Z Nemo bis 9 cat wikitext text/x-wiki This page will be used for referencing the usability materials presented at previous Wikimania and supporting materials for future Wikimania. * 2005 * 2006 * 2007 * 2008 * [[Wikimania/2009|2009]] [[Category:Communication]] 5gt15o5jb85v7m1zgrrau1gf9if2agx 0 457 3070 2997 2009-09-11T12:15:45Z Mormegil 868 Undo revision 2997 by [[Special:Contributions/79.222.238.115|79.222.238.115]] ([[User talk:79.222.238.115|Talk]]) wikitext text/x-wiki ==Wikipedia Usability Presentation Outline == ===About the usability project=== ====Objectives==== The goal of this initiative is to measurably increase the usability of Wikipedia for new contributors by improving MediaWiki, on the basis of user behavioral studies, thereby reducing barriers to public participation. ====Project Scope==== '''Phase 0:''' Form a project team, conduct usability study, and research existing solution. '''Phase 1:''' Simple changes to the user interface that help authors perform basic editing tasks. This may include changes such as visibility of the edit button, access to the help pages and basic instructions, removal of “instruction overload”, etc. '''Phase 2:''' A first attempt at the redesign of the core component of the editing process - the article editor. This will focus on hiding complex formatting language in the standard editing interface and making those features accessible in a separate, more advanced, editing interface. ====The team==== =====The core team===== Naoko Komura, Program Manager<br /> Parul Vora, Interaction Designer<br /> Trevor Parscal, Software Developer<br /> Nimish Gautam, Software Developer<br /> =====Extended Team===== Roan Kattouw, SW Development Consultant<br /> Hannes Tank, Design Intern <br /> Aaron Wright, Volunteer<br /> =====Advisers===== Erik Moeller, Deputy Director<br /> Brion Vibber, CTO<br /> Frank Schulenburg, Head of Public Outreach<br /> ===Usability Study=== ====Methodology==== *Recruiting *Lab and Remote *Profiles ====Tasks==== * Navigate * Edit (formatting, references, templates) * Create a page ====Findings==== * People love Wikipedia (insert quotes from the study participants here.) *Confused, lost and overwhelmed (insert quotes from the study participants here.) *Learning by example (insert quotes from the study participants here.) ===Design + Develop + Deploy=== ====Design==== *Brainstorm <br /> *Prioritize<br /> *Mock-ups <-> Feedback<br /> ====Develop==== *Prototyping <-> Feedback <br /> *QA <br /> *Changes<br /> ====Deploy==== *Staged release *Stealth mode *Open invitation ===Proposed improvements=== ====Acai release (July 2009)==== * Streamlined navigation (screenshots) * Minimalist but versatile approach to the toolbar (screenshot) * Simplified search result page (screenshot) ====Babaco release (September 2009) ==== * Visual navigation - color enhancements * Navigable table of contents in edit page - color enhancements * Wizard for links, images, and tables ====Citron release (January 2010)==== * Content folding * Side-by-side preview * Syntax highlighting kjw3gftersuem99o1f6bud60mj63fp1 0 459 8773 8768 2010-08-13T16:19:41Z Avicennasis 1641 Undo revision 8768 by [[Special:Contributions/Jennie|Jennie]] ([[User talk:Jennie|talk]]) rm spam wikitext text/x-wiki === Bolt Peters === '''Website''': http://www.boltpeters.com<br /> '''Location''': San Francisco, CA <br /> '''About''': Bolt | Peters is a creative research firm dedicated to transforming the personal, social, and cultural role of technology - in a good way. Since 2001, we have completed 231 projects with 1,300 participants, often times using research that is conducted remotely, with participants all over the world. <!--info: nate@boltpeters.com --> <!--contact: nate@boltpeters.com --> === gotomedia === '''Website''': http://www.gotomedia.com/<br /> '''Location''': San Francisco, CA <br /> '''About''': gotomedia is a strategic consultancy specializing in research, visual design and user experience design. Our user experience professionals and award-winning visual designers utilize research techniques to analyze the goals, needs and behaviors of the audience. The results inform the decision-making of clients, engineers, designers and business leaders. gotomedia's approach is scalable to all projects regardless of scope or size. The practice of iterative development cycles based on "function + form" allows our projects to quickly reach measurable business goals. <!--info: sales@gotomedia.org --> <!--contact: --> === Dana Chisnell @ Usability Networks === '''Website''': http://www.usabilityworks.net/<br /> '''Location''': San Francisco, CA <br /> '''About''': <!--info: dana@usabilityworks.net --> <!--contact: --> === Nielsen Norman Group === '''Website''': http://www.nngroup.com/<br /> '''Location''': Freemont, CA<br /> '''About''': The philosophy of the Nielsen Norman Group is simple: To help companies enter the age of the consumer, designing human-centered products and services. Human-centered products emphasize user experience over factors like technology, features, or marketing points. "User experience" encompasses all aspects of the end-user's interaction with your company, your services, and your products. Human-centered products meet the exact needs of your customer, without fuss or bother. They are simple and elegant, a joy to own, a joy to use. Your products reflect your overall company strategy and culture. In corporate cultures that emphasize technology, features, marketing points, or your company organization (in the case of websites), user experience is not given priority, and human-centered products will not result. Are your help lines too expensive? The fact that customers need so much help is a sign of poor products. Want a better product? You probably have to reorganize your company and change your product process. Customer-centered, human-centered design requires corporate commitment, and a seamless merging of the services of multiple disciplines, including engineering, marketing, graphical and industrial design, and interface design. The results are faster design cycles, customers who are more satisfied and more loyal, and the transition of help lines and service desks from complaint posts and cost centers into positive customer experiences: a chance to interact and renew customer commitment, a chance to increase sales and loyalty. <!--info: info@nngroup.com --> <!--contact: --> ===UE Research === '''Website''': http://www.ueresearch.com/index.php<br /> '''Location''': San Jose, CA <br /> '''About''': What makes UEresearch stand out? It's our team. We are brimming with experience, technical expertise, innovative ideas and business savvy. We also love the work we do! As a small firm, we are able to put focus and care on all of our clients’ projects. That is why leading companies as diverse as Dell Computer, Food Network and Hyundai come to us to provide the quality and service they need and deserve. With backgrounds ranging from marketing to clinical psychology to design, our team can provide you with a robust perspective that only comes when problems are examined from multiple angles at once. Deciding who to trust with your company's image, product and/or web design is never easy. UEresearch is a solid investment you can feel confident about. Born out of the successful design and usability company, theUEgroup, our experience and versatility can improve the way you do business! <!--info: info@ueresearch.com --> <!--contact: --> === Tangible UX === '''Website''': http://www.tangible-ux.com/ <br /> '''Location''': Mountain View, CA<br /> '''About''': Tangible is a User Experience consulting firm for Fortune 500, mid-market and start-up companies. Our clients span a wide range of industries, including communications, education, finance, media, entertainment, and high tech. We specialize in helping clients create intuitive, branded user experiences for sophisticated applications and corporate websites delivered across desktop, handheld, mobile, and stand-alone devices. <!--info: james@tangible-ux.com --> <!--contact: --> === blink === '''Website''': http://www.blinkinteractive.com<br /> '''Location''': Seattle, WA<br /> '''About''': Blink Interactive is a Seattle user experience consulting firm dedicated to helping clients achieve their business goals through a flexible user-centered design approach. Blink’s specialized focus on the user experience provides a level of service that result in highly usable and useful systems. Founded in 2000, Blink Interactive is among a select group of Interaction Designers, Usability Engineers and User Researchers with the education, experience and hands-on expertise to ensure a positive, productive user experience. Two central principles guide our work: Understand and balance the business goals of clients with the needs of their end-users. Incorporate user feedback into every project. Because Blink’s service offerings are modular, we are able to partner with established development companies or work with our clients’ internal development teams. Blink works closely with these teams to ensure the client and users’ needs are addressed throughout the entire development phase. <!--info: info@blinkinteractive.com --> <!--contact: --> ===Usability Matters === '''Website''': http://www.usabilitymatters.ca/<br /> '''Location''': Toronto, ON, Canada<br /> '''About''': Our collective expertise encompasses a wide variety of backgrounds and experiences. We've worked across a range of industries, including media, education, automotive, travel, retail, financial, health and not-for-profit. We are comfortable and productive in a variety of work settings: as an integral part of your project team, as consultants, or as objective third-party observers. Our value is in bringing the user's perspective to the table - ensuring user requirements, motivations and goals are a project priority. We strive to create user experiences that exceed expectations while supporting business requirements. <!--info: info@usabilitymatters.com --> <!--contact: --> ===Creative Good === '''Website''': http://www.creativegood.com/<br /> '''Location''': New York, NY<br /> '''About''': Creative Good has an experienced team of customer experience consultants, all of whom have a track record of client business improvement. <!--info: emailus@creativegood.com --> <!--contact: --> === User Interface Engineering === '''Website''': http://www.uie.com/ <br /> '''Location''': North Andover, MA<br /> '''About''': User Interface Engineering is a leading research, training, and consulting firm specializing in web site and product usability. Jared M. Spool founded the company back in 1988 and has built UIE into the largest organization of its kind in the world. With our in-depth research findings based on user observation, we empower development teams to create usable web sites that increase customer satisfaction and loyalty. <!--info: support@uie.com --> <!--contact: --> === Advanced Common Sense === '''Website''': http://www.sensible.com <br /> '''Location''': Chestnut Hill, MA<br /> '''About''': Steve Krug (pronounced “kroog”) is best known as the author of Don’t Make Me Think: A Common Sense Approach to Web Usability, now in its second edition with over 200,000 copies in print. But he’s also spent 20+ years as a usability consultant for a wide variety of clients like Apple, Bloomberg.com, Lexus.com, NPR, the International Monetary Fund, and many others. His consulting firm, Advanced Common Sense (“just me and a few well-placed mirrors”) is based in Chestnut Hill, MA. He currently spends most of his time teaching usability workshops, consulting, and working on a new book about do-it-yourself usability testing. <!--info: skrug@sensible.com --> <!--contact: --> === Meld === '''Website''': http://www.meld.com.au/<br /> '''Location''': Australia<br /> '''About''': Meld Consulting was founded in December 2007 by Steve Baty. After spending the better part of 9 years with Web agency Red Square - the last two as Director of User Experience - Steve had a vision for a new type of Experience design consultancy, one with a balanced view of the people:business:technology tension. Meld can provide you with a range of strategic and tactical user experience services suited to meet your needs. Our strengths in stakeholder and user research, analysis, and strategy provide you with the perfect way to get your project off on the right foot. Rather than following a fixed process, Meld focuses on the needs of your project and adopts the tools and techniques best suited to meeting those needs. <!--info: consultants@meld.com.au --> <!--contact: --> === UX Research and Consulting === '''Website''': http://www.ux-research.com/<br /> '''Location''': Montréal, Québec, Canada <br /> '''About''': UX Research & Consulting offers independent analysis, user research and testing at every stage of the development cycle to companies who wish to improve both usability and user experience. Our expertise includes webservices, desktop software, touch screen applications, interactive television, voice services, mobile devices, product documentation and customer/ physical retail interaction. <!--info: info@UX-research.com --> <!--contact: --> === Navigation Arts === '''Website''': http://www.navigationarts.com/<br /> '''Location''': McLean, VA <br /> '''About''': We recognize that users determine the success of an online experience. Accordingly, we design and build each Web experience according to the needs and preferences of its users, drawing on our expertise in user research and the talent of our senior consultants. <!--info: sales@navigationarts.com --> <!--contact: --> === Akendi === '''Website''': http://www.akendi.com/<br /> '''Location''': Toronto, ON, Ottawa, ON, Vancouver, BC <br /> '''About''': We are an informed design, usability research & product strategy firm. Passionate about the creation of informed designs – whether those designs involve physical products, software, web, or bricks-and-mortar interactions. We work closely with you to research, design, and test all aspects of the human experiences you deliver. <!--info: business@akendi.com --> <!--contact: --> k5o54ci7d8t6y8qg16xj1fk80g77k19 6 460 2319 2009-08-05T02:33:05Z FT2 412 Mockup for discussion wikitext text/x-wiki Mockup for discussion 1vzes724iu83151j3s163808xq4wdsm 6 477 2420 2009-08-07T13:10:28Z Teofilo~usabilitywiki 173 Screenshot of Wikimedia commons. All rights reserved (wikimedia logo) wikitext text/x-wiki Screenshot of Wikimedia commons. All rights reserved (wikimedia logo) clanr5uauddb62qmlv2iywr7nmnk6p5 6 484 2432 2009-08-07T14:15:28Z Joystick 373 Usability Initiative Search proposition wikitext text/x-wiki Usability Initiative Search proposition 7q52mtv6sg65oyoear443mo9xc4ognb 6 487 2444 2009-08-07T16:35:08Z Shuhari 4 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 489 2463 2009-08-07T23:51:56Z Brooke Vibber 143 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 490 2464 2009-08-07T23:52:13Z Brooke Vibber 143 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 491 2466 2009-08-07T23:52:34Z Brooke Vibber 143 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 492 2468 2009-08-07T23:54:16Z Brooke Vibber 143 Created page with 'The current look has very little color, and it's difficult to tell where one thread ends and another begins, let alone finding where subconversations within the thread are separa...' wikitext text/x-wiki The current look has very little color, and it's difficult to tell where one thread ends and another begins, let alone finding where subconversations within the thread are separated: [[File:Forum layout example - current LQT.png|400px]] For comparison, screen shots of a couple newsblog/forum-type sites: [[File:Forum layout example - osnews.png|400px]] [[File:Forum layout example - slashdot.png|400px]] 1dmf1cdwnn1h5fiwtom5wlxoiqhzbd6 6 495 2488 2009-08-08T05:19:54Z Teofilo~usabilitywiki 173 screenshot of firefox error message when using the new interface wikitext text/x-wiki screenshot of firefox error message when using the new interface 5qte794403v6827zgooe7aybziengnp 6 496 2498 2492 2009-08-08T06:49:40Z Teofilo~usabilitywiki 173 uploaded a new version of &quot;[[File:Prototype test on Commons 002.jpg]]&quot;: cropped wikitext text/x-wiki screenshot of [[:Commons:Category:Mulberry Harbour]] p5lkwzqbw631780zreka67sn0xru68x 6 497 2497 2493 2009-08-08T06:48:26Z Teofilo~usabilitywiki 173 uploaded a new version of &quot;[[File:Monobook comparison on Commons 002.jpg]]&quot;: smaller wikitext text/x-wiki screenshot of [[:Commons:Category:Mulberry Harbour]] p5lkwzqbw631780zreka67sn0xru68x 0 501 2518 2509 2009-08-08T20:41:04Z PhiLiP 639 /* Suggested solutions */ wikitext text/x-wiki The initiative will fail if the beta default skin is not made seamlessly compatible with [http://en.wikipedia.org/wiki/Wikipedia:Twinkle Twinkle] and its high use brethren, such as [http://en.wikipedia.org/wiki/Wikipedia:Huggle Huggle] and [http://en.wikipedia.org/wiki/Wikipedia:Friendly Friendly]. For those of you who don't know, Twinkle is a set of JavaScript functions that gives [http://en.wikipedia.org/wiki/Wikipedia:User_access_levels#Autoconfirmed_users autoconfirmed], registered users at Wikipedia a set of tools that aids in fighting vandalism, patrolling newpages and automates many mundane tasks such as adding categories, marking pages with maintenance templates, stub tagging, and similar, vital background operations. Twinkle, Huggle and Friendly are used by a vast number of Wikipedia users, many of whom are Wikipedia's "core" editors, i.e., the ones who will have great influence in making this work and implementing it. There are already complaints on [http://en.wikipedia.org/wiki/Wikipedia_talk:Twinkle Twinkle's talk page] about the script breaking down when using Beta. This page is intended to not just inform the project of the need to make Beta compatible with these programs, but to serve as a clearing house for problems, workarounds and related matters geared toward smoothing out compatibility issues as they arise. ==Bug reports== Please describe below the specific problem you have noticed with the use of Twinkle, Huggle, Friendly, or other script when using Beta. Please be sure, before listing any problem here, that the bug is not evident when using the monobook default skin. Please start each new problem noted inside of third level section header, i.e., <nowiki>===headline===</nowiki> ==Suggested solutions== List or discuss below proposed or possible solutions to identified problems. : Chinese Wikipedia has used a JS script to deal with it. It works for me: [[:zh:MediaWiki:Gadget-vectorskin-thunks.js]]. --[[User:PhiLiP|PhiLiP]] 20:41, 8 August 2009 (UTC) nf2755gef2a6ap72b0kyve8hc79dvh5 0 515 8529 4814 2010-07-21T07:19:06Z Erik Warmelink 2316 /* Why */ wikify wikitext text/x-wiki ==Why== We want to know what aspects of the new designs are being used and the level of proficiency of the user. We want to make page editing easier for new users, but not hinder editing for advanced users. ==How?== Soon, we would like to start tracking the following information on the new toolbar: * the namespace being edited (whether it's a main page, a talk page, etc) * an event ID (unique to the event '''not''' the user) corresponding to events such as "clicked the bold button" * the number of contributions the user has made so far, to give us a ballpark measure of expertise the current user has ====NOTE==== No individually identifiable information will be tracked See [http://wikimediafoundation.org/wiki/Privacy_policy] for more information sley3fibgg7gw6btd9q1ilarbc51m2m 10 517 8639 3202 2010-07-29T13:27:42Z Nemo bis 9 cat wikitext text/x-wiki <div style=" float:right; clear:right; border:solid 1px #9accf6; background:#f1f9ff; padding:1em; padding-top:0.5em; padding-bottom:0.5em; font-size:1.2em; width:20em; color:black; margin-bottom: .2em; margin-left: .5em; "> '''{{{1|{{PAGENAME}}}}}''' {| style="background-color: #f1f9ff" cellpadding="5" {{#if:{{{2|}}}{{{3|}}}| {{!-}} {{!}} {{{3|}}} {{!}} {{{2|}}}}} {{#if:{{{4|}}}{{{5|}}}| {{!-}} {{!}} {{{5|}}} {{!}} {{{4|}}}}} {{#if:{{{6|}}}{{{7|}}}| {{!-}} {{!}} {{{7|}}} {{!}} {{{6|}}}}} {{#if:{{{8|}}}{{{9|}}}| {{!-}} {{!}} {{{9|}}} {{!}} {{{8|}}}}} {{#if:{{{10|}}}{{{11|}}}| {{!-}} {{!}} {{{11|}}} {{!}} {{{10|}}}}} {{#if:{{{12|}}}{{{13|}}}| {{!-}} {{!}} {{{13|}}} {{!}} {{{12|}}}}} |} </div><noinclude>{{Documentation}} [[Category:Templates]]</noinclude> qbrxzrga0p44keplm5v5b4n0uethbmt 10 518 8650 3161 2010-07-29T13:30:35Z Nemo bis 9 cat wikitext text/x-wiki <table class="noprint" style="margin:0px 10%; border: 1px solid #aaa; border-left: 10px solid #b22222; background: #fbfbfb;"> <tr> <td style="border: none; padding: 2px 0 2px 0.9em; text-align: center;"> [[File:Ambox deletion.png]] </td> <td style="padding: 0.25em 0.5em; width: 100%; border: none;">'''This page has been nominated for deletion{{#if:{{{soon|}}}|&nbsp;after a short period of time.''' This delay is intended to give the contributor time to modify the page to make it relevant. If it is relevant, please remove this tag.}}{{#if:{{{1|}}}|.&#32;The user who left this tag provided the following reason:<div style="margin-left:2em; background:#FFF;">{{{1}}}</div>|.}} If you object, remove the template and discuss on [[{{TALKPAGENAME}}|the talk page]].<br /><small>'''Administrators:''' Please check the <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=history}} page history], especially the [{{fullurl:{{FULLPAGENAME}}|diff=0}} last diff], before [{{fullurl:{{FULLPAGENAME}}|action=delete{{#if:{{{1|}}}|&wpReason={{urlencode:{{{1}}}}}|}}}} deleting]</span>.</small></td> </tr> </table> <includeonly>{{{category|[[Category:Deleteme]]}}}</includeonly><noinclude> ---- See [[:Category:Deleteme]] for articles that have been nominated for speedy deletion. [[category:Templates]] </noinclude> fqz9amw2b78jq2b60ojr0azrdt4m645 14 519 3566 2656 2009-10-15T18:22:15Z Guillom 13 [[Category:Wiki maintenance]] wikitext text/x-wiki These pages have been tagged for a deletion. An administrator should come along and delete the pages if required. [[Category:Wiki maintenance]] 5ldr15sovputnjygbx24ska52uq2l41 6 522 2683 2009-08-12T11:30:24Z Purodha 113 Screenshot of new edit toolbar advanced in http://translatewiki.net/ cropped, and with red selection marker with arrow for a proposed move of buttons. wikitext text/x-wiki Screenshot of new edit toolbar advanced in http://translatewiki.net/ cropped, and with red selection marker with arrow for a proposed move of buttons. m8y48biyr85nt92ort3fz1ph8lm3ro1 6 525 2727 2009-08-13T20:46:05Z Rei-artur 537 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 526 2744 2009-08-14T15:38:24Z HereToHelp 732 A ''rough'' mockup of an idea for a new arrangement of links and tabs. partially inspired by [[:File:Babaco-Mockup.png]]. Made entirely of screenshots of MediaWiki software and therefore assumed to present no legal issues. wikitext text/x-wiki A ''rough'' mockup of an idea for a new arrangement of links and tabs. partially inspired by [[:File:Babaco-Mockup.png]]. Made entirely of screenshots of MediaWiki software and therefore assumed to present no legal issues. nmdox5e2v4xvcrr5g60f57h47dawbjz 6 527 3134 2760 2009-09-16T21:46:10Z HereToHelp 732 uploaded a new version of &quot;[[File:Usability icons.png]]&quot;: New version wikitext text/x-wiki Mockup of icons for the toolbar. Self-made. Intended functions listed at [[:File:Usability icons.png/Answers]], but try to figure them out for yourself first. SVG version available at [[:File:Usability icons.svg]]. 6enmrfgdttvky6migvcaup2lu9iiw2v 6 528 3137 2752 2009-09-16T21:54:10Z HereToHelp 732 update wikitext text/x-wiki This is the key to [[:File:Usability icons.png|these icons]]. ==Version 1== # Italic # Bold # Strikethrough # Internal link # External link # Reference / footnote # Insert image # Decrease text size # Increase text size # Superscript # Subscript # Paragraph break <code><nowiki><br/></nowiki></code> # Bulletted list # Numbered list # Insert table # Insert redirect Conspicuously missing: insert signature ==Version 2 (9/16/09)== Top row: # Italic # Bold # Internal link # External link # Signature # Reference / footnote # Insert image # Bulletted list # Numbered list # Paragraph break <code><nowiki><br/></nowiki></code> Bottom row: # Strikethrough # Decrease text size # Increase text size # Superscript # Subscript # Fullscreen mode (functionality does not (yet) exist) # Insert redirect # Insert table # Ignore Wiki formatting <code><nowiki><nowiki></nowiki></nowiki></code> # Mathematical formula 6bll2b3hvftt5p9cxr7fva43ev7gqmr 6 529 3136 3135 2009-09-16T21:48:42Z HereToHelp 732 uploaded a new version of &quot;[[File:Usability icons.svg]]&quot;: Try this again… wikitext text/x-wiki Vector version of [[:File:Usability_icons.png]]. pd9z7zs1c5mkqm4fs8i3pzf71vhybv7 6 532 2776 2773 2009-08-14T19:00:59Z Trevor Parscal (WMF) 3 uploaded a new version of &quot;[[File:Design-LiquidThreads-1.png]]&quot;: Cropped out the browser stuff. wikitext text/x-wiki Mockups of proposed Liquid Threads UI. Designed by Trevor Parscal. 7jb1u0zufgq7afd3lhc29calatvhoi8 6 536 2816 2009-08-17T06:55:56Z Teofilo~usabilitywiki 173 Derivative of [[:File:Sidebar_cssjs.png]] wikitext text/x-wiki Derivative of [[:File:Sidebar_cssjs.png]] 8h43kc6gqf6do0q27e130g40cmnzqqe 6 537 2854 2009-08-18T22:37:34Z Trevor Parscal (WMF) 3 Photograph of whiteboard drawing by Trevor Parscal. wikitext text/x-wiki Photograph of whiteboard drawing by Trevor Parscal. dknzhs8odmi4fxg32v7h7otiyy8zmph 6 541 2875 2009-08-20T17:43:10Z Brooke Vibber 143 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 554 2972 2964 2009-08-31T16:11:53Z Michaeldsuarez 120 Redirecting. wikitext text/x-wiki #REDIRECT[[Main Page]] cbws0g69uruag9ohgl9a4xy7jnbao55 6 555 2977 2009-08-31T18:08:19Z FT2 412 Mockup of mini toolbar idea wikitext text/x-wiki Mockup of mini toolbar idea rbxa0u5mijxeh9ehzb621r2xmpj37p4 6 558 3000 2009-09-02T20:01:24Z Trevor Parscal (WMF) 3 Screenshot of content generation dialogs and navigable table of contents in action. wikitext text/x-wiki Screenshot of content generation dialogs and navigable table of contents in action. 987gxojoco7531mmuxbt3ddsup9w7m6 0 559 8629 5927 2010-07-29T13:17:21Z Nemo bis 9 cat wikitext text/x-wiki The second usabilty release, Babaco, enabled features such as Navigable table-of-contents and dialogues for inserting links, creating tables, and search and replace function since end of September 2009. These features will be enhanced with updated interactive user interface and precision of jumping to sections will be greatly improved on the release scheduled in the first week of February. Read [http://techblog.wikimedia.org/2010/01/babaco-enhancments/ more]. [[File:Babaco_ntoc_click.jpg|thumb|250px |Navigable Table of Contents]] * '''Navigable table-of-contents''' :A new feature in the editing interface which shows an article outline next to the textarea. This feature enables you to jump to sections of an article (e.g., the “Early Life” section of a biography) with a single click. The table of contents shows where in the article you are, making navigation while editing easier. You can resize or hide the table of contents from the textarea based on the type of editing or when the screen space is limited. <br style="clear: both;"/> [[File:Babaco_dialogs.pdf|thumb|250px |Dialogs]] * '''Dialogs''' :When creating links or tables, clicking the tool icon now opens a dialog box which will help you to create wiki-markup by filling out a simple form. There are several different types of dialogs. ::*'''Links:''' The new [[:Image:Babaco_link_dialog_example.jpg | link dialog]] allows you to more easily create links, both links to pages within the wiki (“internal links”) as well as link to other pages on the web (“external links”). When creating links, the link suggest feature automatically suggest internal pages based on what you’ve entered. ::*'''Tables:''' The [[:Image:Babaco_table_dialog.jpg| table dialog]] automatically generates wiki-text for tables based on a given width and height and lets you add a header row with one check of a box. ::*'''Search and replace:''' Also new in this release is the [[:Image:Babaco_search_replace.jpg | search and replace tool]] which enables users to search for text and replace while editing. <br style="clear: both;"/> [[File:Babaco_language_specific_icons.jpg|thumb|250px |Language-Specific Icons]] * '''Language-specific icons''' :We’ve added some language-specific icons for Bold and Italic to make them more intuitive. For example, '''B''' and ''I'' signify Bold and Italic in English, but '''N''' and ''C'' are used in Spanish. You can read more about the language-specific text format icons [[Text_format_icons|here]]. <br style="clear: both;"/> [[Category:Releases]] gutbhtztg91yl00s6tk169ik2to9zfw 0 560 10261 9215 2017-02-21T03:45:21Z Krinkle 709 prettytable=>wikitable wikitext text/x-wiki == Browser Compatibility Matrix for features in Babaco == You may also be interested in the [[Releases/Acai/Compatibility_Matrix|compatibility matrix]] for features in Acai. {|class="wikitable" !rowspan="2"|Browser&nbsp;<br/>Feature&nbsp; !colspan="5"|Internet Explorer !colspan="4"|Firefox !colspan="3"|Chrome !colspan="4"|Safari !colspan="5"|Opera !colspan="1"|Camino |- !width="30"|5.5 !width="30"|6 !width="30"|7 !width="30"|8 !width="30"|9 !width="30"|1 !width="30"|2* !width="30"|3 !width="30"|3.5 !width="30"|1 !width="30"|2 !width="30"|3 !width="30"|3 !width="30"|4 !width="30"|5 !width="30"|iP !width="30"|9 !width="30"|9.5 !width="30"|9.6 !width="30"|9.8 !width="30"|10 !width="30"|1.6 |- !rowspan="2"|Distribution |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:13.6%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:15.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:10.6%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.5%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:1.9%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:24.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:21.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:6.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.8%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.7%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:3.7%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:4.5%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.4%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:2.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |- |align="center"|<small>0.1%</small> |align="center"|<small>13.6%</small> |align="center"|<small>15.1%</small> |align="center"|<small>10.6%</small> |align="center"|<small>0.0%</small> |align="center"|<small>0.5%</small> |align="center"|<small>1.9%</small> |align="center"|<small>24.0%</small> |align="center"|<small>21.0%</small> |align="center"|<small>0.1%</small> |align="center"|<small>6.1%</small> |align="center"|<small>0.8%</small> |align="center"|<small>0.7%</small> |align="center"|<small>3.7%</small> |align="center"|<small>4.5%</small> |align="center"|<small>0.4%</small> |align="center"|<small>0.1%</small> |align="center"|<small>2.0%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |- |align="left"|'''Navigable TOC''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->-- |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 -->P |style="color:green"|<!-- C-1 -->P |style="color:green"|<!-- C-2 -->P |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->-- |style="color:green"|<!-- O-9.8 -->-- |style="color:green"|<!-- O-10 -->P |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Dialogs: Internal/External Links''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->-- |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 -->P |style="color:green"|<!-- C-1 -->-- |style="color:green"|<!-- C-2 -->-- |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->-- |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->-- |style="color:green"|<!-- O-9.8 -->-- |style="color:green"|<!-- O-10 -->P |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Dialogs: Insert Tables''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->-- |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 -->P |style="color:green"|<!-- C-1 -->-- |style="color:green"|<!-- C-2 -->-- |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->-- |style="color:green"|<!-- O-9.8 -->-- |style="color:green"|<!-- O-10 -->P |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Dialogs: Search and Replace''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:red"|<!-- IE-7 -->F |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->-- |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 -->P |style="color:green"|<!-- C-1 -->-- |style="color:green"|<!-- C-2 --> -- |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->-- |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->-- |style="color:green"|<!-- O-9.8 -->-- |style="color:green"|<!-- O-10 -->-- |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Watch/Unwatch''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 --> P |style="color:green"|<!-- C-1 --> P |style="color:green"|<!-- C-2 --> P |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->P |style="color:green"|<!-- O-9.8 -->P |style="color:green"|<!-- O-10 -->P |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Collapsing Tabs''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 --> P |style="color:green"|<!-- C-1 --> P |style="color:green"|<!-- C-2 --> P |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->P |style="color:green"|<!-- O-9.8 -->P |style="color:green"|<!-- O-10 -->P |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Search Suggestions''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 -->P |style="color:green"|<!-- IE-8 -->P |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 -->P |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 --> P |style="color:green"|<!-- C-1 --> P |style="color:green"|<!-- C-2 --> P |style="color:green"|<!-- C-3 -->P |style="color:green"|<!-- S-3 -->P |style="color:green"|<!-- S-4 -->P |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 -->P |style="color:green"|<!-- O-9.8 -->P |style="color:green"|<!-- O-10 -->P |style="color:green"|<!-- C-1.6 -->P |- |align="left"|'''Collapsible Templates''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |<!-- IE-7 --> -- |<!-- IE-8 --> -- |<!-- IE-9 --> -- |<!-- FF-1 --> -- |<!-- FF-2 --> -- |style="color:green"|<!-- FF-3 -->P |style="color:green"|<!-- FF-3.5 --> P |<!-- C-1 --> -- |<!-- C-2 --> -- |<!-- C-3 --> -- |<!-- S-3 --> -- |<!-- S-4 --> -- |style="color:green"|<!-- S-5 -->P |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |<!-- O-9.6 --> -- |<!-- O-9.8 --> -- |<!-- O-10 --> -- |<!-- C-1.6 --> -- |} Estimated browser distribution based on information from w3schools.com as of August 2009 [http://www.w3schools.com/browsers/browsers_stats.asp] {|class="wikitable" !Mark !Description |- |style="color:green"|P |Pass: Renders and functions properly |- |style="color:red"|F |Fail: Does not render or function properly |- |style="color:blue"|XF |Expected Fail: Does not render or function properly, but is not expected to due to expected browser limitations |- |style="color:orange"|RF |RTL Fail: Renders and functions properly in left to right mode, but not in right to left (as seen on our http://prototype.wikimedia.org/ar ). |- |style="color:black"|-- |For the browsers which were not part of the test |- |style="color:black"|* |For Firefox 2.0.0.5 and above |} == How can I help? == We need more people to follow our [[#Testing Procedure|testing procedure]] and report back to us on their experiences. Uploading screenshots and adding information to the [[Talk:Releases/Babaco/Compatibility Matrix|discussion page]] is a great way to help us out! == Testing Procedure == * Visit prototype.wikimedia.org [http://prototype.wikimedia.org/en.wikipedia.org/Main_Page] [[File:Releases-Babaco-Navigable-TOC.png|thumb|300px]] '''Navigable Table of Contents''' * Visit featured article [http://prototype.wikimedia.org/en.wikipedia.org/Manchester_Small-Scale_Experimental_Machine] * Click edit [http://prototype.wikimedia.org/en-wp/index.php?title=Manchester_Small-Scale_Experimental_Machine&action=edit] * Verify the table of contents matches the content of the article * Verify clicking on the links in the table of contents scrolls the textarea and moves the cursor to the right place * Verify that moving the cursor from one section to another causes the various sections to be highlighted in the table of contents <div style="clear:both"></div> [[File:Releases-Babaco-Internal-Link-Dialog.png|thumb|300px]] '''Internal Links''' * Move the cursor to the end of the article * Click the link icon * Verify that a dialog appears titled "Insert link" * Verify that entering the letter "A" causes the link suggestions box to display a list of articles beginning with the letter "A" and the status icon become orange (there is no article for the letter A) * Verify that clicking one of the suggestions causes the field to be filled with the article's title and the status icon become green (there is an article with that title). * Change the value of the link text field * Click the button labeled "Insert" * Verify that the dialog closed and the expected wiki-text was inserted after the cursor <div style="clear:both"></div> [[File:Releases-Babaco-External-Link-Dialog.png|thumb|300px]] '''External Links''' * Move the cursor to the end of the article * Click the link icon * Verify that a dialog appears titled "Insert link" * Click the "To an external web page" tab * Verify the contents of the dialog changed to include a field labeled "Link URL" * Add "en.wikipedia.org" (or any other URL) to the value of the link URL field * Add "Wikipedia" (or any other text) to the value of the link text field * Click the button labeled "Insert" * Verify that the dialog closed and the expected wiki-text was inserted after the cursor <div style="clear:both"></div> [[File:Releases-Babaco-Table-Dialog.png|thumb|300px]] '''Tables''' * Click the advanced toolbar section tab (if the section is not already visible) * Move the cursor to the end of the article * Click the table icon * Verify that a dialog appears titled "Insert table" * Click the checkbox labeled "Include header row" * Click the button labeled "Insert" * Verify that the dialog closed and the expected wiki-text was inserted after the cursor <div style="clear:both"></div> [[File:Releases-Babaco-Search-And-Replace-Dialog.png|thumb|300px]] '''Search and Replace''' * Click the search and replace icon * Verify that a dialog appears titled "Search and replace" * Enter "Williams" (or any other string contained in the document) to the field labeled "Search for" * Enter "TESTING" (or any other string different from the value of the search for field) to the field labeled "Replace with" * Click the button labeled "Replace" * Verify that the dialog closed and the all instances of the value of the search for field have been replaced with the value of the replace with field <div style="clear:both"></div> rkkpjf6i3bobyz3amzxsn9qnantncds 6 561 3014 2009-09-02T21:10:08Z Trevor Parscal (WMF) 3 Screenshot of how Babaco's external link dialog should look. wikitext text/x-wiki Screenshot of how Babaco's external link dialog should look. 6jmnk42vhtormklvuczjxstaw9bd8nd 6 562 3015 2009-09-02T21:10:24Z Trevor Parscal (WMF) 3 Screenshot of how Babaco's internal link dialog should look. wikitext text/x-wiki Screenshot of how Babaco's internal link dialog should look. s5hr5gvta98jambkgchlq5ivlo1iqsw 6 563 3016 2009-09-02T21:10:44Z Trevor Parscal (WMF) 3 Screenshot of how Babaco's navigable table of contents should look. wikitext text/x-wiki Screenshot of how Babaco's navigable table of contents should look. coluh7t9icdrv7hwf0zu9mkkkce3tlv 6 564 3017 2009-09-02T21:11:06Z Trevor Parscal (WMF) 3 Screenshot of how Babaco's search and replace dialog should look. wikitext text/x-wiki Screenshot of how Babaco's search and replace dialog should look. 83c3p75qhrizzwsh88pfbzsfp05jc8e 6 565 3018 2009-09-02T21:11:21Z Trevor Parscal (WMF) 3 Screenshot of how Babaco's table dialog should look. wikitext text/x-wiki Screenshot of how Babaco's table dialog should look. 8jpr89dymr2rwzkxqwigdescdlvi8d5 6 573 3080 2009-09-12T17:20:34Z Tgr 14 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 574 3083 2009-09-12T20:01:36Z Shuhari 4 Screen shot of Preference Statistics of English Wikipedia on September 12th, 2009 wikitext text/x-wiki Screen shot of Preference Statistics of English Wikipedia on September 12th, 2009 told517baxavbqa6tc3zthgcld17rxw 0 575 3130 3129 2009-09-16T20:06:51Z 69.17.48.227 /* Domain */ wikitext text/x-wiki ==Tags for Code Review== We'll use these tags on our Babaco code commits to categorize what that particular commit did [http://www.mediawiki.org/wiki/Special:Code/MediaWiki MediaWiki commit history] ===Type=== *'''bugfix''' - we were trying to accomplish X via method Y; the code didn't do method Y correctly, now it does *'''designfix'''- we were trying to accomplish X via method Y; method Y doesn't actually accomplish X, so we changed it to method Z ===Domain=== * '''visual''' - changes the look *'''functional''' - changes the way it functions *'''enhancement''' - does something new ===Importance (optional)=== *'''minor''' - we can get by if it's not included immediately *'''critical''' - we ''can't'' get by if it's not included immediately ==Usage== Just add 'bugfix, visual' to the commit message, for example, or 'critical, designfix, functional' etc. p8ptxb5z8tlo5o3mmn5dwhwqs6m0l33 10 578 8640 3183 2010-07-29T13:27:50Z Nemo bis 9 cat wikitext text/x-wiki <div style=" clear: both; margin: 1em 0 0 0; border: 1px solid #aaa; background-color: #ecfcf4; padding: 5px; "> {{#ifeq:{{{heading|μ}}}|<!--**DEFINED BUT EMPTY**--> |<!--**NOTHING**--> |<div style="padding-bottom:3px; border-bottom: 1px solid #aaa; margin-bottom:1ex">{{#ifeq:{{{content|μ}}}|μ |<span class="editsection plainlinks" id="doc_editlinks">{{#ifexist: {{{1|{{Documentation/docname}}}}} |<!--** /doc EXISTS** -->[[{{fullurl:{{{1|{{Documentation/docname}}}}}|action=edit}} edit]] [{{purge|purge}}] |<!--**/doc DOESN'T EXIST**-->[[{{fullurl:{{{1|{{Documentation/docname }}}}}|action=edit&preload=Template:Documentation/preload}} create]] [{{purge|purge}}] }}</span> }} <span style="{{#if:{{{heading-style|}}}|{{{heading-style}}}|{{#ifeq:{{NAMESPACE}}|{{ns:template}}|font-weight: bold; font-size: 125%|font-size: 150%}}}}">{{#if:{{{heading|}}}|{{{heading}}}|{{#ifeq:{{NAMESPACE}}|{{ns:template}}|[[Image:Template-info.svg|50px|link=]] Template documentation|Documentation}}}}</span></div> }}<!-- --><div id="template_doc_page_transcluded" class="dablink plainlinks"><!-- -->{{#ifexist: {{{1|{{Documentation/docname}}}}} |<!--**/doc EXISTS**-->This [[Wikipedia:Template documentation|documentation]] is [[Wikipedia:Transclusion|transcluded]] from [[{{{1|{{Documentation/docname}}}}}]]. <small style="font-style: normal">([{{fullurl:{{{1|{{Documentation/docname}}}}}|action=edit}} edit] &#124; [{{fullurl:{{{1|{{Documentation/docname}}}}}|action=history}} history])</small><br /> }}<!-- -->{{#switch: {{SUBPAGENAME}} |sandbox|testcases=<!--**DO NOT SHOW THESE LINKS ON THE SANDBOX/TESTCASES PAGES**--> |#default= {{#switch: {{SUBJECTSPACE}} |{{ns:template}} |{{ns:user}}= {{#ifexist: {{FULLPAGENAME}}/sandbox |This template has a [[/sandbox|sandbox]] <small style="font-style: normal">([{{fullurl:{{ #rel2abs: /sandbox }}|action=edit}} edit])</small> <!-- -->{{#ifexist: {{FULLPAGENAME}}/testcases |and [[/testcases|testcases]] <small style="font-style: normal">([{{fullurl:{{ #rel2abs: /testcases }}|action=edit}} edit])</small>}} for editors to experiment. |{{#ifexist: {{FULLPAGENAME}}/testcases |This template has [[/testcases|testcases]] <small style="font-style: normal">([{{fullurl:{{ #rel2abs: /testcases }}|action=edit}} edit])</small> for editors to experiment.}} }}}}}} </div> {{#if:{{{content|}}}|{{{content}}}|{{#ifexist:{{{1|{{Documentation/docname}}}}} | {{ {{{1|{{Documentation/docname}}}}} }} }}}} <div style="clear: both;"></div> </div><noinclude> [[Category:Templates]]</noinclude> npyh1salm2gwp70nlqq2g3p0m1j1ggw 10 579 6783 3177 2010-05-02T19:30:09Z Koavf 22 redlinks wikitext text/x-wiki {{#switch: {{SUBPAGENAME}} |sandbox|testcases={{ #rel2abs: ../doc }} |#default={{SUBJECTPAGENAME}}/doc }} 53u96v0tgu0wxkisr5zbsk971xu3cjn 10 580 8648 3178 2010-07-29T13:30:09Z Nemo bis 9 cat wikitext text/x-wiki <includeonly><span style="font-family:monospace;"><nowiki>{{</nowiki>{{#if:{{{subst|}}}|[[Help:Substitution|subst]]:}}[[{{{LANG|}}}{{{SISTER|}}}{{ns:Template}}:{{{1|}}}|{{{1|}}}]]<!-- -->{{#if:{{{2|}}}| &#124;{{{2}}} }}<!-- -->{{#if:{{{3|}}}| &#124;{{{3}}} }}<!-- -->{{#if:{{{4|}}}| &#124;{{{4}}} }}<!-- -->{{#if:{{{5|}}}| &#124;{{{5}}} }}<!-- -->{{#if:{{{6|}}}| &#124;{{{6}}} }}<!-- -->{{#if:{{{7|}}}| &#124;{{{7}}} }}<!-- -->{{#if:{{{8|}}}| &#124;{{{8}}} }}<!-- -->{{#if:{{{9|}}}| &#124;{{{9}}} }}<!-- -->{{#if:{{{10|}}}| &#124;{{{10}}} }}<!-- -->{{#if:{{{11|}}}| &#124;{{{11}}} }}<!-- -->{{#if:{{{12|}}}| &#124;''...'' }}<nowiki>}}</nowiki></span></includeonly><noinclude> [[Category:Templates]] {{documentation}}</noinclude> qpsa2lewvx38v42wryti2pcc0k5fe4m 10 581 8647 3179 2010-07-29T13:29:51Z Nemo bis 9 cat wikitext text/x-wiki <code style="white-space:nowrap;">{{#switch:{{{2|pair}}} |close |single = <!--nothing--> |open |pair |#default = &lt;{{{1|tag}}}{{#if:{{{params|}}}|&#32;{{{params}}}}}&gt; }}{{#switch:{{{2|pair}}} |open |close |single = <!--nothing--> |pair |#default = {{{content|}}} }}{{#switch:{{{2|pair}}} |open |single = <!--nothing--> |close |pair |#default = &lt;&#47;{{{1|tag}}}&gt; }}{{#switch:{{{2|pair}}} |single = &lt;{{{1|tag}}}{{#if:{{{params|}}}|&#32;{{{params}}}}}&#47;&gt; }}</code><noinclude> {{documentation}} [[category:Templates]] </noinclude> 2uztvw7a0edp8ox218sxl4iua85nup7 10 582 9188 3180 2010-10-26T23:44:09Z Guillom 13 cleanup wikitext text/x-wiki __NOTOC__ This template automatically displays a documentation box like you are seeing now, of which the content is transcluded from another page. It is intended for pages which are [[Wikipedia:Transclusion|transcluded]] in other pages, i.e. templates, whether in the template namespace or not. == Usage == === Normal /doc === &lt;noinclude&gt;&#123;&#123;{{{template-name|Documentation}}}&#125;&#125;&lt;/noinclude&gt; === Any /doc page === &lt;noinclude&gt;&#123;&#123;{{{template-name|Documentation}}}|Template:any page/doc&#125;&#125;&lt;/noinclude&gt; === In-line content === &lt;noinclude&gt;&#123;&#123;{{{template-name|Documentation}}}|content=This is documentation.&#125;&#125;&lt;/noinclude&gt; === In-line content with [view][edit] links === &lt;noinclude&gt;&#123;&#123;{{{template-name|Documentation}}} |1 = Template:any page/doc |content =&#123;&#123;Template:any page/doc|parameters}} }}&lt;/noinclude> === Best practice === This code should be added at the bottom of the template code, with no extra space before "<code>&lt;noinclude></code>" (which would cause extra space on pages where the template is used). The parameter can be used as shown above to transclude an arbitrary documentation page. Categories and interwiki links that apply to the template itself should be added to the documentation page, inside <code>&lt;includeonly> &lt;/includeonly></code> tags. If the documentation page contains includeonly or noinclude tags as part of the documentation, replace the "<" with "&amp;lt;". === Customizing display === Overrides exist to customize the output in special cases: * <code>{&#123;documentation| '''heading''' = ...}}</code> − change the text of the "documentation" heading. If this is set to blank, the entire heading line (including the first [edit] link) will also disappear. == Functions == If the documentation page doesn't exist, the "edit" link includes a [[mw:Manual:Creating pages with preloaded text|preload]] parameter so that clicking it will pre-fill the edit form with the basic documentation page format. == Rationale == Use of this template allows templates to be [[Wikipedia:Protection policy|protected]] where necessary, while allowing anyone to edit the documentation, categories, and interwiki links. <includeonly> [[Category:Template documentation| ]] </includeonly> nkdiigt9uqa3pfo4ysrwplcj3cj8nig 10 583 3181 2009-09-20T20:44:11Z ChyranandChloe 407 created page wikitext text/x-wiki === Usage === === See also === <include<includeonly></includeonly>only> <!-- CATEGORIES AND INTERWIKIS HERE, THANKS --> </include<includeonly></includeonly>only> a1dfnyjsswvfz53zthhhl08479edvoc 10 584 8654 3182 2010-07-29T13:31:22Z Nemo bis 9 cat wikitext text/x-wiki <span class="noprint plainlinks purgelink">[{{fullurl:{{{page|{{FULLPAGENAME}}}}}|action=purge}} <span title="Purge this page">{{{1|Purge}}}</span>]</span><noinclude> [[Category:Templates]]</noinclude> pq0ilea5fdsiu460rlz69c640ajv0de 10 585 3184 2009-09-20T20:53:57Z ChyranandChloe 407 created page wikitext text/x-wiki |<noinclude>{{Documentation}}</noinclude> 2ofv2tfg465cdzm0n3gl7w1r0r77s1o 10 586 3185 2009-09-20T20:54:06Z ChyranandChloe 407 created docs wikitext text/x-wiki === Usage === This is the <nowiki>{{!}}</nowiki> meta-template. This is an auxiliary template allowing the encoding of "<code>|</code>" within template parameters. It is necessary if the character is used in wiki table syntax, or if the parameter is automatically wikilinked and you wish to use a pipe to specify different link text from the target page name. In other cases it is better to use "<code>&amp;#124;</code>". This template cannot be used for putting the character as text in a wiki table; in that case, again, "<code>&amp;#124;</code>" can be used. Note that no special template is needed for "<code>!</code>" (exclamation mark). This is a '''high risk template''', and it usually cannot be [[WP:SUBST|substituted]] (see conditions for substing on [[#Substitution|the section below]]). === Substitution === The template page states that <nowiki>{{!}}</nowiki> cannot be substituted. That's not completely true because it is perfectly okay to [[Wikipedia:Substitution|substitute]] <nowiki>{{!}}</nowiki> as soon as an unescaped "'''<tt>|</tt>'''" works as expected, i.e. after substituting the template containing <nowiki>{{!}}</nowiki>, or after eliminating an [[mw:Help:Extension:ParserFunctions#.23if:|#if:]] containing <nowiki>{{!}}</nowiki>. <includeonly> <!-- CATEGORIES AND INTERWIKIS HERE, THANKS --> </includeonly> 1z3s905z4a2tiy77ocw7tp4xpua64ii 10 587 3188 2009-09-20T21:04:48Z ChyranandChloe 407 created template wikitext text/x-wiki |-<noinclude> {{documentation}} </noinclude> 2zsavivng30v2w46mrxq9i40e1wnnr8 10 588 8649 3204 2010-07-29T13:30:23Z Nemo bis 9 cat wikitext text/x-wiki <div style=" float:right; clear:right; border:solid 1px #9accf6; background:#f1f9ff; padding:1em; padding-top:0.5em; padding-bottom:0.5em; width:20em; color:black; margin-bottom: .2em; margin-left: .5em; "> <span style="font-size:1.2em;">'''Archives'''</span> {| cellpadding="0" width="100%" style="text-align: center; background-color: transparent; font-size:.9em;" {{#ifexist:{{#rel2abs:./Archive 1|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 1|{{{root|}}}}}|Archive 1]] {{!}} {{#ifexist:{{#rel2abs:./Archive 2|{{{root|}}}}} | [[{{#rel2abs:./Archive 2|{{{root|}}}}}|Archive 2]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 3|{{{root|}}}}} | [[{{#rel2abs:./Archive 3|{{{root|}}}}}|Archive 3]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 4|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 4|{{{root|}}}}}|Archive 4]] {{!}} {{#ifexist:{{#rel2abs:./Archive 5|{{{root|}}}}} | [[{{#rel2abs:./Archive 5|{{{root|}}}}}|Archive 5]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 6|{{{root|}}}}} | [[{{#rel2abs:./Archive 6|{{{root|}}}}}|Archive 6]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 7|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 7|{{{root|}}}}}|Archive 7]] {{!}} {{#ifexist:{{#rel2abs:./Archive 8|{{{root|}}}}} | [[{{#rel2abs:./Archive 8|{{{root|}}}}}|Archive 8]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 9|{{{root|}}}}} | [[{{#rel2abs:./Archive 9|{{{root|}}}}}|Archive 9]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 10|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 10|{{{root|}}}}}|Archive 10]] {{!}} {{#ifexist:{{#rel2abs:./Archive 11|{{{root|}}}}} | [[{{#rel2abs:./Archive 11|{{{root|}}}}}|Archive 11]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 12|{{{root|}}}}} | [[{{#rel2abs:./Archive 12|{{{root|}}}}}|Archive 12]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 13|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 13|{{{root|}}}}}|Archive 13]] {{!}} {{#ifexist:{{#rel2abs:./Archive 14|{{{root|}}}}} | [[{{#rel2abs:./Archive 14|{{{root|}}}}}|Archive 14]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 15|{{{root|}}}}} | [[{{#rel2abs:./Archive 15|{{{root|}}}}}|Archive 15]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 16|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 16|{{{root|}}}}}|Archive 16]] {{!}} {{#ifexist:{{#rel2abs:./Archive 17|{{{root|}}}}} | [[{{#rel2abs:./Archive 17|{{{root|}}}}}|Archive 17]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 18|{{{root|}}}}} | [[{{#rel2abs:./Archive 18|{{{root|}}}}}|Archive 18]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 19|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 19|{{{root|}}}}}|Archive 19]] {{!}} {{#ifexist:{{#rel2abs:./Archive 20|{{{root|}}}}} | [[{{#rel2abs:./Archive 20|{{{root|}}}}}|Archive 20]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 21|{{{root|}}}}} | [[{{#rel2abs:./Archive 21|{{{root|}}}}}|Archive 21]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 22|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 22|{{{root|}}}}}|Archive 22]] {{!}} {{#ifexist:{{#rel2abs:./Archive 23|{{{root|}}}}} | [[{{#rel2abs:./Archive 23|{{{root|}}}}}|Archive 23]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 24|{{{root|}}}}} | [[{{#rel2abs:./Archive 24|{{{root|}}}}}|Archive 24]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 25|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 25|{{{root|}}}}}|Archive 25]] {{!}} {{#ifexist:{{#rel2abs:./Archive 26|{{{root|}}}}} | [[{{#rel2abs:./Archive 26|{{{root|}}}}}|Archive 26]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 27|{{{root|}}}}} | [[{{#rel2abs:./Archive 27|{{{root|}}}}}|Archive 27]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 28|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 28|{{{root|}}}}}|Archive 28]] {{!}} {{#ifexist:{{#rel2abs:./Archive 29|{{{root|}}}}} | [[{{#rel2abs:./Archive 29|{{{root|}}}}}|Archive 29]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 30|{{{root|}}}}} | [[{{#rel2abs:./Archive 30|{{{root|}}}}}|Archive 30]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 31|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 31|{{{root|}}}}}|Archive 31]] {{!}} {{#ifexist:{{#rel2abs:./Archive 32|{{{root|}}}}} | [[{{#rel2abs:./Archive 32|{{{root|}}}}}|Archive 32]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 33|{{{root|}}}}} | [[{{#rel2abs:./Archive 33|{{{root|}}}}}|Archive 33]]}} {{!}}- }} {{#ifexist:{{#rel2abs:./Archive 34|{{{root|}}}}} | {{!}} [[{{#rel2abs:./Archive 34|{{{root|}}}}}|Archive 34]] {{!}} {{#ifexist:{{#rel2abs:./Archive 35|{{{root|}}}}} | [[{{#rel2abs:./Archive 35|{{{root|}}}}}|Archive 35]]}} {{!}} {{#ifexist:{{#rel2abs:./Archive 36|{{{root|}}}}} | [[{{#rel2abs:./Archive 36|{{{root|}}}}}|Archive 36]]}} {{!}}- }} |} {{#tag:inputbox| bgcolor=transparent type=fulltext prefix={{#if:{{{root|}}}|{{{root}}}|{{FULLPAGENAME}}}}/ break={{#if:{{{search-break|}}}|{{{search-break}}}|no}} width={{#if:{{{search-width|}}}|{{{search-width}}}|22}} searchbuttonlabel={{#if:{{{search-button-label|}}}|{{{search-button-label}}}|Search}} }} </div><noinclude> [[Category:Templates]] {{Documentation}}</noinclude> 1b9462uqo6b1iiznliau3wnwwhwvwbo 0 597 9377 8623 2013-01-23T01:18:34Z Krinkle 709 wikitext text/x-wiki This is the page about the project to enable template calls on MediaWiki pages to be editable by their own forms. This project is distinct from extensions such as [http://www.mediawiki.org/wiki/Extension:Semantic_Forms Semantic Forms], which allows for editing an entire page using a form; instead, each template call would be editable independently, using a pop-up form in the "edit" page. The main inspiration for this project is the [http://de.wikipedia.org/wiki/Wikipedia:Helferlein/Vorlagen-Meister Vorlagen-Meister] (template handler or, literally, "template master") gadget on the German Wikipedia. In that system, each template is responsible for defining its own field structure, in XML form, on the ".../XML" subpage of the template's own page. Here is one example of such an XML file on the German Wikipedia: http://de.wikipedia.org/wiki/Vorlage:Infobox_Band/XML . When a user with this gadget enabled goes to edit a page that includes a call to such a template, they can right-click on the call in order to pop up a form, containing a text entry for each field in the template; if they submit this form, the changes they made in the form show up in the source code. Note that this editing can be done for every template, not just the infobox ones; here, for example, is the XML page for the "internetquelle" template, which looks like the German equivalent of the English "web cite": http://de.wikipedia.org/wiki/Vorlage:Internetquelle/XML. Under the current plan, the template forms project for Wikimedia would re-use some of the XML structure of the Vorlagen-Meister gadget. There would be a few key differences, however: * the feature would be implemented in PHP and Javascript, not strictly in Javascript * it would be enabled by default for every user * additionally, by default every template call would show up on the edit page as "minimized" in some way; see "Interface for editing template calls", below * the XML definition for templates would be located directly in template pages * additional input types could be defined by other extensions; a map input type, for geographical coordinates, is an obvious candidate for an extension-based type * there would be support for internationalization of the strings used within each form: the label and descriptive text for each field, and, in the case of "enumerated" inputs, i.e. those with a set of recommended values (such as appears with a dropdown input), possibly also those values (not the actual string that would show up in the template call, just what's displayed in the form). If an XML file does not exist for a given template, or one exists but it is not parseable, a button will still appear in place of the template call; but when the button is pressed, the system will instead either display a simple textbox for editing the template call; or parse the template itself and display a "best-guess" form for editing the call, based on the fields contained in the template. Of these, the former seems more viable, on the theory that it's better to have a cumbersome interface than an incorrect one. ==Interface for editing template calls== By default, the textarea in the edit page would be replaced by a Javascript-enabled edit box that (1) did syntax highlighting, and (2) turned template calls into clickable rectangles. The edit box would basically look like a standard [http://en.wikipedia.org/wiki/Comparison_of_JavaScript-based_source_code_editors Javascript-based source code editor], like CodeMirror or CodePress; [http://code.google.com/apis/ajax/playground/ see here] for an example of CodeMirror in action. The template calls, on the other hand, might look like [http://galactica.wikia.com/index.php?title=Battlestar_Galactica_Re-Imagined&action=edit this example] from Wikia; note that the "stub" button at the top of the page represents a call to the "stub" template. Clicking on this button would bring up a window that might contain both a form for editing the call and a way to edit the call's wiki-text directly. ==Specification structure== The template specification has to handle translation in one way or another. Since the proposed first usage of this system is on [http://commons.wikimedia.org/wiki/Main_Page Wikimedia Commons], which is meant to support all languages, this is a very relevant issue. The plan is for as much of the form to be translateable as possible: field labels, field description messages, and possibly values as well, in the case of enumerated fields (like dropdowns). Here is the proposed XML structure, for a simple template that contains two parameters: "author" and "license" (information that appears on Wikimedia Commons): <source lang="xml"> <templateinfo> <group id="main"> <param id="author"> <label> <msg language="en">Author</msg> ... </label> <description> <msg language="en">The creator of this image; preferably a link to a user page</msg> ... </description> </param> <param id="license"> <label> <msg language="en">License</msg> ... </label> <description> <msg language="en">The license under which this image will be published</msg> ... </description> <options> <option name="CC-by"> <msg language="en">Creative Commons Attribution</msg> ... </option> <option name="CC-by-sa"> <msg language="en">Creative Commons Attribution-Share Alike</msg> ... </option> </options> </param> </group> </templateinfo> </source> The presence of ellipses (...) indicates where other language translations could go. The <nowiki>"<group>"</nowiki> tag is used to specify groupings of fields within the form; this could, for instance, lead to all fields in one group being put into one HTML "fieldset". ===Untranslated values=== The structure should also support elements in only one language, with no translation provided. There, in place of a series of <nowiki><msg></nowiki> tags, there would simply be a string literal. In other words, instead of: <source lang="xml"> <description> <msg language="en">The license under which this image will be published</msg> ... </description> </source> It would simply be: <source lang="xml"> <description>The license under which this image will be published</description> </source> ===Defining data type=== A planned enhancement for this structure is to also allow for defining the data type or class of a specific template parameter. This would be accomplished through a "<nowiki><type></nowiki>" tag, enclosed within the "<nowiki><param></nowiki>" tag. A simple call to this tag could look like: <source lang="xml"> <type name="Number" /> </source> ...while a more complex call could look like: <source lang="xml"> <type name="Datetime"> <field name="date format">DD MM YYYY HH MI SS AM</field> </type> </source> ===Defining the interface and display=== The above specification does not allow for defining anything about the display of the form, including which form input types should be used, and specific display settings for both the inputs and the text. For all those, it is proposed that other tools and applications can define additional data, by using the "<nowiki><data></nowiki>" tag, which itself is split up via tags called "<nowiki><field></nowiki>"; this tag can be defined within three other tags: "<nowiki><templateinfo></nowiki>", "<nowiki><group></nowiki>" and "<nowiki><param></nowiki>", depending on whether they modify the entire form, a field/parameter group, or a single field/parameter. This would allow individual tools and applications, both browser-based and otherwise, to define whatever interface settings they wanted for each parameter/form field. Here, for example, is a theoretical call for the "license" parameter defined above: <source lang="xml"> <param id="license"> ... <data app="stevesbot"> <field name="inputtype">Radiobutton</field> <field name="cssclass">spiffy-radiobutton</field> </data> <data app="AcmeIPhoneApp"> <field name="widget">Option selector</field> <field name="labelColor">Green</field> </data> </param> </source> Within the Template Forms code, a hook would be provided to enable tools and applications to modify the display of each field in the form, based on that tool's (or any other's) display settings. ===Document Type Definition=== Here is the Document Type Definition (DTD), created by Trevor Parscal, for the proposed XML format: <source lang="xml"> <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE template [ <!ELEMENT template (description?,params?,data*)> <!ELEMENT templateinfo (param|group)*> <!ELEMENT params (param|group)*> <!ELEMENT param (label?,description?,options?,type?,data*)> <!ATTLIST param id ID #REQUIRED> <!ELEMENT group (label?,description?,param*,data*)> <!ELEMENT label (#PCDATA|msg)*> <!ELEMENT description (#PCDATA|msg)*> <!ELEMENT options (option*)> <!ELEMENT option (#PCDATA|msg)*> <!ELEMENT type (field*)> <!ATTLIST type name CDATA #REQUIRED> <!ELEMENT field (#PCDATA)> <!ATTLIST field name CDATA #REQUIRED> <!ELEMENT msg (#PCDATA)> <!ATTLIST msg lang CDATA #REQUIRED> <!ELEMENT data (field*)> <!ATTLIST data app CDATA #REQUIRED> ]> </source> ==Technical implementation== The current plan is for this functionality to get implemented in two parts: a new extension, [http://www.mediawiki.org/wiki/Extension:TemplateInfo TemplateInfo], and additions to the [http://www.mediawiki.org/wiki/Extension:UsabilityInitiative UsabilityInitiative] extension. The TemplateInfo extension is responsible for defining two things, both implemented in PHP: * a tag function, <nowiki><templateinfo></nowiki>, that takes in the rest of the XML and handles display, transclusion and usage of it in an appropriate manner. * an additional action for the MediaWiki API so that the XML definition can easily be retrieved via API for a given template; this action will also validate the XML, and return a helpful error message if it's invalid. The actual display of the form will be handled entirely in Javascript, using the jQuery library, within the UsabilityInitiative code. Any feedback or questions about this proposal are welcome on the talk page. [[Category:Features]] dy2rc3aiesep9tedcd131dor3ozp2zi 0 600 6781 3286 2010-05-02T19:29:52Z Koavf 22 redlinks wikitext text/x-wiki This page tries to help and offer tips to the user that employs a [[w:smartphone|smartphone]] and other [[w:mobile device|mobile device]]s in Wikipedia. == Viewing== Mobile devices have a narrow viewport, compared with a computer. If you are a registered user, you go to "my preferences" to make reading more easy. In appearence, you can select '''Chick''' or '''Myskin''' (MonoBook is the default non-mobile devices) and also mark "enable jump to accessibility links". You cannot use yet a skin that includes views, personal tool and search in the page top. In gadgets, you can mark "focus the cursor in the search bar on loading the [[Main Page]]". == Editing == In some mobile devices [[w:carriage return|carriage return]] does not properly work. To avoid this, you can use a tip: click in the "insert headline" button in the [[w:wikipedia:toolbars|edit toolbar]], a carriage return and "== Headline text ==" are included. Delete the text and conserve the carriage return. Sometimes, and specially when the page is long, some sections can disappear after editing and the article can be cut. To avoid it, go to My Preferences and mark in Gadgets "Add an edit link to the [[w:Wikipedia:Lead section|lead section]] of the page". Then, only edit the section that you want to modify. Also facilitates the edition mark "Move edit link next to the section headers", because of the narrow viewport in the mobile devices. To include links to categories, articles, templates, external pages and so on, you can select "wikimarkup" instead of "insert". == See also== * [[W:Wikipedia:Mobile access|Wikipedia:Mobile access]] * [[w:Village pump|Village pump]] anlujqsx6cness9jek3li4lifst01m2 0 604 8848 8731 2010-09-01T15:06:21Z 212.42.176.45 /* Forward to a friend */ new section wikitext text/x-wiki __NEWSECTIONLINK__ *<big>To discuss the Vector skin or anything else go to [[Talk:Prototype]].</big> *<big>To discuss the current Toolbar go to [[Toolbar]].</big> == Watch + Unwatch (as Icons) == In the Babaco Design phase, we have been updating existing toolbar icons and developing new ones. In attempting to pull "watch" & "unwatch" out of drop down menu and up to the always-visible tab level, we are considering representing this with icons as well. We have prototyped this [http://prototype.wikimedia.org/en.wikipedia.org/ here]. We are interested in hearing your opinion on this change. We are interested in the use of icon, the icon itself, and we are also particularly interested in your feedback on the animation we have employed while the server calls are being made. :* I like the animation, and displaying the difference between watched and unwatched with colors. :* The icon itself is nice, but the star could be confused with the star for Featured articles as used for instance in en:wikipedia articles like [http://en.wikipedia.org/wiki/Autism en:Autism] :** Indeed. Maybe we could use a bookmark symbol instead. --[[User:Mephiles602|Mephiles602]] 17:36, 17 October 2009 (UTC) :* a bug: The hint text for adding and removing is both the same. On previous versoins you could see it by the Text Watch/Unwatch. I just noticed the hint text in the past was the same as well, but with only a difference in color you need a different hint-text. :* On the prototype the Move fuction is not available. Together with other (adminstrator) fuctions like Delete and Protect you still need a drop down menu. [[User:HenkvD|HenkvD]] 15:24, 17 October 2009 (UTC) == Watch icon & feedback message == To avoid the confusion with featured article icons, we could consider using an icon with glasses (it would be closer to the "watch" feature). I looked for "eyes" icons but they don't look good. I think I still prefer the star, which is a pretty universal symbol for favoriting something. I have another comment though. I think we could get rid of most of the feedback message that displays when you watchlist a page. Right now, a gray frame appears [[MediaWiki:Addedwatchtext|that states]]: :The page "'''Foo'''" has been added to your [[Special:Watchlist|watchlist]]. Future changes to this page and its associated talk page will be listed there, and the page will appear '''bolded''' in the [[Special:RecentChanges|list of recent changes]] to make it easier to pick out. Although this frame is better than the previous feedback action (the user was redirected to another page only to tell them that their action was succesful), I think we could go a bit further and trim the message to keep only what is necessary. A feedback message is not really the place for documentation: * The user doesn't need this message to explain what the watchlist is. If they want to know, they will click the "watchlist" link and find by ourselves; if any information about what the watchlist is should be given, the watchlist should be the place for it. * Is the information about the recent changes really useful? On large wikis, nobody uses the recent changes page anyway, because they're going too fast. On all wikis, any change or a watched page that would appear bolded in the recent changes would also appear in the user's watchlist anyway. And, as I said for the watchlist, this information (watched pages are bolded in the recent changes page) should be given on the recent changes page, not here. So this information is completely unnecessary here. * Last, the user don't need the message to tell them what page has been added to their watchlist. They know that already, they're on the page! This is an example of a message showing the implementation model rather than conforming to the user's mental model. [[File:Watch feedback.png|thumb|300px|Quick proposal]] By shortening out the message to the ''actual feedback'' ("You have added this page to your [[Special:Watchlist|your watchlist]]."), we could display it as a temporary info notice right below the star icon (see attached picture). It would be automatically dismissed after a few seconds. [[User:Guillom|guillom]] 20:22, 17 October 2009 (UTC) Thanks so much for your feedback guillom - we really appreciate it. Messaging is certainly something we think about and would like to work on further along the road. We will definitely consider your suggestions when we do. --[[User:Parul Vora|Parul Vora]] 01:12, 11 November 2009 (UTC) == It should only be a user preference : customization is the key! == This is an important change to the interface, and should not be taken lightly. It might disturb significantly the users. Plus, an icon without text (and only a tooltip) will never be as clear and easy to use as "Watch / Unwatch". Please remember the following discussion. [[User:Dodoïste|Dodoïste]] 21:10, 17 October 2009 (UTC) For watchlists specifically, we want to look into a "star icon" type approach that's familiar from GMail, Firefox, and other apps. This would save space, allow us to always have the watch feature present, and make the watch state immediately obvious.--Eloquence 04:56, 22 September 2009 (UTC) :I've been using gmail and Firefox for one year and one year and a half respectively. Thanks for explaining me what the star actually means, 'cause I've been wondering what it is until now. I felt it was not important since it is so small and clueless. So I never really tried to use that star. 160.53.250.114 11:09, 22 September 2009 (UTC) ::Case in point: I don't think that the star (or any icon) will work. Also, remember that watch is not available to anonymous editors. So the skin will have to change by privilege. I like the idea of each user being able to customize which buttons are shown to his/her liking.HereToHelp (talk) 00:08, 23 September 2009 (UTC) :::That makes three things we want: (1) better defined defaults, (2) responsive to editing privileges and screen resolution, and (3) customization. The fourth concept is a "star icon", that is the icon would light up if the page is watch and remain either hollow or dimmed if the page is not; well right now if a page is "watched" the text simply changes to "unwatch", the reversed if the page is not watched. I think this fourth concept is not worthwhile discussed alone, there are two reasons for this: (1) without the text, and for new users, the idea of a star lighting up would be ambiguous; (2) if we had the text and the star, then why not cut the redundancy of the star. Now, with customization, then this could be something to our own choosing, and those who want it or something similar will get exactly that. ChyranandChloe 04:58, 23 September 2009 (UTC) :I disagree that it should be a user preference. Preferences are already way too much cluttered by dozens of useless options, we don't want to add dozens of others that are equally unnecessary. [[User:Guillom|guillom]] 06:20, 18 October 2009 (UTC) ::You're half wrong here. Preferences are already way too cluttered by dozens of useless options '''on the french Wikipedia'''. On english Wikipedia, there are fewer gadgets and user preferences, and as far as I can tell, they are much more useful. The quantity of user preferences on fr.wiki is a problem the french users should deal with themselves. It has nothing to do with the Usability Initiative. [[Special:Contributions/89.217.133.127|89.217.133.127]] 09:09, 18 October 2009 (UTC) :::So I am half right as well? :) Anyhow, preferences are mostly the same on all Wikimedia wikis, so I'm not sure I get your point, unless you're saying that there should be a ''gadget'', not a ''user preference'' to change the appearance of the Watch button (and in this case, I'd disagree too, but as you said, it would be a local matter, and I'd probably not argue about it). [[User:Guillom|guillom]] 09:52, 18 October 2009 (UTC) ::::Oh, so you're totally right. :-) But what should we do then ? Some users may like this feature, but some might really dislike it. If we can't solve this issue with a user preference, what should we do ? Should we make a pool to gather opinions ? [[Special:Contributions/89.217.133.127|89.217.133.127]] 12:18, 18 October 2009 (UTC) [[Category:Feedback]] == Forward to a friend == Hello there, It would be really useful to be able to email a link to a specific page to a contact from the page; for their interest/referral. Is this possible/planned? All the best, Jenni B das69o2jqpefgnvtwc86hlhg63zdet4 6 608 3348 2009-10-03T15:15:53Z Dodoïste 287 Bug with Babaco's edit TOC, using IE 8 and Vista or XP. wikitext text/x-wiki Bug with Babaco's edit TOC, using IE 8 and Vista or XP. 1s3cd3ps4hzuv8k55jou3okhjqk0np8 0 611 8891 8134 2010-09-15T20:49:49Z 78.160.127.128 /* Icon Set + Gallery */ wikitext text/x-wiki __NOTOC__ {{Internal}} == Background == The Usability Team strives to design their icons to be as cross-culture and cross-language friendly as possible. The 'Bold', 'Italics', and other character formatting icons proved particularly challenging. In the end, we have decided our favored approach is to support and use language-specific icons for the 'Bold' and 'Italics' buttons (making them more intuitive, easier to identify and use), but to design these in a manner that they can be easily generated in other languages. We have started off with the 5 languages with the largest wikis: English, German, French, X, X. These alone should work for many closely related languages. If an appropriate icon for your language is not present in the set, you can follow the instructions below to create the icons for your language. We both encourage and would greatly appreciate your efforts. Please also add your work to the growing set so that others do not have to duplicate your work. We encourage people to use the icons we have provided for the size and baseline character formatting. We have used the latin letter 'A'. <br /> We have created these icons using the [http://www.droidfonts.com/ Droid font family]. It was developed by Ascender in fall of 2006 explicity for Google and the Open Handset Alliance for use on the Android platform. It was designed for on-screen readability and is licensced under the Apache license. The collection provides an extensive set of styles (including bold and italics of course), weights, and language support (including Western and Eastern European Languages, Cyrillic, Greek, Turkish, as well as glyphs for Chinese, Japanese, and Korean). This is a tutorial on how to create language specific bold/ italic icons for our toolbar. Take a look at icons that have already been created before you start to create one yourself. When you have succeeded to create a new icon please contribute it to [http://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons this page] on Wikimedia Commons.<br /> This page offers a tutorial using Adobe Illustrator and Photoshop and another one using the Opensource applications [http://www.inkscape.org| Inkscape] and [http://www.gimp.org| Gimp].<br /> The result should be similar, no matter which applications you prefer.<br /> Finally: Please check to see whether your icon looks similar to universal [[File:toolbaricon_bold_A.jpg| bold]] and [[File:toolbaricon_italics_A.jpg| italic]] icon. If you have any problems you are welcome to ask for help on the discussion page. ==Using Adobe Illustrator + Photoshop== ===Preparation=== {| class="wikitable" style="width:800px" |- ! '''Before you begin''' |- | Download and install the '''Droid Serif''' (bold and italic) font.<br /> It is available for free download at [http://www.fontsquirrel.com/fonts/Droid-Serif/ fontsquirrel] or at [http://damieng.com/blog/2007/11/14/droid-font-family-courtesy-of-google-ascender/ damieng.com] |} ===Illustrator=== {| class="wikitable" style="width:800px" ! '''Start with Illustrator''' ! |- | Create a new Illustrator document. : Make it any size; we used 200px by 200px. : Use RGB colormode. : Use Screen resolution (72 ppi). | [[File:IconHTnewDocument.jpg |thumb |250px| Create a new document like this]] |- | Type your letter. : Using the Text tool, type the letter of your choice as a CAPITAL LETTER. : Use Droid Serif bold or italic. : Size: 100px | [[File:IconHTtype.jpg |thumb |250px| Type letter in Droid Serif 100]] |- | Switch from the Type Tool to the Selection Tool, and select your letter. | |- | Create outlines. : In the main menu bar, go to the "Type" menu and choose "Create Outlines." | |- | Apply a linear gradient fill. : Choose the "Linear Gradient" from the fill/swatch menu. : Click on the Gradient Fill tool to edit this Gradient. : Make the left stop: R122 G122 B122; make the right stop: R77 B77 B77. | [[File:IconHTgradient.jpg |thumb |250px| Apply Gradient]] |- | Give it a 2.5px stroke in black. | [[File:IconHTstroke.jpg |thumb |250px| Add Stroke]] |- | Copy it. (Left-click on the letter: Copy) | |} ===Photoshop=== {| class="wikitable" style="width:800px" ! '''Switch to Photoshop''' ! |- | Create a new file. :Choose "No color profile." : This document size should automatically be the size of your letter. If it is not, you can adjust it manually. | |- | Paste your icon. : Click the selection tool. You will be asked if you want to place it. Press Enter. : Make sure that the file is exactly as high and wide as the letter. | |- | Resize to 14 px. : In the Image menu, go to "Image Size". : Make sure "Constrain Proportions" and "Resample Image" are checked. : Choose "Bicubic (sharper)". : Scale it down to 14px height.<br /> | |- | Add effects. :Open Layer Properties (by double-clicking the layer icon in the Layer window's menu). :Check "Bevel & Emboss." ::'''Change default values:''' ::Size: "1px" ::Soften: "0px" ::Angle: "90°" ::Make sure "Use global light" is '''not''' checked. ::Highlight modus: Opacity: "40%" | [[File:IconHTlayerProperties.jpg |thumb |250px| ]] |- | Duplicate this layer.<br /> : Right-click on the layer in the Layer menu and select "Duplicate Layer." Edit the properties of this layer:<br /> ::Layer opacity: 20% ::Shape opacity: 0% | |- | Go to layer properties of this new layer. Delete Effect: "Bevel & Emboss"<br /> Add stroke. :'''Change default values:''' :Size: "1px" :Position: "inside" :Color: #000000 | [[File:IconHTlayerStroke.jpg |thumb |250px| ]] |- | Delete the white background layer. : Select background layer in Layer menu, and right-click to delete OR drag to the trash. | |- | Go to Image/ Canvas Size and set it to be 22px*22px. Position the letter in the center. | |- | Save this file as a png(-24). Please note the [[#Naming Guideline| Naming Guidelines]] | |} '''You are done!''' Please add your icon to [http://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons this page] on Wikimedia Commons and the Gallery below, so others need not duplicate your hard work! ==Using Inkscape + Gimp== ===Preparation=== {| class="wikitable" style="width:800px" |- ! '''Before you begin''' |- | Download and install the '''Droid Serif''' (bold and italic) font.<br /> It is available for free download at [http://www.fontsquirrel.com/fonts/Droid-Serif fontsquirrel ] or at [http://damieng.com/blog/2007/11/14/droid-font-family-courtesy-of-google-ascender damieng.com] |- | Download and install the gimp plugin [http://registry.gimp.org/node/186 layer effects] |} ===Inkscape=== {| class="wikitable" style="width:800px" |- ! '''Start with Inkscape''' |- | Create new document that is 100px X 100px<br /> :You can do this by creating a new file using the 'default' template(CTRL+N) and then editing the Document Properties (Shift + CTRL +D).<br /> :Make sure the background is transparent (Alpha = 0% = 0). | [[File:IconHT_ink_newdocument.jpg |thumb |250px|Change document properties like this.]] |- |Type the letter of your choice as a CAPITAL LETTER<br /> :Click on the Text tool in the toolbar on the left<br /> :Choose font: droid serif<br /> :Choose bold or italics, depending on which icon you are making<br /> :Size = 100<br /> :Click apply and close this menu | [[File:iconHT_ink_textproperties.jpg |thumb |250px|Change the textproperties like this.]] |- |Zoom in (Use the magnifying glasses in the left toolbar menu) until the letter is displayed in a convenient size for detail-editing.<br /> |- |Switch to the select-tool (F1)<br /> |- |Open the Fill and Stroke menu (in the main menu bar, go to Object → Fill and Stroke).<br /> :Select "Insert a linear gradient" (the 3rd icon) | [[File:iconHT_ink_gradient1.jpg |thumb |250px|Apply a gradient]] |- |Edit the stops for this gradient. :Click "Edit" in the Linear Gradient submenu. :This opens the Gradient editor. :In the dropdown menu, choose the leftmost stop of your linear gradient. ::apply R:122 G:122 B:122 ::make sure Alpha = 100% ('''Which is a value of 255!''') :In the dropdown menu, choose the rightmost stop of your linear gradient. :Doubleclick circle → the gradient editor pops up ::apply R:77 G:77 B:77 ::make sure Alpha = 100% ('''Which is a value of 255!''') ::close gradient editor |- | Alternatively, Click on the gradient tool (left menu)<br /> That brings a stroke on the letter with a rectangle left and circle right<br /> Doubleclick circle → the gradient editor pops up :apply R:122 G:122 B:122 :make sure Alpha = 100% ('''Which is a value of 255!''') :close gradient editor Doubleclick circle → the gradient editor pops up :apply R:77 G:77 B:77 :make sure Alpha = 100% ('''Which is a value of 255!''') :close gradient editor | [[File:iconHT_ink_gradient2.jpg |thumb |250px|Edit the gradient]] |- |Switch to the Select tool and give it a your letter a stroke (use fill and stroke menu in Object -> Fill and Stroke) :Click on the Stroke Paint tab and choose black, 100% alpha :Click on Stroke Style tab and edit width = 2.5px | [[File:iconHT_ink_stroke1.jpg |thumb |250px|Add a black stroke]] [[File:iconHT_ink_stroke1.jpg |thumb |250px|Edit width to 2.5px]] |- |Use the main (horizontal) toolbar to edit the size and the position by editing the "x" and "y' values:<br /> :X: 0px<br /> :y: 0px<br /> :H: 100px Make sure height and Width are locked!<br /> In most cases the letter won't be wider than it's height, so there will be white space on the right side of the letter. That is ok.<br /> If your letter is too wide you will have to adjust the width of the document so the letter fits in. | [[File:iconHT_ink_position.jpg |thumb |250px|Edit the size and the position of your letter]] |- |Save your file as ''normal.svg'' |} ===Gimp=== {| class="wikitable" style="width:800px" |- ! '''Switch to Gimp''' |- | Open the ''normal.svg'' file you just created in Inkscape |- | Create new layer <small>(this layer is only for your convenience, it will be deleted in the end)</small><br /> :Choose layer fill type: white white<br /> :In the Layer Dialog, place this layer below the layer with the icon. (you can simply drag and drop it the dialog) | [[File:iconHT_gimp_layer.jpg |thumb |250px|Create new white background layer]] |- |Make sure the layer with the letter/icon in the layer dialog is selected.<br /> Click on "bevel and emboss" (from the main menu bar, go to Script Fu → Layer Effects → "Bevel and Emboss") '''Change these default values:''' :Inner bevel :Depth: 10 :Size: 10 :Angle: 90° :Highlight Mode: Screen :Check Merge with layer | [[File:iconHT_gimp_bevelandemboss.jpg |thumb |250px|Add and edit layer effect: "bevel and emboss"]] |- |Scale image down to 14px height & width (From the main menu bar, go to Image → Scale Image<br /> Interpolation: Cubic | [[File:iconHT_gimp_scale.jpg |thumb |250px|Scale Image down to 14px*14px]] |- |Add a stroke. From the main menu bar, go to Script Fu → Layer Effects → Stroke :color: black :opacity: 50% :position: 0 (=inside) :Check merge with layer | [[File:iconHT_gimp_stroke.jpg |thumb |250px|Add and edit layer effect: "stroke"]] |- |Delete white background layer (Select background layer in layer dialog, then click on the "Delete this layer" Trash icon to delete it) |- | Go to Image/ Canvas Size and set it to be 22px*22px. Position the letter in the center. | |- |Save as png. Please note the [[#Naming Guideline| Naming Guidelines]] |} '''You are done!''' Please add your icon to [http://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons this page] on Wikimedia Commons and the Gallery below so others need not duplicate your hard work! ==Naming Guideline== Please upload your Icon to [http://commons.wikimedia.org/wiki/WikiEditor_Toolbar_Icons this page] on Wikimedia Commons and name your file like this:<br /> "toolbaricon_" + "bold_" or "italic_" + the actual letter + fileformat (".png") '''Example''': For this tutorial the file would be named:<br /> "''toolbaricon_bold_F.png''" == Icon Set + Gallery == {| class="wikitable" |- ! Language(s) !! Bold Icon !! Italics Icon |- | Universal Roman (Default) || [[File:toolbaricon_bold_A.jpg]] || [[File:toolbaricon_italics_A.jpg]] |- | English || [[File:toolbaricon_bold_B.jpg]] || [[File:toolbaricon_italics_I.jpg]] |- | German, Swedish, Norwegian, Danish || [[File:toolbaricon_bold_F.jpg]] || [[File:toolbaricon_italics_K.jpg]] |- | French || [[File:toolbaricon_bold_G.jpg]] || [[File:toolbaricon_italics_I.jpg]] |- | Spanish || [[File:toolbaricon_bold_G.jpg]] || [[File:toolbaricon_italics_C.jpg]] |- | Dutch || [[File:toolbaricon_bold_V.jpg]] || [[File:toolbaricon_italics_C.jpg]] |- | Portugese || [[File:toolbaricon_bold_N.jpg]] || [[File:toolbaricon_italics_I.jpg]] |- | Polish || [[File:toolbaricon_bold_P.jpg]] || [[File:toolbaricon_italics_K.jpg]] |- | Chinese || [[File:toolbaricon_bold_粗.png]] || [[File:Toolbaricon italic 斜.png]] |- | Czech || [[File:Toolbaricon bold T.png]] || [[File:Toolbaricon italic K.png]] |- | Indonesian<!-- '''Tebal''' and ''Miring'' --> || [[File:Toolbaricon bold T.png]] || [[File:Toolbaricon italic M.png]] |- | Telugu || [[File:Toolbaricon bold బొ.png]] || [[File:Toolbaricon italic వా.png]] |- | Turkish (tr) || [[File:Toolbaricon bold K.png]] || [[File:Toolbaricon italic E.png]] |- | Russian (ru) || [[File:Toolbaricon bold Ж.png]] || [[File:Toolbaricon italic К.png]] |- | Georgian (ka) || [[File:Toolbaricon_bold_მ.png|22px]] || [[File:Toolbaricon italic კ.png|22px]] |- | Hungarian || [[File:toolbaricon_bold_F.png]] || [[File:toolbaricon_italic_D.png]] |} f33ascfx387h2izx9iuene3wy3e3hxg 10 614 8661 3455 2010-07-29T13:33:49Z Nemo bis 9 cat wikitext text/x-wiki <span class="noprint plainlinks">[{{fullurl:{{{1|{{FULLPAGENAME}}}}}|action=edit}} {{#if:{{{2|}}}|{{{2}}}|edit}}]</span><noinclude> [[category:Templates]] </noinclude> iuk4pclec5n8v4h2ftx7mwl368ohbm7 10 615 8867 8691 2010-09-07T21:10:44Z Renamed user akdllvjbhlnbjfl 2449 wikitext text/x-wiki <div style="float:right"> ''{{edit|Template:Ideas}}''</div>Gallerys '''Ideas list (add your own!)''' # Syntax highlighting similar to WikiEd.[http://en.wikipedia.org/wiki/File:WikEd_screenshot.png] - [[Talk:Prototype/Archive_4#Color-coding_wiki_code|Archived discussion 1]] - [[Talk:Prototype/Archive 8#Syntax_highlighting_editor|Archived discussion 2]] - [http://mwcodemirror.sourceforge.net/. SourceForge project with live demonstration] # Collapsible references similar to WikiEd.[http://screencast.com/t/5GKIGSUs0RL][http://screencast.com/t/KPYt3MP4Ru] # Simplify edit page warnings. [[:File:Interface mark four.png|Mockup]] # Template selector. [[Talk:Prototype/Archive_4#I_want_a_better_damn_template_system|Discussion and mockup]] # "Edit saved" message. [[Talk:Prototype/Archive_4#Message_after_editing:_your_edit_was_successful|Discussion and mockup]] # Document-sharing services such as [http://docs.google.com/ Google Docs]. # Easier navigation [[Talk:Babaco_Designs#Tabbed_Naviation_and_new_Mock-up|Discussion and mockup]] # Interwiki links. [[Talk:Prototype/Archive 8#Interwiki links|Discussion and mockup]] # Login-area constantly available at the top (like [http://ubuntuusers.de/ ubuntuusers]; practical for [https://addons.mozilla.org/de/firefox/addon/4429 Secure Login]. what dedects it automatically # Nice image galleries like the [http://www.huddletogether.com/projects/lightbox2/ Lightbox] # Change photo edit facility, which is easy to use # Fixed positioning for Nav / Search Box - so it's always on the page as you scroll - [[Talk:Prototype/Archive 8#Search Box / Navigation - why not try fixed positioning?]], [http://usability.wikimedia.org/wiki/User:Aaron_dub/vector.css link to my custom prototype css] # Leave wiki exactly as it was - it was obviously successful - why change it? # How about adding a "shake" for random feature for iPhones!<noinclude> [[Category:Templates]] [[Category:Feedback]]</noinclude> # The cursor should already be in the search box when you access Wikipedia as well as stay in there while reading articles. This would be much more comfortable and user-friendly! # Bookmark articles without adding to watch-list - for favourites and research subjects, with personal folders or tags. Essential for the heavy reader, such as myself. f1yhyvv1khuzcmxv56d1g5501zbiuis 0 617 8610 3940 2010-07-29T12:58:08Z Nemo bis 9 cat wikitext text/x-wiki [[Usability,_Experience,_and_Progress_Study/Notes/Judy | "Judy"]] - Wed @ 9am<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Mark | "Mark"]] - Wed @ 10am<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Alexandra | "Alexandra"]] - Wed @ 2pm<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Angelique | "Angelique"]] - Thurs @ 9am<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Cheryle | "Cheryle"]] - Thurs @ 10am<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Stephen | "Stephen"]] - Thurs @ 11pm<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Jack | "Jack"]] - Thurs @ 2pm<br /> [[Usability,_Experience,_and_Progress_Study/Notes/Terrence | "Terrence"]] - Thurs @ 3pm<br /> == General Comments/Notes == == Bugs we've found == * error message between preview and edit tab * tables - not class wikitable or strokes * insert mess is still underneath edit box * no line at the bottom of article pages (see judy, architect) * insert link dialog does not flush out text entry contents [[Category:Usability studies]] gkpsuygb1f7ywwtoavgi3zjfhwps5hk 0 618 3748 3746 2009-10-21T00:07:19Z 216.38.133.254 /* Nimish's hilights */ wikitext text/x-wiki == Parul's Notes == * has edited once - light rail system * i'm going to ignore this, but i'm intrigued. * i've only logged in once, so i can't say this is different than when i did it before (maybe 6 weeks) * not adding something - i think it's a new engtry - she had searched and it said it wasn't there. * was wondering if it was just looking for the page title and not looking for that phrase in the body of the entry - looking for the search. * clicks on advanced search, searching for content within that article. maybe put it in quotes. someone else might have a different name for it * i'm still not certain that there's not some stub article. * nothing below the search results when it asks me to check the search results below * searches for more specific? goes through the motions of checking for an article. noe valley google shuttle * nothing changed on this page. * keeps searching because she seems convinced that it must be there * creates this page from the link there. * grayed out but i don't understand why - it means i've just been there. * this is a little confusing.....lots of information * this is asking more of me than i want to give at the moment. maybe it should have more of a flow chart. start here - if you have trouble go here. maybe take me to an article wizard and let me opt out of it. * drawing board, user space, a lot of different names here and it sounds like it's wiki jargon. * if i have to learn the interface than i'm less interested in spending time writing the article. * i would use this safe place, then add it to the real world. * big white box that tells me where to type. * completes minor edit etc before she types. * goes through each feature before saving page. * reads all instructions and all elements on the page * i would want to give the introduction * makes bold * hover over * "not a clear icon to me" * now that's bold, i would assume * now i would * link - puts in link using "wiki text" says it's wrong (needs to have something * finds difference - internal link. * goes back to check behavior * it would be good to know that before i get there. maybe it has to send a query first. * creates a table with no problems. * that's, like, not real friendly * that did what i expected it to do, but it took me two steps to get there. * for a short article that would be good. for a longer article it wouldn't be good. * where the seals are? or images? * "OH BOY!" when she sees a template * i think they're discouraging people from editing. just because this - WOW. * trying to find my way through here. please don't edit this page, go to the daughter page. * all of this stuff down here i don't understand. i don't know what transcluded means. it's a link so maybe it'll tell me. included by reference. * this is the danger. * i'm intimidated by this. * she uses main search to search within the page. does not see search and find and uses browser find. * would have been nice to have some kind of search function. * would be nice to do it on the fly. * that whole editing thing could have been easier! * ==Nimish's hilights== * doesn't know if stub article might already exist, concern with duplicating other's work * search article contents vs titles confusing * starting a page full of too much information, confusing * terminologly: user space, sandbox, drawing board ** scared "put it(page) in a safe place" * "I think they're discouraging people from editing" * "transcluded" -> didn't know what this means * "how to search within the page?" -> NTOC still not specific enough exx6c7g4evfs4ftibh1hi4k9izdfo19 0 620 3749 3747 2009-10-21T00:09:01Z 216.38.133.254 /* Nimish's hilights */ wikitext text/x-wiki == Parul's Notes == * Environmental Consultant * I use it everyday, multiple times a day for research and topics of interest. If I really like a movie that I saw the night before and look at the director, etc. Find out more information. * Being in the technical field, I look for areas to begin research. Has all these references I can easily follow up on. * Not a list of topics where I'm like - I really need to edit topic so and so. More stumble upon. * I saw something I wanted to edit, but I don't know if I did. I think maybe last week. * there's always something to take a look at. * had found search before he consciously realized it had moved. * i would imagine a page like this, especially a technical page has probably been reviews a lot of time. it doesn't jump out at me that there would be an issue with it. i scan a lot of times for the links. i'm also interested in family history. * looks for something to add for a long time! * goes to discussion to see if there is a reason that someone hasn't added. * didn't understand the difference between a discussion page or a talk page and haven't invested * it's just laid out a little differently * this makes a little bit more sense * this editing window is a little difficult. if someone had never done it before, they'd be overwhelmed. the combination of text and code.... * goes back to the article to read the page, rather than reading it in the window. * off hand i don't have all of the dates * i can make a paragraph, so long as we remove it later. * i might create a paragraph in word * for my own ease of use. once it was ready i'd import it to the editing page and then add citations there. * "I don't know if that's true, see i haven't checked that" * it's doing the same thing i would be doing. i'm not sure. if i was writing that elsewhere. i'm not sure when i'd know when to enter a link or not. * if it hadn't mentioned gambling elsewhere in the text...probably want to link to it * would want to add links after? * types and highlights links. that's pretty cool * confirms by this symbol * i think it's better. but linking wasn't difficult - it was the references. * external webpage - i'm wondering what the difference between what a link is and a reference. * this would make sense once you got used to it. that's pretty useful. * found cheat sheet - it's all laid out for you * there used to be.....this stuff is left over. * citing pages that don't have references or resources. * it took me a while the first time..... * it's not code, computer editing ling. "infobox". i don't know, there might be.... * like a credit card info. but philosophically i'm not sure that's what wikipedia wants to do. * basic and advanced table. someone could change that or the fields * so bare bones. waiting for more information - where to put borders in. it doesn't tell me anything. not sure what a table would be used for. * it still gave me a feeling of complete editability and streamlined for ease of use. * maybe i'm just using it incorrectly. * if there was something that i was passionate about -- a band i loved -- i would add a reference. not if it's something i don't care about. * creating a page on here, in my mind, is like writing an article for publication in a magazine. you would have to still take the time and involvement and effort to try and craft a quality piece of information. * not "citation needed". i know there are user groups....if i got involved in just helping out. * no personal incentive right off the bat. * how clumsy. i knew what a pain....what the difficulties are of using it. i knew what i was getting into. * there's nothing that i'm like "oh geez". navigational bar seems well laid out. search box doesn't make a difference - where it's always at. == Nimish's hilights== * found moved search before he realized it, is ''intuitive'' yay! * assumed someone will fact-check it if note left on discussion page ogervts1a9tng62mi33vnfnt8qz2fgj 0 621 3750 3537 2009-10-21T00:13:54Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * sciency type stuff. main work is writing about southeastern cultures. using it in my writing. * been writing my whole life. * isn't sure if you're able to edit without an account * logs ip address.... * ==Nimish's hilights== * Professional blogger * Just copying -- we can't get rid of wikitext * Expected dialogs after seeing one * Edit/preview 'bug' * confused to how to upload * scroll down instead of using NTOC * used terminology of "publish" instead of "save", maybe this is why she saved constantly instead of previewing? soy5o4ozh1csj7b335wiewaqmtesrog 0 623 3547 3546 2009-10-15T17:06:08Z 69.105.154.153 wikitext text/x-wiki == Parul's Notes == * notices categories * "code" * the text is here, which is the most helpful thing * uses link box without seeing tabs. for an internal link * links and citations - citations are sources for where the information comes from * this is all subjective, seems like the things that are wildly known vs. controversial * if you read it, it becomes clearer - i didn't really read it before. * it's more convenient that it's set up that way - it's just different. it's easier to just see that you can put in one word and that it prompts you for pages that exist. but then, like i said, it's.....from other stuff i've done, i'm used to writing the whole. * It's not apparent to me, how to see the page without saving it. Oh no, it has show preview. oops. it says to preview it before saving. * Admittedly mostly because I didn't read it. * Once she she's the two link functions, uses them with ease - with highlighted text or to start the action. * tries on her own to make it formatted the same - i.e. with a bullet * now with a bullet! i did it! * once i knew how that worked, it's actually pretty easy * external links....how it moves the cursor to not exactly to where you need to type. if you wanted to add a link to appear after.....which seems like the logical next place. *it should be a step or two to get to a page you can edit. once you're on that page, you can find your way around...but it's not organized in a way that's super easy. * for example - i didn't need to use the advanced stuff...didn't understand why it's advanced. wasn't an issue - hidden. if i was gonna need to do that - it's not immediately apparent. * links - internal link really easy to use. * it was....it didn't give me errors. * it turned out how i was expecting it to. makes me more likely to make me want to do edits. * it doesn't look like you want or save - frustrating. 7wdh4m47zqupf7oyttptdpnyc4wbmtd 0 624 3550 2009-10-15T18:01:39Z 69.105.154.153 Created page with '== Parul's Notes == * current events - news buff * festivals in alameda * section edit - arts and culture section "i believe it's formatting - i'm not sure if * can do lots of th...' wikitext text/x-wiki == Parul's Notes == * current events - news buff * festivals in alameda * section edit - arts and culture section "i believe it's formatting - i'm not sure if * can do lots of things - would expect it to be "ok this is what you can do". survey - that's it you can't do anything more * this was a lot easier than i expected. * "websites don't have common sense, but programmers do" * should say "would you like to contribute" would you like to edit. * harder - in advanced tab so i would expect it to be. * would be easier if you had the table and didn't have to do the programming * if i would have looked at the other one...perhaps, i don't know, i could have went to help * oqr8u3kvyv79jnkxj4269879pf292ce 14 625 3551 2009-10-15T18:02:26Z Guillom 13 [[Category:Multimedia usability]] wikitext text/x-wiki [[Category:Multimedia usability]] ah4y36oij9fcyo95gwbbnkrumkixhzv 14 626 3619 3618 2009-10-16T13:04:12Z Guillom 13 actually, make that bold wikitext text/x-wiki This category hosts all materials related to the '''[[Multimedia:About|Multimedia usability project]]'''. [[Category:Root]] r0u4ubwtw8frv90cnaomismi90d6jfz 14 627 3553 2009-10-15T18:03:12Z Guillom 13 This is the master category for all categories on this wiki. wikitext text/x-wiki This is the master category for all categories on this wiki. 7swmf36hbqbu9iqlznhvwoihfnvk0wn 100 628 5783 5537 2010-02-10T21:17:38Z Guillom 13 not really a draft any more wikitext text/x-wiki == Types of user testing == * Focus group (group process): presenting ideas and designs to a small group of people and observing how they react to them. Discussion between members of the group is critical<ref>Krug 2006, p.133</ref>. Goal: getting a quick view of how people feel about ideas in the early stages of the product's development. * Usability testing (one-to-one interview): observing how individuals use the product, the difficulties they encounter while using the product and performing specific tasks. Goals: getting more familiar with the users' mental model(s), identifying critical issues and testing improvements. == User research plan == A quick analysis shows that: * The team is already aware of critical issues with the upload process and workflow. * The community of users is happy to provide information and feedback on a continuous basis. * The more usability studies, the more information we get and the better the product becomes. But we have to optimize the use of our limited budget, and we can't afford many full-scale usability studies. As a consequence, we propose the following research plan: * '''[[Multimedia:Preliminary user research|Preliminary user research]]''' in the very early stages of the project: interviews of users, discussions with stakeholders, focus groups (Multimedia meeting in Paris) and online survey(?). *: Timeline: October-November 2009 *: Type: formative testing<ref>For more information about formative vs. summative testing, see ''[http://www.alistapart.com/articles/usability-testing-demystified/ Usability Testing Demystified]'', Dana Chisnell, [http://www.alistapart.com A List Apart], October 6, 2009.</ref> *:Goals: *:* Observing and understanding why and how users use the product *:* Identifying or confirming critical issues that users encounter during its use *:* Collecting input from various stakeholders * '''[[Multimedia:UX study, March 2010|Formal usability study]]''' six months later: "classic" study with usability firm, lab etc. Participants would be confronted with two interfaces: the initial interface as it was before any improvement, and a prototype interface with some improvements based on the preliminary research *: Timeline: February/March 2010 *: Type: both formative and summative testing *: Goals: *:* Formally validating the issues identified by the preliminary study *:* Checking progress and improvements of the prototype *:* Letting users show us issues that may be masked before by more critical problems that we fixed in the meantime<ref>Krug 2006, p.139</ref>. * '''Formal usability study''' at the end of the project: Possibly with a reduced number of participants. *: Timeline: October 2010 *: Type: mostly summative testing *: Goals: *:*testing improvements and identifying remaining issues. * [[Multimedia:Metrics]] == Bibliography == * S. Krug, ''Don't make me think: A common sense approach to web usability'', Second edition, 2006. * A. Cooper, R. Reiman & D. Cronin, ''About Face 3: The Essentials of Interaction Design'', Wiley, 2007. == Notes and references == <references /> [[Category:Multimedia usability - Research]] sr1ds59gnh01k36dvacpxaflxwgwj9a 0 629 3578 3576 2009-10-15T19:11:30Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki == Parul's Notes == *writer/blogger - smoothie company unemployed. writing a novel of my own - historical romance. * going to school - studying art, junior college * learn by example - take a look at the hypertext above. * copying external link from one above - has not use (or seen?) the toolbar * proofread in edit box - no immediate preview * changing his written text to work within the syntax for his link. easier to do that than to link? * see if the previous author of the article. copy + paste. * after being showed the toolbar, he still copies by example. * mimic what the coding, looking for shortcuts * uses cheat sheet to figure out refernce (over button). likes seeing examples? * cheat sheet on references - page text - look at copy! * at this point i don't know what it's asking me to do. i can see what it's telling me to do. * now it doesn't tell me what to do. * references - FAIL * that's a lot of hypertext information that makes my eyes dance all over the screen. * that's enough to make me say i don't know what i'm doing at this point. * right column/left column photos + templates + infoboxes 4964kdbxye7tp9nfgfcz1rnrd2kyozv 100 631 6180 5798 2010-03-23T19:02:19Z 82.74.192.60 clean up wikitext text/x-wiki <div class=plainlinks> How do similar websites work? What could we learn from them? == Criteria == Besides a general evaluation, we try to answer the following questions: * What is the minimum information required to upload a file? * Is multiple upload possible? If so, is there a limit? * Do they provide large batch upload tools? Are there unofficial such tools? * Do they care at all about copyright? What do they do to avoid copyright violations? * Do they allow/facilitate mobile uploads? * How do they categorize content? (if at all) * How do they rate content? (if at all) * Do they have a review workflow? * Do they facilitate reuse? Some general indicators also help contextualize information: * number of users (at least one media file) * number of active users (TBD) (may be difficult to get and/or make figures consistent) * total number of media files * growth rate (total number of files / time since creation, brought down to 1 day) See also [[w:List of photo sharing websites|List of photo sharing websites]] == [http://www.flickr.com Flickr] == ; Description : Flickr is an image and video hosting website, web services suite, and online community platform. In addition to being a popular website for users to share personal photographs, the service is widely used by bloggers as a photo repository. As of October 2009, it claims to host more than 4 billion images. ([[w:Flickr|source]]) ; General usability : Large invitation to upload photos & videos, both for logged-in and new users (who are prompted to create an account). The interface is simple enough, with good discoverability and many invitations displayed only at the appropriate time. The drop-down menu toolbar imitates desktop applications menus. === Upload === ; Minimum information required to upload a file : Only the actual file. ; Additional information : Privacy settings are proposed on the upload page. It is possible to show more upload options to specify safety level, content type etc. Once the upload is finished, the user can either be done with it, or add a description as they are prompted to. ; Multiple upload : It is possible to upload multiple files at the same time using the default web interface? No limit with the normal (Flash) uploader. Six items at a time with the basic uploader. ; Mobile uploads : They allow and facilitate uploads from mobile devices [http://www.flickr.com/tools/mobile/]. It is done by e-mailing a special address. They also provide an official iPhone application including an upload feature; other third-party companies provide applications for other platforms (e.g. Blackberry). ; Batch upload tools : Flickr offers two [http://www.flickr.com/tools/ desktop uploaders], one for Windows and one for Mac. On the same page you find informations about third-party upload tool plug-ins: [http://connectedflow.com/flickrexport/ FlickrExport], a plugin for iPhoto and Aperture (Mac), and [http://juploadr.org/ jUploadr], which is cross-platform (Windows, Linux and Mac) and cross-site (Flickr and Zooomr). It is also possibile to [http://www.flickr.com/account/uploadbyemail/ upload by email]. === Review === ; Copyright : Users are asked not to upload "anything that isn't [theirs]" ([http://www.flickr.com/guidelines.gne Flickr Community Guidelines]). Flickr is not really interested in copyright complaints; Commons must maintain a list [[Commons:Commons:Questionable Flickr images|blacklist of Flickr users]] making false or erroneous copyright claims. ; Content classification : Users can tag their photos and videos. They can decide if other users can, too (friends or family, contacts, every Flickr user). Uploaders may also use personal sets & collections to organize their works, or add their pictures to topical groups. ; Content rating : Any registered user can add a picture that isn't theirs to their "favorites". Some groups also serve as a rating system. ; Review workflow : For accounts: Flickr staff review people's uploads and flag the account according to whether the owner is able to moderate their content. For content: registered users can "flag" a picture and ask Flickr to review its "safety level" === Impact & reuse === ; Statistics & metrics : Everyone can see on photo pages how many times a photo was viewed. Pro Users can also see referrers information for the last 28 days. ; Reuse :It is generally possible to view photos at different sizes and download them. Original size is available only for photos by Pro Users. Users can "prevent" (make it more difficult for) others to download their photos, or they can limit the possibility to other users, contacts, friends or family. It is also possible to select a Creative Commons license. : They also facilitate reuse of their pictures elsewhere on the web b y providing code snippets to be inserted in web pages. Registered users can also use the one-click "blog this" feature to use a picture on their blog (if the author has not disabled the feature). === Other notes and resources === == [http://www.youtube.com YouTube] == ; Description : YouTube is a video sharing website on which users can upload and share videos. [...] The company is based in San Bruno, California, and uses Adobe Flash Video technology to display a wide variety of user-generated video content, including movie clips, TV clips, and music videos, as well as amateur content such as video blogging and short original videos. Most of the content on YouTube has been uploaded by individuals, although media corporations including CBS, the BBC, UMG and other organizations offer some of their material via the site, as part of the YouTube partnership program. Unregistered users can watch the videos, while registered users are permitted to upload an unlimited number of videos. ([[w:YouTube|source]]) ; General usability : Fairly visible invitation to "add a video" === Upload === ; Minimum information required to upload a file : Any registered users can upload a file. OGV files are ok. Only the file is needed to upload. ; Additional information : After the upload, the user is prompted to add a title (suggested from the file name), a description, tags and a category. It is also possible to add additional information such as geotagging later. After the first video is uploaded, YouTube sends an e-mail to the user to help them go further and discover features. ; Multiple upload : It is possible to upload multiple files at the same time using the default web interface. After a file has been selected for upload, another "add a video" field appears. It is also possible to use the "[http://www.youtube.com/my_videos_multiupload multi-upload plugin]" and to provide a list of videos that will be uploaded in the background while the user does something else. ; Mobile uploads : It is possible to upload videos via their [http://m.youtube.com/my_videos_upload?is_adult=True&hl=fr&gl=US&client=mv-google#top mobile gateway or by e-mail]. ; Batch upload tools : None known of. === Review === ; Copyright : There is a warning on the upload page, telling people they shouldn't upload videos for which they don't own the copyright. ; Content classification : The uploader may specify a general category (People, Education, etc.) and free tags. YouTube also displays "Similar videos" next to each video. ; Content rating : Registered users can give a rating from 1 to 5 stars. The rating is systematically displayed with each video, including in search results. ; Review workflow : Registered users may "flag" videos for review by YouTube staff. === Impact & reuse === ; Statistics & metrics : Any user can see video views numbers and its evolution with time. They also provide anonymized statistics about the sex, age and location of viewers. ; Reuse : Youtube's terms of service legally prohibit downloading and reuse outside of youtube. Practically, they have not yet been known to enforce this agreement but downloading must be accomplished via third-party tools which periodically break as the Youtube site operation changes. However, Youtube encourages the embedding of videos they host in third party websites. They provide code snippets that can be customized (color of the player, size of the video, etc.) with immediate preview === Other notes and resources === == [http://www.facebook.com Facebook] == ; Description : Facebook is a social networking website where users can add friends and send them messages, and update their personal profiles to notify friends about themselves. ([[w:Facebook|source]]) ; General usability : It is pretty straightforward to upload pictures through the 'Photos' > 'Upload photos' path. === Upload === ; Minimum information required to upload a file : Only the actual file ; Additional information : caption, tags, people ; Multiple upload : Not when sharing a picture on one's wall. However, a user may create an album and then upload several pictures at once using a Java interface. The "simple" uploader allows to select up to 5 files to be uploaded together. ; Mobile uploads : It is possible to upload photos from mobile devices via [http://www.facebook.com/mobile/?v=photos e-mail upload]. ; Batch upload tools : None official. Some 3rd-party apps exist. === Review === ; Copyright : When uploading through the Java interface, the user implicitely states that he has the right to upload the picture(s). It is then possible to "report a photo" if it is inappropriate. It it infringes the author's copyright, the author may file an automated DMCA notice. ; Content classification : A user may create albums. ; Content rating : Facebook provides a general "like" feature. ; Review workflow : "Report this photo" (see 'copyright'). === Impact & reuse === ; Statistics & metrics : None. ; Reuse : No. === Other notes and resources === == [http://www.fotopedia.com Fotopedia] == ; Description : Fotopedia claims to be "the first collaborative photo encyclopedia." ; General usability : dark background, very "photo" look. Photos are the real stars of the website. Smooth slideshows. No prominent invitation to participate to the general website (it doesn't seem to be possible), but there is an invitation to add pictures on each topic page. However, a large emphasis is put on adding existing pictures from Fotopedia or Flickr, and the "upload from computer" link is carefully hidden. General appearance is clean and pretty, but general usability is not-so-good. === Upload === ; Minimum information required to upload a file : The file (from Flickr or one's computer) + the page it should be added to. ; Additional information : None. ; Multiple upload : No. ; Mobile uploads : No. ; Batch upload tools : [http://www.fotopedia.com/download Yes], available for MacOS & Windows only. === Review === ; Copyright : Users can specify a default license in their preferences (All rights reserved, PD & all 6 CC licenses). The default license is CC-BY-NC. ; Content classification : Upload is possible only in relation to a page / article. ; Content rating : Registered users can "vote up" or "vote down" for a picture to be added to a page. Fotopedia puts a huge emphasis on the quality of their content. ; Review workflow : Any user may file an "abuse report" for inappropriate content or copyright violation. === Impact & reuse === ; Statistics & metrics : No. ; Reuse : Download is possible. They offer a "widget editor" to customize embedded pictures and then provide the associated HTML code snippet. === Other notes and resources === When a page doesn't already exist, the user is prompted to create it. Fotopedia imports the first sentences of the Wikipedia article of the same name and asks the user to confirm that the subject is the same. == [http://picasaweb.google.com Picasa Web Albums] == ; Description : Picasa Web Albums (PWA) is a photo sharing web site from Google, often compared to Flickr and similar sites. It allows users with accounts at Google to store and share 1 GB of photos for free. ([[w:Picasa|source]]) ; General usability : Users need a Google account. The main way to upload pictures to Picasa Web Albums is to use the Picasa desktop application. ''clarity, explorability, invitation to participate'' === Upload === ; Minimum information required to upload a file : Google account + album ; Additional information : Tags ; Multiple upload : Up to 5 files at once. ; Mobile uploads : Yes, mainly by e-mail [http://picasa.google.com/support/bin/answer.py?hl=en&answer=83342]. ; Batch upload tools : Picasa (Windows, Linux, MacOS) === Review === ; Copyright : No proactive check. ; Content classification : Users add pictures to their own albums. ; Content rating : Like/unlike for registered users ; Review workflow : Anyone can "report abuse" via a link on the image page === Impact & reuse === ; Statistics & metrics : None known of. ; Reuse : They provide a "link to this photo" widget that allows to link to or embed the picture in a web page. === Other notes and resources === == [http://www.photobucket.com Photobucket] == ; Description : Photobucket is an image hosting, video hosting, slideshow creation and photo sharing website. It is usually used for personal photographic albums, remote storage of avatars displayed on internet forums, and storage of videos ([[w:Photobucket|source]]) ; General usability : The main page contains many invitations to join and participate. === Upload === ; Minimum information required to upload a file : the file ; Additional information : tags, description ; Multiple upload : "Bulk uploader" as a Java applet ; Mobile uploads : Possible [http://tutorials.photobucket.com/tutorial_6.html by e-mail] or using a dedicated commercial applications depending on the service provider & phone used ([http://mobileuploader.photobucket.com/phoneChoice.aspx?carrier=Verizon example]). ; Batch upload tools : None known of. === Review === ; Copyright : No proactive check ; Content classification : User albums, title, description, tags ; Content rating : ? ; Review workflow : "Report inappropriate content" wizard === Impact & reuse === ; Statistics & metrics : Basic users can see statistics for 5 photos/videos; Pro users have unlimited stats. ; Reuse : direct link, code snippet, derivative products such as mugs, cards, etc. === Other notes and resources === == [http://www.dailymotion.com Dailymotion] == ; Description : ([[w:Dailymotion|source]]) ; General usability : ''clarity, explorability, invitation to participate'' === Upload === ; Minimum information required to upload a file : ''only the actual file? additional information?'' ; Additional information : '' information that is recommended to be added before or after the upload'' ; Multiple upload : ''is it possible to upload multiple files at the same time using the default web interface? If so, is there a limit?'' ; Mobile uploads : ''Do they allow/facilitate uploads from mobile devices? (PDAs, cell phones, smart phones, etc.)'' ; Batch upload tools : ''official? unofficial? cross-platforms?'' === Review === ; Copyright : ''What do they do to avoid copyright violations? Do they care at all?'' ; Content classification : ''How do they categorize content? (if at all)'' ; Content rating : '' Is it possible to rate the content? Who can do it??' ; Review workflow : ''Do they have a review workflow? For accounts? content?'' === Impact & reuse === ; Statistics & metrics : '' what kind of statistics do they provide? To whom?'' ; Reuse :''Do they encourage / facilitate reuse of their content? If so, how?'' === Other notes and resources === == [http://www.panoramio.com Panoramio] == ; Description : Panoramio is a geolocation-oriented photo sharing website. Currently, some of the photos uploaded to the site can be accessed as a layer in Google Earth and Google Maps, with new photos being added at the end of every month. The site's goal is to allow Google Earth users to learn more about a given area by viewing the photos that other users have taken at that place. ([[w:Panoramio|source]]) ; General usability : The main page features a big invitation to join. === Upload === ; Minimum information required to upload a file : Only the actual file. ; Additional information : geotagging, title, tags, description ; Multiple upload : yes, up to 10 at once (selection file by file) ; Mobile uploads : No. ; Batch upload tools : "Panoramio doesn't support batch uploads. Each photo must be individually uploaded to ensure the best quality and geolocation accuracy." [http://www.panoramio.com/help/adding_photos] === Review === ; Copyright : No proactive check. ; Content classification : Classification is mainly done by location ; Content rating : Registered users can flag as "the best" picture. ; Review workflow : Registered users can report as "inappropriate or offensive" === Impact & reuse === ; Statistics & metrics : Anyone can see the number of page views for each image. ; Reuse : No. === Other notes and resources === == [http://www.archive.org Internet Archive] == ; Description : The Internet Archive (IA) is a nonprofit organization dedicated to building and maintaining a free and openly accessible online digital library, including an archive of the World Wide Web. ([[w:Internet Archive|source]]) ; General usability : There is an invitation to upload but it isn't that prominent. === Upload === ; Minimum information required to upload a file : The file, title, description, keywords ; Additional information : author, Creative Commons license ; Multiple upload : yes, using the Flash in-browser uploader ; Mobile uploads : No. ; Batch upload tools : For batch upload, the Internet Archive provides an [http://www.archive.org/create.php?ftp=1 FTP server]. This solution is considered "old" and doesn't work very well, and maintenance and improvements are given low priority. It is an official alternative, not deprecated, but not exactly encouraged either. :From the website, you log in, follow the upload link, and click the FTP alternative. You pick a name for your new "item". The item name will become part of the URL, so it must be unique. Then you are given the login details to the FTP server. You can use any FTP client. When you have logged in, there is a subdirectory having the name of your new item. You can upload one or more files to this subdirectory. When you are finished, you click a submit link on the website. The Internet Archive now moves the contents from the FTP subdirectory to its internal storage architecture. This can take some time if there were many files. After this, you arrive at a web form where you add metadata for your new item, including optional descriptions for each uploaded file. :When uploading the Wikipedia visitor statistics logfiles to the Internet Archive, one such "item" was created for each month (e.g. [http://www.archive.org/details/wikipedia_visitor_stats_200712 December 2007]). Each item contained some 1440 files, totaling tens of gigabytes. The biggest problem was that FTP transfer bandwidth appeared to be limited to 3.5 megabits per second per session. Nobody could explain why this was so. By opening three parallel FTP sessions, a total of 10 megabits per second was reached, but the upload for each item took in the range of 24 hours. It felt like a reliable but clunky "web 1.0" solution, still waiting to be replaced by a modernized web 2.0 batch uploader. :There is also a batch upload tool called [http://wiki.creativecommons.org/CcPublisher CcPublisher] provided by Creative Commons for Windows, Mac and Linux platforms. It is not under active development any more. === Review === ; Copyright : They ask to "contribute books, audio, and video files that [users] have the right to share." ; Content classification : with tags ; Content rating : Registered users can write reviews of collections. ; Review workflow : None known of. === Impact & reuse === ; Statistics & metrics : None known of. ; Reuse : None known of. === Other notes and resources === == [http://www.kongregate.com/collabs Kongregate Collabs] == ; Description : ([[w:Kongregate#Collabs|source]]) ; General usability : ''clarity, explorability, invitation to participate'' === Upload === ; Minimum information required to upload a file : ''only the actual file? additional information?'' ; Additional information : '' information that is recommended to be added before or after the upload'' ; Multiple upload : ''is it possible to upload multiple files at the same time using the default web interface? If so, is there a limit?'' ; Mobile uploads : ''Do they allow/facilitate uploads from mobile devices? (PDAs, cell phones, smart phones, etc.)'' ; Batch upload tools : ''official? unofficial? cross-platforms?'' === Review === ; Copyright : ''What do they do to avoid copyright violations? Do they care at all?'' ; Content classification : ''How do they categorize content? (if at all)'' ; Content rating : '' Is it possible to rate the content? Who can do it??' ; Review workflow : ''Do they have a review workflow? For accounts? content?'' === Impact & reuse === ; Statistics & metrics : '' what kind of statistics do they provide? To whom?'' ; Reuse :''Do they encourage / facilitate reuse of their content? If so, how?'' === Other notes and resources === </div> [[Category:Multimedia usability - Research]] buqs46r03168mtnllfnqztk3tbjfgbn 100 632 7040 6731 2010-05-14T23:10:19Z NeilK 1629 /* Test environments */ wikitext text/x-wiki <div class=plainlinks> This page aims at keeping track of Multimedia usability-related content on other wikis or websites. These links should be added later to the relevant pages. == MediaWiki == To do: Skim through MediaWiki extensions to see if some could be of use * [[:mw:Media Projects Overview|Media Projects Overview]] * [[:mw:Extension:GlobalUsage|Extension:GlobalUsage]] * [[:mw:User:Guillom/File management wishlist|User:Guillom/File management wishlist]] * [[:mw:Extension talk:Add Media Wizard]] * [[:mw:Extension:Workflow]] * [[:mw:Extension:CategoryWatch]] == Meta-wiki == * [[:m:GLAM-WIKI_Recommendations|GLAM-WIKI_Recommendations]] * ... == Wikimedia Commons == * [[:commons:Commons:Bugs|Commons:Bugs]] * [[:commons:Commons:Tools|Commons:Tools]] * [[:commons:Commons:Batch uploading|Commons:Batch uploading]] * [[:commons:Commons:Move toward Commons 2.0 !|Commons:Move toward Commons 2.0 !]] * [[:commons:Commons:Microformats Project|Commons:Microformats Project]] * [[:commons:User:Teofilo/Software wishlist|User:Teofilo/Software wishlist]] * [[:commons:User:Guillom/KIPI|User:Guillom/KIPI]] * [[:commons:User:Pfctdayelise/Aims and goals]] * ... == Toolserver == To do: list media-related tools. * [http://toolserver.org/~magnus Magnus' toys and tools] * [http://toolserver.org/~magnus/commcomm/index.html?category=Pictures%20of%20the%20day%20(2009) Commons Commander] * [http://toolserver.org/~magnus/glamorous.php?doit=1&category=Images+from+the+German+Federal+Archive&use_globalusage=1&ns0=1 Glamorous, German Federal Archive] ** [http://toolserver.org/~magnus/glamorous.php?doit=1&category=Images+from+the+Tropenmuseum&use_globalusage=1&ns0=1 Tropen Museum] * [http://toolserver.org/~bryan/stats/ Bryan's stats] * [http://toolserver.org/~magnus/amalglamate.php GLAM stats] == Strategic planning process == To do: Skim through http://strategy.wikimedia.org to find related strategy proposals. * [[:strategy:Category:Proposals for improving media usability|Category:Proposals for improving media usability]] * [[:strategy:Category:Proposals for Commons|Category:Proposals for Commons]] * ... == Blog articles == * [http://brianna.modernthings.org/article/40/top-10-software-extensions-wikimedia-commons-needs-in-2008 Top 10 software extensions Wikimedia Commons needs in 2008], Brianna Laugher, December 2007. * [http://brianna.modernthings.org/article/117/the-coming-challenges-for-wikimedia-commons The coming challenges for Wikimedia Commons], Brianna Laugher, July 2008. * [http://blog.wikimedia.de/2009/02/11/bilder-suchen-und-finden-auch-auf-deutsch/ Bilder suchen und finden, auch auf Deutsch], Daniel Kinzler, February 2009. * [http://www.gpaumier.org/blog/251_ten-features-that-would-dramatically-improve-wikimedia-commons/ Ten features that would dramatically improve Wikimedia Commons], Guillaume Paumier, June 2009. * [http://www.gpaumier.org/blog/297_digikam-the-perfect-tool-for-wikimedia-commons-photographers/ digiKam, the perfect tool for Wikimedia Commons photographers?], Guillaume Paumier, September 2009. * http://brianna.modernthings.org/article/241/guest-antweb-goes-cc-by-sa * ... == Mailing list discussions == * [http://lists.wikimedia.org/pipermail/wikitech-l/2007-August/032652.html Commons tech wishlist], Brianna Laugher, August 2007 ([http://lists.wikimedia.org/pipermail/wikitech-l/2007-August/thread.html#32652 thread]). * [http://lists.wikimedia.org/pipermail/wikitech-l/2009-October/045627.html Image view statistics?], Michael Peel, October 2009 ([http://lists.wikimedia.org/pipermail/wikitech-l/2009-October/thread.html#45627 thread]). * ... == SVG tools == * [http://code.google.com/p/svgweb/ svgweb] * [http://jsxgraph.uni-bayreuth.de JSXgraph] == Test environments == * http://prototype.wikimedia.org/sandbox.2/Main_Page * http://commons.prototype.wikimedia.org/wiki/Special:UploadWizard == IxD, UX, etc. == * [http://www.experiencedynamics.com/science-usability/ui-style-guides UI style guides] * [http://uxdesign.com/ux-defined UX design defined] ([http://uxdesign.com/ux-defined-2 page 2]) * [http://experiencematters.wordpress.com/2009/10/31/design-experiences-to-meet-emotional-needs/ Infuse Emotion Into Experience Design] * [http://www.cooper.com/journal/2003/03/design_research_why_you_need_i.html Design Research: Why You Need it] on cooper.com * [http://www.useit.com/alertbox/9605.html Top 10 mistakes in web design] Organizations: * [http://iainstitute.org/ Information Architecture Institute] * [http://www.ixda.org Information Design Association] * [http://www.baychi.org/baydux/ BayDUX] * [http://uxnet.org User Experience Network] Tools: * [http://websort.net/ Web Card sorting] == General user survey == * [[:foundation:File:Wikipedia General Survey-Overview 0.3.9.pdf|File:Wikipedia General Survey-Overview 0.3.9.pdf]] * http://www.wikipediastudy.org * [http://www.slideshare.net/philipp/unu-merit-wikipedia-survey Presentation at Wikimania 2009] == Other neat stuff == * http://www.thecssninja.com/demo/drag-drop_upload/ * http://www.angelblade.com/contests/ * http://questioncopyright.org/understanding_free_content * http://gomockingbird.com/mockingbird/index.html?project=acb0b5f1c9ea1f8e3c2d3584377999fcd1f613a0 * http://ehive.com/create * [http://www.youtube.com/watch?v=MxpjGZinies End-user programming] * [[:w:en:WAI-ARIA|WAI-ARIA]] * http://museums.wikia.com/wiki/MuseumsWiki * http://www.pictura-im.nl/ * http://thecleversheep.blogspot.com/2008/11/12-tools-to-teach-about-creative.html * http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline * http://www.useit.com/alertbox/20000319.html * [[:m:Dynamic links to external resources]] </div> [[Category:Multimedia usability]] a3tshw1jl7txio04jtitvzludgpnepo 8 633 3563 3562 2009-10-15T18:19:40Z Guillom 13 tsss wikitext text/x-wiki Multimedia hub l5a57gypv0r7xomrfl1x2ltt5mxkwb4 8 634 3564 2009-10-15T18:20:03Z Guillom 13 Multimedia:Hub wikitext text/x-wiki Multimedia:Hub qcv0jct78xoke691xzwty48s1j44wz9 14 635 3567 2009-10-15T18:22:34Z Guillom 13 [[Category:Root]] wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 0 637 3594 3591 2009-10-15T22:39:32Z Erik Zachte 309 wikitext text/x-wiki ==Squid Log Scan Fact Sheet== The idea is to extract from the 1:1000 sampled squid log the edit and submit calls that are relevant to the usability project and track edit/save ratio of relevant calls over time. #Only script index.php #Only mime type "text/html" #Only article space 0 (few newbees will edit other namespaces) #No failed calls #No edit calls that were result of clicking a link to a not existing page, as most probably 95% are unintentional edit calls, where people who do not know what a red link implies clicked that link. #No requests issued by bots #No incomplete log records (where e.g. destination wiki is masked) The following are frequencies in which index.php result codes are found in the 1:1000 sampled squid logs from just over 6 months: Note: counts needs update, criteria 1-3 were not yet applied TCP_DENIED/403,action=edit 321390 TCP_DENIED/403,action=submit 33 . TCP_MISS/000,action=edit 7352 TCP_MISS/000,action=submit 1186 . TCP_MISS/200,action=edit 800200 TCP_MISS/200,action=submit 75768 TCP_MISS/206,action=edit 20 TCP_MISS/206,action=submit 269 . TCP_MISS/301,action=edit 662 TCP_MISS/302,action=edit 184217 TCP_MISS/302,action=submit 116141 . TCP_MISS/400,action=edit 6 TCP_MISS/403,action=edit 2746 TCP_MISS/404,action=edit 119 TCP_MISS/404,action=submit 206 TCP_MISS/417,action=edit 53 TCP_MISS/417,action=submit 716 . TCP_MISS/500,action=edit 362 TCP_MISS/500,action=submit 81 TCP_MISS/502,action=submit 87 TCP_MISS/503,action=edit 7 TCP_MISS/503,action=submit 5878 TCP_MISS/504,action=edit 53 TCP_MISS/504,action=submit 91 Here are the relevant html codes from [http://wiki.squid-cache.org/SquidFaq/SquidLogs Squid FAQ] (see also [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html w3 spec]): 000 Used mostly with UDP traffic. 200 OK 206 Partial Content 301 Moved Permanently 302 Moved Temporarily 400 Bad Request 403 Forbidden 404 Not Found [417 Expectation Failed] 500 Internal Server Error 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout ;Discard errors *TCP_DENIED is almost exlusively bad requests from ill behaving browsers. *Status codes with range 400 or above are valid but failed requests, e.g. the squid server could not pass on the request to a server or service (TCP_MISS/503) ;Discard cruft *Status codes that occur on less than 1% or all requests (000, 206 and 301) have not been not further investigated, and are discarded. This first selection leaves TCP_MISS/200,action=edit 800200 [1] TCP_MISS/302,action=edit 184217 [2] . TCP_MISS/200,action=submit 75768 [3] TCP_MISS/302,action=submit 116141 [4] ;Discarding clicks to non existing pages url contains 'redlink=1' TCP_MISS/200,action=edit 434602 [1] TCP_MISS/302,action=edit 492 [2] . TCP_MISS/200,action=submit 75768 [3] TCP_MISS/302,action=submit 116141 [4] Explanation: Almost all TCP_MISS/302 (2) are result of clicking a missing link. Roughly half of TCP_MISS/200 (1) are as well. So missing links can result in 200 or 302, this initially was somewhat confusing. On further inspection this turns out to be language dependent (configuration item ?). Here are counts for wikis with most hits: 30108,wp:de,action=edit,redlink=1,TCP_MISS/200 1759,wp:de,action=edit,redlink=1,TCP_MISS/302 6756,wp:en,action=edit,redlink=1,TCP_MISS/200 129361,wp:en,action=edit,redlink=1,TCP_MISS/302 56032,wp:es,action=edit,redlink=1,TCP_MISS/200 2332,wp:es,action=edit,redlink=1,TCP_MISS/302 23094,wp:fr,action=edit,redlink=1,TCP_MISS/200 493,wp:fr,action=edit,redlink=1,TCP_MISS/302 19301,wp:it,action=edit,redlink=1,TCP_MISS/200 646,wp:it,action=edit,redlink=1,TCP_MISS/302 49288,wp:ja,action=edit,redlink=1,TCP_MISS/200 5569,wp:ja,action=edit,redlink=1,TCP_MISS/302 9585,wp:nl,action=edit,redlink=1,TCP_MISS/200 558,wp:nl,action=edit,redlink=1,TCP_MISS/302 13210,wp:pl,action=edit,redlink=1,TCP_MISS/200 121,wp:pl,action=edit,redlink=1,TCP_MISS/302 18140,wp:pt,action=edit,redlink=1,TCP_MISS/200 318,wp:pt,action=edit,redlink=1,TCP_MISS/302 26393,wp:ru,action=edit,redlink=1,TCP_MISS/200 1345,wp:ru,action=edit,redlink=1,TCP_MISS/302 398,wp:zh,action=edit,redlink=1,TCP_MISS/200 15875,wp:zh,action=edit,redlink=1,TCP_MISS/302 ;Discard previews and unsuccessful saves When a user clicks the 'Save Page' or 'Preview' buttons, script index.php is invoked with parameter 'action=submit'. The extra info that tells script index.php how to respond is not available in the squid log. But much can be learned from the result code. :TCP_MISS/200 (3): result of a preview request or unsuccessful save (e.g. edit conflict) :TCP_MISS/302 (4): result of successful save, were user is redirected to the saved page. TCP_MISS/200,action=edit 434602 [1] TCP_MISS/302,action=edit 492 [2] . TCP_MISS/302,action=submit 116141 [4] ;Discard further cruft (2) TCP_MISS/200,action=edit 434602 [1] TCP_MISS/302,action=submit 116141 [4] ;Breakdown by User/Bot bot=N,TCP_MISS/200,action=edit 300183 bot=Y,TCP_MISS/200,action=edit 134419 . bot=N,TCP_MISS/302,action=submit 83814 bot=Y,TCP_MISS/302,action=submit 32327 Code used to detect bots is roughly this: if agent string contains <nowiki>'http://'</nowiki> # url only allowed/expected with bots and agent string does not contain 'bsalsa.com' # exception: bsalsa messed up, see http://www.bsalsa.com/forum/showthread.php?t=724 and agent string does not contain MSIE + version number # most likely false positives then bot is true if agent contains 'bot' or 'crawl(er)' or 'spider' then bot is true Note: the large edit:save ratio for bots obviously has nothing to do with usability. Possibly some bots access articles without intention to save, e.g. to harvest raw text parameters for info box, or list of used templates. ;Discard bots bot=N,TCP_MISS/200,action=edit 300183 bot=N,TCP_MISS/302,action=submit 83814 ;Count edit/submits and ratio per wiki (show here when combined 100 or more) wk:lt edits 133, submit 3, ratio 44.3 wx:mw edits 411, submit 30, ratio 13.7 wk:es edits 194, submit 24, ratio 8.1 wp:id edits 1758, submit 233, ratio 7.5 wp:ms edits 530, submit 71, ratio 7.5 wb:de edits 245, submit 34, ratio 7.2 wb:pt edits 125, submit 18, ratio 6.9 wp:sw edits 239, submit 41, ratio 5.8 wp:af edits 154, submit 27, ratio 5.7 wx:meta edits 449, submit 86, ratio 5.2 wb:es edits 108, submit 22, ratio 4.9 wp:ja edits 13904, submit 2813, ratio 4.9 wp:pt edits 8977, submit 1875, ratio 4.8 wb:fr edits 82, submit 18, ratio 4.6 wp:es edits 18430, submit 4038, ratio 4.6 wp:eo edits 420, submit 93, ratio 4.5 wk:no edits 119, submit 27, ratio 4.4 wp:fa edits 1220, submit 275, ratio 4.4 wp:el edits 636, submit 148, ratio 4.3 wp:tl edits 287, submit 69, ratio 4.2 wk:ru edits 243, submit 66, ratio 3.7 wp:ro edits 956, submit 260, ratio 3.7 wp:th edits 949, submit 265, ratio 3.6 wp:bs edits 114, submit 33, ratio 3.5 wp:ta edits 127, submit 36, ratio 3.5 wb:en edits 439, submit 131, ratio 3.4 wk:it edits 82, submit 24, ratio 3.4 wp:vi edits 845, submit 257, ratio 3.3 wk:de edits 205, submit 66, ratio 3.1 wk:fr edits 577, submit 193, ratio 3.0 wp:sq edits 116, submit 39, ratio 3.0 wp:hr edits 478, submit 163, ratio 2.9 wp:bg edits 705, submit 256, ratio 2.8 wp:da edits 614, submit 222, ratio 2.8 wp:mr edits 84, submit 30, ratio 2.8 wp:pl edits 4603, submit 1635, ratio 2.8 wp:tr edits 2803, submit 992, ratio 2.8 wp:ar edits 1852, submit 689, ratio 2.7 wp:en edits 88576, submit 32352, ratio 2.7 wp:ko edits 1670, submit 618, ratio 2.7 wp:nl edits 4226, submit 1565, ratio 2.7 wp:sk edits 330, submit 121, ratio 2.7 wp:de edits 14306, submit 5505, ratio 2.6 wp:ru edits 9094, submit 3541, ratio 2.6 wp:sr edits 620, submit 242, ratio 2.6 wp:zh edits 3273, submit 1254, ratio 2.6 wk:en edits 1184, submit 477, ratio 2.5 wp:cs edits 1005, submit 408, ratio 2.5 wp:lv edits 143, submit 57, ratio 2.5 wx:species edits 221, submit 90, ratio 2.5 wk:pt edits 156, submit 64, ratio 2.4 wp:fr edits 10463, submit 4433, ratio 2.4 wp:lb edits 79, submit 33, ratio 2.4 wv:en edits 123, submit 51, ratio 2.4 wp:it edits 7249, submit 3138, ratio 2.3 wk:tr edits 85, submit 39, ratio 2.2 wn:en edits 134, submit 61, ratio 2.2 wp:ka edits 172, submit 82, ratio 2.1 wp:mk edits 176, submit 83, ratio 2.1 wk:ko edits 69, submit 34, ratio 2.0 wp:fi edits 1222, submit 603, ratio 2.0 wp:hu edits 1536, submit 776, ratio 2.0 wp:lt edits 316, submit 159, ratio 2.0 wp:sl edits 225, submit 113, ratio 2.0 wp:no edits 855, submit 444, ratio 1.9 wp:simple edits 332, submit 177, ratio 1.9 wp:sv edits 1733, submit 895, ratio 1.9 wp:he edits 1332, submit 722, ratio 1.8 wp:ml edits 119, submit 67, ratio 1.8 wq:en edits 159, submit 89, ratio 1.8 wp:eu edits 122, submit 71, ratio 1.7 wp:uk edits 754, submit 456, ratio 1.7 wm:incubator edits 81, submit 51, ratio 1.6 wp:br edits 71, submit 48, ratio 1.5 wp:ca edits 700, submit 454, ratio 1.5 wp:et edits 226, submit 148, ratio 1.5 wp:la edits 109, submit 74, ratio 1.5 wp:az edits 108, submit 75, ratio 1.4 ws:de edits 151, submit 111, ratio 1.4 ws:en edits 190, submit 134, ratio 1.4 wx:commons edits 4710, submit 3445, ratio 1.4 wk:fi edits 100, submit 75, ratio 1.3 wp:gl edits 129, submit 98, ratio 1.3 wp:hi edits 198, submit 147, ratio 1.3 wp:nn edits 68, submit 54, ratio 1.3 ws:fr edits 176, submit 138, ratio 1.3 ws:ru edits 100, submit 80, ratio 1.3 wk:nl edits 77, submit 78, ratio 1.0 wk:pl edits 105, submit 174, ratio 0.6 . total shown edits 223571, submit 79506, ratio 2.8 . wb:Wikibooks, wk:Wiktionary, wn:Wikinews, wp:Wikipedia, wq:Wikiquote, ws: Wikisource, wv:Wikiversity, wx:special wiki '''Caveat 1''': What is strange is that wx:mw (mediawiki wiki) and meta have high edit/submit counts. One would expect mostly experienced editors there, and therefor a edit/submit ratio closer to 1 than on other wikis. Further research, cross checking needed. '''Caveat 2''': If certain user assisted (= semi-automatic) bots would no be recognized as bots (= give no clue in the agent string in the squid log record), that would give serious pollution of the counts. For instance if a spell checker bot asks the user to confirm a suggested correction directly in the edit screen, that could generate hundreds of aborted edits in one evening session. further research , cross checking needed. [[File:EditSaveRatio.png]] [[File:SavesPerDay.png]] 0gj69oundvp0fgfruzf684at0feuqej 0 638 3585 3584 2009-10-15T22:00:29Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki == Parul's Notes == * quality control * logs in - camera/performance * hits edit. now i got a page with code - this is probably too technical for me! * there's a toolbox (looking through left navigation) * gives up quickly (looking for how to make a new section) * editing text even while deleting...i won't mess with that * edits by section and looking for examples * playing around - trying to link to a page that doesn't exist * creates new page for teacher - nothing/no code - maybe he's used to seeing code * too lazy for help * explore toolbar * link - struggles until the icon is to the right * superscript * sees template text - goes back and forth to verify it's infobox (with poking) * would assume that header section would be in the code first * trial and error - superscript * comfortable with captcha - like on craigslist * table generation! * highlights text for references - expects highlighted part to be in text body and goes to figure out how to add the "footer/ref" text * like a word doc. would prefer if it was like a word document * for a mac user this is a bit unusual * dl7uqezfxxjolzcc6n3f4gt8eervg4o 0 639 3595 3588 2009-10-15T22:48:31Z Parul Vora~usabilitywiki 185 /* Parul's Notes */ wikitext text/x-wiki == Parul's Notes == * my peers are the referees * clxa98376byw4flcfw70huqg39qqa7c 6 640 3592 3589 2009-10-15T22:29:17Z Erik Zachte 309 uploaded a new version of &quot;[[File:EditSaveRatio.png]]&quot; wikitext text/x-wiki First attempt to plot Edit/Save ratio for large wikipedias (further testing/cross checks needed) hvtr6io6ulhnkxdq30pnz9wkcbvf1ju 6 641 3593 3590 2009-10-15T22:29:32Z Erik Zachte 309 uploaded a new version of &quot;[[File:SavesPerDay.png]]&quot; wikitext text/x-wiki First attempt to plot Saves per day for largest wikipedias (more tests and cross checks needed) eapxq4uq5sy9rj6okrhb6j917cg5o7n 14 642 3603 2009-10-16T09:32:34Z Guillom 13 [[Category:Multimedia usability]] wikitext text/x-wiki [[Category:Multimedia usability]] ah4y36oij9fcyo95gwbbnkrumkixhzv 100 643 4993 4990 2009-12-12T00:37:06Z Guillom 13 on second thought wikitext text/x-wiki Wikimedia France is organizing, in collaboration with the Wikimedia Foundation, a '''[[:m:Multimedia Usability Project Meeting France|meeting in Paris]]''' related to multimedia participation on Wikimedia projects. It will take place on 6-8 November 2009. IRC channel open during the entire meeting: #WikimediaMultimedia on <irc.freenode.net>. Twitter hashtag: [http://twitter.com/#search?q=%23WikimediaMultimedia #WikimediaMultimedia] == Relevant pages == * '''[[Multimedia:Meeting in Paris/Notes|Documentation]]''' ** [[Multimedia:Meeting in Paris/Summary|Summary]] * [[:m:Multimedia Usability Project Meeting France/Participants|Participants]] * [[:m:Multimedia Usability Project Meeting France/Request for comments|Request for comments]] * [[:m:Talk:Multimedia Usability Project Meeting France/Request for comments|Brainstorming page]] (in English) * [[:m:Multimedia Usability Project Meeting France/fr/ideas|Brainstorming page]] (in French) * [[m:Multimedia Usability Project Meeting France/Schedule/Demos|Demos]] * [http://spreadsheets.google.com/pub?key=tr9gZCyNHBFtKwxWJYCJzmA&single=true&gid=0&output=html schedule] * [http://blog.wikimedia.fr/ameliorer-lergonomie-de-wikimedia-commons-pour-encourager-la-participation-1157 Article from Delphine], on Wikimedia France's blog (French) == Photos == See [[:commons:Category:Wikimedia Multimedia Usability Meeting 2009|Category:Wikimedia Multimedia Usability Meeting 2009]] on Wikimedia Commons. <gallery> File:Multimedia Workshop 2009 007.jpg|Michael Dale presenting Add Media Wizard work File:Multimedia Workshop 2009 008.jpg|Michael Dale walking through his demos File:Multimedia Workshop 2009 009.jpg|Ryan Kaldari presenting his [http://angelblade.com/contests custom front-end] for managing photo contests File:Multimedia Workshop 2009 010.jpg|[[:commons:User:Husky|Hay Kranen]] presenting the [http://wikiportret.nl/ custom front-end] developed by Wikimedia Nederlands for managing celebrity photo submissions (in the [http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/wikiportrait/ MediaWiki SVN repo] now!) File:Multimedia Workshop 2009 011.jpg|Magnus Manske presenting his selection of crazy tools File:Multimedia Workshop 2009 012.jpg|Jan and Michael hacking File:Multimedia Workshop 2009 013.jpg|Ryan Kaldari and Samuel Klein File:Multimedia Workshop 2009 014.jpg|Magnus Manske and Brion Vibber File:Multimedia Workshop 2009 015.jpg|Mathias Schindler and Frank Schulenburg </gallery> == Preparation == * Collect data before the meeting *: [[Multimedia:Preliminary user research|Preliminary user research]] *: [[Multimedia:Initial survey|Initial survey]] == Expectations == * Goals of the team: identifying major issues, exploring and assessing solutions, and coming up with a draft roadmap. * We have an opportunity here to accomplish much more than "just" what the Ford team is able to do. * Gathering of people with much experience, ideas and expertise; it would be a shame to only focus on the multimedia usability project, because we just can't address all issues. * Joint projects: let the community, volunteers and chapters engage in activities and projects in a larger plan. * Some areas of discussion (e.g. partnerships) may not fit exactly in the [[Multimedia:Meeting in Paris/Notes/Backbone|proposed workflow]] of the meeting; be bold and creative. [[Category:Multimedia usability - Research]] [[Category:Multimedia usability - Meetings]] [[Category:Multimedia meeting in Paris|*]] m3w7ofnhw600v4r3jly1ahh20nvlp45 100 644 8988 8987 2010-10-12T22:11:09Z Guillom 13 polish wikitext text/x-wiki The main goal of the survey was to get a better understanding of why the respondents used Wikimedia Commons (or why they did not), what activities they engaged in and why; it was part of our [[Multimedia:Preliminary user research|preliminary user research]]. An underlying goal was to see how users reflected upon their own use of Wikimedia Commons, and to compare this subjective self-reflection to objective data. Last, we wanted to identify behavioral patterns based on correlations between goals, activities and levels of activity. The survey ran during three days and was linked from all Wikimedia websites for all logged-in users. It was [[:m:Media participation survey|available in 20 languages]] in order to address the multilingual nature of Wikimedia websites and particularly Commons. During this time, 25,150 complete responses to the questionnaire were recorded. We used Pearson's χ² tests to evaluate the independence or correlation of some factors, using a threshold of 0.01%. == Schedule == The goal was to have some data before the [[Multimedia:Meeting in Paris|Meeting in Paris]] (6-8 November 2009). The fundraising team needed the sitenotice starting November 2nd. We had a very short window of 1 week (26 October - 1 November), which meant translating the survey in 2-3 days. == Results == ''Larger versions of the charts are available at the end of this document.'' === Users === [[File:Media survey 2009 - 1. Why and why not use.svg|thumb|Reasons for looking up files in Commons (or not).]] First, we asked the users if they used Wikimedia Commons, and for what purpose; if they used it infrequently or not at all, we asked why not ({tab:survey-why-use}). Almost 2/3 (62%) of the respondents declared they used Commons (users), while the others declared they did not (non-users). More than half the users identified their main goal when searching files on Commons as to illustrate an article on Wikipedia or another Wikimedia project<ref group="Note">See [[#Limitations|Limitations]].</ref>; the second goal was to use media files offline. We also investigated the reasons why some respondents did not use Commons; given that the target audience of the survey was logged-in Wikimedia users, we expected them to be aware of Commons, even if they did not participate in it. On the contrary, it appeared that 70% of the respondents who did not use Commons simply did not know about it until the survey. Other reasons included issues due to the search feature or the predominance of English as the ''lingua franca''. {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Distribution of the major motivations chosen by respondents when asked why they used Wikimedia Commons |- ! Reason to use Commons !! Respondents !! (%) |- | to illustrate Wikip/media || 8611 || 55% |- | to use offline || 4331 || 28% |- | to use online || 1426 || 9% |- | other || 1369 || 9% |} {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Distribution of the major motivations chosen by respondents when asked why they did not used Wikimedia Commons |- ! Reason not to use Commons !! Respondents !! (%) |- | don't know Commons || 6578 || 70% |- | other || 1235 || 13% |- | search issues || 893 || 9% |- | English issues || 707 || 8% |} === Motivations to participate === [[File:Media survey 2009 - 4. Why participate.svg|thumb|Main goals of participants.]] The users were then asked if they also participated in the activities of Wikimedia Commons. More than half the users (60% of users, 37% of respondents) declared they did. Baytiyeh & Pfaffman recently studied the motivations of "administrators" volunteering their time on Wikipedia<ref name="Baytiyeh2009">''[http://portal.acm.org/citation.cfm?id=1600117 Why be a Wikipedian].'' H. Baytiyeh and J. Pfaffman. In ''CSCL'09: Proceedings of the 9th international conference on Computer supported collaborative learning'', pages 434-443. International Society of the Learning Sciences, 2009.</ref>. They found that the main reason was a desire to learn and "an altruistic desire to create a resource for others to use". Our survey was broader and was not intended to be as thorough as Baytiyeh's; however, the fundamental difference between Wikipedia and Wikimedia Commons elicited our curiosity: were the motivations shared universally amongst Wikimedia projects? We asked the participants to identify the main reason why they participated in Wikimedia Commons ({tab:survey-why-participate}). 65% of respondents declared their main motivation was to illustrate Wikipedia or another Wikimedia projects. The altruistic desire to share with the world was consciously identified as main reason to contribute by only 11% of respondents; this proportion reaches 28% when consolidated with similar, but less explicit answers. Overall, contributing to Wikimedia Commons is widely considered by participants as a means to illustrate Wikipedia (or other Wikimedia projects), rather than a goal in itself. {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Distribution of the major motivation chosen by the respondents when asked why they participated in Wikimedia Commons. |- ! Reason to participate in Commons !! Respondents !! (%) |- | to illustrate Wikip/media || 6045 || 65% |- | to share with the world || 1001 || 11% |- | to keep Commons running || 979 || 10% |- | to collect free works || 689 || 7% |- | for fun || 408 || 4% |- | other || 230 || 2% |} [[File:Media survey 2009 - 5. Why not participate.svg|thumb|Main reasons for not participating.]] Users who stated they participated only infrequently or not at all were asked why not ({tab:survey-why-not-participate}). Our hypothesis was that the upload process (interface & policies) was too complicated, especially for users who did not speak English. In reality, 2/3 of the non-participants gave a reason related to a lack of awareness or appeal from Wikimedia Commons (they had other priorities, they were not interested or they did not even know they could participate). Only 12% or non-participants mentioned the perceived technical or legal complexity of the upload process as the major reason for not participating. It must however be emphasized that these reasons are intertwined: some respondents explained that participating in Commons was not a priority because the complexity of the upload process required a lot of time. These results show the need for a large-scale communication and outreach campaign to raise awareness and understanding about Wikimedia Commons. In order to facilitate the perennial recruitment of new participants, we suggest to hold this campaign only after significant improvements have been made to the user experience on Commons. {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Distribution of the major reason chosen by the respondents when asked why they did not participate in Wikimedia Commons. |- ! Reason to participate in Commons !! Respondents !! (%) |- | have other priorities || 1886 || 28% |- | did not know they could || 1327 || 19% |- | are not interested || 933 || 14% |- | upload is complex || 785 || 11% |- | other|| 583 || 9% |- | confusing classification || 478 || 7% |- | English issues || 393 || 6% |} === Motivations & levels of participation === In order to make behavioral patterns emerge, we looked for correlations between motivations and levels of participation. A strong correlation can be established between respondents who uploaded between 10 and 100 files, and respondents whose main motivation is to illustrate Wikipedia. On the other hand, these participants care significantly less about the mission (to collect free works) or the functioning (to keep it running) of Wikimedia Commons, and rarely associate it with "having fun". A similar correlation shows for participants who uploaded between 100 and 1000 files, whose main goal is to illustrate Wikipedia and who are significantly less interested in keeping Commons running. Our proposed explanation is that participants in these two groups are mainly "Wikipedians", uploading media files to Commons on an as-needed basis, while writing or improving articles on Wikipedia. Another correlation exists between respondents who uploaded more than 10,000 files and those who identify "fun" as their main motivation. On the other hand, these highly active "Commoners" care significantly less about illustrating Wikipedia or other Wikimedia websites. === Activities & levels of participation === ==== General analysis ==== [[File:Media survey 2009 - 2. Files uploaded.svg|thumb|Distribution of respondents by amount of files uploaded to Commons.]] We asked the participants how many files they had uploaded to Wikimedia Commons, how many edits they had made there and the frequency at which they performed certain tasks. We were surprised to find that half the participants declared they had uploaded less than 10 files to Commons: this means that many Wikimedia participants upload very few media files to Commons, or even none at all. Another third occasional participants uploaded between 10 and 100 files ({tab:survey-files-uploaded}). {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Distribution of respondents by number of media files uploaded to Wikimedia Commons. |- ! Files uploaded !! Respondents !! (%) |- | less than 10 || 4698 || 50% |- | 10 to 100 || 3048 || 33% |- | 100 to 1000 || 1238 || 13% |- | 1000 to 10000 || 273 || 3% |- | more than 10000 || 93 || 1% |} ==== Correlations ==== There is a strong correlation between the frequency of upload and the number of files uploaded. While it may seems obvious for modest participants, this finding is particularly significant for highly active users, who not only contribute many media files, but do so on a regular basis. A strong correlation can also be established between the number of uploads and the number of edits. Participants who upload a lot of media files (and thus contribute the most content) are also the most active participants with regard to general maintenance activities. Last, participants who upload a high number of files are correlated to those who work significantly on categories. Our proposed explanation is that participants who upload many files are experienced users; they are familiar with the policies and guidelines of Commons, particularly the need to classify the content appropriately in order to facilitate its findability by other users. === Language & project of origin === [[File:Media survey 2009 - 6. Referrers.svg|thumb|Referrer of respondents.]] Given the multilingual and central nature of Wikimedia Commons, one of our goals was also to weigh the influence of the language and website of origin. During the survey, we recorded the HTTP referrer of all respondents and consolidated these results by language, using the ISO 639-1 code. Then, we looked for correlation between the language and the participation, in order to identify possible patterns. We integrated the number of articles in each associated language version of Wikipedia, provided by the [[Special:Statistics]] page as of May 3rd, 2010. Likelihood to participate in Commons was determined by studying the correlation between participants from each language, and participants who reported they participate in Commons "regularly", "sometimes" or "not at all". For languages not included in these results, no conclusive correlation could be established with a behavioral pattern. Three groups stood out ({tab:lang-size-participation}). Respondents coming from Wikimedia websites in Arabic, Bulgarian, Catalan, Czech, Danish, Finnish, French, Hebrew, Italian, Dutch, Norwegian, Polish, Swedish and Chinese language are correlated with regular participants in Wikimedia Commons. Users from projects in German, Hungarian and Vietnamese language are in a similar but less pronounced situation. On the other hand, respondents originating from a Wikimedia project in English, Japanese, Portuguese, Russian and Turkish language show the opposite correlation: many of them do not participate in Wikimedia Commons. The size of Wikipedia does not seem to be a decisive factor; we suggest that policies and culture on each wiki are, in fact, mostly responsible for these differences. {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Likelihood to participate in Wikimedia Commons depending on the language of origin. |- ! [[:w:ISO 639-1|ISO 639-1]] !! Language !! Articles !! Participation |- | en || English || 3280896 || not likely |- | de || German || 1062882 || likely |- | fr || French || 943683 || very likely |- | pl || Polish || 697703 || very likely |- | it || Italian || 683962 || very likely |- | ja || Japanese || 673245 || not likely |- | nl || Dutch || 600749 || very likely |- | pt || Portuguese || 567177 || not likely |- | ru || Russian || 531270 || not likely |- | sv || Swedish || 355065 || very likely |- | zh || Chinese || 307064 || very likely |- | no || Norwegian || 257380 || very likely |- | ca || Catalan || 240267 || very likely |- | fi || Finnish || 237528 || very likely |- | cs || Czech || 162116 || very likely |- | hu || Hungarian || 160724 || likely |- | tr || Turkish || 143958 || not likely |- | da || Danish || 128272 || very likely |- | ar || Arabic || 126284 || very likely |- | vi || Vietnamese || 120572 || likely |- | he || Hebrew || 103943 || very likely |- | bg || Bulgarian || 97211 || very likely |} === Own works === ==== General analysis ==== [[File:Media survey 2009 - 3. Own works.svg|thumb|Proportion of own works among the respondents' uploads.]] From a workflow point of view, it makes a significant difference whether users are uploading works they created themselves ("own works") or works created by other people (either relatives or strangers). If they created the work themselves and they want to share it on a Wikimedia website, they only have to choose a free license compatible with the Wikimedia licensing policy. Uploading someone else's work requires a completely different workflow, involving the possibility to check with third-party copyright holders that they actually gave permission to use their work under the specified free license. In order to gain a better understanding of these two cases, we asked the users to evaluate the proportion of own works amongst the total number of files they had uploaded. Based on preliminary analysis, we originally defined four slices: less than 10%, from 10% to 50%, from 50% to 90% and more than 90% own works ({tab:survey-own-works}). It appeared the answers were generally very similar for users in the two central groups (between 10% and 90%). The two extreme groups, however, are most significant; 39% of the participants declared they had uploaded more than 90% of own works, thus constituting a group of "Creators" (photographers, illustrators, mapmakers, etc.). 32% of the participants uploaded less than 10% of own works. {| class="wikitable sortable" style="margin: 1em auto 1em auto;" |+ Distribution of the proportion of own works according to the respondents. |- ! Own works !! Respondents !! Respondents (%) |- | less than 10% || 3010 || 32% |- | 10% to 50% || 1315 || 14% |- | 50% to 90% || 1399 || 15% |- | more than 90% || 3626 || 39% |} ==== Own works & upload frequency ==== A strong correlation can be established between the ratio of own works and the frequency of uploads. Participants who uploaded less than 10% of own works are also the ones who rarely upload media files at all. Similarly, there is a strong correlation between participants who uploaded between 10 and 90% of own works and those who upload new files on an occasional or a regular basis. Last, participants who uploaded more than 90% of own works are correlated to the participants who upload new files very often. ==== Own works & motivations ==== From an outreach and recruitment point of view, it is of particular interest to analyze the motivations of participants depending on their ratio of own works. For example, our initial hypothesis was that participants who uploaded less than 10% of own works would be "Wikipedians" who occasionally looked for acceptable files to illustrate their article and uploaded them to Commons. In reality, our results show there is a strong correlation between participants who uploaded less than 10% of own works and the participants motivated by fun, the collection of free works and the functioning of Commons. On the contrary, these users show a significantly lower motivation for illustrating Wikipedia. Our proposed explanation is that users who uploaded less than 10% of own works are actually "Gleaners", who look for media files of interest, under an acceptable license, and collect them on Wikimedia Commons. Similarly, we expected participants who uploaded more than 90% of own works ("Creators") to be mainly motivated by fun or the desire to share their work with the world. In reality, while there is indeed a correlation between these users and the desire to share with the world, a correlation can also be established with users whose main motivation is to illustrate Wikipedia or another Wikimedia project. These users are significantly less motivated by fun or the will to keep Commons running. "Creators" are thus not necessarily "Commoners"; a large part of them are actually "Wikipedians". === Limitations === As with any survey, there is a possibility that the respondents did not understand the intended meaning of the questions. We introduced control questions to identify and limit such misunderstandings. Also, some respondents may have misjudged their actual levels of participation. We provided links to automated tools to help them check these metrics during the questionnaire. Last, the study was originally intended to be targeted at all visitors of Wikimedia Commons, as well as all logged-in users from all Wikimedia websites. A technical glitch prevented us from targeting logged-out visitors; it therefore introduced a Wikimedia-specific bias in the analysis of why the respondents used Wikimedia Commons. This means our results focus on the "active" Wikimedian population, and further research will be necessary to better understand the "passive" users of Wikimedia Commons<ref group="Note">"Active" users are generally called "editors", or "participants", and "passive" users "readers". However, in the case of a media library, "readers" does not really apply. </ref>. == Conclusions == This study was realized as part of a research-driven design process aiming to improve the user experience while contributing multimedia content to Wikimedia websites. We showed that the nature of Wikimedia Commons made it unique, different both from popular media sharing platforms and from other Wikimedia websites. The growth of its content has been dramatically faster than the one of its community. New tools and/or processes have to be developed in order to help the community absorb the increasing inflow of new files. We presented the results of an online user survey, which showed that Commons was not very well known and used, even among Wikimedia participants: half the respondents had uploaded less than 10 files. Commons is considered by many to be only a mean to add a media file to a page on another Wikimedia project, such as an article on Wikipedia. By analyzing the correlations between the answers of the respondents, we identified several types of users, such as "Wikipedians", "Commoners", "Creators" and "Gleaners". Further research is needed to understand the influence of language on a multilingual and multicultural collaborative website like Wikimedia Commons. As the first study on this topic, and particularly on Wikimedia Commons, our research was exploratory by nature. Our results confirmed some hypotheses we made, but also clearly invalidated others. This conclusion naturally demonstrates the need for a more thorough investigation about the goals, needs and motivations of users contributing multimedia content to Wikimedia websites, or at least willing to to some extent. The online survey was only one of the venues we used to collect information about users. We also invited them to contribute to an open forum, we interviewed and observed users and we met with stakeholders and subject matter experts. We present the consolidated findings of this additional user research below, as well as the product development process and the design decisions that ensued. == Notes == <references group="Note"/> == References == <references /> == Large versions of the charts == [[File:Media survey 2009 - 1. Why and why not use.svg|thumb|400px|center|Reasons for looking up files in Commons (or not).]] [[File:Media survey 2009 - 2. Files uploaded.svg|thumb|600px|center|Distribution of respondents by amount of files uploaded to Commons.]] [[File:Media survey 2009 - 3. Own works.svg|thumb|600px|center|Proportion of own works among the respondents' uploads.]] [[File:Media survey 2009 - 4. Why participate.svg|thumb|600px|center|Main goals of participants.]] [[File:Media survey 2009 - 5. Why not participate.svg|thumb|600px|center|Main reasons for not participating.]] [[File:Media survey 2009 - 6. Referrers.svg|thumb|1100px|center|Referrer of respondents.]] [[Category:Multimedia usability - Research]] tcyfhwsjqwjacoetik3r2o7wa8sa25c 100 645 3797 3631 2009-10-24T09:06:18Z Guillom 13 /* List of stakeholders */ reworded wikitext text/x-wiki {{draft}} "A stakeholder is any person or organization, who can be positively or negatively impacted by, or cause an impact on the actions of a company, government, or organization." ([[:w:en:Stakeholder analysis|source]]) == List of stakeholders == * regular Commons participants * active wikimedians who don't participate a lot or at all to Commons * professional photographers & artists * OTRS volunteers * people who use Commons but don't participate (yet) * MediaWiki developers * operations/infrastructure team * GLAMs * chapters * ... == Criteria for analysis == * Interest(s) in the project and impact of the project on their goals ** Potential benefits ** Changes required ** Disruption caused * Assessment of impact/power on the project * Assessment of interest in the project * Assessment of adaptability * Potential strategies for obtaining support or reducing obstacles * ... [[Category:Multimedia usability - Research]] evox5t43u55f65m1a9giayax1fugz2m 100 646 9054 9036 2010-10-19T17:26:46Z Guillom 13 /* Tools */ +link wikitext text/x-wiki As defined on [[Multimedia:User research]], the '''Preliminary user research''' is taking place in the [[Multimedia:Project schedule|very early stages of the project]] (October-November 2010). It is mostly formative and consists of [[Multimedia:Ethnographic interviews|Ethnographic interviews]] of users, discussions with [[Multimedia:Stakeholder analysis|stakeholders]], focus groups, and possibly an [[Multimedia:Initial survey|initial survey]]. Goals: * Observing and understanding why and how users use the product * Identifying or confirming (critical) issues users encounter during their use * Collecting input from various [[Multimedia:Stakeholder analysis|stakeholders]] == Tools == * {{UR stats}} Questions that can be answered using a statistical analysis of existing data (for example [http://toolserver.org/~bryan/stats/ Bryan's stats]). This includes a study of [[multimedia:demographics and content dynamics|demographics and content dynamics]]. * {{UR survey}} Questions that can be answered using a [[Multimedia:Initial survey|survey]]. * {{UR interview}} Questions that can be answered using [[Multimedia:Ethnographic interviews|Ethnographic interviews]] / field studies. * {{UR open talk}} Questions that can be answered using an [[:commons:Commons:Usability issues and ideas|open forum]]. == Knowing and understanding the users == Goal: knowing who to design for. ;Who's a user?: A ''user'' is any person passively or actively using the website. A ''participant'' is a user who edits the website. Participants are a subset of the user population. === What do we want to know? === * What does the population of Commons look like? * {{UR stats}} {{UR survey}} What are the different groups of typical users of Commons? What kind of users should we design the product for? (=> extract personas) ** Estimate of ** {{UR stats}} Distribution of participants by number of files uploaded (ranges) ** {{UR stats}} Ratio of "own works" / total ** {{UR stats}} Ratio of massively-imported files (large collections) / total * {{UR survey}} {{UR interview}} What are the users' goals? * {{UR interview}} What is the mental model of the users? How do they think the product works? * {{UR interview}} {{UR open talk}} What do they like about the product? === Participants' goals === The higher goal is mostly universally shared across all participants: sharing free knowledge. However, this may take many forms, e.g.: * The participant's goal is to contribute free content as an encyclopaedic article, a textbook, a lesson etc. and they occasionally want to add a media file to their work. * The participant's goal is to contribute free content by sharing their own media files on Commons. * The participant's goal is to seek existing sources of free content and make them available on Commons by mass import. * The participant's goal is to keep Commons working by engaging in meta-activities (category work, license review & permissions, quality review & promotion). For each goal, we can derive a specific context of use. == Knowing and understanding the context of use == Goal: knowing the constraints & typical workflows. === What do we want to know? === * {{UR survey}} {{UR interview}} What are their typical tasks and activities to achieve these goals? (=> scenarios / use cases) * {{UR survey}} {{UR interview}} Do they edit a lot? Upload a lot? * {{UR interview}} What is the context of use? (work, home? Place in a workflow? Environmental constraints (free license)) * {{UR interview}} What knowledge is required to achieve these goals? (not to actually use the product; e.g. free works) * {{UR stats}} Should we focus our efforts on specific kinds of media types? ** i.e. focus on most represented types because the impact is bigger ** or focus on underrepresented types to encourage participation ** {{UR stats}} Breakdown of media files by type (count by file extension?) ** {{UR stats}} Distribution of media files by size (ranges) == Identifying major issues == Users have a unique insight in the product. As a consequence, they often request changes or new features. It is important for the design team to listen to these suggestions, because they can lead to identifying the underlying issues. In other words, users are welcome to request changes or new features, but it will only really help if they indicate what problem(s) this change or feature would solve. Storytelling is a useful way to achieve this. === What do we want to know? === * {{UR interview}} How easy / difficult is it for a newcomer to participate? * {{UR survey}} {{UR interview}} What are the major hinderances to participating in Commons? * {{UR interview}} {{UR open talk}} What are the users' major frustrations with the current product? == Bibliography == * A. Cooper, R. Reiman & D. Cronin, ''About Face 3: The Essentials of Interaction Design'', Wiley, 2007. == Other resources == * [http://www.intranetjournal.com/articles/200308/ij_08_15_03a.html Law & Order: Content Owners and Developers], Paul Chin, August 2003. * [http://www.intranetjournal.com/articles/200304/ij_04_18_03a.html Survey Says! Measuring Intranet User Response], Paul Chin, April 2003. ([http://www.intranetjournal.com/articles/200304/ij_04_18_03b.html part 2]) [[Category:Multimedia usability - Research]] 84vaqezf1uo7xfxax7z5lfgfd7l0xy3 100 647 8573 8561 2010-07-26T16:55:26Z Guillom 13 #REDIRECT[[Multimedia:Hub]] wikitext text/x-wiki #REDIRECT[[Multimedia:Hub]] 2ok8cpupk1o05z344e8q2sygnwkkvf0 6 648 3623 2009-10-17T01:04:51Z Trevor Parscal (WMF) 3 Wireframes for improved Babaco dialog boxes. Created by Trevor Parscal. wikitext text/x-wiki Wireframes for improved Babaco dialog boxes. Created by Trevor Parscal. ayv2hlw90d1gqtqgsrsl03wr5um0mlf 6 649 3641 2009-10-17T20:34:40Z Guillom 13 for [[Opinion Watch]] Public domain as far as I'm concerned, existing interface is GPL wikitext text/x-wiki for [[Opinion Watch]] Public domain as far as I'm concerned, existing interface is GPL naxodazhjng6dxtf3gl4w9hvobq8aty 100 650 9371 5367 2011-08-22T12:21:19Z Ruslik0 224 fixing dr wikitext text/x-wiki #REDIRECT [[Multimedia:Upload wizard]] 6h8l6b7tji32aoi6zw4zqyfbxcd6kgv 14 651 3654 2009-10-18T09:33:59Z Guillom 13 [[Category:Multimedia usability]] wikitext text/x-wiki [[Category:Multimedia usability]] ah4y36oij9fcyo95gwbbnkrumkixhzv 100 652 9347 9346 2011-01-04T23:29:01Z 216.38.130.165 wikitext text/x-wiki {{draft}} This page is used by the team to note down ideas & things to remember later. Please do not use it as a general brainstorming page. * [[Multimedia:Permission review workflow]] * easy transfer from any Wikimedia / [[:mw:Manual:$wgForeignFileRepos|$wgForeignFileRepos-enabled]] MediaWiki wiki to Commons * transparent upload from any Wikimedia / [[:mw:Manual:$wgForeignFileRepos|$wgForeignFileRepos-enabled]] MediaWiki wiki to Commons ** => must deal with the "watchlist issue" * red / page background color flag for possible copyright violations * Configurable settings for wikis with an EDP; most usual cases; auto-resize if resolution is too high * view stats inc. geo information (to see if the audience is local or not) * drag-and-drop from the desktop to the browser January 2011 brainstorming * Enable cross-origin request sharing to Apache config for upload.wikimedia.org -- this enables browser-based editing and other forms of reuse. Since upload.wikimedia.org holds no user secrets this is safe. * When temp uploading stable and lasts for days/weeks, then allow bulk uploads with FTP, etc. ** temporary duration of files set by configuration or policy * Licenses in the database. * Searchable by license / license characteristics * What does Toolserver do -- these are candidates for making into "real" features ** We don't really know everything that's on the Toolserver does -- survey, inventory, somehow? * See stats about how many times image viewed / full size download / trackback for used? * Queue of articles that need images or illustrations ** Failed example -- JIRA with Greenspun project ** Successful example -- http://en.wikipedia.org/wiki/Wikipedia:Graphic_lab ? Move this to Commons? (Kaldari-- this is successful because it's a shared community). ** Successful example -- reward board ** Successful example -- WikiCup * Way to regenerate all thumbnails ** Possible to do this by storing relationship between an image and all derivative transformations, then expiring the first * Brainstorm**2 about ways to involve community better ** Fame: Blogposts about contributors (e.g. Bryan Tong Minh) [[Category:Multimedia usability]] 5z9hjnof7qkfxwuaz15sw22i6syzmrv 6 653 3660 2009-10-18T16:26:41Z Dodoïste 287 Screen capture of accessibility issue with the new navigation tabs. wikitext text/x-wiki Screen capture of accessibility issue with the new navigation tabs. 17qqmp6jlonmqaz7gvp3073druy8b2s 10 654 3686 3669 2009-10-19T13:09:54Z Guillom 13 smaller wikitext text/x-wiki [[File:Nuvola apps kmplot.svg|20px|Statistics]]<noinclude>[[Category:Multimedia usability - Templates]]</noinclude> 8figvn04a2js34b29j72yprr5xyeiis 14 655 8636 3670 2010-07-29T13:26:18Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Multimedia usability]] [[Category:Templates]] i3z0xabvimn64awrlxm8xz6fmehqo1g 10 656 3688 3674 2009-10-19T13:10:15Z Guillom 13 smaller wikitext text/x-wiki [[File:Internet-group-chat.svg|20px|Open talk]]<noinclude>[[Category:Multimedia usability - Templates]]</noinclude> jekebz2xz7p49ekc6n06xxjzx7ovv5k 10 657 3689 3673 2009-10-19T13:10:35Z Guillom 13 smaller + fix wikitext text/x-wiki [[File:Help-browser.svg|20px|Survey]]<noinclude>[[Category:Multimedia usability - Templates]]</noinclude> j5jlemj8cmu9bhhgad086l3jygk8wns 10 658 3687 3675 2009-10-19T13:10:04Z Guillom 13 smaller wikitext text/x-wiki [[File:Nuvola apps kuser.svg|20px|Ethnographic interview]]<noinclude>[[Category:Multimedia usability - Templates]]</noinclude> 3undwlkzokanm9rfzkkdodbfdjw31hl 6 662 3725 2009-10-20T16:15:23Z Dodoïste 287 Usually, when I add a new link, I type the text first, then I select it, and I click on the link button. With the new dialog box, when I do that the text I have already written doesn't appear in the "Link text:" form. I am obliged to rewrite it again. wikitext text/x-wiki Usually, when I add a new link, I type the text first, then I select it, and I click on the link button. With the new dialog box, when I do that the text I have already written doesn't appear in the "Link text:" form. I am obliged to rewrite it again. p48ngh6yzin5yadge5r9i87yhytamht 6 664 3741 3740 2009-10-20T19:57:13Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:NewDocument.jpg]]&quot; wikitext text/x-wiki screenshot: new document rthp5xmuc5mr2sjwacd2qlzar4bmfz4 100 668 8975 5626 2010-10-08T22:12:15Z 216.38.130.166 added detailed calendar for Oct. wikitext text/x-wiki {{draft}} <div style="border:solid 1px #B2B2B2;background-color:#E5E5E5;color:#868686;padding:5px;margin-bottom:5px;" > ; 13 - 18 October 2009 * Get started! * Create workspace ([[Multimedia:Hub]] and linked pages) * Start [[Multimedia:Preliminary user research|Preliminary user research]] * Start [[Multimedia:Initial survey|Initial survey]] ; 19 - 25 October 2009 * Finish [[Multimedia:Initial survey|Initial survey]] * Have [[Multimedia:Initial survey|Initial survey]] translated * Put [[Multimedia:Initial survey|Initial survey]] & translations live * Test [[Multimedia:Initial survey|Initial survey]] * Put [[Multimedia:Initial survey|survey]]'s CentralNotice & translations live * Draft project schedule * Prepare [[Multimedia:Ethnographic interviews|Ethnographic interviews]] ; 26 October 2009 - 1 November 2009 * Run [[Multimedia:Initial survey|Initial survey]] * Prepare [[Multimedia:Meeting in Paris|Meeting in Paris]] * Start processing data from [[Multimedia:Initial survey|Initial survey]] ; 2 - 8 November 2009 * Process data from [[Multimedia:Initial survey|Initial survey]] * Continue project planning * Prioritize * Prepare & attend [[Multimedia:Meeting in Paris|Meeting in Paris]] ; 9 - 15 November 2009 * Get up-to-speed after the busy previous week * Process data from [[Multimedia:Meeting in Paris|Meeting in Paris]] * Attend KDE imaging event ; 16 - 22 November * Process data from [[Multimedia:Meeting in Paris|Meeting in Paris]] * Prioritize * Process data from [[Multimedia:Initial survey|Initial survey]] (factor analysis) * Plan, schedule & start running [[Multimedia:Ethnographic interviews|Ethnographic interviews]] ; 23 - 29 November * Go to Paris for visa interview at the US embassy * Continue to run [[Multimedia:Ethnographic interviews|Ethnographic interviews]] ; 30 November - 6 December * Process data from [[Multimedia:Meeting in Paris|Meeting in Paris]] * Process data from [[Multimedia:Open forum]] * Prioritize * Do [[Multimedia:Domain research/Upload|Domain research/Upload]] ; 7 - 13 December * Move to SF * Process data from [[Multimedia:Ethnographic interviews|Ethnographic interviews]] ; 14-20 December * Process data from [[Multimedia:Ethnographic interviews|Ethnographic interviews]] * Do [[Multimedia:Domain research/Upload|Domain research/Upload]] * Process data from [[Multimedia:Meeting in Paris|Meeting in Paris]] * Review UI for the add-media wizard * Start [[:Category:Multimedia usability - Requirements definition|Requirements definition]] ; 21-27 December * Continue [[:Category:Multimedia usability - Requirements definition|Requirements definition]] & prioritize * Analyze & abstractify upload workflow ; End of December 2009 * Design upload workflow * Design mockups for the upload interface * Seek partners for [[Multimedia:Joint projects|Joint projects]] </div> [[File:Multimedia usability - Development & UX plan 20100129.jpg|thumb|Development and UX plan, January 2010]] ; January - February 2010 * Develop first prototype * Prepare [[Multimedia:Lab study|Lab study]] 1 * Prepare 1st report? (perhaps after [[Multimedia:Lab study|Lab study]] 1) * Formalize [[Multimedia:Joint projects|Joint projects]] collaborations with partners ; March 2010 * Put 1st prototype live for [[Multimedia:Lab study|Lab study]] 1 * Run [[Multimedia:Lab study|Lab study]] 1 * Process data from [[Multimedia:Lab study|Lab study]] 1 * Refine workflows & designs * Prepare [[Multimedia:Wikimania|Wikimania]] submission ;April - September 2010 * Research, design, develop, test, refine * Report * Attend [[Multimedia:Wikimania|Wikimania]] ;October 2010 * Oct 8 :Code drop to protoype - backend revisions * Oct 11 :Wikitech - documentation circulation * Oct 15 :Code drop to protoype (frontend improvements) :Blog posts / Village pump / Signpost to get community looking at prototype * Oct 20 :Dark launch to live Commons * Oct 22 :Code drop to protoype (more frontend) * Oct 26 :Due to all-staff meetings, effectively the final working day October -- decide on release now or on Nov 1 ;November * Nov 1 :Launch on live Commons (if not before) :Blog posts announcing launch :Final reports * Nov 5 :Tech blog post :Code drop to prototype * Nov 12 :Code drop to prototype * Nov 15 :Bug fixes deployed to production * Nov 19 :Code drop to protoype * Nov 26 :Code drop to prototype * Nov 29 :Bug fixes deployed to production r4osq6wjkoqr3fchn2nh0jj75jigepp 100 669 9043 5781 2010-10-15T20:11:04Z Guillom 13 typo wikitext text/x-wiki '''Ethnographic interviews''' are part of the [[Multimedia:Preliminary user research|Preliminary user research]]. They consist of field observations and interviews. == Things we want to know == * What are the users' goals? * What is the mental model of the users? How do they think the product works? * What do they like about the product? * What are their typical tasks and activities to achieve these goals? (=> scenarios / use cases) * Do they edit a lot? Upload a lot? * What is the context of use? (work, home? Place in a workflow? Environmental constraints (free license)) * What knowledge is required to achieve these goals? (not to actually use the product; e.g. free works) * How easy / difficult is it for a newcomer to participate? * What are the major hinderances to contributing media content to Wikimedia? * What are the users' major frustrations with the current upload process? == Context & sequence == Contextual inquiries will be performed in the user's usual environment (field observation), in order to cause little disruption and to observe the user as they usually interact with Commons and the upload process. Each interview should not take more than 1 to 2 hours. If human and time resources are not sufficient to collect enough data, phone interviews will be conducted, preferably coupled to a webcam. * Discuss with the user to identify their goal(s). * Ask the user to show us the complete workflow from the creation to the completed upload (or the inclusion of the work to a Wikimedia wiki page if it's their goal). * Let them show us as if they were teaching us how to do what they do. * Ask them to show us precise tasks they perform regularly. * Ask them to show us tasks they perform less often, observe the changes == Persona hypothesis == The goal of the [[:en:Persona (marketing)|persona]] hypothesis is to identify key patterns and to make sure ethnographic interviews cover all these patterns. It is mostly based on preliminary research and existing knowledge about the users. It will be refined using the results of the [[Multimedia:Initial survey|initial survey]]. The interviews will help refine or revise the personas during the [[Multimedia:Modeling|modeling]] phase. Several considerations can help identify and distinguish patterns: * '''Roles:''' The extraordinary diversity of Wikimedians, and the absence of hierarchy or technical specialization make it difficult to identify clear roles, as opposed to those that would emerge in a business environment. * '''Behavioral variables:''' both for passive users (goal when using, way of navigating) and active participants ( frequency of upload, amount of uploads, type of media files uploaded, goal when uploading). * '''Expertise:''' technical expertise (computer literacy, Internet literacy, web 2.0, wikis) and domain expertise (free licenses, local policies of wikis: description/categories, [[:m:Non-free content|Non-free content]], etc.). * '''Environment:''' location, culture, language. We can then propose a first set of hypothesized personas: * '''Agatha''' is an illustrator. She likes to contribute vector diagrams and maps on various subjects to Commons. * '''Audrey''' is an active English Wikipedian who works as a botanist. She writes many articles and occasionally adds pictures to Commons to illustrate her articles. * '''Albert''' is an active Wikipedian who works in IT. He mostly edits sci-fi articles on Wikipedia and uploads fair-use pictures from copyrighted movies and TV series. He almost never uses Commons. * '''Charles''' is an active editor at Wikisource. He scans old documents, uses OCR and proofreads them to provide plain text versions. He uses Commons as a storage place for his scans. * '''Edmond''' is a photographer who loves the idea of Commons, and wants to share his works with the rest of the world. He promotes Commons to his relatives and participates in digging up the best of Commons to make it more visible. * '''Julie''' is project manager for a middle-sized German museum. Her task is to upload 50.000 pictures of works of art to Commons to increase the visibility of her employer. * '''Hercule''' is a retired history teacher with a passion for the French revolution. He only speaks French and wants to illustrate Wikipedia articles with old documents found in archives and libraries. * '''Maurice''' is an OTRS volunteer. He knows a lot about free-works-related intellectual property laws and Commons policies. He often reviews permissions and deletes copyright violations. * '''Niles''' is a photographer and Commons enthusiast. He likes to take pictures of town halls, landscapes and buildings, and uploads them to Commons to illustrate the appropriate pages on Wikipedia. * '''Billie''' is a professional photographer. She contributes middle-resolution, high-quality pictures to Commons to increase her visibility as a photographer. * '''Nina''' is a Spanish middle-aged accountant. She can read some basic English and works on a computer. She knows Wikipedia but has never edited. However, she likes the idea of Commons and would like to participate. * '''Marilyn''' is an amateur photographer who uses other media sharing websites such as flickr. She doesn't use Commons yet but could be interested in sharing her works on Commons too. == Schedule == A call for volunteers was sent on November 18 & 19 on the [[:w:fr:Wikipédia:Le Bistro/19 novembre 2009#Aidez à améliorer l'ergonomie de Commons|village pump of the French Wikipedia]], [[User:Guillom|guillom]]'s [http://www.gpaumier.fr/blog/581_aidez-a-rendre-plus-facile-lajout-dimages-sur-wikipedia/ personal blog] and social networking / microblogging platforms (identi.ca, twitter, facebook). Wikimedia France offered to relay the call on their blog, as part of [http://blog.wikimedia.fr/ameliorer-lergonomie-de-wikimedia-commons-pour-encourager-la-participation-1157 their article about the Meeting in Paris]. Interviews are planned for weeks 47 & 48 in [[:w:fr:Toulouse|Toulouse]] and [[:w:fr:Paris|Paris]]. == Notes == * [[/Adrienne|Adrienne]] * [[/Jastrow|Jastrow]] * [[/Kropotkine|Kropotkine]] * [[/Lucas|Lucas]] [[Category:Multimedia usability - Research]] [[Category:Multimedia usability - Ethnographic interviews|*]] 042gm74xjs409jaiaahs7vvtmhv2vw7 6 670 3785 2009-10-22T19:43:28Z Trevor Parscal (WMF) 3 Wireframe of LiquidThreads discussion system. Designed by Trevor Parscal. wikitext text/x-wiki Wireframe of LiquidThreads discussion system. Designed by Trevor Parscal. qqc0kknqxduwn64kmgvlaqq8q7lz5vc 6 684 4054 3837 2009-11-03T18:53:11Z Juxn~usabilitywiki 176 uploaded a new version of &quot;[[File:IconHTnewDocument.jpg]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 685 3838 2009-10-27T01:20:16Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 686 3839 2009-10-27T01:20:36Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 687 4069 3840 2009-11-04T19:43:22Z Juxn~usabilitywiki 176 uploaded a new version of &quot;[[File:IconHTstroke.jpg]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 688 3841 2009-10-27T01:20:56Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 689 3842 2009-10-27T01:21:09Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 691 5995 5984 2010-03-05T02:10:54Z Ryan lane 953 uploaded a new version of &quot;[[File:Selenium architecture diagram.svg]]&quot;: Modified arrows to show how traffic initiates. Added arrow legend. Modified arrow pointing to varnish from developers to point to grid instead, since varnish doesn't reverse wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 706 3938 2009-10-28T23:29:18Z Catrope 268 Screenshot comparing the redesign on sandbox 5 (above) with the current design (below). The new font suffers from significant kerning, especially around the ''m''s. wikitext text/x-wiki Screenshot comparing the redesign on sandbox 5 (above) with the current design (below). The new font suffers from significant kerning, especially around the ''m''s. hwehvatgx37dr0qn0jl2aocqbxmz9pc 6 708 3947 2009-10-29T10:51:32Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 709 3948 2009-10-29T10:51:46Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 710 3961 3949 2009-10-29T19:42:08Z Juxn~usabilitywiki 176 uploaded a new version of &quot;[[File:IconHT ink newdocument.jpg]]&quot; wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 711 3950 2009-10-29T10:52:08Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 712 3951 2009-10-29T10:52:23Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 713 3952 2009-10-29T10:52:38Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 714 3953 2009-10-29T10:52:49Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 715 3957 2009-10-29T19:29:41Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 716 3958 2009-10-29T19:29:52Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 717 3959 2009-10-29T19:30:03Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 6 718 3960 2009-10-29T19:41:11Z Juxn~usabilitywiki 176 Illustrates the how to do icons page. wikitext text/x-wiki Illustrates the how to do icons page. jsj4jmvqygrg3win7js8ynb92ye7mp9 10 721 8658 4001 2010-07-29T13:33:14Z Nemo bis 9 cat wikitext text/x-wiki Thanks for experimenting with the {{<includeonly>{{{s|subst:}}}</includeonly>#if:{{{1|}}}|page [[:{{{1}}}]] on}} the Wikipedia Usability Initiative wiki. Your test worked, and has now been reverted or removed. Please see the [[Main Page]] if you would like to learn more about this project. Thanks.<noinclude> [[Category:Templates]]</noinclude> 3m2p6vvpwgz4mx9v4i733dlks5pocmj 0 725 8607 4463 2010-07-29T12:57:08Z Nemo bis 9 cat wikitext text/x-wiki == Introduction and Setup (7 minutes) == ==== Greeting ==== Hi, I’m XXX, thanks so much for coming in today! ==== Overview and Permission to Record ==== Before we get started let’s get these consent forms filled out. Basically we’re going to be recording both your computer screen, and your face through that camera, and then our audio conversation. Those recordings are going to be posted on the internet under Creative Commons licensing, so they’ll be available for anyone who’s interested in this research to view at least part of them. By signing here, you’re agreeing that’s okay. Also, if you initial down below, we’ll label the video with your first name. If you’d rather we didn’t, we’ll label it with a made-up name instead. Do you have any questions? Great, let’s talk a little about what were going to be doing here today. We’re collecting feedback on Wikipedia.org. Basically, I’ll ask you some questions and then watch you use the web site. The whole thing will take about 45 minutes. ==== Set up ==== Your job is really easy, you just have to be yourself and act as you naturally would. I did not design this website, and I don’t actually work directly for Wikipedia, I’m just collecting feedback, so I promise, nothing you say could hurt my feelings! As you use the site, please be honest with your positive and negative thoughts. There are no right or wrong answers. You are not being tested; the Wikipedia webpage is being tested. ==== Background Questions ==== So let’s get started with a few quick background questions. What was it you were doing on Wikipedia when you filled out the survey a few weeks ago? You said you come to Wikipedia XXX often. What are you usually looking up/doing? How has your experience been in the past? (Non-editors) You mentioned that you haven’t edited Wikipedia before, but you’d be willing to. What are the reasons that you haven’t in the past? Can you tell me what you know now about the process of editing? (Editors) You mentioned that you have contributed to Wikipedia before. Please tell us about those experiences. Can you tell me what you know now about the process of editing? ==== Roles + Think Aloud ==== Next I’d like to have you go on Wikipedia to do a couple of tasks. There’s one thing that I would like you to do differently. Please think aloud as you use the web site today. For example, if you are reading something read it out loud and feel free to say anything that comes to your mind as you read - for example that’s interesting or what in the world are they talking about? Also, talk out loud while you’re doing a task, so I can understand what you are thinking and doing. (e.g.: Now I’m going to try to use the search engine) And, if you get to a point where you would naturally stop working, let me know. I’ll let you decide your task is complete, whether you find what you are looking for or not. Just tell me when you’re finished. Were going to be focusing on navigating through the website and making changes to Wikipedia entries. For the tasks that we’re going to do, we will be previewing your changes but for most of the time we won’t be permanently saving your changes (note: we will walk them through that if necessary) Do you have any questions before we continue? Okay, let’s go to the Wikipedia website. Does this all look pretty much how you’re used to it? Let’s go ahead and log in. == Tasks (10-15 min each) == ==== Personal Content ==== Let’s go ahead and visit the page you were looking at when you filled out the survey for this interview. Go ahead and continue doing that, or walk me through how you were doing that… (Alternatively: Hometown; Favorite sports team, movie, singer, actor; Last meal you had/book you read; College or University you attended.) If you wanted to add a paragraph of info to this page, how would you do that? Go ahead and show me. (Steer towards making a change in the lower part of the article, to see if they use the ToC. Pre-fab sentence to give user if they don’t know what to add: Free knowledge for everyone on the planet. If necessary, show them how to preview and cancel their changes instead of saving them here, and continue to do this throughout as needed, as we don't want to save any changes!) Great, let’s go back up to the top and take a look at that. (Do they use the ToC to get there?) Is that something you think you might do? Why/why not? What other types of things might you want to edit? Why? (fix typo, add section, add reference, add comment on discussion page…) How did you feel about that process? How was that process? What do you think about the way this is all laid out (the text, the navigation, and the other elements on the edit page)? How’s the information on this page? What information would you expect to be there? What information do you actually see there? Why do you think this information is here? During this process, probing more deeply on: overall toolbar, help. What about this section over here on the right (table of contents), what is it for? (Observe interaction with abbreviated headings and text position when using ToC to navigate.) Please go to the discussion page for this article. Have you ever read, used or contributed to a discussion page for a Wikipedia article? (if yes) Please tell me about that. ==== Formatted Content ==== Let’s go ahead and go to another entry on Wikipedia. You can choose whatever’s interesting to you. Alternatively: Hometown; Favorite sports team, movie, singer, actor; Last meal you had/book you read; College or University you attended. Let’s say you wanted to add some information here from another source, say a document on your computer or in this case, another website. (Let user choose if there's something they would like to add. Help them come up with examples. How would you go about doing that? Is that something you would do? Why/why not? How was that process? (if user doesn't mention References) Did you see the section about references? Would you add a reference from your text to the XX site? Why/why not? Go ahead and show me how you would do that. (if user doesn’t mention External Links) Did you see the section about external links? Would you also add the CC site to the external links? Why/why not? Go ahead and show me how you would do that. Note: if there is not a 'References' or 'External Links' on the Wikipedia entry that the user is viewing, direct them to the entry for “The Cathedral and the Bazaar” Let's say you wanted to link to another Wikipedia article from within this article (called internal linking). How would you go about doing that? Is that something you would do? Why or why not? Let’s give it a try. … Great, thanks! (If this attempt was for an article that exists, add another one that doesn’t, or vice versa. Observe whether user is aware of and correctly interprets the icon to the right of the field.) How was that process? Great, thanks so much for trying that! There’s one more thing I’d like to try here, if you don’t mind. Let’s see if we can add a table. How do you think you would do that? ==== Editing a Page that uses a template ==== (If doesn't happen on homewtown or other page): Let’s go ahead and take a look at the Wikipedia page on San Francisco, CA. If you wanted to edit just the 'Transportation' section here, how would you go about doing that? If you wanted to add a new section here, how would you go about doing that? Transportation section (hand user printed instructions): *Create a new section, call it “Bridges” * Include this text under the section heading: =====Golden Gate Bridge===== =====San Francisco – Oakland Bay Bridge===== *Save your changes * Then, above this text at the top of the section, please add the following: See also: Golden Gate Bridge and link 'Golden Gate Bridge' to the Wikipedia entry on the Golden Gate Bridge. (Make sure they know to make ‘bridge’ bold and ‘see also’ italicized) How was that experience? Let’s say you moved to San Francisco and wanted to change the population field to be one greater. How would you do that? (Point out where this information is on the actual entry if necessary). Let’s say you wanted to add San Francisco's motto to the page. How would you do that? How do you feel about all that? What do you think about all the stuff that’s on this (edit) page? == Looking Back (5 minutes ) == ==== General (Navigation, Instructions, Help) ==== What do you think of everything you've seen and used? ==== Summaries (Likes + Dislikes) ==== What might encourage or increase your participation on Wikipedia.org? Is there anything that you would want to see changed/done differently on the Wikipedia website? Particularly related to the tasks you completed today? If so explain. Any other likes or dislikes that you’d like to mention? Anything else you’d like to share with me or ask me? Would it be okay for us to contact you if we have any follow up questions or information? === Incentive and future contact === Well [participant name] that does it for us. Here’s your $75 Amazon gift certificate. Again, thanks so much for coming in and talking to us- it’s really useful for our research! [[Category:Usability studies]] 2q5z2en0cal0a34yhweedhshdvoecvi 6 726 4041 2009-11-02T23:32:32Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 727 4042 2009-11-02T23:32:48Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 728 4043 2009-11-02T23:33:07Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 729 4453 4070 2009-11-09T20:26:50Z Trevor Parscal (WMF) 3 uploaded a new version of &quot;[[File:Wireframe-Babaco-WikiEditor.pdf]]&quot;: Updated version of WikiEditor wireframes. Designed by Trevor Parscal, Nimish Goutam and Parul Vora. wikitext text/x-wiki Wireframes of refined WikiEditor user interface. Designed by Trevor Parscal. o01etf4srd69a8fbjwj2212gy8g83ac 6 730 4076 2009-11-04T22:48:48Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 731 4077 2009-11-04T22:49:03Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 732 4078 2009-11-04T22:49:17Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 733 4079 2009-11-04T22:49:30Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 734 4080 2009-11-04T22:49:54Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 735 4081 2009-11-04T22:50:10Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 736 4082 2009-11-04T22:50:27Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 737 4083 2009-11-04T22:50:43Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 738 4084 2009-11-04T22:50:57Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 739 4085 2009-11-04T22:51:21Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 740 4086 2009-11-04T22:51:38Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 100 742 4988 4164 2009-12-12T00:33:37Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki In order to get useful output from the meeting, please use the following backbone to document your discussions. It will save a lot of time to everyone. You should create one page for each major area of discussion identified during the first brainstorming session. <center>Use this to create a notebook page for an area of discussion.</center> <inputbox> type=create preload=Multimedia:Meeting in Paris/Notes/Backbone default=Multimedia:Meeting in Paris/Notes/ buttonlabel=Click here to create bgcolor=white width=50 </inputbox> == List of notes == {{Special:Prefixindex/Multimedia:Meeting in Paris/Notes}} [[Category:Multimedia meeting in Paris]] sjpzqkkuw7iq03xztgh3xmi6qgghrgd 100 743 4987 4129 2009-12-12T00:33:29Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * ... * ... == Major issues == '''What are the major issues related to this topic?''' * ... * ... == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * ... * ... == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * ... * ... == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... [[Category:Multimedia meeting in Paris]] bvtwyhiqrug2ntq52wpo5zwz8ytq589 100 744 4986 4359 2009-12-12T00:33:18Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Target Group Analysis == * People who never used Commons at all * Wikipedians (who are unaware of the existance of Commons) * Readers/Users of the Wikimedia projects * Cultural Institutions ** Museums ** Libraries ** Archives * Educators * Photographers and other multimedia creators == What the target groups want to get out of Commons == * Use * Re-use * Upload == Problem Analysis == * Wikimedia Commons is not visible enough on Wikipedia (see Polish Wikipedia) * There is no good explanation about what free licences are * Lack of information about what inspires us to use free licences (e.g. convincing case studies) * There is too much information * We need to explain why we do things like we do it (e.g. why is collecting meta data important?) * The help (as one of the main functions on the main page) is not visible enough (overkill of useless information) * Commons is not perceived as an independent project (note: controversial) * The communication with the user is mostly aggressive / impersonal tone (bots) * Some of the people who are the public face of Commons are not friendly enough, but are very active and hard-working members of the community (nasty-but-diligent-guy-problem) -- worse on Commons than on other projects, because there too few places for reflective communication (like in WikiProjects) * People don't now enough about exciting projects on Commons (Atlas etc.) == Slogans (brainstorming) == * "Commons – a great way to share something with the world!" * "View the world from different angles!" (with different pictures of the same item, taken by different photographers) * "See how your picture helps educating people!" * "Universal access to culture" == Solutions / Proposals == === education / outreach related === * "Welcome bar" on top of the page for new users (see http://stackoverflow.com/) * Introduction video about a) what Commons is, and about b) the usage of Commons (how to use, re-use, upload). (See the [http://www.google.com/chrome/intl/en/features.html?hl=en&brand=CHMI Google Chrome] introduction page for example) * Enticement materials ("10 reasons why you should contribute to Wikimedia Commons", "pictures make the difference") * Wiki seminar about communication with other users / conflict resolution * Leaflet for Museums * Leaflet for Libraries / Archives === other noteworthy ideas === * "Did you like this picture? See more pictures of this type…" == Limits of outreach / educational initiatives == * As soon as the nasty-but-diligent-guy appears, all efforts are in vain == Criteria for good Commons-related educational / outreach materials == * positive tone (what you can do instead of what you can't) * attractive materials (for the target group photographers) * should capture what is fun on Commons * simple, understandable language * keep everything simple, not too much information, focus on the most important points * should direct the reader to more detailed information * the right mix between fact-based and inspirational == Target specific positioning messages (museums, libraries, archives) == === Museums === * Contextualization ("access for your target market") * Taking the content to other places * Engagement (the amount of time people spend with your collection) * The more the museums are visible online, the more people can be activated to visit the museum * Re-assurance: "Nothing can replace the real thing" === Libraries === * Wikipedia is a knowledge repository (common mission) * The power of volunteers: ** Case study I: OCR – Wikisource adds value to the full text search ** Case study II: Wikimedians check and improve your metadata (authority records) * Wikipedians giving classes: "How Wikipedia works" (both for the general public and the library staff) / Broaden the demographics of the users * Case study: multilingualism, annotation, disambiguation (Sj) * Case study: Jeffdelonge (Wikimedian who saved a collection while he was a library intern) === Archives === * Preservation ** materials are accessible online (and can take less damage) ** the data is available somewhere else * Metadata can be reviewed and improved (Case studies: Federal Archive) (wisdom of crowds) * Case study Durova === All === * Wikimedia's mission * Wikimedia is an international, non-profit organization * You can focus on your job, while we are doing the low-level work === Arguments against a partnership === * "the integrity of the collection" (ruining the reputation) == GLAM Next steps == # Identify a person in your organization that is responsible for the project # For further information see: … # Contact the local chapter == Additional information for Chapters == * The most common pitfalls ** content terminology "content liberation" (see [[w:en:WP:GLAM]]) ** not pitching the right level ** copyright fear ** not being explicit about the amount of work / not being clear enough about the whole project ** disrespect ("we know it better than you" / being dressed in t-shirts / not respecting the work of the last decades) ** knowing whom to send (is the person qualified to do the job? does the person talk the same language?) * The most common objections ** commercial use of my stuff ** anyone can do anything with it? ** we want to be attributed / we don't want to be associated with a different (e.g. vandalized) version ** but it's already free on our website / why do you have to upload it to Commons? ** why do you need a high resolution ** control of my stuff (I can't delete etc.) ** (Also see [[:wmuk:Cultural_partnerships/Content_partnerships#Drawbacks]]) [[Category:Multimedia meeting in Paris]] tejo2ao66dgfu906swnrtmfgrgtxbho 100 745 4977 4349 2009-12-12T00:31:13Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * ... * ... == Major issues == '''What are the major issues related to this topic?''' * ''Education about free licenses'' ** the current form tries to educate about free works at the same time the user is uploading ** => upload form is too complicated ** too much text => people don't read => useless in the end * ''Commons is a separate project'' ** and presented as such ** The upload has to be done from Commons. ** It's then difficult to add the file to the actual page. * ''1 upload form for all users, whatever their experience etc.'' ** Upload workflow is too complicated (branches etc.) ** it's easy to get lost in the process * ''Small core Commons community'' ** Too few admins, too little manpower to manage the incoming flow ** Users are required to provide perfect uploads (licensing information, categories, etc.) ** Upload form is too complicated ** Lack of user-friendliness (messages from bots, etc.); also linked to the little manpower; community interaction * ''Repetitiveness'' ** when uploading similar pictures; the upload form is not designed for multiple uploads ** when preparing metadata beforehand and having to give all the info all over again * ''Commons is user-focused, not participant-focused'' ** No prominent invitation to upload, only a link in the sidebar ** The home page of Commons is designed for people who want to use files, not contribute them * ''Multilingualism'' ** difficult communication with the uploader to guide them == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * [[mw:Extension:Firefogg|Firefogg]] / transcode while uploading (Michael Dale) * [[mw:Extension:Add Media Wizard|Add Media Wizard]] (Michael Dale) * Upload API (Michael, Bryan TM) * External upload tool developed for photo contests (Ryan Kaldari) * [http://www.wikiportret.nl Wikiportret] (Hay Kranen): incentive + dedicated external website * [http://toolserver.org/~magnus/commonshelper.php CommonsHelper] (Magnus Manske) * [http://toolserver.org/~magnus/pushforcommons.php Push for Commons] (Magnus Manske) * [http://toolserver.org/~bryan/flickr/upload Upload from flickr] (Bryan TM) * Auto-categorization (Multichill) * ... == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * Auto-categorization (Duesentrieb) * ... == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... ==Notes taken from Google Wave== Critical issues: * It is complicated * Redundant, information can come from the file itself * Too complicated * Multiple user interfaces for different use cases * Form is designed for single uploads * Commons design is driven by the assumption and fear about copyright confusion * Too easy to get lost in the upload process * Need to educate about licensing * 200.000 uploads per month vs. 100 active Commonists checking images * If you upload an image wrong, you get harrassed by a bot giving you a crash course in world wide copyright * Language issues are a barrier for both documentation and user-to-user assistance * People on local projects do not understand the utility of uploading their images to commons (and are sometimes resistant) Proposals and recommendations: * Get rid of questions that do not make sense (PD questions in the "own work" section) * (Andrew) To fix, make uploading a properly multi-stage process. FIRST, upload the image. THEN, say whether it's your own work or not. If it's their own work, don't give them a lecture on copyright law. If it isn't, use a series of simple questions and answers to determine whether it can be uploaded, and what its appropriate license is. At each point, try to avoid overloading the user. * (Andrew) Use proper fields for structured data (dates, unexplained "Permission:" field, "Other versions". * Fix the OTRS permissions approval process, it's strange and mysterious. * "Quarantine" section for copyright clearance. lower barrier to upload images and let people check it. * (Brion:) "Red label" warnings when using images that aren't fully cleared yet * Combination of instant gratification + clear way to have people find and fix things after == wiki way * If uploading from Wikipedia have it directly send to commons when you click the "own work" check box. * (Ariel) This can be a problem when the photo is fair use because of the contents (eg image of a building where there is no freedom of parnorama in that country) * Inline upload form via add media wizard on edit page [in progress - mdale] * Integrate CommonSense deeper into the upload mechanism * Upload file *first*, extract EXIF metadata, *then* ask for more details from user * Copyright questions mainly for third-party sourced images, which usually come from web. URL source and any copy metadata in the file are excellent sources of info without bugging the user. * World-wide PD calculator that interprets the place/date info to determine PD status of an image * "Report copyright problem" button for one-click directing things to admin attention queue * Add the ability to upload multiple files from a "batch" (sharing licensing and source information if appropriate, but not descriptions and other metadata). * Add a new option for importing images cross-wiki rather than the fun image moving bots we use now. [[Category:Multimedia meeting in Paris]] thcamwj4b26vg4kk5mcnjz6c6ii69ca 0 747 4443 4425 2009-11-08T14:11:39Z X-romix 1256 Replaced content with 'moved to http://en.wikipedia.org/wiki/User:X-romix/SciRefs' wikitext text/x-wiki moved to http://en.wikipedia.org/wiki/User:X-romix/SciRefs gcpb7lynegmnuc6rzftblalh6qugpeh 100 749 4978 4347 2009-12-12T00:31:24Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * Search engine such as Google, Yahoo and Bing * Internal search engine from Wikipedia, Commons and other Wikimedia projects == Major issues == '''What are the major issues related to this topic?''' * Internal search does not take advatage of language indicator and does not pick up international content * Some meta data are embedded to media files (usually not localized); not used for search ** image EXIF, movie subtitles, ... * Meta data maintained on the description pages are not machine readable * Meta-Data search: license/license-feature, size, media-type, etc * Export of image metadata (creator, etc), embedding for external search engine * Image content localization/parametrization ** localization/parametrization of embedded maps == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * Multilingual image search (Duesentrieb's WikiWord) * Add media wizard (Michael Dale) * [http://toolserver.org/~magnus/fist.php Free image search tool (FIST)] (Magnus Manske) * [http://toolserver.org/~magnus/catscan_rewrite.php New CatScan] (Magnus Manske) * [http://toolserver.org/~magnus/commcomm/index.html Commons Commander] (Magnus Manske) * http://toolserver.org/~daniel/WikiSense/CheckUsage.php * http://toolserver.org/~daniel/WikiSense/CatScan.php * http://toolserver.org/~daniel/WikiSense/CommonSense.php == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * Semantic MediaWiki (eval Scalability) * Integration of WikiWord-Thesaurus with internal search (lucene) * Bryan Tong Minh's Global Commons - Coming soon! [http://www.mediawiki.org/wiki/Extension:GlobalUsage] == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... [[Category:Multimedia meeting in Paris]] iuhm4ocv2kk77x46bf41g6is7po3h3q 100 750 4976 4325 2009-12-12T00:31:01Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * ... * ... == Major issues == '''What are the major issues related to this topic?''' * ... * ... == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * Add media wizard (Michael Dale) * Video player (Michael Dale) * "Instant Commons" a.k.a. $wgForeignFileRepos (Chad) * [[:mw:Extension:GlobalUsage]] (Bryan and Andrew): now active on [[test:Special:GlobalUsage|test.wikipedia.org]] * ... == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * WordPress plugin with add media wizard/InstantCommons features; & same for other CMSes * ... == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... [[Category:Multimedia meeting in Paris]] a223bo1tpy3vuxga9n1qh7uevxomdjy 100 751 4983 4207 2009-12-12T00:32:45Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * ... * ... == Major issues == '''What are the major issues related to this topic?''' * ... * ... == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * Video sequencer (Michael Dale) * [http://toolserver.org/~magnus/commcomm/index.html Commons Commander] (Magnus Manske) * ... == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * ... * ... == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... [[Category:Multimedia meeting in Paris]] evua6k2fe6td703ot1koykp2l9fjzyj 100 752 4979 4345 2009-12-12T00:31:36Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki Multi-lingual Support can benefit the approach from contents, structure, search and interface. Contents, structure, surface are inter-related and interface has effect on every aspect. == Workflow analysis == '''What's the current workflow related to this topic?''' * MediaWiki interface is translated by the translation called, betawiki.net. * Contents and some meta data are translated through wiki interfaces. * Press releases etc are translated on meta == Major issues == '''What are the major issues related to this topic?''' ===Interface=== * Language-sensitive rendering is needed. * Auto-detect of the language preference is not supported. For example, RTL switch is not available. * Translation communities are scattered and need a central hub. === Content=== ==== textual page content ==== * translatewiki.net even for this? The Translate extension maybe ... It could make a big difference on Meta and Commons ... * use twn community but store on commons ?? ==== Templates (license-Tags, etc) ==== * translatewiki.net (experimental) === Media-Content === ==== localized Subtitles ==== * Structure (Page titles, categories) * Babel-Extension useful for translators, but also for commons * Language settings (ui-lang, gender, skin, etc) not copied on first login (SUL) : When a user creates a new profile on a wiki, many more of the aspects that relate to his profile should propagate for instance... gender, timeformat, skin, preferred language ... all as a default.. When a UI preference is changed, it should be asked if this change is to propagate. * Coordination of translator communities (translatewiki vs. meta - transcom) : Example, the fundraiser 2009 consists of meta texts and translatewiki.net UI messages. In order to get the whole done for one language both are to be done.. This is not considered. Consequently we have not an assured result. * File name convention needs to be standardized. : Rationale: File name in right-to-left is almost impossible to deal with left-to-right language users. However, imposing English naming convention is unfriendly to non-English users. === Search === Please see [http://www.mediawiki.org/wiki/Extension:GlobalUsage Search] section for issues related with multi-lingual search == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * Template-localization hack on Commmons (Multichill) : Some fairly standard text like "license texts" are localised at translatewiki.net. However there are issues with this as the localisations should be Country specific for the big text... * <nowiki>{{lang}}</nowiki> tags to indicate content language. : When descriptions are stored with this tag for a language, we could show if these templates contain particular parameters that would indicate that they may need to be translated.. For instance.. Tropenmuseum Indonesia content with a Dutch text and no Indonesian text. * Multilignual Image Search (Duesentrieb's WikiWord) [http://toolserver.org/~daniel/wikiword/wikiword.php] : This is a great tool but it relies on the existence of Wikipedia articles. It would be good if Wiktionary content could be used in order to expand the values for languages.. There are issues but they have been solved... There are technical superior solutions that could contain both the Wikiword and the Wiktionary data. == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * standard templates (xml dump) to be imported into new wikis (esp. for smw support) ** notice-box, infobox, language-indicators, license tags, ... * Use traslatewiki.net for both software interface, contents and editable meta data. == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... [[Category:Multimedia meeting in Paris]] cafo6m3w8o2xgdntevf2c3ykaun3cnm 100 753 4984 4215 2009-12-12T00:32:54Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * ... * ... == Major issues == '''What are the major issues related to this topic?''' * ... * ... == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * [[:mw:Extension:GlobalUsage]] (Bryan TM) * ... == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * ... * ... == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' * ... * ... [[Category:Multimedia meeting in Paris]] 72yqry9yy6xch7aa1u1ihys6ld6z3fb 10 754 8643 4244 2010-07-29T13:28:26Z Nemo bis 9 cat wikitext text/x-wiki [[file:SciRefs_leftbr.png]]<noinclude> [[Category:Templates]]</noinclude> sc1a12aeqgfqvi48e8cnkv80zu73t5e 10 755 8664 4246 2010-07-29T13:34:31Z Nemo bis 9 cat wikitext text/x-wiki [[file:SciRefs_rightbr.png]]<noinclude> [[Category:Templates]]</noinclude> i0854e82r5o52gpa51nhkv1ehecu9ij 10 756 8666 4249 2010-07-29T13:34:44Z Nemo bis 9 cat wikitext text/x-wiki {{[[Template:{{{1}}}|{{{1}}}]]}}<noinclude> see http://en.wikipedia.org/wiki/Template:Tl [[category:Templates]] </noinclude> 4yegncqri58j5lddmgm75cdioaqey7s 100 757 4982 4364 2009-12-12T00:32:32Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki == Workflow analysis == '''What's the current workflow related to this topic?''' * ... * ... == Major issues == '''What are the major issues related to this topic?''' * ''There are several different possible sources'' ** and we have to accomodate them all (or do we?) ** GLAM ** Commons users ** Contests ** Already on the web (LOC, Flickr, etc.) * Streamline multifile uploading process * Copyright verification * ''Poor metadata handling'' ** Machine readable (import various types and merge to "our format", and export 1 standard type so third parties can import the data to their own collections) ** Human-entered * Organization and integration of images (once images are metadata-correct, we need to engage the community effectively to categorise and improve and incorporate to Wikipedia) * ''Processes/guidelines are inconsistent'' * Role accounts (one time uploads), this gives the GLAM "ownership" of their files and makes reporting easier (reports based on uploads-by-user) * Making bots easier to build and share components (rather than creating bespoke software for each project) * Documentation ** Best practices * ''We are currently not able to provide feedback'' ** Usage data (e.g. Dopplr summary) that lists number of page hits, images used in which articles, number of clickthroughs... ** Change data - doesn't have to be "pretty" but enables export of changes (e.g. categories, dates) so they can incorporate back into their collection. Flickr does this. * Custom templates with the right format of data for the institution. E.g. some institutions prefer we list the "accession number", whilst others prefer "record number", "image number", URL etc etc. The fields should be relevant to the institution. == Tools and workarounds == '''What are the existing tools or workarounds used to circumvent these issues?''' * Batch uploading documentation[http://commons.wikimedia.org/wiki/Commons:Batch_uploading] * Commonist[http://commons.wikimedia.org/wiki/Commons:Tools/Commonist] - java program (Datura) * Commonplace[http://commons.wikimedia.org/wiki/Commons:Tools/Commonplace] - Windows/Linux program ([[User:IlyaHaykinson|IlyaHaykinson]]) * Upload API[http://commons.wikimedia.org/w/api.php] (Michael, Bryan TM) * External upload tool developed for photo contests ([[User:Kaldari|Kaldari]]) * Flickr (as a staging server) * Drop.io (as a staging server) * Imagecopy built by Multichill (wrapper around Commons Helper)[http://meta.wikimedia.org/wiki/Pywikipediabot/imagecopy.py] * FlickrRipper[http://commons.wikimedia.org/wiki/Commons:Tools/Flickrripper] - transfer multiple flickr images at once * Custom bots/tools **pyWikipedia bots[http://meta.wikimedia.org/wiki/Pywikipedia] **Eloquence upload script[http://commons.wikimedia.org/wiki/Commons:File_upload_service/Script] **Nichalp's Upload Script[http://commons.wikimedia.org/wiki/User:Nichalp/Upload_script] == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) *Enhance Commons *3rd Party front-end sites *Client programs (like Commonist or Flickr Uploader) ===FlickrBot 2.0=== Create a bot that allows a users to upload an entire photostream from Flickr to Commons. Allow searching Flickr by: User, Group, Set, Pool Automatically populated categories, titles, etc. from the Flickr info. Allow user to browse the images and choose which ones are good for uploading before they are passed to the upload script. Use duplicate checking. Could be implemented by combining Multichill's pywiki FlickrBot for pulling files from photostreams with MM's FlickBot for uploading them to Commons. ===Commons Helper 2.0=== New version of Commons Helper that will be developed by Mangus. Problem with old Commons Helper: Translating Wikipedida specific templates to Commons templates. Solution: Use script to create parse tree from remote template and then construct new Commons template from the parse tree. ===Staging server=== Set up a server to house files to be organized before they are pushed to Commons. This server would also host custom uploading interfaces taylored to specific users/institutes. * Make uploading easier: **FTP **Drag and Drop **Flash multi-file uploading * File format for mass upload description data and structured information ** This may depend on having clean structured license metadata! * Allow creation of role accounts for institution representatives, contenst participants, etc. * Feedback opportunity for Wikimedia users in the Staging Area regarding the Previews * Report Sheet: Number of images, number of images used, number of page views * Generic Reports on single images * Reports for Groups, set of images * Capacity planning for server and storage deployment as mass uploads increase * Allowing and Creating Role Accounts for Mass uploads * Reporting and exporting of changes back to the GLAM * Clickthrough statistics for links clicked to the GLAM institutions * Export images to Flickr * Implement institution specific templates == Solutions analysis == '''What are the advantages and drawbacks of these solutions?''' (existing or not yet) * Efficiency in solving the issue * Drawbacks * Feasibility * ... == Prioritization == '''What issues should we focus on?''' === Short term === * Improve flickrripper * More active development of Commonist * Make a web based contests tool === Medium term === * Create web based tool to upload lots of files * Create web based tool to upload lots of flickr files === Long term === * Integrate the web based tools into Commons [[Category:Multimedia meeting in Paris]] a2cigooobaqzow4wq8vvawyazq6fx6g 10 758 8645 4303 2010-07-29T13:29:12Z Nemo bis 9 cat wikitext text/x-wiki <div id="X-romix_SciRefs_On"></div><noinclude> [[Category:Templates]]</noinclude> 8vbunzrcn2dnxgjgqiaxq2cpk2gnoc4 100 763 6369 4360 2010-04-01T08:44:30Z Amire80 1559 bullets wikitext text/x-wiki Multimedia Usability Meeting, Paris - November 6-8, 2009 Upload process issues: * It is complicated and easy to get lost * Redundant, information can come from the file itself * Multiple user interfaces for different use cases * Form is designed for single uploads * Commons design is driven by the assumption of and fear about copyright confusion, help text is written in the negative (what you can't do) instead of the positive (what you can do) * Need to educate about licensing is intertwined with uploading process * If you upload an image wrong, you get harrassed by a bot giving you a crash course in world wide copyright * Language issues are a barrier for both documentation and user-to-user assistance * People on local projects do not understand the utility of uploading their images to commons (and are sometimes resistant or might be put off by agressive talk page messages) Metrics: * 200.000 uploads per month vs. 100 active Commonists checking images * Bryan's stats: http://toolserver.org/~bryan/ * Erik Zachte's report card: http://stats.wikimedia.org/reportcard/ [includes Commons stats] * http://commons.wikimedia.org/wiki/Commons:MIME_type_statistics Proposals and recommendations: * Get rid of questions that do not make sense (PD questions in the "own work" section) * (Andrew) To fix, make uploading a properly multi-stage process. FIRST, upload the image. THEN, say whether it's your own work or not. If it's their own work, don't give them a lecture on copyright law. If it isn't, use a series of simple questions and answers to determine whether it can be uploaded, and what its appropriate license is. At each point, try to avoid overloading the user. * (Andrew) Use proper fields for structured data (dates, unexplained "Permission:" field, "Other versions". * Fix the OTRS permissions approval process, it's strange and mysterious. * "Quarantine" section for copyright clearance. lower barrier to upload images and let people check it. * (Brion:) "Red label" warnings when using images that aren't fully cleared yet * Combination of instant gratification + clear way to have people find and fix things after == wiki way * If uploading from Wikipedia have it directly send to commons when you click the "own work" check box. * (Ariel) This can be a problem when the photo is fair use because of the contents (eg image of a building where there is no freedom of parnorama in that country) * Inline upload form via add media wizard on edit page [in progress - mdale] * Integrate CommonSense deeper into the upload mechanism * Upload file *first*, extract EXIF metadata, *then* ask for more details from user * Copyright questions mainly for third-party sourced images, which usually come from web. URL source and any copy metadata in the file are excellent sources of info without bugging the user. * World-wide PD calculator that interprets the place/date info to determine PD status of an image * "Report copyright problem" button for one-click directing things to admin attention queue * Add the ability to upload multiple files from a "batch" (sharing licensing and source information if appropriate, but not descriptions and other metadata). * Add a new option for importing images cross-wiki rather than the fun image moving bots we use now. Mass upload group use case 1: huge pile of images with structured information use case 2: huge pile of images without structured information Sources: * GLAM * Commons users * Contests Issues Hints: http://commons.wikimedia.org/wiki/Commons:Batch_uploading Proposal: * Staging Area * File format for mass upload description data and structured information * This may depend on having clean structured license metadata! * Feedback opportunity for Wikimedia users in the Staging Area regarding the Previews * Making bots easier * Documentation: Best practices * Report Sheet: Number of images, number of images used, number of page views * Generic Reports on single images * Reports for Groups, set of images * Capacity planning for server and storage deployment as mass uploads increase * Allowing and Creating Role Accounts at Commons for Mass uploads * Reporting and exporting of changes back to the GLAM * Clickthrough statistics for links clicked to the GLAM institutions Lightning talk notes: * Ryan Kaldari demoing specialized contest management tool: http://www.angelblade.com/contests/ * inspired by "Wikipedia Loves Art" type mass photography events * has scoring for photo assessment * Michael Dale demoing Add Media Wizard goodness * Chad Horohoe demoing current InstantCommons implementation in MediaWiki (ForeignFileRepository support) * Hay Kranen talked about Wiki loves art and Wikiportret (meta link) Smaller working groups * Reviewed http://www.thecssninja.com/demo/drag-drop_upload/ (FF 3.6, Chrome, Safari nightly) * Reviewed FF 3.6 full-screen support (slow, stops video when exiting, apparently no JS bindings - Michael filing bugs) * Reviewed and then deployed GlobalUsage on test wiki. krhmz2d29vgml5t73wm74wz149eq14k 100 765 4439 4394 2009-11-08T13:02:31Z Multichill 1265 http://www.wdl.org/en/item/74/ wikitext text/x-wiki Integration discussion — encouraging reuse by other non-MediaWiki sites. Problems * When reuse occurs, attribution etc does not occur properly. * No programmatic way in MediaWiki to present the licensing information/attribution info. We can provide the description pages via the API * Some way of resolving issues with moved or deleted images. * Some images are deleted when they are replaced in another format. * Issues with what license the file is under, GFDL requires the entire text of the GFDL in the license. * What size image do we embed? Similar examples * Wikimedia UK has an on-hover text system for its blog for its blog . * Example given: Dutch government (Kennisnet) allows students to make websites. * The images at [http://www.wdl.org/en/item/74/ wdl] have a nice share this button Proposals * Reuse HTML/facebook/blog/forum code generator, that allows selection of an individual image, and generates appropriate HTML with proper attribution. We can only do this for appropriately licensed images. * Perhaps already exists, but needs fixing. * Distinguishing between reuse and sharing. * Need to allow the user to select the size. * Adds EXIF data. * Note in the EXIF data that it came from commons, with all metadata (author, license, ...). * Plugins for embedding media in popular CMS systems, which allow correct reuse of commons images (à la InstantCommons). * WordPress, Drupal, WordPress, twitter, Moodle * Just a plain Flickr-like "Share this" link to grab HTML to embed the object * Some sort of tracking of reuse is a good idea. * Extension of GlobalUsage? API module to grab trackbacks/etc * Some sort of integration with GlobalUsage. * Some sort of content-addressable scheme to resolve issues with renamed and modified images. * Consider transferring the image, resolves maintenance issues with deleted/renamed/modified files. * Develop statistics on hotlinked images (Referrer-header based). * Include some sort of token in generated image URLS for reuse so we can track their usage. (do this for InstantCommons as well) * Consider privacy. * We need to make InstantCommons more accessible and advertised. * Improve MediaWiki as a third-party reuser. 64cyeibjke8vwfqz56afdd6bn024oag 100 766 4395 4382 2009-11-07T15:20:18Z Guillom 13 cleanup wikitext text/x-wiki Discussion of Staging/Quarantine Area for file uploads Summary Requirements of the two systems Competitions/Multi uploads to the same "group" of images * Send the users to a special upload form. * Customisable images. * Tying images together. * GLAM * Staging area not on Commons, but elsewhere (Toolserver, something else?) * We need some bulk modifications. * Need tools for some data processing (shell-only mostly) * Some institutions want more feedback than others. * A more GLAM-driven approach may be warranted in some cases. Ask the GLAM to upload some kind of data, and have supported metadata formats. Have them associate the appropriate fields, and it works fine. This is easier than driving by in a black mercedes and grabbing a hard drive. * Some of the problems will be metadata in random formats, and require manual munging. * Three possibilities: museums that have staff, and can upload the content themselves; those that have e.g. a well structured website that we can extract metadata from; those that have never published, and don't have organized information. Need to capture all three. * Different projects: GLAM web interface, scraping tools and libraries, and an organised effort to get GLAMs involved with the system. * Some mechanism for allowing uploads of all kinds of files, and to convert them to Wikimedia formats. * Work with Internet Archive to pass on huge (50T) files, with GLAMs. * Use of role accounts. Individual * Staging area on Commons - almost like flagged revs, but not. * Some way of pushing back into the staging area. * Items in the staging area should be deletable. * Items in the staging area should expire. * Requiring email address (for PUSH message about expiry) * Still needs to be part of the normal upload process--from MediaWiki's perspective--not in a different server, etc. The "staging" area would be some sort of flag on the image. * It's for fixing licensing and metadata. * Bulk modification tools should be available in the staging area. * Integration directly into the upload process. "Your upload isn't done yet, so fill in the following information". * Problem: use as personal web space * Social features ("Help me" button). * Automatically delete from staging area after N hours/days? Commonalities * Some kind of "token" system allowing individual approval of groups/projects, other than for individual staging area. * Groups/GLAM — some way of making sure that review is undergone. cdyi10ws1aq87dfs7rceo8evknm3vco 100 767 4398 4372 2009-11-07T15:44:06Z Brooke Vibber 143 /* Export methods */ wikitext text/x-wiki *''Saturday, November 7, 2009 - room 2'' *''Moderator: Duesentrieb'' *''Note-taker: Brion'' ==Structured data!== * metadata about pages/revisions * metadata about media files ** from MediaWiki [categories etc] ** embedded *** inherent: file size, page count etc *** add'l data [EXIF, ICTP, XMP] ** supplied on description page ** external data *** For batch uploads... would these come into the page? ==What's the authoritative source?== * Wikitext as primary source? [editable] ** -> cache in index [searchable, queryable] ** -> can override other sources [exif, file-inherent data] ** External (read-only) authority databases? *** (Do we need/want such or just import things per-source when doing batch uploads?) ==Structured data use cases== * media file metadata export for re-use ** api, embedded *** [Modify EXIF or XMP data to embed extra stuff?] [Recommend pushing that to later -brion] *** orig artists, repo, institution... ** Including info from authority files ** using structured data about things+files for search and research ==Let's try to keep this minimal?== * Real use cases? ** search *** license, keywords etc ** reuse *** -> Generate byline **** author(s) **** license ** Main fields... (many of these can be tied to Dublin Core fields, so import/export for academic collections can hit common denominators) *** Fixed data formats **** license ***** license features ***** dc:rights, creative commons extensions **** geo coordinates **** file format ***** jpeg vs tiff vs ogg **** media type ***** drawing vs photo vs map **** filesize / resolution **** content language ***** dc:language **** source collection + identifier **** source URL ***** dc:source **** creation date ***** dc:date *** Freetext [can have multilingual variants] **** author ***** dc:creator **** description ***** dc:description **** source ***** dc:source **** "other fields" from foreign source ***** keywords ****** (problems with consistency? controlled vocabularies with some sources, but don't match up reliably) ***** people shown in picture ***** etc How to source/edit the stuff... * source fields from file inherent/EXIF * scary templates ** Nesting is required for extracting triples sanely... *** <nowiki>{{Information|desc={{en|hello}}{{de|hallo}}}}</nowiki> **** We _think_ we can break this out **** "template" "Information@desc/en" "hello" **** "template" "Information@desc/de" "hallo" Normalization of property specs/extraction most important Normalization of property values can be left for later ==Metadata extraction spec== Possibility... * Define for <dc:description> sourcing from: ** "template" "Information@desc/<lang>" ** "exif" "Description" * Gives us these trips: ** "File:Hallo.jpg" "dc:description@lang=de" "hallo" ** "File:Hallo.jpg" "dc:description@lang=en" "hello" ** "File:Hallo.jpg" "dc:description" "Created with The Gimp" * also other sources of info available: ** revision data / uploader / editor ** external authority data [rdf triples given from bulk uploader?] Possibly spec as a special page or a mediawiki:horrid or config file. ;) Whatever consider that it may change; so we need to be able to re-run metadata extraction in bulk. ==Backend storage & search...== * mysql? (page/field/keyword trips ... or searchindex?) * lucene? (for each page page: field/keyword pairs) * specialized triple store? (sparql) ** potentially really cool searches possible! ** recommend leaving this to later - third parties cover this area well like dbpedia and freebase * Look at what Semantic MediaWiki does for its storage * Minor note: with RDF triples, subject can be tricky (page vs image vs subject of image) ** SMW -- talk page's subject is the page, so you can put data about a page there ;) ** This seems simpler ==Horrible questions: licensing?== * metadata licensing is a scary world out there... * Let's pretend the problem doesn't exist for now ;) ** [but database protection stuff in Europe may need to be looked at... but we think that hits on our side mostly] ==Points of action!== * Good news: exif extraction is already here * Work: template extraction sounds feasible and not too insane ** [brion: see about a proof of concept to make sure this works like we think :D] * Work: need to specify an extraction spec language * Work: core DB storage + query/dump export * Work: need to add interface to add the fields to search backends ** Lucene <- key for live ** MySQL fulltext <- good for third-parties ==Other considerations== * sometimes metadata is about *subject of image* instead of *image*. Ughhhhh? ** at minimum, need to be able to spec for the subject... maybe * Location: for paintings -- have loc of the painting or the subject of the painting? == Export methods == * raw RDF via API * XML RDF in special:export and dump XML ** ^if included in dumpBackup and OAI export, our Lucene indexer can easily ingest that! * RDFa embedded in HTML pages 5vwerp8v7y9de0uprbpcsm1wfo2cv9q 100 768 7060 4975 2010-05-18T00:09:19Z Guillom 13 +wireframes wikitext text/x-wiki We used the time period (approximately 90 minutes) to develop mock-ups of an alternative Wikimedia Commons frontpage from scratch, and to develop an alternative file description page / gallery pop-up. See explanations below. == Commons Main Page == [[File:Commons_main_page_project_Paris_2009.jpg|800px|thumb|center|Project of the main page of Commons]] [[File:Commons 2010 wireframe 1.png|800px|thumb|center|Associated wireframes]] This mock-up presumes a revised skin with a widescreen mode, where the current sidebar is collapsed by default and can be expanded by clicking a slider on the left-hand side. The language links are collapsed into a single drop-down. The objective here is to significantly reduce the information overload on the frontpage, and to feature compelling and relevant content and entrypoints. The top-left rectangle represents a dynamic gallery (advancing from one slide to the next after a certain number of seconds), which could feature various types of high quality content every day: * a featured photograph * a featured illustration * a featured sound file * a featured video * a featured restoration * a "valued image" etc. To the right are high-visibility entry points for the two primary types of engagements with Wikimedia Commons: searching media, or sharing files. We propose that the search be improved to autocomplete on category names even if no category namespace is specified. The "Our Mission" button would lead to a friendly and compellingly designed portal page explaining the mission of Wikimedia Commons in terms of its social and cultural image, again using beautiful examples to illustrate the page. The exact order of the three buttons is still to be determined. The bottom row of boxes, under the heading "Discover Wikimedia Commons" is used as follows: * Cultural Treasures: Featuring cultural partnerships by highlighting objects of high value and linking to the partnership page * Our Community / Our World: Linking to pages like "Meet our photographers", perhaps showcasing community members * Explore: Category tree (we need a nicer widget for this), explore by map, featured categories, etc. == Media description page == [[File:Commons_picture_description_page_project_Paris_2009.jpg|thmub|800px|center|Project of the typical picture description page on Commons]] This mock-up presents a revised media description page, again in widescreen mode. Caption and media content are presented closely together as they are the most relevant information on the page. It may be desirable to either automatically determine reasonable screen real estate usage for the caption and media file, or to allow the user to drag the caption (resize or move to the right). Our objective is to provide a user experience that suits different needs (focus on description, focus on media content). It may be desirable to have a single "View settings" button that makes it possible to switch between different modes (with caption, without caption, full-screen slideshow, etc.). We discussed that it would be desirable to view all media files associated with a page (directly or indirectly) through a single pop-up gallery widget, as is common on many websites, rather than requiring users to manually click through to each media description page. :Check [http://de.wikipedia.org/wiki/Benutzer:Magnus_Manske/commons_siblings.js some JS] of mine that [http://toolserver.org/~magnus/file_siblings.php?language=commons&project=wikimedia&sort_by_date=0&sib_cat=1&sib_gal=1&mode=json&file=Glaciers_and_Icebergs_at_Cape_York.jpg uses the toolserver] to show "related" Commons images on de.wikipedia. --[[User:Magnus Manske|Magnus Manske]] 16:10, 7 November 2009 (UTC) [[Category:Multimedia meeting in Paris]] bvt27l55bujhznrsi6wtqmyxbdnl0cb 100 769 5498 4980 2010-01-22T18:27:30Z Guillom 13 +link wikitext text/x-wiki See also [[Multimedia:Metrics]]. == Major issues == '''What are the major issues related to this topic?''' * ''We have only very limited metrics'' Reasons to have metrics: * data to design or improve MW * statistic indicators to measure progress * communication / outreach / relationships with GLAMs == Currently available statistics == '''What are the existing tools or workarounds used to circumvent these issues?''' * http://stats.wikimedia.org/reportcard/ * http://commons.wikimedia.org/wiki/Commons:MIME_type_statistics * http://toolserver.org/~bryan/stats/ ** Graph: <http://toolserver.org/~bryan/stats/commons_upload_deletion_ratio_monthly.png ** Text data: <http://toolserver.org/~bryan/stats/commons_upload_deletion_ratio_monthly.txt * http://stats.grok.se * http://wikistics.falsikon.de/ * http://www.trendingtopics.org/ * http://commons.wikimedia.org/wiki/Commons:Template_i18n/Interface_language_statistics * http://commons.wikimedia.org/wiki/User:Multichill/Categorization_stats * http://commons.wikimedia.org/wiki/User:Multichill/Commonscat_stats == Other possible solutions == '''What other solutions could be used to circumvent these issues?''' (Be bold and creative) * Count of good/bad images (?) * Metadata that needs to be filled out? * High vs low-quality/resolution? * Internal & external usage? * Distribution of media files by size (ranges) * Source: own work / batch upload from partnership / other * Distribution of uploads per wiki-age of users (ranges) * File views across all projects (only description pages are available) (and at what size?) What needs to be developed * aggregate thumbnail views in hitcount stats * official storage of hit count data on WMF servers and toolserver (ideally in MySQL table?) * geoIP agP-lookup based aggregation of country information * deploy GlobalCheckUsage - add view to toolserver * Pretty one-page summary of where images by a user/in a category are used. * Pingback/callback system (spam? don't worry yet) ** most important thing we need pingback for is InstantCommons subscriptions to notify of file updates/deletions * Referer/usage aggregator ** Aggregator eats live squid logs, every few minutes saves aggregated data into MW database: *** which images *** what thumb sizes *** referrers [pages on wikis / external sites] *** geolookup of viewer IPs - regional breakdown Notes on hit stats aggregation at http://www.mediawiki.org/wiki/Hit_stats_aggregation == Prioritization == '''What issues should we focus on?''' * Pageview and referer aggregators: easy wins * Global Check Usage stats: easy win [[Category:Multimedia meeting in Paris]] mylu6ytif7tztext3njl740dvs94ync 100 770 4985 4406 2009-12-12T00:33:04Z Guillom 13 [[Category:Multimedia meeting in Paris]] wikitext text/x-wiki *GLAM lifecycle is more than getting media *A lot of chapters are doing GLAM projects. Some are done, some are running and some are still in the planning phase. Some projects we discussed (doesn't include projects still in early planning) **[[:commons:Deutsche Fotothek|Deutsche Fotothek]] **[[:commons:Tropenmuseum|Tropenmuseum]] **NYPL classes **Pharos has interns! Making video's **UK chapter had a project and starting up more (in initial phase) **Polish chapter is doing some small projects and had some setbacks **[[:commons:Library of Congress|Library of congres]] **[http://www.wdl.org World Digital Library] **Volunteers doing digitalization **(a lot!) *Where to do the processing of the data? Toolserver? Is it reliable? *How to share information among ourselves and toward glams. ** [[:meta:GLAM|Meta for central place]] for internal ** [[:outreach:GLAM|Outreach central place]] for external ** [[:commons:Batch uploading|Have a central location for tools/share tools]] ** Use (already existing!) [http://lists.wikimedia.ch/listinfo/chapters-cultural-partners mailinglist] to share information in a private manner *What kind people do we need to develop relationships? **Local? **WMF central? **We probably need both to be flexible *We should look if we can get grants for this *If there's enough demand the WMF could probably support it *We have to do capacity planning for storage and human *Having a lot of images still need to be worked on (categorization etc) at Commons shouldn't be that big of problem. Just do some images and add them to articles to get attention. *More images will attract more users *Good examples will help chapters to also startup GLAM relations. [[Category:Multimedia meeting in Paris]] 8s4afwncxzjekr2594tiaraqc0vq930 6 772 4376 4374 2009-11-07T13:10:07Z Polimerek 243 wikitext text/x-wiki Project of the main page of Commons developed during [[Multimedia:Meeting in Paris]] [[Multimedia:Meeting in Paris/Notes/User Experience|User Experience]] session. CC-BY-SA 3.0 ojit26rzbww2sqrz75bo7824mpgxbwu 6 774 4397 4380 2009-11-07T15:35:48Z Polimerek 243 wikitext text/x-wiki Project of the typical picture description page on Commons developed during [[Multimedia:Meeting in Paris]] [[Multimedia:Meeting in Paris/Notes/User Experience|User Experience]] session. CC-BY-SA 3.0 tqtvppumjfev7ek6jx2c1nokf8xgr5u 100 775 4616 4613 2009-11-14T20:25:56Z Duesentrieb 1293 Metadata, Search wikitext text/x-wiki == [[Multimedia:Meeting in Paris/Notes/Upload|Upload]] == * Main issues: The current interface is too complicated. * It should be simplified and the software should be smarter. * Next step: Design new interface, implement prototype * Movers: Ford project team, ... == [[Multimedia:Meeting in Paris/Notes/Staging Area|Staging area]] == * Main issues: The files uploaded to Commons are published immediately, without any way to fix mistakes or manage collections. * Staging areas will help with the review and publishing of files, both for individual and partnerships uploads. * Next step: define technical specifications & feasibility. * Movers: Ford project team, Bryan (for discussion about implementation; most likely not sufficient time for the actual implementation), ... == [[Multimedia:Meeting in Paris/Notes/Metadata|Metadata]] == * Main issues: We can't currently access or query structured data to narrow a search or to facilitate use/reuse. * Solutions: Extraction of data from templates & export. * Next step: Evaluate feasibility of template extraction. * Movers: Wikimedia Deutschland ([[User:Duesentrieb|Duesentrieb]]) == [[Multimedia:Meeting in Paris/Notes/Search|Search]] == * Main issues: It is difficult to search in other languages than English, and to narrow down a search based on specific criteria that can't be queried. * Solutions: Multilingual search & structured data search. * Next step: Integrate multilingual search & make use of newly structured data. * Movers: Wikimedia Deutschland ([[User:Duesentrieb|Duesentrieb]]) == [[Multimedia:Meeting in Paris/Notes/Multilingual Support|Multilingual support]] == * Main issues: Commons doesn't cater the expected user experience of non English users. * Solutions: Language-specific display and rendering * Next steps: Come up with scalable solutions * Movers: Ford project team, ... == [[Multimedia:Meeting in Paris/Notes/Metrics|Metrics]] == * Main issues: We have only very limited metrics to design the software, measure progress and impact. * Solutions: Existing tools & tools to come. * Next steps: Prioritize metrics to track & implement tracking. * Movers: Ford project team, ... == [[Multimedia:Meeting in Paris/Notes/Integration|Integration]] == * Main issues: It is currently difficult to reuse content of Commons in a reliable, perennial way that provides good credit. * Solutions: Plugins for CMSs, bidirectional communication between 3rd party & Commons. * Next steps: Form a dedicated team to focus on integration. * Movers: ... == [[Multimedia:Meeting in Paris/Notes/User Experience|Interface redesign]] == * Main issues: The pages are cluttered and not appealing to the audience. * Solutions: redesign * Next steps: Make mockups & prototype * Movers: Ford project team, ... == [[Multimedia:Meeting in Paris/Notes/Mass Upload|Mass upload]] == * Main issues: The existing mass upload clients don't accommodate the variety of cases (sources, structure of data, etc.) and don't allow enough batch organization. * Solutions: Versatile upload tool and/or a staging area. * Next step: Evaluate existing tools, share information and determine the directions. * Movers: ... == [[Multimedia:Meeting in Paris/Notes/GLAM Lifecycle|GLAM lifecycle]] == * Main issues: Lack of understanding of the complete process from initial engagement to publishing. * Solutions: share experience & information among active people who interact with the GLAM process. * Next steps: Propose scalable solutions (human & technical resources, chapter support). * Movers: ... == [[Multimedia:Meeting in Paris/Notes/Education and Outreach|Education]] == * Main issues: Lack of awareness & understanding of Commons' presence & mission. * Solutions: outreach materials & programs * Next steps: Create the materials & design programs. * Movers: [http://outreach.wikimedia.org/ WMF Outreach] rdrr0bd9mphuy1bi2i4x6wbkgt6p8sk 14 776 4416 2009-11-07T20:59:23Z X-romix 1256 Created page with '[[Category:Scripting]]' wikitext text/x-wiki [[Category:Scripting]] 2chzy5twn6id9d8m340ohm4d0jbyffb 0 780 4730 4729 2009-11-24T00:21:04Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki We are prototyping color changes to ease navigation and better the user experience. Please view our latest prototype [http://prototype.wikimedia.org/s-5/index.php?title=Main_Page&action=edit here], check out the screenshots below, and give us your feedback! Please note that this is a sandbox site and is constantly changing! [[File:wui_colorscheme_editor.jpg | thumb | left | 600 px | editor]] [[File:wui_colorscheme_mainpage.jpg | thumb | left | 600 px | main page]] [[File:wui_colorscheme_article.jpg | thumb | left | 600 px | article]] o0fwzg0q0nrr42jolo1x9csmjdx2ikz 0 781 4805 4745 2009-11-30T01:54:31Z 129.215.149.99 pic wikitext text/x-wiki [[File:Interface mark five.png|thumb|center|800px|A proposed version (right) contains all the text of the current version (left), but presents it in a more logical and clear fashion. It also includes a request that all work submitted be neutral, verifiable and encylopedic - the core of our complex rulebook. Note how it also takes up less room.]] We would like to simplify and clean up the messages and warnings below the edit box. We think you would like to see this too [[Talk:Prototype#Can_we_please_tidy_up_and_simplify_the_warnings_on_the_edit_page.3F| see this discussion]]. Click here to see early [[Acai_Designs#Layout_.28Cleaning_up_the_Clutter.29| mockups]] and let us know what you think. n6fdoxfga8mzla2my66bx56l4pgn89u 0 782 8599 7614 2010-07-29T12:32:28Z Nemo bis 9 cat wikitext text/x-wiki {{Internal}} This page contains an overview of the Beta retention, based on the user feedback survey and an analysis of the opt-in preference data. There is more detailed information on the following as well: * [[Beta_Feedback_Survey/Reason for Leaving | Reasons for leaving]] * [[Beta_Feedback_Survey/What Users Liked | What users liked]] * [[Beta_Feedback_Survey/Retention Rates by Browser | Retention rates by browser]] * [[Beta_Feedback_Survey/User Comments | User Comments]] The data presented here was collected from August 8 to October 29, 2009. ==Background== The Usability Beta is currently conducting two feedback surveys: # '''Feedback Survey''': The feedback survey allows users to give general feedback about the Beta program. There are a series of multiple-choice questions as well as open ended questions around likes/dislikes about the Beta, usage of features, etc. # '''Opt-out Survey''': When a user elects to opt-out of the Beta, there is an optional survey they can fill out upon exiting. The questions are the same as those in the Feedback Survey, but also include specific questions about reasons for leaving the Beta. In addition to capturing the user feedback, the survey also logs the browser, OS, and screen resolution used by the participant. For screenshots of the Beta surveys, click [[Beta_Feedback_Survey/Feedback Surveys|here]]. == Update: April 30, 2010 == * ''Note: There is a potential issue with the Commons data. We are investigating the data and will update once we know more.'' * April ended with a total of 698,018 users having tried the Beta. * The cumulative retention rate across all projects decreased slightly to 79.9% as of April 30. [[File:Usability_retention_apr_2010.jpg]] == Update: March 31, 2010 == March ended with a total of 635,942 users having tried the Beta. * Approximately 64,400 additional users tried the Beta in March. * The cumulative retention rate across all projects increased slightly to 80.0% as of March 31. [[File:Beta_retention_march.jpg]] == Update: February 28, 2010 == February ended with a total of 571,579 users having tried the Beta. * Approximately 59,100 additional users tried the Beta in February. This number is down slightly, even considering the fact that February is a shorter month. * The cumulative retention rate across all projects held steady at 79.8% as of February 28. [[File: Beta_retention_february.jpg]] === Individual Projects: February Retention and Trends === In Feb 2010, the incremental retention was 80.4%. This is down slightly from Jan 2009, where the incremental retention was 81.5% * enwiki retention was down slightly (83.2% in Feb vs. 84.3% in Jan). Cumulative retention for enwiki was 83.6% as of Jan. * dewiki retention was down slightly (72.6% in Feb vs. 75.1% in Jan). Cumlulative retention for dewiki was 72.2% as of Jan. * jawiki retention was down slightly (71.5% vs. 72.1% in Jan). Cumulative retention for jawiki was 62.9% as of Jan. * kowiki retention is still low (57.9% vs. 64.1% in Jan). Cumulative retention was 58.5% as of Jan. [[File: Beta_february_2010_incremental.jpg]] == Update: January 31, 2010 == January ended with a total of 512,462 users having tried the Beta. * Approximately 70,500 additional users tried the Beta in January. * The cumulative retention rate across all projects was 79.8% as of January 31. [[File: Beta_retention_january_2010.jpg]] === Individual Projects: January Retention and Trends === In Jan 2010, the incremental retention was 81.5%. This is down slightly from Dec 2009, where the incremental retention was 82.4% * enwiki retention was down slightly (84.3% in Jan vs 85.6% in Dec). Cumulative retention for enwiki was 83.6% as of Jan. * dewiki retention was up slightly (75.1% in Jan vs. 74.1% in Dec). Cumlulative retention for dewiki was 72.1% as of Jan. * jawiki retention in Jan 2010 appears to have increased (72.1% in Jan vs. 64.9% in Dec). Cumulative retention for jawiki was 62.0% as of Jan. * Kowiki retention is still low (64.1% in Jan vs 63.2% in Dec). Cumulative retention was 58.6% as of Jan. [[File: Beta_january_incremental_retention.jpg]] == End of Year Update (as of December 31, 2009) == The following is an year-end update for the Usability Initiative. Overall, usage of the the Beta has been continuing to increase and retention rate continues to inch upwards. === Snapshot as of December 31, 2009 === * A total of 441,756 users have tried the beta. In December, approximately 79,000 users joined the beta. * The cumulative retention rate, across all projects, is 79.5% (vs. 78% at the end of October) * Most of the beta users come from the top 20 projects, which account for approximately 89% of the beta users. '''Cumulative Retention Rates:''' [[File:Beta_retention_year_end.jpg]] === Individual Projects: December Retention and Trends === * enwiki, which has the largest beta usage, has a cumulative retention rate of 83.5%. Retention for enwiki has been rising steadily, with retention rate for the month of December at 85.5% (vs. 82.4% prior to Sep 12). Note: The Sep 12 date does not have any particular significance other than it's the date we ran the report. We will try to republish the data with more standard time periods (e.g., beginning of the month) * dewiki has stayed strong. The December retention rate for dewiki was 74.3%. Dewiki retention was 69.7% prior to Sep 12 and has been hovering in the mid-70s ever since). * jawiki is retention is still lagging at 64.9% for December. It looks like the retention may have improved over the last 2 months, but there is a lot of noise in the data, so we cannot be certain. While we would like to say that the font size change affected retention, we cannot conclude this because of the noise. * kowiki is lagging as well, with a cumulative 58.0% retention, though the number of beta users is still relatively low (3,371 have opted into the Beta as of Dec 31). * plwiki, which had an issue with gadget compatibility, has improved quite a bit. Its December retention was 75.8%. Prior to Sep 12, its retention rate was 65.3%. '''December 2009 Retention Rates:''' [[File:Incremental_retention_rate_december.jpg]] The detail behind the updated retention analysis, including both cumulative rates as well as incremental rates (e.g., rates for the month of December) may be found [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdDVMM2l2SGM2dUtBU25MLUtTMFEwMFE&hl=en here]. Previous retention analysis may also be found [[Beta Feedback Survey|here]]. ==Previous Summary (as of November 30, 2009)== The following table lists the retention rates for the Usability Beta with the top 10 highly accessed language Wikipedias broken out: [[File:Beta_retention_1dec09.jpg]] The entire list of retention rates for all language wikis is located [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdDVMM2l2SGM2dUtBU25MLUtTMFEwMFE&hl=en here]. A couple points: # Almost 380,000 users have opted into the Beta since the start of the program with an overall retention of about 79% (vector - the retention rates cited will all be for vector retention) as of November 30, 2009. # The retention rate for enwiki is strong (83%). # Several wikis in the top 10 have retentions below the average. Most notably, jawiki and plwiki have retention rates under 70%. '''Analysis of Language Wikis with Low Retention''' We did a review of the user comments submitted as part of the survey. Because of the volume of comments was very high, we were unable to do a quantitative review of the comments. Rather, we looked for general patterns that might help us understand why certain language wikis had a lower retention rate. Here’s what came out of the data: * '''jawiki:''' Many jawiki users noted that the font size in the Beta was too small. We confirmed this with Firefox and IE. There were also a number of comments on the layout (e.g., users not used to the location of the search box, users liked/did not like the new layout), but the most common comment by far was that the font size was too small. * '''dewiki:''' Unlike jawiki, there wasn’t one particular comment that seemed to appear significantly more frequently than others. In comparison with the users of other language wikis, it does appear that dewiki users are having a more difficult time adjusting to the new location of the search box. Other frequent comments included: like/dislike new layout and/or colors, beta seemed slow, spacing issues in tabs for long German words. :* Another potential contributor to the lower retention rate for dewiki users is the number of IE6 users. These users had a much lower retention rate than average dewiki user (60% for IE6 vs. 70% average). The effect of IE6, however is limited since IE6 users comprised only about 3% of the dewiki users who completed the survey. * '''zhwiki:''' Users of zhwiki noted a few issues: :* Traditional vs. Simplified Chinese: Some users mentioned that the Beta showed only Simplified characters, even when they tried to switch to Traditional characters. :* Slow: Some users mentioned that the beta was "slow." :* Font size too small: Like users of jawiki, some users of zhwiki complained that the font size was too small. Regarding '''plwiki,''' we found that the Beta was not compatible with the refTools gadget. Starting September 29, this gadget was made compatible with the Beta, so we hope that the plwiki retention rate will be higher in the future. [[Category:Statistics]] edbsge5ksysb4hsjjryiffg7flirbx7 0 784 9257 8601 2010-11-04T00:24:23Z MC10 1995 fix bold wikitext text/x-wiki {{Internal}} For the Opt-Out survey, we asked users to indicate why they were leaving the beta. The choices were: * Too hard to use * Did not function properly * Did not perform predictably * I did not like the way it looked * I did not like the new tabs and layout * I did not like the new toolbar * Other Here is the breakdown of the responses for the top 10 language wikis; [[File:reason_codes.jpg]] The cells shaded red indicate areas where the particular language wiki had responses notably worse than average. * '''zhwiki''' and "Did not function properly." The overall retention for zhwiki, however, is about average at 77%. * '''ruwiki''' and "Did not like the way it looked." The overall retention for ruwiki was also about average at 79%. * '''plwiki''' and "Did not like the new toolbar." This may have been caused by the interoperability with refTool. * '''jawiki''' and "Too hard to use." * '''dewiki''' and '''plwiki''' and "did not like the new tabs and layout." For dewiki, this may be because longer German words caused spacing issues with the tabs. This issues should be fixed with the upcoming cascading tabs feature. * '''jawiki''' and '''zhwiki''' and "Did not function predictably." [[Category:Statistics]] 1uvldhbu3nlpkkm1llzqiwi2z28ah0x 0 785 8603 4652 2010-07-29T12:40:24Z Nemo bis 9 cat wikitext text/x-wiki {{Internal}} =Summary= Here is the Beta retention by language wiki and browser: [[File:beta_retention_by_browser.jpg]] The red cells represent browsers that have a retention rate 5% less than the average for the particular language wiki. =Detailed Information= The detailed information by browser (e.g., different versions of IE) as well as percentage of beta users of each browser type is located [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdDNfR1BZcTF3dnNSSUV3eDB6Q2FYTFE&hl=en here]. [[Category:Statistics]] q4brft940pekz7ptmxd1qx77ahtd471 0 786 4650 4649 2009-11-18T00:16:09Z Howief (WMF) 1286 wikitext text/x-wiki =1. Feedback Survey= [[File:usability_beta_feedback_survey.jpg]] =2. Opt-Out Survey= [[File:usability_beta_opt-out_survey.jpg]] k5mqy4eb0lyh5s49a73n5u62w2reo2k 0 793 8604 7546 2010-07-29T12:40:31Z Nemo bis 9 cat wikitext text/x-wiki Here are the user comments from the Beta Survey. Translations into English (using Google Translate) are included. * [http://docs.google.com/leaf?id=0Bykdcg5HdSKbNjg5NGY4OTEtZmVkOC00Y2U4LWE5OWUtYmM4NDRkMmQzYmVh&hl=en enwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdFYyaHFhcXpLLWNyazZQeTh3bnFhS3c&hl=en dewiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdDBmbFRJRV9IN2NvOEU1Z2xTRWRyTVE&hl=en ruwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdDEyRWNHQUE4YkR1Z0ROQXN5NUJPa2c&hl=en eswiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdEE2RE1QbDRERmdHbUJMamxzOWoyWGc&hl=en zhwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdExBcGtmc3JHaFdTSmNaMEZlX19zU1E&hl=en frwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdGNfOG1VVEVHWXBCaU5iazNnMkptbkE&hl=en ptwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdHp2X3FGamJoemo0UlZJRDlUNVEwdmc&hl=en itwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdFVWYm1ZdUpudkFZY1NiWHVHUFFJcGc&hl=en jawiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdEZCX1hSZ1JoTkRQeEgxTEJ0UUNLWlE&hl=en plwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdG9wZDZ0VFBoS3NMZ1JLLWZISlItMWc&hl=en nlwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdEJuT0NOc1otbnY3WW9OanY3aXZQeFE&hl=en huwiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdFQtT0R5b0ZGY3JRcS0tYmFIQXM0Y0E&hl=en kowiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdEZlUnFXQ0tEeGg2VFdBVDNfaG9qbFE&hl=en hewiki] * [http://spreadsheets.google.com/ccc?key=0Aikdcg5HdSKbdDZqQXN5TEZnSGNmY25aX3ZKRHRXR1E&hl=en commons] == Updated == Note enwiki and commons are no longer included as they have the usability initiative things as default * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndGJ5aS1ReDIzWkpXQ1NCd2ZrMHZlNEE&hl=en kowiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndG5qbHN1TjFDSXUtMmROWklkZW56UUE&hl=en nlwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndGkxUkJoSHBaR2UybGNXODZGajYwRHc&hl=en ptwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndHF1ZDVraTg5a3JjTG5Jd2tlZ0pZbnc&hl=en ruwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndDFfZEVDTUdjNk5SQjN5ZEhRSEJXclE&hl=en zhwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndHlkUkx1Wk1vYktndWVURjBOME9kQUE&hl=en dewiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndGJPMVRxOW9pN3NlMkVxMk0xQkVpa3c&hl=en eswiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndFNrM3FIaldEcFlIR1A5SVFZa0JVWWc&hl=en frwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndDF3aU54QmxSUHgyZVhjeHM3VVc1YUE&hl=en hewiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndFBZeWptZDgyWklLSzhfRkRmMlhLMUE&hl=en itwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndFlsbmprN0Yxd3NPekNQXzdFYktSUnc&hl=en plwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndHo4SEN1aDg3Nkl2NGNqY29zVzNrTUE&hl=en arwiki] * [http://spreadsheets.google.com/ccc?key=0Amn4DEPLbG-ndFNqeWY2Nm1MemE1NGtOdVd1U3VyM1E&hl=en jawiki] [[Category:Statistics]] pvfwtgt8601uk1f6kvktl91pjx6y5i3 6 794 4779 4699 2009-11-27T07:06:37Z Datumizer 1241 uploaded a new version of &quot;[[File:Wikimedia vector skin vertical tab mockup.png]]&quot;: Mark the affected region with a red box. wikitext text/x-wiki Mock-up of vertical side tabs for inter-wiki links. Can supply HTML source if desired. su2extd6hq6907eozg73d6yp7vmihrw 6 796 4720 2009-11-24T00:17:04Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 797 4731 2009-11-24T00:21:21Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 798 4732 2009-11-24T00:22:09Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 799 4737 2009-11-24T02:26:58Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 800 4740 2009-11-24T02:29:30Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 804 4757 2009-11-25T20:56:11Z 83.119.125.27 Created page with 'ClickTracking is an extension running on all WMF wikis registering clicks on certain UI elements for a certain portion of page views. == Current configuration == * Status: enabl...' wikitext text/x-wiki ClickTracking is an extension running on all WMF wikis registering clicks on certain UI elements for a certain portion of page views. == Current configuration == * Status: enabled * Ratio: 1:1000 == Things being clicktracked == * Toolbar buttons * Left side bar links == Wishlist == * Old toolbar buttons * Save/Preview/Show changes buttons, new Publish/Cancel buttons * New Wikitext/Preview/Changes tabs * ... f3b4eo0jl6741628t3zot2ac9h6lzo0 10 806 8659 8401 2010-07-29T13:33:31Z Nemo bis 9 cat wikitext text/x-wiki ==Wikimedia Foundation's "backstage" projects== {| class="plainlinks" style="background:transparent; margin:auto; text-align:left; width:100%;" cellpadding="2" |- | [[File:Wikimedia Community Logo.svg|35px|link=meta:|logo Meta-wiki]] | '''[[meta:|Meta-wiki]]'''<br />Community coordination | [[File:Strategywiki.png|35px|link=strategy:|logo Wikimedia Strategy]] | '''[[strategy:|Wikimedia Strategy]]'''<br />Wikimedia Strategic planning | [[File:Wikimedia Outreach.png|35px|link=http://outreach.wikimedia.org|logo Wikimedia Outreach]] | '''[http://outreach.wikimedia.org Wikimedia Outreach]'''<br />Wikimedia Outreach wiki |- | [[File:Mediawiki-logo.png|35px|link=mw:|logo MediaWiki]] | '''[[mw:|MediaWiki]]'''<br />MediaWiki software coordination | [[File:Bug blank.svg|35px|link=mediazilla:|logo Bugzilla]] | '''[[mediazilla:|Bugzilla]]'''<br />A bug tracker for MediaWiki | [[File:Incubator-notext.png|30px|link=incubator:|logo Incubator]] | '''[[incubator:|Incubator]]'''<br />For potential new language versions |- | [[File:Wikimedia Community Logo-Toolserver.svg|35px|link=http://wiki.toolserver.org|logo Toolserver]] | '''[http://wiki.toolserver.org Toolserver]'''<br />Wikimedia Toolserver | [[File:Wikimedia Community Logo-Mailservices.svg|35px|link=http://lists.wikimedia.org|Test Wikipedia]] | '''[http://lists.wikimedia.org Wikimedia Mailservices]'''<br />Wikimedia Mailing Lists | [[File:Wikitech-logo.png|35px|link=http://wikitech.wikimedia.org|Wikitech]] | '''[http://wikitech.wikimedia.org/ Wikitech]'''<br />Wikimedia technical documentation |- | [[File:Wikimania.svg|35px|link=wmania:|logo Wikimania]] | '''[[wmania:|Wikimania]]'''<br />The International Conferences | [[File:Test wiki logo.png|35px|link=testwiki:|Test Wikipedia]] | '''[[testwiki:|Test Wikipedia]]'''<br />For testing software changes | [[File:Pictogram voting question.svg|35px|link=http://survey.wikimedia.org|Wikimedia Surveys]] | '''[http://survey.wikimedia.org/ Wikimedia Surveys]'''<br />Wikimedia surveys website |- | [[File:Nuvola mimetypes log.png|35px|link=http://stats.wikimedia.org|Wikistats]] | '''[http://stats.wikimedia.org/ Wikistats]'''<br />Wikimedia Statistics | [[File:Wikimedia Labs logo.png|30px|link=http://en.labs.wikimedia.org|Wikimedia Laboratories]] | '''[http://en.labs.wikimedia.org/ Wikimedia Laboratories]'''<br />Developing new extensions and features |}<noinclude> [[Category:Navigational templates]]</noinclude> 1ws3akpkvgxge4ekzbvodn34hfd0c5p 100 810 4825 2009-12-01T09:28:24Z Guillom 13 * [[:w:en:digiKam|digiKam]] & other KDE applications supporting the KIPI plugins (~~~) * [[:w:en:Windows Live Photo Gallery|Windows Live Photo Gallery]] * [[:w:en:iPhoto|iPhoto]] [[Category:Multimedi wikitext text/x-wiki * [[:w:en:digiKam|digiKam]] & other KDE applications supporting the KIPI plugins ([[User:Guillom|guillom]]) * [[:w:en:Windows Live Photo Gallery|Windows Live Photo Gallery]] * [[:w:en:iPhoto|iPhoto]] [[Category:Multimedia usability]] ci1elega5atdmhtew653soiccoclknz 100 811 8793 8791 2010-08-16T15:45:25Z Guillom 13 Reverted edits by [[Special:Contributions/Endz24|Endz24]] ([[User talk:Endz24|talk]]) to last revision by [[User:Guillom|Guillom]] wikitext text/x-wiki == Edit location == Widget allowing to add/modify/remove geographical information using OpenStreetMap == Annotations tool == Tool to annotate pictures * review the existing annotation tool, see if it's scalable, it import/export is possible/easy, if it can be improved, etc. * integrate a way to tag people? places? things? * make it work with other view sizes == Image editing tools == Basic image editing tools: * lossless crop * lossless rotate * preserve metadata * add possibility to save the resulting image with another name (not really necessary for rotate, but probably needed for crops) Related bugs: * [[:bugzilla:6672]]: EXIF orientation not used (rotation from digital cameras) * [[:bugzilla:7757]]: allow cropping images when rendered * [[:commons:User:Platonides/rotateImage.js]] == Video editing tools == See Michael Dale's work, including subtitling == To sort == * Video files: see Michael's work * SVG files: http://code.google.com/p/svg-edit/ * Photos, PNGs, etc. Related bugs: * [[:bugzilla:17012]]: Attach source files to uploaded images == SVG editing == Related bugs: * [[:bugzilla:5899]]: Allow on-wiki editing of SVG images * [[:bugzilla:16052]]: Support for multilingual SVGs *: When we do this, add a way to merge existing SVGs so that users can easily turn them into a single multilingual file. [[Category:Multimedia usability - Requirements definition]] mijugrs7l8zoaw7aapdop3vtukn7fj2 6 812 4847 2009-12-02T20:43:04Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 813 9310 8170 2010-12-09T19:40:29Z 82.113.121.248 /* Insert table dialog */ wikitext text/x-wiki ==Insert table dialog== [[File:Ideas for tabledialog.pdf|thumb|200px|page=1]] Please visit [http://prototype.wikimedia.org/s-3/index.php?title=Main_Page&action=edit Sandbox3] to test the dialogs. We are not sure about the preview * Because it does not reflect the table dimensions * It reflects tableborder, sortable table amd header row only * People might want to edit this preview-table, which is not possible. Therefor the preview should be named "Example" and should look not editable. (See mockup #1 - #2) * Maybe it is a wiser decision not to show this preview/example at all. (See mockup #4) ===Comments=== * I think you should use what's on page three. That one is the best. --[[User:Mephiles602|Mephiles602]] 16:47, 7 December 2009 (UTC) * I like the modal windows the best--[[User:Poindexterc|Poindexterc]] 9 December 2009 (UTC) * I like the second mockup the best. I really don't like the overly "Web 2.0" look of the dialogs. Why not make them a bit more subtle like the rest of the Vector style? --[[User:Cmelbye|Cmelbye]] 02:23, 10 January 2010 (UTC) * }-[ extrem bad concept! unusabl. you'll never need for one singl change. and never or seldom for changing each. but under the dark gry mask none of us can see, what happens, where is something found, and so none of us can decide, if change or not. kill the mask, might be, then we can test. Skipper Michael, pfl.wp, --[[Special:Contributions/82.113.121.248|82.113.121.248]] 19:40, 9 December 2010 (UTC) ==Table editor== ''Cross-posted from [[Talk:Prototype#New_table_editor]]''<BR/> I propose a table editor like this: (forgive my bad graphic skills and the misaligned arrows)<br /> [[File:Tableedit.png]] <br /><br /> It will allow user to edit the table on one side through text boxes or textareas(I would prefer these), with the ability to add/delete rows and columns . There will be a preview which can be updated via a button.<br /> The only problem (and its a trivial one) I forsee with this suggestion is that the text boxes are too small. This could be fixed by: * Using scrollable textareas * Using textboxes which expand when clicked *: To see what I mean, try out this HTML code :<source lang=html4strict> <input type=text onfocus="this.size=this.value.length+5" onblur="this.size=5" value="click to expand..." size=5/> </source> :If you don't want to test the source, type this in your browser address bar: <code><nowiki>javascript:window.open("about:blank").document.write('<input type=text onfocus="this.size=this.value.length+5" onblur="this.size=5" value="click to expand..." size=5/>');</nowiki></code> :A floating effect can be done by using absolute positioning with a greater z-index for the textbox, so that the rest of the table doesn't get stretched when the textbox expands * Making the editing table bigger See the file on commons for more information (I've annotated it).<br /> Please tell me what you think and the feasibility of this. Thx, [[Special:Contributions/59.183.163.183|59.183.163.183]] 02:12, 27 March 2010 (UTC) You should probably also read the comments at Bugzilla Bug 2194 ( [https://bugzilla.wikimedia.org/show_bug.cgi?id=2194] I don't know how to make links to bugzilla, sorry) regarding table editors and the like. [[Special:Contributions/88.107.46.47|88.107.46.47]] 00:13, 4 June 2010 (UTC) == Regex search-and-<s>destroy</s>replace == I think we should allow regex not only in find string, but in replace string, too. I mean a string '<nowiki>{{dummy}}</nowiki>' with find string <code><nowiki>{{([a-z]+)}}</nowiki></code> should be replaced to '<nowiki>template dummy</nowiki>' with a replace string <code><nowiki>template $1</nowiki></code>. I don't know, it could be already realized, although I still don't know. [[User:Wizardist|Wizardist]] 11:04, 22 April 2010 (UTC) ==Optimize citation text fields== I really like have the citation tool in the native Wiki environment. I think the date a work was published is a very important and common field, and should be included alongside the accessdate field rather than in the expanded view. I also think the accessdate field should be pre-loaded with today's date, rather than make me have to click an icon. Without the icon, we could probably get rid of the empty line. We should also explain or link to explanation of preferred date formats. Also, showing the preview should automatically show bot the wikitext and parsed text with one click. Lastly, what is that asterisk doing by the Work* field? [[:en:User:HereToHelp|HereToHelp]] ([[:en:User talk:HereToHelp|talk]]) 23:46, 14 May 2010 (UTC) == Make dialogs modeless == I think they would be more convenient to use if I could do anything when they're displayed, like changing the position of the cursor, writing something in the main text area and so on. Currenty, I need to close the window losing everything in it. [[User:Lampak|Lampak]] 12:28, 24 June 2010 (UTC) hs9c400192k75hb6myzl4q69qcs2uvq 0 814 8602 8257 2010-07-29T12:40:21Z Nemo bis 9 cat wikitext text/x-wiki What users liked (enwiki): * Overall positive: ** Beta is great, nuff said! :) ** Liked almost everything. Disliked nothing ** Between this and Google Chrome I can pretend that I'm not even running Vista. * Look/feel: ** A much cleaner, more open or spacious feel. ** I loved it! The look is clean. ** Love the design. ** It looks pretty slick. ** The interface is cleaner and much easier to navigate. ** I like the format; it is clean, concise, and easy to use once I got used to the differences * Toolbar/editing experience: ** The expandable toolbar seems to be good. ** I liked the new editing. It seems to be a good combination of not cluttering things up, not making it totally WYSYWIG (which I think also would be bad) and providing enhanced access to more features. ** I like the cleaner look. New edit toolbar. Overall a BIG success. * Search box location: ** I like the search box at the top ** Good: A good place to put the search box. * Navigation: ** I like the grouping of the page/discussion tabs away from the others Some didn’t feel changes were enough (enwiki): * I don't see that it offers anything on top of the old system. * Other than below, not noticed any problems nor have I noticed anything fantastically brilliant, but then I haven't experiment with it: I have used it as normal as possible to provide a fair comparison. * I don't yet understand what is different from the normal version. * I thought the Beta was pretty much the same. The editing page was nicer but the old style graphics were better. This feels too glossy, the other had a more gritty feel. [[Category:Statistics]] chqxh2w5vr5dccub7kopskfw4vz52rs 14 817 4876 2009-12-04T12:55:08Z Guillom 13 [[Category:Multimedia usability]] wikitext text/x-wiki [[Category:Multimedia usability]] ah4y36oij9fcyo95gwbbnkrumkixhzv 100 818 5750 5291 2010-02-09T18:52:00Z Guillom 13 moved [[Multimedia:Uploading]] to [[Multimedia:Upload]]: hop wikitext text/x-wiki == Workflow == === Workflow and interface redesign === * most likely cases (own work, * simple, not too verbose * but we need to educate them a little => quick tutorial for first-time users Related bugs: * [[:bugzilla:16414]]: Upload form should prevent submission of filename with disallowed extension * [[:bugzilla:4647]]: Allow per-wiki customizable fields on upload form (e.g., for source) * [[:bugzilla:9133]]: Drag and drop uploading * [[:bugzilla:10976]]: Upladed file size calculations to compare with upload quota * [[:bugzilla:11416]]: Upload window bigger * [[:bugzilla:14926]]: Multiple customizable upload forms * [[:bugzilla:16181]]: Simplify the UI of the upload form * [[:bugzilla:16968]]: Special:Upload gives tedious warning about changing spaces to underscores in file names * [[:bugzilla:21288]]: After upload warning, "return and choose different name" serves empty page * [[:bugzilla:21338]]: New user right: "Allow large uploads" * [[:bugzilla:21645]]: Create a more specific warning when (re)uploading a file is protected * [[:bugzilla:13928]]: SpecialUpload warning results in long buttons * [[:bugzilla:22026]]: Description page and upload summary are blank === Staging area === aka holding area, incomplete uploads, quarantine section, etc. Related bugs: * [[:bugzilla:4995]]: Ability to block users from uploading files only *: Listing this bug only as a reminder. This is probably ''not'' the way we want to handle this kind of users. * [[:bugzilla:2537]]: Ability to [[m:Help:Show preview|preview]] summary in "[[Special:Upload|Upload file]]" page. *: Will probably be INVALID after the redesign of the upload process, since we don't want any (wiki)text on the upload page itself. Preview will be included in the next step of the upload where the user provides pieces of information about their file. * [[:bugzilla:16437]]: Ability to preview vector/re-rendered images in Special:Upload "warning" interstitial. * [[:bugzilla:20326]]: Option to strip some metadata on upload (GPS/geolocation privacy) === Multiple Upload === Allow several files to be uploaded at the same time (5 to 10) * possibility to add the same description(s), license(s), category(ies), geocode to all the pictures * but also to specify custom data for each Related bugs: * [[:bugzilla:488]]: Upload more than one file at a time * [[:bugzilla:16751]]: Support multiple file uploads via Special:Upload (backend/infrastructure) * [[:bugzilla:16752]]: Support HTML 5 multiple upload control * [[:bugzilla:16753]]: Support Flash-based upload widget to handle multiple file selection * [[:bugzilla:18132]]: Support multiple file uploads with upload-by-URL === Reupload === Related bugs: * [[:bugzilla:4636]]: Overwriting a file loses new summary/description text * [[:bugzilla:20971]]: Upload new versions of files with different file type *: See also [[Multimedia:Using and reusing content#General|bug 4421: Image file extension should not be part of the name]] * [[:bugzilla:15676]]: Duplicate image reuploading should be forbidden * [[:bugzilla:9246]]: When uploading a new version of a file watch this page is not automatic * [[:bugzilla:17194]]: Special uploadtext for the reupload form * [[:bugzilla:12490]]: Warning needed if dimensions of reupload differ == Smart upload == === Metadata extraction === Extract relevant metadata from files on upload * Priority: EXIF * IPTC and XMP would be nice too, especially since XMP can host multilingual descriptions * where we store these metadata (existing templates, structured data) will be determined later. See [[Multimedia:Metadata#Metadata extraction]] === Category suggestion === based on file name, keywords, description, metadata, etc. === Automatic conversion === Related bugs: * [[:bugzilla:14373]]: Automatically convert uploaded files * [[:bugzilla:20252]]: Support for WAV and AIFF by converting files to FLAC automatically. == Copyright & permissions == === Permissions workflow === Rethink it, make it more straightforward === PD calculator === worldwide PD calculator === EDP management === Some wikis have fair-use or similar policies. See [[:m:EDP|EDP]]. == Source of upload == === Upload by URL === from 3rd-party websites (flickr, Internet Archive, etc.) * Check if the source or the file provides useful metadata * Check if the source or the file provides copyright information Related bugs: * [[:bugzilla:18202]]: Upload-by-URL should run in background, report feedback interactively to user * [[:bugzilla:18243]]: Upload via URL: More meaningful error messages when HTTP error encountered * [[:bugzilla:18112]]: Retain URL as metadata on upload-by-url === Inline upload === upload while editing a page === Cross-wiki upload === * coupled to Inline upload and [[Multimedia:Crosswiki integration|Crosswiki integration]] Related bugs: * [[:bugzilla:1552]]: Upload to Commons from any Wikimedia website * <s>[[:bugzilla:18885]]: Red links for media files do not support shared repositories</s> [[:rev:60593]] === Other === Related bugs: * [[:bugzilla:17957]] Infrastructure for image/video file uploads by FTP [[Category:Multimedia usability - Requirements definition]] 0iudsjkjhgj9fft0arhrj49btt84jh7 100 819 5340 5265 2010-01-11T19:34:48Z Guillom 13 +1 wikitext text/x-wiki Related bugs: * [[:bugzilla:14171]]: Allow Special:FileDuplicateSearch to match against previously deleted images * [[:bugzilla:2606]]: Should be possible to delete an image description page without deleting the image *: Related to RevDelete / single-revision delete * [[:bugzilla:1710]]: Ability to watch all articles in a category * [[:bugzilla:9501]]: List/indication of unpatrolled uploaded media files * [[:bugzilla:14417]]: Generate upload log entry when duplicate file uploaded * [[:bugzilla:2586]]: Allow deleting the most recent version of an image * [[:bugzilla:12874]]: batch deletion for file histories * [[:bugzilla:14148]]: Render file links in the dupe files list like links from wikitext * [[:bugzilla:14446]]: Image with missing versions behave oddly * [[:bugzilla:14901]]: Email notification mistakes edit for new page creation * [[:bugzilla:17370]]: Viewing metadata for deleted files and old revisions == Workflows == * report a problem * nominate for deletion (should these two be merged?) * promotion * review on upload * topic-specific notifications (e.g. sort of topical watchlist of images nominated for promotion/deletion or uploaded) == Resources == * http://www.digikam.org/drupal/node/321 [[Category:Multimedia usability - Requirements definition]] hpuxpbwx23540w9jcvlk1im7e56n1ed 100 820 5588 5288 2010-01-29T17:27:52Z Guillom 13 /* General */ ++ wikitext text/x-wiki == General == * [[:bugzilla:4421]]: Image file extension should not be part of the name * [[:bugzilla:6579]]: Allowing protecting files without protecting image pages * [[:bugzilla:19915]]: <nowiki><audio></nowiki> controls size too big * [[:bugzilla:5614]]: :Integrate an applet to allow viewing of panoramic images, large maps (gigapan / ptviewer) * [[:bugzilla:893]]: Easier image syntax handling * [[:bugzilla:2443]]: Image alt text should be compulsory * [[:bugzilla:5416]]: Please set the "title" property for the image on an image description page * [[:bugzilla:7003]]: Allow percentage values for thumbnail sizes relative to default thumbnail width * [[:bugzilla:7866]]: Allow downloading multiple image files in a compressed archive *: Probably something for the toolserver folks * [[:bugzilla:10151]]: Bad image list doesn't strip image parameters from link * [[:bugzilla:10587]]: enable caption for "border" and "frameless" mode * [[:bugzilla:11239]]: Image captions ending with external links display inconsistently * [[:bugzilla:8298]]: Access information from a file description page where the file is used * [[:bugzilla:13214]]: <nowiki><gallery></nowiki> shouldn't rescale small bitmap images * [[:bugzilla:13650]]: decimal fractions in image sizes are parsed incorrectly * [[:bugzilla:15464]]: Feature: missing gallery image names become upload links * [[:bugzilla:16409]]: New "link=" parameter in [[Image: - cannot link to Media: * [[:bugzilla:16457]]: Allow images in galleries to have their own borders * [[:bugzilla:17398]]: Allow Image link= parameter when using thumb or frame * [[:bugzilla:17685]]: Gallery: No Image prefix needed? (not working) * [[:bugzilla:18682]]: Can't provide alt text for files in <nowiki><gallery></nowiki> * [[:bugzilla:19906]]: Provide a method to allow alternate text for images to be provided at the file description page * [[:bugzilla:20712]]: Anchor tag surrounding a thumbnail's img tag no longer has a title attribute. * [[:bugzilla:21981]]: Auto file name/label feature for <nowiki><gallery></nowiki> * Sometimes the caption is much more detailed than the description on the file description page (example: [[:w:en:Fault-tolerant system|Fault-tolerant system]]). Yet when the user clicks the file to see a larger size, they see the file description page's text, and not the caption with the context of the article. We have to find a better way to handle this (also related: caption / description / alt text). == Search == Related bugs: * [[:bugzilla:8738]]: Improve media (image) search display * [[:bugzilla:13438]]: Allow Special:MIMESearch to work under miser mode == File description page == Related bugs: * [[:bugzilla:3498]]: Image history is confusing ** [[:bugzilla:10863]]: Links on commons upload summaries do not link to commons * [[:bugzilla:4588]]: Group pages by templates in list of file links on Image page * [[:bugzilla:11243]]: Show images on image description page previews * [[:bugzilla:12649]]: Show metadata information from SVGs on file description page * [[:bugzilla:15155]]: Large images preview and navigation (enhancement) * [[:bugzilla:16081]]: Add widescreen resolutions to Image size limits for file description pages * [[:bugzilla:16677]]: Media: view URLs should HTTP-redirect to canonical File: namespace * [[:bugzilla:16956]]: Show IPTC metadata on image description page * [[:bugzilla:17259]]: Image redirect records duplicate link information in redirects and imagelinks tables * [[:bugzilla:17370]]: Viewing metadata for deleted files and old revisions * [[:bugzilla:17474]]: Image pages contain same named links, but to different items * [[:bugzilla:18017]]: Image page should list places that image redirects are used * [[:bugzilla:18107]]: Old revisions of file pages should have old versions of files/images as the primary image. * [[:bugzilla:20647]]: Allow way to choose thumbnail frame for video on its File: description page == Size selector == Allow viewing ang downloading at various sizes Related bugs: * [[:bugzilla:2581]]: View image in several resolutions * [[:bugzilla:6834]]: SVG image should have link to PNG version == Visual warnings == for files suspected to infringe a copyright, etc. Related bugs: * [[:bugzilla:9616]]: Automatic image watermarking * [[:bugzilla:8298]]: New "magic word" to assign an arbitrary CSS class to an image from the image description page == View map == Widget to see on a map where the media file was recorded, and possibly other geocoded files nearby == Rendering == Related bugs: * [[:bugzilla:4688]]: Allowing tag Image to access SVG layers * [[:bugzilla:4689]]: Allowing tag Image to access SVG objects == Reuse from other CMSes == Related bugs: * [[:bugzilla:18133]] WordPress plugin for picking media out of Wikimedia sites [[Category:Multimedia usability - Requirements definition]] pmasnf97b15ruel7kc29okhqei2523d 100 821 4897 4888 2009-12-06T08:47:01Z Guillom 13 cont. wikitext text/x-wiki Summarized from [[:commons:Commons:Usability issues and ideas|Commons:Usability issues and ideas]] == Recruiting participants == * Newcomers are not sufficiently enticed to join the community. * Very few members of the general public are familiar with Commons. * Commons is not "usable" from a corporate perspective, and virtually no media conglomerates or commercial ventures contribute any content. * There is no "unified" watchlist, that would encourage users of other Wikimedia projects to be more involved in Commons. == Creating content == * SVG is not widely used and known. == Uploading content == * Uploading several pictures of the same subject is long and complicated, because the user has to redo all the work (description, category, license) each time. And they have to wait for each picture to upload. * People who upload their own work and just want to share their pictures on Wikipedia are asked to decide things like what license to use. At the same time, we have to make sure people understand what rights they keep and what rights they give away. * The permissions process is too complicated; acceptable images are deleted because of badly worded e-mails. * The software doesn't extract relevant metadata from files (e.g. EXIF), nor does it provide category suggestions. * It is not possible to upload a new version of a file using another file extension. * The "simple" upload form is too verbose and complicated; it mixes an upload form and a complete tutorial. * The upload form provides too many fields and the buttons at the bottom are unneeded for most users. * When preparing a mass upload, there is no cross-platform tool to store the metadata, descriptions etc. offline. * Adding pictures takes a lot of time; this hinders the participation. == Using and reusing content == * Some local wikis use a template with a picture to show audio files, but clicking the picture doesn't play the file. * It is currently not possible to download downsized versions of high-resolution files for people who have small bandwidth. * Linking commons image to facebook does not show any preview; see [http://www.facebook.com/help.php?page=416&hloc=en_US Facebook guidelines]. == Searching, finding and exploring content == * Commons is full of low quality content and there is no quality control * There is duplicate content. * Categories are only available in English; it is difficult to use them for people who can't read/write English. * Galleries vs. categories: duplicate? * When using the search feature, it is impractical to have only a few thumbnails (and their associated text). If the user is looking for media files, we should display media files. * When browsing categories, it is extremely cumbersome to have to browse through all subcategories to explore the content. [http://toolserver.org/~daniel/WikiSense/CategoryIntersect.php CatScan] * Our category system discourages inexperienced users and is overall very inefficient. == Crosswiki integration == * Moving files from a Wikimedia project to Commons is difficult. * Moving files from a Wikimedia project to Commons removes the files from the uploader's (and possibly other people's) watchlist. * When a file is moved to Commons with a different name, the old name doesn't work any more. == Maintenance == * Proposing files to deletion or reporting copyvios is too complicated. * When on a file description page mirrored from Commons on a local wiki, it is annoying and unsettling for the user to have to go to Commons, a separate website. == Feature requests == This section contains feature requests for which no associated issues could be identified. * social tagging: allow a public per-user tags * allow tagging and search by tags into large "super-categories" [[Category:Multimedia usability - Research]] 7ar5afeoyflcr4y89lqip96gtac0qv8 6 826 4933 2009-12-09T14:44:31Z Catrope 268 Screenshot of in-development version of show changes tab. wikitext text/x-wiki Screenshot of in-development version of show changes tab. jc04mg0epbhjq6dbgudcj2xne2du84y 100 828 4968 2009-12-11T21:39:10Z Guillom 13 The main open forum is located at [[:commons:Commons:Usability issues and ideas|]]; a summary is available at [[Multimedia:Issues reported by users]]. [[Category:Multimedia usability - Research]] wikitext text/x-wiki The main open forum is located at [[:commons:Commons:Usability issues and ideas|Commons:Usability issues and ideas]]; a summary is available at [[Multimedia:Issues reported by users]]. [[Category:Multimedia usability - Research]] syzd65pvxzumhtutkok0n1cs7pxzppf 100 829 4995 4991 2009-12-12T00:38:16Z Guillom 13 sort key wikitext text/x-wiki * woman in her thirties == Commons == === Goals === * to illustrate articles she has written * to share photos and make them available for other articles * photos from vacations * photos found elsewhere * pictures scanned from books (engravings, paintings) === Upload workflow === * doesn't retouch images a lot * basic editing: rotating, cropping, adjusting the color balance (using Photoshop or iPhoto) * is already on Commons; goes to the upload page through the link in the sidebar * chooses "own work" * doesn't read the lengthy instructions * changes the automatically generated file title by a descriptive title in the upload form * checks the fields * in order to fill in the "date" field, she goes back to the file explorer and looks at the date there ** or, just puts today's date * adds a description in French, sometimes using the appropriate Wikipedia article * tries to add a translation of the description to English using Wikipedia and Wiktionary interlanguage links * skips the other fields * skips geotagging: doesn't know how to do * adds a general category using the autosuggest feature: types a few letters and sees what categories are brought up ** as a consequence, only searches among existing categories * if she doesn't find a precise category she's looking for, adds a more general category during upload; then, when the upload is completed, clicks on the category name and browses it until she finds the subcategory she's looking for. She eventually replaces the general category by the precise subcategory * always uploads files one by one ** because : doesn't have many files to upload and doesn't know how to upload several files at a time * to add the picture to a Wikipedia page: copy/pastes the file name, then writes the rest using her knowledge of wikisyntax * occasionally creates categories ** adds the category, previews, clicks on the red link and creates the page === Questions === * search on Commons: by categories * difficult to search in English, or in categories in other languages (e.g. in Russian) * the software interface is localized, but the help and reference pages often come in English * CommonSense: doesn't know what to do with it; unusable * licenses nightmare == Flickr == === Goals === why flickr? * way easier than Commons * to share more personal pictures than on Commons * albums "without any encyclopaedic value" * personal albums: allow to collect pictures in groups that have a meaning to the author, but not necessarily an encyclopaedic meaning to the user === Upload workflow === * now uploads the same picture to flickr * explores the top links in the drop-down menus as one would do for a desktop application * usually imports several files at a time (up to 10) * selects the file, checks the permissions (friends, family) and uploads * then, on the landing page, clicks to add a description & tags * occasionally adds a descriptive title * adds a description in French * occasionally uses tools such as "Rotate" available in the menu over the image on the image page === Questions === Search * never uses Google Images, because she can never be sure about copyright * by tags * very long * can search in French * can search by license * allows the user to easily find content elsewhere * finds flickr tags "more intuitive" Other * doesn't geotag often on flickr * doesn't need help pages; "I understand" * contextual help: "You may want to..." (e.g. "add tags to this batch") * tested the photo organizer; feels she doesn't have the time * Commons is great in that you don't have to check the copyright status of each file you use; it's safe (especially for promoted pictures (FP/QI)) [[Category:Multimedia usability - Ethnographic interviews|Adrienne]] 2zfhml99y3zjgnmfhyxgyavq2f2eawd 14 830 4989 4981 2009-12-12T00:34:35Z Guillom 13 +meetings wikitext text/x-wiki [[Category:Multimedia usability - Research]] [[Category:Multimedia usability - Meetings]] hnjxl18tjt9lgj195okou6q79a03yuj 14 831 4994 2009-12-12T00:37:25Z Guillom 13 [[Category:Multimedia usability - Research]] wikitext text/x-wiki [[Category:Multimedia usability - Research]] okb9vxmvp2eor5ly6btfh3bkmj6ipxy 100 832 5037 5035 2009-12-14T22:14:23Z Guillom 13 cleanup, fmt wikitext text/x-wiki * Woman in her thirties * Main focus: taking photographs of objects in museums & during political rallies * uses the English interface == Goals == Goals when contributing museum pictures: * to give a good view of museum collections * to provide freely reusable pictures * the intended audience is mostly academic => to increase awareness about free licenses Goals when contributing pictures of political rallies: * to provide freely reusable pictures that can be used on other websites * to increase awareness about Commons == Upload workflow == * shoots photographs in RAW * develops them (exposure, noise, saturation, author metadata) using a dedicated software * does minor retouching using the GIMP * saves as JPG using a descriptive title * uploads pictures one by one; doesn't use batch upload tools; has never tried Commonist * customizes the "upload file" link in the sidebar using her personal JS, so that the link directs to the basic upload form * often copy/pastes from a similar picture * processes a picture, uploads it, processes the next one during the upload and so on * often uploads series of pictures, so descriptions are similar to each other * copy/pastes the license, uploads, and adds categories later * category work using HotCats; tries, then clicks and browses to see if a more precise subcategory applies. Also takes this opportunity to check if there are similar pictures == Other activities & facts == * regularly browses categories she's interested in to improve categorization, detect copyright violations * uses the HotCats gadget * when assembling several pictures, metadata are lost * gets many e-mails asking for confirmation that people can reuse her pictures * communication is complicated in a multilingual environment; people have to talk through templates == Commons & Wikipedia == * if the subject or the artist is not well known, adds some pictures to the Wikipedia article * most of reuse confirmation requests are about pictures displayed Wikipedia, which are a lot more visible than those on Commons only * spends more time working on Commons than on Wikipedia == Specifics of museum photography == * takes pictures of the labels, buys official catalogues * makes it a point to add the ID number / inventory number * the wiki platform is very useful for people working on museum pictures: they can easily add/improve descriptions == Wishlist == * statistics of freely-licensed pictures hosted somewhere else than Commons * interproject watchlist (especially for Commons) * toolserver tool that browses a family of interwiki-linked articles to see if one of them contains a picture [[Category:Multimedia usability - Ethnographic interviews]] 4fk35s314m23ewzkdgfoh7t2aqlf4u6 0 835 8627 5970 2010-07-29T13:17:12Z Nemo bis 9 cat wikitext text/x-wiki __NOTOC__ {{Draft}} {{Internal}} [[File:Citrus_medicus_fruit.jpg|thumb|right]] We welcome your constructive feedback. Please use the [[Talk: Citron_Designs | Discussion]] page for all of your comments. <div style="clear:both"></div> == Templates == [[File:Updated Citron templates.pdf|thumb|200px|page=1 | Latest Design]] [[File:Citron templates.pdf|thumb|200px|page=1 | Older Design]] === Motivation === * Reduce the confusion factor that infoboxes and templates have on new users. * Provide access to article contents that doesn't require navigating through large volumes of template text. * Provide an editing interface for template information, contents, and fields that is suitable for advanced and new editors. === Approach === * Collapse templates within the editor to allow easier access to an articles contents. * Maintain current method of editing templates (by expansion) while also introducing an easier method for templates that can afford such an interface (by GUI, dialog). * Create new apis for template authors to be able to control how their template editing interface works. <div style="clear:both"></div> == Left Navigation == [[File:LeftNav_lines.pdf|thumb|200px|]] === Motivation === * Learn how the left navigation is used quantitatively. * Use this information to simplify and reorganize the left navigation bar. === Approach === * Nimish's click tracking data is available [here | here] * Make highest used links always visible * Categorize and collapse less frequently visited links. <br /> <div style="clear:both"></div> == Babaco Fixes == === Colors (W3C) === === Closed Tabs === === Simple Search === === Dialogs === [[File:Dialog_Ref.jpg|thumb|200px|]] [[File:Dialog_File.jpg|thumb|200px|]] [[File:Dialog_IGallery.jpg|thumb|200px|]] <div style="clear:both"></div> ===Publish/Cancel Button Styling === == Below the Editor == [[File:100120_vacuuming_06.jpg|thumb|200px|]] [[File:Vacuuming_old.pdf|thumb|200px|page=1]] === Motivation === * Clean up all of the stuff below the editor that everyone has hard time with. * Make user flow more explicit === Approach === * Organize and group links, messages intuitively * Consolidate redundant links, messages * Remove duplicate links and messages where applicable * Collapse information that is advanced and visually overhelming * Repeat "Publish" and "Cancel" buttons on the top and bottom of the editor. * Give greater emphasis to the "Publish" button * See Also: Side by Side Preview <div style="clear:both"></div> [[Category:Releases]] 20oa55k1bush3kosqholjpzwo9zt4fc 10 836 8655 6779 2010-07-29T13:31:51Z Nemo bis 9 cat wikitext text/x-wiki {| class="plainlinks" style="margin:auto; width:37%; background-color:#FFFFFF; border:1px solid #007F8F; -moz-border-radius: 9px;-webkit-border-radius: 9px; border-radius: 9px; padding:1px; text-align:center;" id="social_bookmarks" |- | '''Share this:'''&nbsp; <span title="Share on Facebook">[[File:F icon.svg|16px|Bookmark with Facebook|link=http://www.facebook.com/sharer.php?u={{fullurle:{{FULLPAGENAME}}}}&t={{urlencode:{{FULLPAGENAME}} - Wikimedia Strategy}}]]</span> <span title="Share on Digg">[[File:Digg-icon.png|Share on Digg.com|link=http://digg.com/submit?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}} - Wikimedia Strategy}}]]</span> <span title="Share on delicious">[[File:Del.icio.us-icon.png|Share on delicious|link=http://delicious.com/post?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}} - Wikimedia Strategy}}]]</span> <span title="Share on reddit">[[File:Reddit.png|Share on reddit.com|link=http://reddit.com/submit?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}} - Wikimedia Strategy}}]]</span> <span title="Share on StumbleUpon">[[File:Stumbleupon.png|Share on stumbleupon.com|link=http://stumbleupon.com/submit?url={{fullurle:{{FULLPAGENAME}}}}&title={{urlencode:{{FULLPAGENAME}} - Wikimedia Strategy}}]]</span> <span title="Share on Technorati">[[File:Technorati icon.png|Share on Technorati|link=http://www.technorati.com/faves?add={{fullurle:{{FULLPAGENAME}}}}]]</span> <span title="Share on Twitter">[[File:Twitter.png|alt=Share on twitter.com|link=http://twitter.com/?status=Check%20out%20this%20link%20from%20Wikimedia%20{{fullurle:{{FULLPAGENAME}}}}|Share on twitter.com]]</span> |}<noinclude> [[Category:Templates]]</noinclude> rig5i7r8jjz39ipyzcsa54gmcd141z7 6 838 5014 2009-12-12T20:33:09Z Catrope 268 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 839 10290 9338 2021-09-11T22:53:18Z Krinkle 709 wikitext text/x-wiki [[File:Wikipedia Usability Initiative Logo.png|right|Wikipedia Usability Initiative logo]] The '''Wikipedia Usability Initiative''' ran from 2009 to 2011 and was realized by a grant from the U.S.-based Stanton Foundation. The goal of this initiative is to measurably increase the usability of Wikipedia for new contributors by improving the underlying software on the basis of user behavioral studies, thereby reducing barriers to public participation. With an initial focus on English Wikipedia, eventually this research and development will be implemented across all languages and possibly to other [[w:Wikimedia_projects#Wikimedia_projects|Wikimedia projects]]. == Contribution Ideal == *Become involved and share concepts for the development of [[w:Wikipedia|Wikipedia]] and other [[w:Wikimedia Foundation#Projects, initiatives and chapters|Wikimedia projects]]. *Create an article with a detailed summary and add it to the [[list of proposals and ideas]]. == Information == [[File:Naoko Komura Wikipedia Usability Initiative .pdf|thumb|Wikipedia Usability Initiative presentation by Naoko Komura (PDF)]] * This project has a limited [[Wikipedia Usability Initiative/Project Scope|scope]] which corresponds to our grant, so please get familiar with this to best contribute. * If you are new here, you may be assisted by taking a look at our [[Wikipedia Usability Initiative/FAQ|frequently asked questions]]. * If you want to learn more about other present and past efforts to improve usability, our [[Wikipedia Usability Initiative/Links|links]] to related sites may be helpful. * We're collecting a list of [[Resources|resources]] that may be useful in the field of human-computer-interface design and development. == Work in Progress == === Research and Evaluation === * [[Environment Survey|Qualitative Environment Survey]] being conducted on existing MediaWiki extensions which may provide some benefit to the usability of Wikipedia. * [[Wikipedia Statistical Survey|Quantitative Statistical Survey]] of English Wikipedia being conducted which focuses on volume of edits, new editors, and other related metrics. * [[Usability and Experience Study]] of new and non editors of English Wikipedia (March, 2009). * [[Usability, Experience, and Progress Study]] (September 2009). * [[Usability, Experience, and Evaluation Study]] (March 2010). * [[Beta Feedback Survey | Beta Feedback - Retention and Survey Results]] - overview of feedback from our Beta testers. * [[Statistical Evaluation]] - overview and results of tools we're developing to collect anonymous usage data. * [[Good Reads]] - interesting research and industry literature on relevant topics. === Design === * Details on the three [[Releases]]: ** [[Acai Designs]]: Phase I of proposed usability improvements. ** [[Babaco Designs]]: Phase II of proposed usability improvements. ** [[Citron Designs]]: Phase III of proposed usability improvements. * [[Style Guide]] * [[Cross Cultural Considerations]] === Development === * [[Sandbox]] for testing experimental code and evaluating existing extensions. * [[Prototype]] of proposed usability improvements for various Wikipedia projects. == Getting Involved == * [[Talk:Prototype|Feedback]] on the staging of changes seen on our prototype sites is being collected. * We need [[Your Opinion]] on changes that might affect you. [[Category:Wikipedia Usability Initiative]] 9ctt60xm72hutg4n8rnhxbdzaks4hip 0 840 5017 2009-12-12T23:38:36Z Kozuch 15 moved [[FAQ]] to [[Wikipedia Usability Initiative/FAQ]] wikitext text/x-wiki #REDIRECT [[Wikipedia Usability Initiative/FAQ]] dmpnusprb0surlkvtg2mpyoj80b029g 0 841 5019 2009-12-12T23:38:46Z Kozuch 15 moved [[Links]] to [[Wikipedia Usability Initiative/Links]] wikitext text/x-wiki #REDIRECT [[Wikipedia Usability Initiative/Links]] nn3zhxh7ply7ihkz271m40r22wvgzoc 0 842 5021 2009-12-12T23:39:06Z Kozuch 15 moved [[Project Scope]] to [[Wikipedia Usability Initiative/Project Scope]] wikitext text/x-wiki #REDIRECT [[Wikipedia Usability Initiative/Project Scope]] 3jo2dxt3mg1riiyn3jt230zsqg9fiqq 100 845 5040 5039 2009-12-14T22:53:46Z Guillom 13 cleanup, fmt wikitext text/x-wiki * Man in his thirties * Main focus: moving pictures from other projects to Commons * goal when contributing: to illustrate Wikipedia articles == Upload workflow == * watches a lot of articles related to Physics * when he finds an article without a picture, he browses the interwiki links (primarily en.wikipedia) to see if pictures are available in other language versions of the same topic. * moves the file using CommonsHelper (and his TUSC account) * doesn't do a lot of checking except for the license; often keeps the automatically-generated description & categories * then adds the "now commons" template on the original file page. == Other facts == * rarely uses the built-in search engine, except for proper nouns * rarely uploads self-created works * doesn't spend a lot of time on Commons * as an OTRS volunteer, he prefers to stick to text permissions, because he finds media-related permissions too complicated. [[Category:Multimedia usability - Ethnographic interviews]] l2jma0e69kbzjq1dwl7hdh7rq8f6p6v 100 846 5065 5041 2009-12-15T03:41:34Z Guillom 13 cont. wikitext text/x-wiki * Man in his twenties == Upload workflow (new image) == * skips the long text on upload page * selects file * adds a descriptive filename * adds the date of the upload in the "date" field * adds a description in English * doesn't add categories, says it's too much to ask * gets a red warning because he didn't select a license * once the upload is complete, changes the date to the one the picture was taken, by looking at the date displayed in metadata == Other notes == * it's difficult to find images because they are mostly in subcategories [[Category:Multimedia usability - Ethnographic interviews]] 604tcnmw89xfv6v480rpafmzu1stsvs 0 847 10262 5470 2017-02-21T03:45:31Z Krinkle 709 prettytable=>wikitable wikitext text/x-wiki == Browser Compatibility Matrix for features in Citron== You may also be interested in the [[Releases/Babaco/Compatibility_Matrix|compatibility matrix]] for features in Babaco. {|class="wikitable" !rowspan="2"|Browser&nbsp;<br/>Feature&nbsp; !colspan="5"|Internet Explorer !colspan="4"|Firefox !colspan="3"|Chrome !colspan="3"|Safari !colspan="5"|Opera !colspan="1"|Camino |- !width="30"|5.5 !width="30"|6 !width="30"|7 !width="30"|8 !width="30"|9 !width="30"|1 !width="30"|2* !width="30"|3 !width="30"|3.5 !width="30"|1 !width="30"|2 !width="30"|3 !width="30"|3 !width="30"|4 !width="30"|iP !width="30"|9 !width="30"|9.5 !width="30"|9.6 !width="30"|9.8 !width="30"|10 !width="30"|1.6 |- !rowspan="2"|Distribution |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:13.6%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:15.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:10.6%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.5%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:1.9%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:45.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:45.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:6.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.8%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.7%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:3.7%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.4%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:2.0%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |height="100" valign="bottom"|<div style="background-color:#000;height:0.1%"></div> |- |align="center"|<small>0.1%</small> |align="center"|<small>13.6%</small> |align="center"|<small>15.1%</small> |align="center"|<small>10.6%</small> |align="center"|<small>0.0%</small> |align="center"|<small>0.5%</small> |align="center"|<small>1.9%</small> |align="center"|<small>45.0%</small> |align="center"|<small>45.0%</small> |align="center"|<small>0.1%</small> |align="center"|<small>6.1%</small> |align="center"|<small>0.8%</small> |align="center"|<small>0.7%</small> |align="center"|<small>3.7%</small> |align="center"|<small>0.4%</small> |align="center"|<small>0.1%</small> |align="center"|<small>2.0%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |align="center"|<small>0.1%</small> |- |align="left"|'''Content folding''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 --> |style="color:green"|<!-- IE-8 --> |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> |style="color:green"|<!-- FF-3 --> |style="color:green"|<!-- FF-3.5 --> |style="color:green"|<!-- C-1 --> |style="color:green"|<!-- C-2 --> |style="color:green"|<!-- C-3 --> |style="color:green"|<!-- S-3 --> |style="color:green"|<!-- S-4 --> |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 --> |style="color:green"|<!-- O-9.8 --> |style="color:green"|<!-- O-10 --> |style="color:green"|<!-- C-1.6 --> |- |align="left"|'''Dialogs: Internal/External Links''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:red"|<!-- IE-7 --> |style="color:red"|<!-- IE-8 --> |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> |style="color:green"|<!-- FF-3 --> |style="color:green"|<!-- FF-3.5 --> |style="color:green"|<!-- C-1 --> |style="color:green"|<!-- C-2 --> |style="color:green"|<!-- C-3 --> |style="color:green"|<!-- S-3 --> |style="color:green"|<!-- S-4 --> |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 --> |style="color:green"|<!-- O-9.8 --> |style="color:green"|<!-- O-10 --> |style="color:green"|<!-- C-1.6 --> |- |align="left"|'''Dialogs: Insert Tables''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:red"|<!-- IE-7 --> |style="color:red"|<!-- IE-8 --> |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> |style="color:green"|<!-- FF-3 --> |style="color:green"|<!-- FF-3.5 --> |style="color:green"|<!-- C-1 --> |style="color:green"|<!-- C-2 --> |style="color:green"|<!-- C-3 --> |style="color:green"|<!-- S-3 --> |style="color:green"|<!-- S-4 --> |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 --> |style="color:green"|<!-- O-9.8 --> |style="color:green"|<!-- O-10 --> |style="color:green"|<!-- C-1.6 --> |- |align="left"|'''Simplified Search''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:red"|<!-- IE-7 --> |style="color:green"|<!-- IE-8 --> |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> |style="color:green"|<!-- FF-3 --> |style="color:green"|<!-- FF-3.5 --> |style="color:green"|<!-- C-1 --> |style="color:green"|<!-- C-2 --> |style="color:green"|<!-- C-3 --> |style="color:green"|<!-- S-3 --> |style="color:green"|<!-- S-4 --> |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 --> |style="color:green"|<!-- O-9.8 --> |style="color:green"|<!-- O-10 --> |style="color:green"|<!-- C-1.6 --> |- |align="left"|'''Side-by-side preview''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 --> |style="color:green"|<!-- IE-8 --> |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> |style="color:green"|<!-- FF-3 --> |style="color:green"|<!-- FF-3.5 --> |style="color:green"|<!-- C-1 --> |style="color:green"|<!-- C-2 --> |style="color:green"|<!-- C-3 --> |style="color:green"|<!-- S-3 --> |style="color:green"|<!-- S-4 --> |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 --> |style="color:green"|<!-- O-9.8 --> |style="color:green"|<!-- O-10 --> |style="color:green"|<!-- C-1.6 --> |- |align="left"|'''Language-specific tool icon''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:green"|<!-- IE-7 --> |style="color:green"|<!-- IE-8 --> |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> |style="color:green"|<!-- FF-3 --> |style="color:green"|<!-- FF-3.5 --> |style="color:green"|<!-- C-1 --> |style="color:green"|<!-- C-2 --> |style="color:green"|<!-- C-3 --> |style="color:green"|<!-- S-3 --> |style="color:green"|<!-- S-4 --> |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:green"|<!-- O-9.6 --> |style="color:green"|<!-- O-9.8 --> |style="color:green"|<!-- O-10 --> |style="color:green"|<!-- C-1.6 --> |- |align="left"|'''Add Media Wizard''' |<!-- IE-5.5 --> -- |<!-- IE-6 --> -- |style="color:red"|<!-- IE-7 --> F |style="color:red"|<!-- IE-8 --> F |<!-- IE-9 --> -- |<!-- FF-1 --> -- |style="color:green"|<!-- FF-2 --> P |style="color:green"|<!-- FF-3 --> P |style="color:green"|<!-- FF-3.5 --> P |<!-- C-1 --> -- |<!-- C-2 --> -- |style="color:red"|<!-- C-3 --> F |style="color:red"|<!-- S-3 --> F |style="color:red"|<!-- S-4 --> F |<!-- S-iP --> -- |<!-- O-9 --> -- |<!-- O-9.5 --> -- |style="color:red"|<!-- O-9.6 --> F |style="color:red"|<!-- O-9.8 --> F |style="color:red"|<!-- O-10 --> F |<!-- C-1.6 --> -- |} Estimated browser distribution based on information from w3schools.com as of August 2009 [http://www.w3schools.com/browsers/browsers_stats.asp] {|class="wikitable" !Mark !Description |- |style="color:green"|P |Pass: Renders and functions properly |- |style="color:red"|F |Fail: Does not render or function properly |- |style="color:blue"|XF |Expected Fail: Does not render or function properly, but is not expected to due to expected browser limitations |- |style="color:orange"|RF |RTL Fail: Renders and functions properly in left to right mode, but not in right to left (as seen on our [http://prototype.wikimedia.org/ar. |- |style="color:black"|-- |For the browsers which were not part of the test |- |style="color:black"|* |For Firefox 2.0.0.5 and above |} == How can I help? == We need more people to follow our [[#Testing Procedure|testing procedure]] and report back to us on their experiences. Uploading screenshots and adding information to the [[Talk:Releases/Acai/Compatibility Matrix|discussion page]] is a great way to help us out! == Testing Procedure == === Add Media Wizard === * Visit an edit page [http://usability.wikimedia.org/w/index.php?title=Polar_bear&action=edit] * Verify clicking on "image insert icon" displays the add-media-wizard dialog * Verify clicking on an image result item brings up the insert dialog * Modify the text description with wiki syntax <nowiki>"this is a ''test'' [[description]]"</nowiki> * Verify the "insert into page" button inserts in image embed syntax * Preview the page to see the image in the output. ==== Crop Tool ==== * Verify the "crop tool" gives you a crop selection icon and lets you crop the image * Verify the inserted crop image matches y our cropped selection ==== Search and play videos ==== * Try searching for "ogv" * verify the result video clips can be played inside the insert dialog * do the insert, verify the clips can be played in the page during preview and save. 1mrff47sdo3vysv5a2y0pj5pq5emce6 0 848 6170 6169 2010-03-22T11:47:50Z 59.183.142.249 wikitext text/x-wiki {{Preview Crop |Image = Polar_bear_taxidermied.jpg |bSize = 327 |cWidth = 182 |cHeight = 343 |oTop = 13 |oLeft = 99 |Location =right |Description =test }} c83vm1j5cz1bnkb6qhm67f9gnkxqrbl 6 849 5056 5055 2009-12-15T01:50:09Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:Cheryle props.ogv]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 850 5085 2009-12-15T23:05:38Z Catrope 268 Screenshot of a first, rudimentary prototype of syntax highlighting and template recognition. wikitext text/x-wiki Screenshot of a first, rudimentary prototype of syntax highlighting and template recognition. 7rj19i9m22s57zpiztl7sbiswcfxvkx 6 851 5092 5088 2009-12-15T23:31:52Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:Citron templates.pdf]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 100 855 5551 5338 2010-01-27T19:44:26Z Guillom 13 /* Other */ ++ wikitext text/x-wiki == Unified watchlist == A way to integrate the watchlist on Commons to a watchlist on another wiki. Or a list of any watchlists. * Via RSS feeds entered manually by the user * Via special page with checkboxes (include a select/unselect all). * Reasons: A fair amount of Wikimedia users don't want to upload files to Commons because it requires them to have a separate watchlist. Another fair amount of users complain that they aren't properly notified when they get messages about their files on their talk page on Commons. == Special page for global settings == Could be used for global preferences in the end, but would first be used for global watchlist. Allow some sort of sorting with JS magic; possible keys: * number of edits on the wiki * project (all wikipedias together, then sorted alphabetically by language) * language (same) Related bugs: * [[:bugzilla:14950]]: Global preferences == Cross-wiki file move & copy == Facilitate one-click file moves from any Wikimedia wiki * and one-click file move from Commons to any Wikimedia wiki (e.g. for unfree content that was uploaded to Commons but has to be moved to a local wiki with the relevant EDP) * and one-click file copy from any Wikimedia wiki to any Wikimedia wiki (e.g. for unfree content available on a wiki with the appropriate EDP, and that has to be copied to another wiki with a similarly appropriate EDP). * later: add move from any MediaWiki website / CMS to Commons * to keep in mind: watchlist Related bugs: * [[:bugzilla:5283]]: Moving media files to Commons ought to be much easier, automatic * [[:bugzilla:6071]]: Transwiki image import * [[:bugzilla:18248]]: Redirects to Images on Shared Repos do not work * [[:bugzilla:14801]]: Global deleted image review for Commons admins == Global usage tracking == for any Wikimedia wiki * later: add usage from any MediaWiki website with InstantCommons enabled Related bugs: * [[:bugzilla:1394]]: "File links" on the image pages should list links from other wikis ** Marked as fixed, but polishing is needed * [[:bugzilla:6220]]: Shared repositories support for Special:WantedFiles == Mirrorred file description page == Deal with it; remove it? improve it? Just do something Related bugs: * [[:bugzilla:5995]]: Block local description edits for Commons images *: Related to [[Multimedia:Metadata#Structured data]] * [[:bugzilla:18616]]: Local evaluation of magic words for commons files * [[:bugzilla:18752]]: Show categorization on shared repository on local file page. * [[:bugzilla:22001]]: File history from shared repository parsed in context of local wiki == Other == Related bugs: * [[:bugzilla:14888]]: Special page to list name collisions with shared upload repository * [[:bugzilla:15690]]: More efficient batch lookups in foreign repos * [[:m:User:Duesentrieb/CommonsTicker]] [[Category:Multimedia usability - Requirements definition]] iyfmhbcivpyvstdtb7ear5qly621wlt 100 856 8826 5240 2010-08-27T23:47:44Z NeilK 1629 wikitext text/x-wiki == User-friendly language setting == Possible solutions: * easy: use lang of the SUL'd user's home wiki as default language in preferences * harder: global language setting (overridden by local specific settings) * and in any case, add the language selector to the sign up page on multilingual wikis like Commons, so that users don't need to go in their preferences and change the language as soon as they register. * Make the info public? in order to make it easier for other people to communicate with the user == Sign up == Related bugs: * [[:bugzilla:5309|5309]] Localize captcha images * [[:bugzilla:6466]]: Enable login language selection links on Commons, Meta, MediaWiki, and WikiVersity.org *: See also [[:rev:14901]] (language selector bar) == Multilingual communication == Communication between users is difficult on multilingual sites like Commons; people have to communicate using auto-translated templates. == Multilingual search == == Multilingual categories == Allow translations of categories * see if this can be done as a larger overhaul of the interwiki system ([[bugzilla:11423]]) * talk with Duesentrieb, Siebrand and perhaps interwiki bot owners * see also [[:mw:Multilingual MediaWiki|Multilingual MediaWiki]] == Better language picker == Unlike just about every website on the planet, we have a need to allow quick switching between over 356 languages or dialects, sometimes on the same page. Wikimedia's current solution is to present a menu of 356 choices to scroll through, using the name of the language in the language, ordered by ISO code. The problem cannot be solved by any ordering, as that will always have languages that are harder to find. It is also sub-optimal to mix code pages, listing devanagari alongside roman letters, since there is no obvious order. So we want to do away with a scrolling menu altogether. We want to use a text input that auto-completes with suggestions, much like the search box today. However, this auto-completion also knows about all the translations we have for all language names as well as their ISO codes. So to get to German, you could type ''de'' for its ISO code or '''De'''utsch. You could also type ''ge'' which would give you "de - Deutsch (German)" among its choices, or even the Chinese name for German. We avoid the N**2 problem since if we do not have a translation for a particular language name in a particular language, that simply doesn't become part of the choices offered. == Other == Related bugs: * [[bugzilla:1495]]: Undefined messages in user language don't fall back to MediaWiki: customizations *: Not exactly sure if the problem still exists * [[:bugzilla:8287]]: Enable multilingual extension in Commons *: Probably not the best way to handle this * [[:bugzilla:4125]] Preserve ?uselang=xx / &uselang=xx during sessions [[Category:Multimedia usability - Requirements definition]] 6e4shchppv9s50de3a8ltag46wpr0zx 100 860 5339 5271 2010-01-11T17:01:31Z Guillom 13 +2 wikitext text/x-wiki == Slideshow == for all images of a category (+subcats?) == Categories == more visible, more explicit == Classification == Categories, galleries, etc. Related bugs: * [[:bugzilla:9617]]: Feature: improved 'annotation' method for media (combo of galleries, categories and tags) * [[:bugzilla:3341]]: gallery of images uploaded by a user *: See also [[:mw:Extension:User Image Gallery]] * [[:bugzilla:8951]]: Allow users to specify file categories when uploading * [[:bugzilla:5234]]: Upload Categorization dropdown * [[:bugzilla:15087]] Default thumb image for a category * [[:bugzilla:17955]]: Show end of image names in categories * [[:bugzilla:21795]]: Camera categories: parse category and switch in mediawiki namespace == Site requests == * [[bugzilla:17471]]: Default our search box to "Search" instead of "Go" on Commons * [[bugzilla:18354]]: Change the go button functionality in Commons [[Category:Multimedia usability - Requirements definition]] 198h28n24x83ij4ubdln2we496p524w 100 861 5270 5262 2009-12-31T19:53:29Z Guillom 13 +related bugs wikitext text/x-wiki == Metadata extraction == Related bugs: * [[:bugzilla::657]]: Pull copyright metadata from files on upload * [[:bugzilla::16956]]: Show IPTC metadata on image description page * [[:bugzilla:20326]]: Option to strip some metadata on upload (GPS/geolocation privacy) * [[:bugzilla:12649]]: Show metadata information from SVGs on file description page * [[:bugzilla:17370]]: Viewing metadata for deleted files and old revisions *: See if we still store metadata of deleted files and old revisions == Metadata computation & internal use == * [[:bugzilla::6672]]: EXIF orientation not used (rotation from digital cameras) * [[:bugzilla::13172]] EXIF handling ignores tags with Count >= 1 * [[:bugzilla::3892]] EXIF data shown incorrectly for fractional values == Structured data == Related bugs: * [[:bugzilla:8298]]: Access information from a file description page where the file is used == Metadata search == == Metadata export == Export formats: * in files on download, including downsized versions * queryable via the API? * other standard format (see w/ Liam) Related bugs: * [[:bugzilla::3361]]: Image author, description, and copyright data saved in EXIF fields * [[:bugzilla:9666]]: External link syntax which adds rel="license" == To sort == * EXIF, IPTC & XMP support * [http://dublincore.org/documents/dces/ Dublin Core] * [[:mw:Extension:RDF|Extension:RDF]] [[Category:Multimedia usability - Requirements definition]] 649fi9dv7y4b29guzz8f0e7a13ilq8e 100 870 5320 5232 2010-01-07T19:17:20Z Guillom 13 fix heading wikitext text/x-wiki = Uploading = {{Multimedia:Uploading}} = Maintenance = {{Multimedia:Maintenance}} = Editing = {{Multimedia:Editing}} = Using and reusing content = {{Multimedia:Using and reusing content}} = Crosswiki integration = {{Multimedia:Crosswiki integration}} = Multilingual support = {{Multimedia:Multilingual support}} = Navigation = {{Multimedia:Navigation}} = Metadata = {{Multimedia:Metadata}} = Back-end = {{Multimedia:Back-end}} [[Category:Multimedia usability - Requirements definition]] 2marnli0qtv0d6rnj3brqfxlrjenx8b 100 871 5321 5285 2010-01-07T19:17:51Z Guillom 13 /* Internal file management */ +link wikitext text/x-wiki == Supported formats == Related bugs: * [[:bugzilla:17505]]: No High Dynamic Range Image (HDRI) file formats allowed on Commons * [[:bugzilla:15538]]: Problem uploading compressed Dia file * [[:bugzilla:4947]]: SVGZ (gzipped SVG) support * [[:bugzilla:3664]]: MetaPost scalable vector graphics support *: Not an upload format per se * [[:bugzilla:17858]]: Provide EPUB sanitizer * [[:bugzilla:17959]]: Inline rendering/thumbnailing for Gimp XCF images * [[:bugzilla:19153]]: Enable dng uploads on Commons * [[:bugzilla:20252]]: Support for WAV and AIFF by converting files to FLAC automatically. == File checks == Related bugs: * [[:bugzilla:10847]]: RAR concatenation in images * [[:bugzilla:18803]]: JPEG 2000 image files are not supported, but can be uploaded non-functionally with .jpg extension * [[:bugzilla:3675]]: PATCH: detect which mime types can be recognized reliably * [[:bugzilla:11142]]: blacklist extension handling is broken * [[:bugzilla:15874]]: Solution for permission to upload agains file type check * [[:bugzilla:18372]]: File upload error messages don't properly take $wgFileBlacklist into account * [[:bugzilla:18923]]: uploadcorrupt error message is vague and confusing * [[:bugzilla:7645]]: Validate SVG content == Internal file management == Related bugs: * [[:bugzilla:4421]]: Image file extension should not be part of the name ** http://www.mediawiki.org/w/index.php?title=Special:Code/MediaWiki/path&path=/branches/extensionless-files/ * [[:bugzilla:3829]]: Rework file uploads for better caching, mirroring * [[:bugzilla:9018]]: Temporary upload stash not cleared when uploads cancelled * [[:bugzilla:15430]] Uploads sometimes are incomplete: file is there, but image page is missing * [[:bugzilla:16751]]: Support multiple file uploads via Special:Upload (backend/infrastructure) * [[:bugzilla:20811]]: Blank submit page when uploading a djvu file on Commons or Wikipedia * [[:bugzilla:6481]]: Image upload does not appear in the upload log * [[:bugzilla:9248]]: Give MIME on links to image pages + Switch to disable image linking * [[:bugzilla:13196]]: Screen all previously-uploaded SVG files for invalid structure * [[:bugzilla:17560]]: Half-broken deletion moved image files to deletion archive without updating DB * [[:bugzilla:17577]]: Images can't have far future expires * [[:bugzilla:19751]]: Image undelete inadequately checks filesystem status before deleting archive info from DB (data loss) == Hashes == Related bugs: * [[:bugzilla:17057]]: Images with wrong SHA1 * [[:bugzilla:17070]]: Files with hash of an old version == Rendering == Related bugs: * [[:bugzilla:234]]: PNG thumbnails change binary transparency to alpha transparency, causing IE6 problems * [[:bugzilla:2888]]: Broken thumbnails not being generated * [[:bugzilla:9497]]: Thumbnails of large PNGs are not generated * [[:bugzilla:13493]]: Can't create thumbnail of images with a peculiar aspect ratio * [[:bugzilla:11045]]: Transparent PNGs resized with GD display with ugly background in IE 6 * [[:bugzilla:11822]]: rescaling of animated gif increase size * [[:bugzilla:13252]]: Resizing of Some GIFs Rendering Poorly; Setting Needs Changing? * [[:bugzilla:15488]]: Image thumbnail generator adding large amounts of artefacts * [[:bugzilla:16140]]: images are resized using incorrect color space * [[:bugzilla:16416]]: SVG rendering maximum should base on area, not largest size? * [[:bugzilla:16785]]: Switch in bicubic image scaling for client-side thumbnailing in Internet Explorer 7 * [[:bugzilla:18014]]: Thumbnailing produces much worse results for PNGs than JPG, but PNG is the only real option for serious restoration * [[:bugzilla:18127]]: Mediawiki accepts to create thumbnails with the wrong extension * [[:bugzilla:19960]]: Preserve color profile information for thumbs (ImageMagick update) == SVG rendering == * [[:bugzilla:8901]]: SVG rasterisation on Wikimedia sites (tracking) * [[:bugzilla:19224]]: SVG rendering: problems with paths beyond page extend * [[:bugzilla:3537]]: SVGs fail to render silently if they contain an <image /> element * [[:bugzilla:3593]]: SVG client side rendering * [[:bugzilla:5792]]: SVG→PNG and baseline-shift * [[:bugzilla:5933]]: Incorrect scaling of .svg->.png images * [[:bugzilla:7914]]: Strange behaviour with SVG figure * [[:bugzilla:8566]]: Thumbnail rendering of SVGs broken * [[:bugzilla:9832]]: SVG thumbnail is cropped when displayed at natural size * [[:bugzilla:10501]]: SVG: installed fonts not being rendered * [[:bugzilla:13387]]: SVG: Missing implementation for textLength * [[:bugzilla:13494]]: SVG font scaling bug ("%" and "em" misconverted to "px") * [[:bugzilla:13495]]: SVG text-decoration (including underlining) doesn't render * [[:bugzilla:16284]]: Support Linux Libertine Font for SVG rendering * [[:bugzilla:17187]]: SVG to PNG conversion broken for text * [[:bugzilla:17845]]: DejaVu Sans font renders incorrectly in SVG thumbnails * [[:bugzilla:18463]]: SVG thumbnailing issues - part of the image not rendered * [[:bugzilla:18900]]: probably bug in SVG→PNG rendering mechanism * [[:bugzilla:19053]]: Some arrows direction in SVG are wrongly rendered * [[:bugzilla:19224]]: SVG rendering: problems with paths beyond page extend * [[:bugzilla:19633]]: Scale up thumbnails of small SVG * ? [[:bugzilla:21474]]: Updating SVG with image of same optimal dimensions does not update png render * ? [[:bugzilla:16368]]: [SVG Rendering] Worsening of font rendering quality [[Category:Multimedia usability - Requirements definition]] gg02xwtcxvs780xierktf7muweasau8 0 874 5304 5302 2010-01-05T23:11:57Z Howief (WMF) 1286 wikitext text/x-wiki Here is a proposal for the Protection Controls (Flagged Revs plus current Protection levels). [[File:Protection controls ui proposal.pdf]] 6gadfp5ugn9ty0g5y7zue6btzp0vje4 6 875 5300 2010-01-05T23:10:02Z Howief (WMF) 1286 Protection Controls UI - Proposal wikitext text/x-wiki Protection Controls UI - Proposal 0v5lk9ax3dt303wpv2jfeu5sjnzs35s 100 879 8597 6324 2010-07-29T12:30:33Z Nemo bis 9 cat wikitext text/x-wiki {{draft}} {{internal}} There are several reasons why we want to develop metrics regarding multimedia content on/from Wikimedia websites: * We need data about users to design or improve the software, as part of the [[Multimedia:User research|User research]], or for ethnographic reasons. * We need data to facilitate communication / outreach / relationships with GLAMs. * We need data to measure the changes induced by the Multimedia Usability project, and more generally assess the impact of changes we try. Questions: * What do we need/want to measure, and why? ** Participation: How many people contribute multimedia content? How much? How often? How many people improve Commons (classification, description, etc.) ** Impact: How many people use and reuse our multimedia content? How much? How often? == Content == Ideally with evolution over time. We would need to record this on a regular basis, probably on the toolserver. === Inventory & temporal evolution === {| class="wikitable" |- ! Question !! Implementation !! Notes {{/line | question = How many files do we host on Commons? | implementation = | notes = Can be measured with countless tools, e.g. [http://toolserver.org/~magnus/glamorous.php?doit=1&category=Images+from+Picswiss&use_globalusage=1&ns0=1 here] or [http://toolserver.org/~magnus/catscan_rewrite.php?language=commons&project=wikimedia&categories=Images+from+Picswiss&ns%5B6%5D=1&ext_image_data=1&doit=1 here]. }} {{/line | question = How many files are uploaded on Commons each month? | implementation = | notes = [http://toolserver.org/~magnus/amalglamate.php Here] and [http://toolserver.org/~magnus/diaglam/ here] (experimental!). }} {{/line | question = How many files are uploaded to all Wikimedia projects each month? | implementation = | notes = }} {{/line | question = What are the topics covered by our content? (distribution) | implementation = Count files in the subcategories of [[:commons:Category:Topics|Category:Topics]] | notes = Breakdown of media files by super topical category, e.g. art, science etc. We may need to do some clean-up in the Category:Topics first though. }} {{/line | question = What are the media types of our content? (distribution) | implementation = | notes = E.g. medium: maps, technical drawings, animations, photos. This may be derived from . We could count files in the subcategories of [[:commons:Category:Media types|Category:Media types]] but it doesn't seem to be reliable. We also have historical data in [[:commons:Commons:MIME type statistics|Commons:MIME type statistics]]. We might have to wait until we actually record this somewhere (and extract/migrate existing data). }} {{/line | question = Where does our content come from ? (own work, etc.) (distribution) | implementation = | notes = Count files in the subcategories of [[:commons:Category:Pictures and images by source|Category:Pictures and images by source]]? Doesn't look reliable }} {{/line | question = What location does our content come from? (map) | implementation = Extract location information from geotagging templates on file pages & plot it | notes = See http://poulpy.blogspot.com/2010/02/elles-sont-ou-les-photos-de-commons.html }} {{/line | question = Under which licenses is our content released? (distribution) | implementation = Count files in the subcategories of [[:commons:Category:Copyright statuses|Category:Copyright statuses]], [[:commons:Category:Free licenses|Category:Free licenses]], [[:commons:Category:Creative Commons licenses|Category:Creative Commons licenses]] | notes = When we count in categories, we should probably automatically count separately subcategories that contain more than XX% files of the parent category. It would allow us to have a more accurate overview without having to manually decide which subcategories to count separately. }} {{/line | question = What is the size of our files? (distribution) | implementation = DB query | notes = }} {{/line | question = What upload medium was used? (distribution) | implementation = | notes = "Old" upload form, new upload form, API (bot, desktop applications, add-media-wizard, etc.). Needs schema change & minor change to the upload API. }} |} === Maintenance === {| class="wikitable" |- ! Question !! Implementation !! Notes {{/line | question = How many edits are performed on Commons? And in which namespace? | implementation = | notes = Broken down by namespace }} {{/line | question = How many edits are performed on all Wikimedia projects? Particularly, in the File namespace? | implementation = | notes = in order to be able to compare the evolution of Commons }} {{/line | question = How fast are files categorized on Commons? | implementation = | notes = [[:commons:User:Multichill/Categorization stats|User:Multichill/Categorization stats]] }} {{/line | question = How many files are deleted on Commons each month? | implementation = | notes = Similar to the [http://toolserver.org/~bryan/stats/commons_upload_deletion_ratio_monthly.png upload deletion ratio] but where deletions would be only those of files uploaded during that same period. }} {{/line | question = How long have files been online before they were deleted? | implementation = | notes = }} |} === Relevance (where is it shown) === How often do we serve images in their original huge size? Breakdown of image hosted/served by thumbnail size ==== Internal (Wikimedia projects) ==== {| class="wikitable" |- ! Question !! Implementation !! Notes {{/line | question = How are files from a specific category used across Wikimedia projects? | implementation = [http://toolserver.org/~magnus/glamorous.php?doit=1&category=Images+from+the+German+Federal+Archive&use_globalusage=1&ns0=1 glamorous] | notes = [[:mw:Extension:GlobalUsage|GlobalUsage]]-based }} {{/line | question = How are files from cultural partnerships used across Wikimedia projects? | implementation = [http://toolserver.org/~magnus/amalglamate.php AmalGLAMate] | notes = a GLAM-specific aggregation of images-in-category usage statistics }} |} See also: * Discussion about other [https://wiki.toolserver.org/view/GlobalUsage_weekly_stats GlobalUsage weekly stats]. ==== External (other sites) ==== {| class="wikitable" |- ! Question !! Implementation !! Notes {{/line | question = Can we track external use of content? | implementation = | notes = There is no reliable way to record usage from websites that use a local copy of files they found on Wikimedia Commons. As a consequence, we can only track usage from websites that fetch media files directly from Commons. }} {{/line | question = How many websites use Commons as file repository? | implementation = | notes = }} {{/line | question = How many files from Commons are used on Wikimedia websites? | implementation = | notes = }} {{/line | question = How many files from Commons are used on MediaWiki websites using [[:mw:InstantCommons|InstantCommons]]? | implementation = | notes = needs development to integrate InstantCommons with GlobalUsage }} {{/line | question = How many files from Commons are used on websites using other CMSes? | implementation = | notes = to be discussed when we actually find a way to extend InstantCommons to other CMSes. }} |} == Users == === Typology === We use a typology similar to the one already used on Wikistats & the report card: * active participants: 5+ edits per month ([http://stats.wikimedia.org/reportcard/#fragment-103 Report Card]) * very active participants: 100+ edits per month ([http://stats.wikimedia.org/reportcard/#fragment-103 Report Card]) === Participation === {| class="wikitable" |- ! Question !! Implementation !! Notes {{/line | question = How many new accounts are created at Commons each month? | implementation = | notes = with distinction between accounts created directly on Commons and SUL accounts created automatically }} {{/line | question = How often do uploads succeed? | implementation = Ratio upload screen requested / actual transfers | notes = }} {{/line | question = Who uploads files? | implementation = | notes = user: new, active, very active participants on Commons, also depending on whether they're new, active or very active on another Wikimedia project}} |} === Reach === {| class="wikitable" |- ! Question !! Implementation !! Notes {{/line | question = What is the language used by our viewers? (distribution) | implementation = | notes = [[:commons:User:Multichill/Browser language statistics|example]] }} {{/line | question = What is the location of our viewers? (map) | implementation = | notes = }} {{/line | question = How many viewers see a given image, and at what resolution? | implementation = | notes = image view statistics (image usage coupled to page views); see [[:mw:Hit stats aggregation]]. [http://lists.wikimedia.org/pipermail/wikitech-l/2010-January/046245.html Something in apparently in the works] with Domas & WMDE. }} |} * ideally, we would be able to break down results using all filters, e.g. for a given file, see how many people viewed it, from where, using what language * ideally, we would also be able to collect similar statistics for a set of files (e.g. inside a category). We can measure this only for Wikimedia websites == Resources == * [[Multimedia:Preliminary user research]] * [[Multimedia:Meeting in Paris/Notes/Metrics]] * [http://pchart.sourceforge.net pchart] * [[:commons:Category:Commons statistics|Commons statistics]] * [http://toolserver.org/~bryan/stats/ Bryan's stats] * http://www.wikistats.fr/ [[Category:Multimedia usability]] [[Category:Statistics]] kdu060s12zb9xyo1ppxqtmdkaxk6a47 0 880 5380 5379 2010-01-13T19:15:03Z 216.38.133.254 wikitext text/x-wiki Issues that need to be tackled in Citron before release == IFrame == * '''Major''' ** Text Selection - most context.fn.* functions need IE implementations ** Extra new line at the beginning of the content of the iframe in IE ** Random bugs and mysteries == Template Editing == * '''Major''' ** Editable folding ** 'Capsule' finalizing ** Cross-browser testing ** Folding of <nowiki><ref></nowiki> tags (optional, but probably easy) ** Use background image for clickable expand/collapse instead of image (IE lets you drag the button around) ** IE 8 in "broken" mode display issues ** infinite loops *'''Features''' ** nested collapsible templates == TOC == * '''Major''' ** Update section highlighting when cursor is moved ** Ellipsis is not updating on resize, and size calculations are off (margins aren't being calculated properly) ** Only working when main document scroll bar was at the top * '''Minor''' ** Pointer cursor seems to not stick, should be similar cursor behavior as the special characters and help booklet indexes have ** Needs to automatically size down and eventually hide when browser is being resized and toolbar has no more horizontal room (see below issue with toolbar expandable section wrapping) ** When resizing using right side of scrollbar, grab gets lost while cursor is over the scrollbar, maybe cover the scroll-bar with an invisible div to prevent the scrollbar from grabbing the cursor == Toolbar == * '''Minor''' ** Expandable section tabs must NEVER scale, or must wrap properly niexoqxd2u7uyvu0py73zzewr1fmw8v 100 881 9296 9278 2010-11-24T02:46:46Z 216.38.130.166 /* Messaging */ changes made in http://www.mediawiki.org/wiki/Special:Code/MediaWiki/77212 wikitext text/x-wiki {{internal}} The '''Upload wizard''' is the new upload interface developed for MediaWiki. * Extension page at MediaWiki.org: [[:mw:Extension:UploadWizard]] * Demo at http://commons.prototype.wikimedia.org/uwd/Special:UploadWizard (you must create an account) == Users == * Alice is a user who wants to upload a file. * Carol is the author of the work uploaded by Alice (in case Alice doesn't upload her own work). * Bob is an OTRS volunteer. == Prerequisites == * Alice has an account on the wiki and can upload. * Alice has one or several files to upload. == Workflow == [[File:Multimedia usability - Advanced upload workflow 01262010.JPG|thumb|Overall view of the proposed workflow]] '''Step 0''' * If this is the first time she tries to upload a file, the licensing tutorial is displayed. * (?) The tutorial is also shown to all users the first time they upload with the new upload interface. * (?) Watching the tutorial is mandatory in order to upload a file. * Once the tutorial is over, there's a "Don't show me next time" checkbox (default: checked). * (?) Free / unfree switch '''Step 1: File selection''' [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=1|Step 1]] * Alice selects the file to upload * (?) Only accepted file extensions can be chosen: accepted file formats or file formats that can be converted to accepted file formats. * (?) Alice can add up to 5 or 10 files to upload at the same time [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=2|Step 1 - Multiple files]] * When Alice starts to upload, she gets feedback on the advancement of the upload. [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=3|Step 1 - Feedback]] * The software performs checks in the background: ** checks if a file with the same filename exists; if so, renames automatically (ex. "DSC 4452" renamed to "DSC_4452_2"). ** checks if the file extension is ok; if not, automatically converts to an accepted format ** creates file hash (or fingerprint) and compares it to existing hashes. If it already exists, doesn't upload. Can only be overriden by people with "overwrite same hash" userright. ** extracts metadata: date, author, copyright, description... <br clear="all" /> '''Step 2: Please complete your uploads''' [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=4|Step 2]] * Information is displayed regarding the upload (e.g. file already exists, etc.). * Alice also sees a thumbnailed preview of her file and fields to fill in. Some are mandatory and some are optional. More options can be expanded. * If relevant information was extracted from metadata, the associated fields are pre-filled. * The license is selected at this point (see [[#License selection]]) * If all mandatory information has been provided, go to step 3a; if mandatory information is missing, go to step 3b <br clear="all" /> '''Step 3a: Thank you for sharing these works!''' [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=9|Step 3a]] * "You're done! Thank you" * You may now use this file, upload another file, add more info, explore your files, explore all/similar files * If it was Alice's first upload, send a welcome e-mail. <br clear="all" /> '''Step 3b: Your upload is incomplete''' [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=10|Step 3b]] * Mandatory information is missing. Files are changed to an "incomplete upload" state (e.g. template, or staging area). * Send an e-mail to Alice to remind her to provide the information. Send another reminder 1 day before the file is deleted. <br clear="all" /> == License selection == Three most common cases are displayed: * people uploading their own work * people uploading someone else's work with their explicit permission * files from a website === They are entirely your own work === [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=5|Own work]] * By default, a double license GFDL + CC-by-sa 3.0 is selected and explained in plain English. Users who want to choose other licenses can do so as well; in that case, the most common applicable licenses are displayed. It is also possible to display the full list of applicable licenses, sorted by type. Users can customize in their preferences their default license(s). * The name field is pre-filled with the user's username or their preferred credit name [[:mw:Manual:$wgAllowRealName|if they provided one]]. <br clear="all" /> === Their author gave you explicit permission to upload them === [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=6|Explicit permission from author]] * Files are in a "missing permission" state (template or built-in indicator) * Fields: author (Carol)'s name & e-mail address ("official"), uploader (Alice)'s name and e-mail address, license (selected by default), work(s) the permission is about * Sends a e-mail to Carol with a unique link to a confirmation page. The confirmation page displays the prepared permission and thumbnails of the pictures. Carol clicks to acknowledge the permission, which is sent to OTRS for human confirmation. The permission sent to OTRS contains a unique link to confirm the permission; this confirmation can only be performed by users in the "Permissions support" MediaWiki group (local or global). * When permission is sent to OTRS, files change to a "permission sent" state. * Bob checks the permission. If it is in order, he clicks the confirmation link and thanks Alice & Carol. The files are changed to a "permission confirmed" state including the reference (e.g. OTRS ticket #) automatically added. If the permission isn't correct, Bob gets back to Carol to sort things out. Comments: * What if the author doesn't have an e-mail address / if the permission is in a PDF etc.? * For permissions for multiple files: confirm them all at once if the permission is valid, or confirm them manually. <br clear="all" /> === They come from a website === [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=7|From a website]] [[File:Multimedia Usability - NewUpload Wireframe January 2010.pdf|thumb|page=8|From a website - Same info for all]] * By default, we assume that the files have different authors, sources and licenses, simply because at least the sources should be different (we prefer sources precise enough to be unique for each file). For this reason, * However, it is possible to display global fields that will apply to all files. * When a source URL is given, we check if it corresponds to a known source: flickr, panoramio, wikimedia wikis, etc. If available, we use the service API to retrieve as much relevant information as possible (author, license). <br clear="all" /> === More options === * Derivative work: should be handled on the original file's page. But what if the file is derived from several files? *: → yes, add it as an option in the upload form ''and'' a tool on a file description page. * PD-old *: → ? * Painting/museum? *: → ? * File moved from another Wikimedia project? should be handled by integrated interwiki file move, but this feature won't be available before Fall 2010. *: → yes, add a filter for Wikimedia websites in the "come from a website" section as a temporary measure * Fair use / non-free? shouldn't be needed since we'll have the licensing tutorial *: → no * Free software screenshot? Does this happen often enough to warrant a special case? *: → no == Notes == * '''[[/Tech notes|Tech notes]]''' * See also [[:mw:Extension:UploadWizard]] [[Category:Multimedia usability - Specifications|Upload wizard]] lo2w0o1apoiv6hnabie4qb06xggpn8q 14 883 5366 2010-01-12T18:43:07Z Guillom 13 [[Category:Multimedia usability]] wikitext text/x-wiki [[Category:Multimedia usability]] ah4y36oij9fcyo95gwbbnkrumkixhzv 6 884 5370 5369 2010-01-12T22:06:49Z Krinkle 709 uploaded a new version of &quot;[[File:ScreenshotKrinkle UnexpandedDropdown.png]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 100 889 9195 9194 2010-10-27T00:03:07Z Guillom 13 fix wikitext text/x-wiki {{internal}} We are currently looking for a Creative partner to help us produce an illustrated '''licensing tutorial''' to help our users understand the basics of copyright and free licenses. [[:commons:|Wikimedia Commons]] is a free repository of more than 7 million multimedia files that can be freely used, modified and distributed by anyone, for any purpose. Part of the documents are in the Public domain, while the others have been explicitly shared by their author under a "free license". As part of focused work to improve the user experience of the uploading process to Wikimedia Commons, we want to include a short tutorial to explain the basics of copyright and free works to new users, so that they understand what it entails to share their work on Wikimedia Commons, and what they can and can't do with other people's works. == Overview == === Context === Over the years, uploading a file to [[:w:Wikipedia|Wikipedia]] or [[:commons:Wikimedia Commons|Wikimedia Commons]] has grown increasingly difficult. An example is the [http://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=ownwork complicated upload form] presented to users who want to share their own pictures on Wikimedia Commons. The Wikimedia Foundation recently obtained a grant from the Ford Foundation. The subsequent [[Multimedia:About|Multimedia usability project]] funded by this grant aims to improve the usability of the upload process, in order to make it much easier for anyone to share their media files under a free license on Wikimedia Commons. One of the main issues we have identified with our current upload workflow is that it tries to give an advanced course in worldwide copyright at the same time the user uploads a file. In reality, our research shows (unsurprisingly) that most of the users either give up in front of the instruction creep, or simply ignore it. As a consequence, we have been working on a much simpler, [[Multimedia:Upload wizard|more straightforward upload form]] that would be mostly decoupled from the Licensing 101 course. However, we still need some basic tutorial to explain what a free work is, and what people can and can't upload. We have some basic requirements but remain open to discussion. === Audience === The primary audience for this tutorial is new users who are uploading their first media file to Wikipedia or Wikimedia Commons. Most of them are not familiar with free licenses and have never been educated about copyright. The tutorial will be shown by default to any new user when they first upload a file, regardless of their language, culture or country of origin. The tutorial will have a huge impact; it is both a tremendous opportunity to reach millions of people, and a huge responsibility. == Objectives == === Learning goals === The tutorial must explain the difference between unfree and freely reusable works. During the upload process, users will have to choose between the two options, depending on what kind of file they are uploading, so it is critical that they have a basic understanding of what copyright and free works are about. The tutorial will be a success if the user completes it and: * has a basic understanding of what copyright is * has a basic understanding of what it means to release a file under a free license * understands that any material is considered to be unfree unless explicitly said otherwise * is able to determine, for simple cases, to which of the two big families (unfree or free) a media file belongs. Examples of "simple cases" include: a CD cover, a picture taken by the user, a picture from a movie and a random picture found on the Internet. === Requirements === The tutorial must be: * '''short''': the basic tutorial is not a goal per se, but a necessary step for new users who want to upload a picture. Going through the tutorial shouldn't last more than a minute, max. 2. * '''easily translatable''': Wikimedia websites target an international audience, and Wikimedia Commons in particular is multilingual, as the central media repository for all other Wikimedia websites. * '''from an international, cross-cultural standpoint''': our audience is potentially anyone on the planet who has access to Internet, so we can't use cultural references that could be offensive or misunderstood by a specific subset of our audience. * '''fun, enticing''', not too boring: we want users to actually watch and complete the tutorial. * '''lightweight''': our audience is very broad and we want everyone to be able to watch the tutorial, regardless of their bandwidth. == Product == === Format === There have been several attempts in the past to create comic-like tutorials to explain basic topics about copyright and free licenses (see [[#Supporting information|Supporting information]]), but their format made it particularly difficult to watch online and translate. We think an animated or still comic-like format (that would be displayed in an overlay or inline) is the best way to meet our requirements. We usually prefer vector graphics for that kind of work, and our preferred format is SVG. [[:en:SVG animation|Animated SVGs]] are still in a prototype state, and not yet supported by MediaWiki, so a set of still SVGs would probably be the best way to go for now. We might want to avoid speech bubbles if they make localization more difficult (especially for "verbose" languages). The tutorial should remain stable and shouldn't require frequent updating. === Deliverables === * Duration of the partnership: Advice on overall approach & product * Phase 1: Three to four draft designs * Phase 2: A first proposed set of pictures (possibly presented as a storyboard) for the selected design * Phase 3: A final set of 8 to 10 Inkscape-compatible SVG pictures The final deliverables will be released under [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-sa license]. In-progress files will be privately shared with stakeholders, under the explicit condition that they don't publish or redistribute them. == Project == === Timeline === Specific schedule to be discussed. Steps: * Creative partner & WMF: Sign agreement * Creative partner & WMF: Hold [[Multimedia:Licensing tutorial/Kick-off meeting|kick-off meeting]]: agree on general overview, * Creative partner: delivers Phase 1 draft designs * WMF: shares Phase 1 designs with key stakeholders, provides [[Multimedia:Licensing tutorial/Phase 1 feedback|phase 1 feedback]] and selects a Phase 1 design * Creative partner: delivers Phase 2 proposed set of pictures * WMF: shares Phase 2 designs with key stakeholders and provides [[Multimedia:Licensing tutorial/Phase 2 feedback|phase 2 feedback]] * Creative partner: delivers Phase 3 (final) set of pictures The tutorial will be included in our new Upload wizard when it is released in October 2010. A large communication campaign aiming at encouraging people to add media files to Wikipedia and Wikimedia Commons will be organized, and the tutorial will be prominently featured. === WMF to provide === * links to relevant documentation about copyright and free licenses * expertise about copyright, free licenses and the tutorial's general context * main topics to be included * feedback and decision based on draft designs, and communication with stakeholders * feedback on storyboard / first set of pictures === Extended scope === Depending on funding and the success of this partnership, we might consider to later extend this partnership to create a whole set of tutorials to popularize copyright-related topics that are common on Wikimedia Commons and Wikipedia. Such topics include: * What is a derivative work, and under what terms can one build on someone else's work? ** Related topic: Works made by multiple authors * What is freedom of panorama? * What is public domain? * Why allow commercial reuse? * What is fair use? The requirements for these additional tutorials would be similar to those of the main tutorial, apart from their length; they could be longer, given that the user could actually be interested in watching the tutorial and learning about these topics (as opposed to the basic tutorial where the user just wants to upload a media file). They should use a common theme (e.g. for instance the same characters / visual theme). == Supporting information == * '''[[Multimedia:Licensing tutorial/Main points|Main points to be covered]]''' * [[Multimedia:Licensing tutorial/Kick-off meeting]] * ''[[:w:en:Copyright|Copyright]]'' and ''[[:w:en:Free content|Free content]]'', on Wikipedia * ''[[:commons:Commons:Licensing|Licensing]]'' page on Wikimedia Commons * [[:File:BD-propagande-2 (en).jpg|Example of past comic-like tutorial: Why allow commercial reuse?]] * [[:File:BD-propagande colour en.jpg|Another example: Why use Creative Commons instead of GFDL only?]] * ''[http://questioncopyright.org/understanding_free_content Understanding free content]'' on questioncopyright.org * ''[http://wiki.creativecommons.org/Sharing_Creative_Works Sharing Creative Works]'', by Creative Commons [[Category:Licensing tutorial|*]] l8bqee97urirzliq17m3eway7fjv0dr 6 890 5415 2010-01-17T10:51:17Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 891 5416 2010-01-17T10:51:34Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 892 5417 2010-01-17T10:51:51Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 893 5418 2010-01-17T10:52:17Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 894 5419 2010-01-17T11:01:38Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 895 8908 8907 2010-09-18T11:27:12Z Hoo man 2104 Reverted edits by [[Special:Contributions/190.134.29.23|190.134.29.23]] ([[User talk:190.134.29.23|talk]]) to last revision by [[User:Notafish|Notafish]] wikitext text/x-wiki Please use the [[Talk:Opinion_Left_Navigation|discussion page]] to post comments! ==Integrating the Book creation tool== ===As its own menu-section=== <gallery> File: 1_printexport_closed.jpg | closed File: 1_printexport_open.jpg | open </gallery> ===Integrated in the Toolbox section=== <gallery> File: 2_printexport_closed.jpg | closed File: 2_printexport_open.jpg | open File: 3_printexport_open.jpg | Alternate Version </gallery> j06y85x48jpbkmhru0ogpy2ysdks6m8 6 896 5427 2010-01-19T02:09:45Z Shuhari 4 Presentation slides which were presented to Stanton Foundation on December 15, 2009 wikitext text/x-wiki Presentation slides which were presented to Stanton Foundation on December 15, 2009 ad11yw60ungpinzsjcw9331d7rw579t 6 900 5447 5445 2010-01-20T21:17:45Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:100120 vacuuming 06.jpg]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 901 5452 2010-01-20T22:23:32Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 902 5455 5454 2010-01-20T22:30:47Z Parul Vora~usabilitywiki 185 uploaded a new version of &quot;[[File:LeftNav lines.jpg]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 903 5457 2010-01-20T22:37:18Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 10 907 8651 5506 2010-07-29T13:30:39Z Nemo bis 9 cat wikitext text/x-wiki <span style="color:green">{{{1}}}</span><noinclude> [[Category:Templates]]</noinclude> 40dke2yjcqmmrlvhw1zozz9ev8cq9qo 100 912 8714 5857 2010-08-06T20:19:50Z Guillom 13 moved [[Multimedia:UX study, March 2010/CfP]] to [[Multimedia:UX study, June 2010/CfP]]: delayed wikitext text/x-wiki '''The call for proposals is now closed.''' Thank you for your interest. ---- The '''[[Multimedia:About|Wikimedia Multimedia Usability Project]]''' is a special project of the Wikimedia Foundation, the non-profit that supports Wikipedia. It is realized thanks to a grant from the Ford Foundation and aims to improve the interfaces and workflows for multimedia uploading on Wikimedia websites. == Context == Over the years, uploading a file to [[:w:Wikipedia|Wikipedia]] or [[:commons:Wikimedia Commons|Wikimedia Commons]] has grown increasingly difficult. Users are now presented with a ridiculously verbose and complicated upload form, as a consequence of both implementation-driven design and limited capabilities of the software. The Wikimedia Foundation recently obtained a grant from the Ford Foundation to specifically address this issue. The subsequent 1-year [[Multimedia:About|Multimedia usability project]] funded by this grant aims to improve the usability of the upload process, in order to make it much easier for anyone to share their media files under a free license on Wikimedia Commons. == User research plan == Based on a preliminary assessment, we chose a 3-step research plan: # A '''preliminary user research''' phase in the very early stages of the project (October - December 2009). It consisted of ethnographic interviews of users, discussions with stakeholders and subject matter experts, online survey and free forum open to users. The main goals were to observe and understand why and how users use the product, as well as identify or confirm critical issues that users encounter during its use. # A first '''formal usability/UX study''' six months later (early March 2010). Participants will be confronted with two interfaces: the initial interface as it was before any improvement, and a prototype interface developed in the meantime, based on the preliminary research. The goals of this (both formative and summative) study are: formally recording the issues identified by the preliminary study as a reference for progress and checking that the preliminary changes are a step in the right direction. # A last '''formal usability/UX study''' at the end of the project (October / November 2010), possibly with a reduced number of participants. This study will be mostly summative and will aim to measure progress and improvements using the first study as reference. It will also be used to identify remaining issues. The [[:Multimedia:Hub#Research|preliminary user research phase]] is now over. We are currently working on the second step: the first formal usability / user experience study. We will consider proposals that bundle the two formal studies, as well as individual proposals for the first formal study. == Purpose == One of the major changes we are going to introduce is a complete redesign of the upload interface to make it simpler and more straightforward. Instead of presenting the user with a complicated set of paths and dozen fields to fill in before actually uploading, we want to provide a simpler, context-aware interface consistent with the user's mental model. The goal of the UX study is twofold: * Record the current user experience, as it is without any change, in order to: ** have a reference to compare to at the end of the project ** formally confirm the main issues identified by the preliminary user research ** discover previously uncovered issues * Record the user experience with the new interface to check we're going in the right direction, and identify possible new interaction issues. For that purpose, we want to test both the current and the prototype interface. == Scenario == Basically, we will record the experience of users who want to upload a picture to Wikimedia Commons. The picture might be their own work, but we would also like to study cases that are less clear-cut, in order to avoid research bias. We will favor proposals that offer creative ways to test various cases, based on the design of [[multimedia:newUpload|our proposed new workflow]]. == Specifications == We are looking for UX and Usability firms, researchers, and enthusiasts to help us to evaluate the changes we have made to the existing software and identify issues that have remained hidden. Generally we are looking to: * recruit appropriate users * have about 10 participants. We will consider in-person and remote interviews. Given the multilingual nature of Wikimedia Commons, we will also consider interviews of users who don't speak English. * conduct interviews of tasks and open ended questions with video and audio of the participant, moderator, and computer screen. * analyze and synthesize all of the information from the interviews * share video highlights and the full interview audio + video with our community online, under a [[:w:free license|free license]]. A lot of additional documentation about our research & work is available from our [[Multimedia:Hub|hub for multimedia usability]]. == Apply == If you or your company is available to help, please e-mail gpaumier[[File:At sign.svg|15px|replace this]]wikimedia.org. Let us know how you can help or with a proposal and we will get back to you. Thanks! DEADLINE: February 10th, 2009 [[Category:Multimedia usability - Research]] nr9u2h2xwf2uuv497e442hh75aljlam 0 918 5633 5632 2010-02-02T22:49:01Z Howief (WMF) 1286 wikitext text/x-wiki This page has been redirected to [[Beta Feedback Survey|here]]. ofqcuntuaj20p3tspfzy2wmfba931g7 6 919 5574 5570 2010-01-28T23:30:00Z Howief (WMF) 1286 uploaded a new version of &quot;[[File:Beta retention year end.jpg]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 100 920 8722 8721 2010-08-06T21:44:56Z Guillom 13 +info wikitext text/x-wiki [[File:Multimedia UX study June 2010 final report.pdf|thumb|Full project report]] In June 2010, the Wikimedia Foundation conducted a User experience study as part of the [[Multimedia:Hub|Multimedia usability project]] to assess the current upload form on Commons and to check the direction chosen for a new upload wizard was sensible. For more information on the study, you may take a look at the original [[Multimedia:UX study, June 2010/CfP|Call for proposals]] and a [http://www.gpaumier.org/blog/691_wikimedia-multimedia-ux-testing-videos/ recap of the study]. The full study report is available as a PDF document (see opposite). The summary videos highlighting the main findings of the study are presented below (sound must be enabled). <br clear="all" /> == Current interface testing video == [[File:Multimedia usability project 2010 - Current interface testing.ogv|thumb|center|800px|Current interface testing]] == Prototype testing video == [[File:Multimedia usability project 2010 - Prototype testing.ogv|thumb|center|800px|Prototype testing]] == Room for improvement video == [[File:Multimedia usability project 2010 - Room for improvement.ogv|thumb|center|800px|Room for improvement]] [[Category:Multimedia usability - Research|UX study, June 2010]] 5fivuxtr0jnt9yb5xwp26nxpp193zct 6 921 5575 2010-01-28T23:30:51Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 922 5589 2010-01-29T23:42:04Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 923 5590 2010-01-29T23:43:06Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 924 5591 2010-01-29T23:43:27Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 925 5592 2010-01-29T23:43:52Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 926 5593 2010-01-29T23:44:13Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 929 5616 2010-02-01T19:40:28Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 932 9368 5651 2011-08-22T12:19:09Z Ruslik0 224 fixing dr wikitext text/x-wiki #redirect [[Style Guide]] bhaaiqlkbr839jjhx1uwb01w7slfr8s 0 934 8913 5990 2010-09-19T18:35:21Z 94.221.217.108 ortho wikitext text/x-wiki {{Internal}} __NOTOC__ ==Tabbed navigation== ===Organization=== The concept of the Vector tabbed navigation is to separate views or ''types'' of pages from ''actions'' to be performed on those pages. Some of these actions can be performed on the article and discussion page independently (e.g. Edit, View History) and some actions can be applied to both pages (e.g. Watch). The most used tabs site-wide are always visible, others are placed in a drop-down menu. If you are adding a new page, please maintain this functional separation. If it is a page type, it should be grouped with the tabs on the left. If it is an action that is performed on the page, it should be grouped with the tabs on the right. Please maintain an appropriate hierarchy within the "page type" and "page action" categories. * Illustrations needed **Image of tabs highlighting types Vs. actions **Example of added tabs (language variant, admin tools) <br /> === Background Color === The background color of the tabs plays an important role in their function. Vector uses separate colors for "active" tabs and "inactive tabs". The background of the content area should match the background color of an active tab (in Vector HEX VALUE). This way, the active tab is grouped with the content area. Additionally, the inactive tabs should be a significantly different color to reinforce this activity. Breaking these conventions would break the tab/folder metaphor. We additionally do not recommend adding any extra lines or other things that visually disconnect the active tab from the content area or removing lines that visually connect inactive tabs from the content area. * Illustrations needed ** tab, content area ** good example, bad example (that polish one that adopted our stuff) ===Text Labels=== The text labels are displayed in "Arial", 12px, regular. We recommend to keep this typeface. If you want to change it you should choose a legible and simple typeface. We recommend to use the same typeface as used in other navigation elements (left navigation, ntoc, toolbar). Please note that the tabbed navigation is the main navigation element of a wiki. For this reason it should be prominent, easy to access and the text labels should be displayed in a propper, legible size. ==== Text Label Colors ==== The text labels basically behave just like normal links: * blue text = link to existing page * red text = link to not existing page (only occurs for "discussion") * black text = active We use regular font weight. If you decide to change this, we recommend to keep that value on all status. For example: A switch from regular to bold as a mouse over effect evokes resizement of the tab, which looks like a "jump effect". This should be avoided. === Interaction === As a mouse over effect we use underlinement of text labels. This corresponds to commonly used link behaviour and supports good user interaction. We recommend not to use a change of background color or font weight (using bold as mouse over effect). Underlinement as mouse over effect may be turned off, though we encourage to keep it. ==The Toolbar== The basic idea of the toolbar is a limited, preselected row of the most important icons according to the data we collected with a clicktracking survey. If you change this row, we highly recommend not to display more than 7 icons, to maintain easy, comprehensible interaction. The expanded toolbar, as you get it when you click on "advanced", is the right place to add extra icons. ===Icons=== ====Text format icons==== In an effort to be comprehensible in many languages, the toolbar uses the letter "A" for character formatting icons as the default value. However we support the use of language specific icons (for example, "B" for Bold and "I" for Italic in English and "F" for Fettdruck and "K" for Kursiv in German). The set of textformatting icons can be found on [http://commons.wikimedia.org/wiki/Vector_edit_toolbar this page] on Wikimedia Commons. If you use a language wiki that does not have language-specific icons already on Commons, and have basic knowledge of Inkscape + Gimp or Adobe Illustrator + Photoshop, we welcome your contributions. We have created this [[Text format icons| "How To"]] guide to walk you through the steps to create these icons and get them on Wikimedia Commons. ====Toolbar icons==== If you want to add any icons to the toolbar we recommend to keep the icon style, which adopted the GNOME Icon Style. We created another [[Toolbar icons| "How To" Page]] to help you creating appropriate icons. Feel free to add new icons for the toolbar to this [[Additionally Vector Toolbar Icons]] or leave a comment on the discussion page. == Article Page Content Area == === Color === ===usage of lines, boxes=== === Headings === ===typefaces=== ===innern tabs=== === Thumbnails === 220px now. phasing out 180px. == Edit Page Content Area == == Left Navigation == ===structure and organization=== ===color=== ===usage of lines, boxes=== == Logo == === Localization === k4vhszj8ke8kxqpr1iflm1tsmvjo5rc 0 935 5653 2010-02-03T21:23:52Z Juxn~usabilitywiki 176 moved [[Style Guidelines]] to [[Style Guide]]: naming issues wikitext text/x-wiki #REDIRECT [[Style Guide]] gwckoma8rqa3bhvgvjm4j5evcdetb0a 100 936 9351 9344 2011-01-05T01:37:41Z 216.38.130.166 added difficulty wikitext text/x-wiki <div align="center"> {| class="wikitable sortable" |- ! Name !! Category !! Description !! Priority !! Difficulty !! Design !! Development !! Release !! Notes {{Multimedia:Specifications/line | name = [[Multimedia:Upload wizard|Upload wizard]] | category = [[Multimedia:Upload|Upload]] | description = A new upload interface & workflow to replace Special:Upload | priority = 1 - high | difficulty = 1 - high | design = [[user:guillom|Guillaume Paumier]] | development = [[:mw:user:NeilK|Neil Kandalgaonkar]] | release = | notes = [[Multimedia:Upload wizard/Tech notes|Tech notes]] · [[Multimedia:Upload wizard#Messaging|Messaging]] · [[Multimedia:Upload wizard/Questions & Answers|Q & A]] }} {{Multimedia:Specifications/line | name = [[Multimedia:Licensing tutorial|Licensing tutorial]] | category = [[Multimedia:Upload|Upload]] | description = A basic, high-level tutorial about copyright and free licenses | priority = 1 - high | difficulty = 3 - medium | design = [[user:guillom|Guillaume Paumier]] | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Flows|Workflows]] | category = [[Multimedia:Maintenance|Maintenance]] | description = A generic workflow/ticketing system for issues, tasks & processes | priority = 2 - medium | difficulty = 1 - high | design = [[user:guillom|Guillaume Paumier]] | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:"Report an issue" wizard|"Report an issue" wizard]] | category = [[Multimedia:Maintenance|Maintenance]] | description = A wizard to help users report issues efficiently and to direct them to the appropriate venue | priority = 2 - medium | difficulty = 3 - low | design = [[user:guillom|Guillaume Paumier]] | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:MediaWiki Dashboard|MediaWiki Dashboard]] | category = [[Multimedia:Maintenance|Maintenance]] | description = A personal dashboard that allows users to aggregate more interesting information feeds and facilitates internal communication | priority = 2 - medium | difficulty = 2 - medium | design = [[user:guillom|Guillaume Paumier]] | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Interface cleanup|Interface cleanup]] | category = [[Multimedia:Using and reusing content|Using and reusing content]] | description = Clean-up of the asset description page & user interface | priority = 2 - medium | difficulty = 3 - low | design = [[user:guillom|Guillaume Paumier]] | development = [[:mw:user:NeilK|Neil Kandalgaonkar]] | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Interwiki upload|Interwiki upload]] | category = [[Multimedia:Crosswiki integration|Crosswiki integration]] | description = Ability to upload to Commons from any Wikimedia wiki | priority = 2 - medium | difficulty = 2 - medium | design = [[user:guillom|Guillaume Paumier]] | development = [[:mw:user:NeilK|Neil Kandalgaonkar]] | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Multilingual search|Multilingual search]] | category = [[Multimedia:Multilingual support|Multilingual support]] | description = Ability to search media in languages other than English | priority = 2 - medium | difficulty = ?? | design = | development = [[:mw:user:Duesentrieb|Daniel Kinzler]] | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Multiple upload|Multiple upload]] | category = [[Multimedia:Upload|Upload]] | description = Ability to upload multiple files at once | priority = 2 - medium | difficulty = 2 - medium | design = [[user:guillom|Guillaume Paumier]] | development = [[:mw:user:NeilK|Neil Kandalgaonkar]] | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Drag'n'drop upload|Drag'n'drop upload]] | category = [[Multimedia:Upload|Upload]] | description = Ability to catch file drag'n'drop events and tie it to the upload process | priority = 3 - low | difficulty = 2 - medium | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Category suggestion|Category suggestion]] | category = [[Multimedia:Maintenance|Maintenance]] | description = Suggestion of categories based on description | priority = 1 - high | difficulty = 1 - high | design = | development = | release = | notes = I seriously question the usefulness of this feature -- NeilK }} {{Multimedia:Specifications/line | name = [[Multimedia:Patrol files|Patrol files]] | category = [[Multimedia:Maintenance|Maintenance]] | description = Tools & workflow to help patrol & review recently uploaded files | priority = 2 - medium | difficulty = 2 - medium | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Location editor|Location editor]] | category = [[Multimedia:Editing|Editing]] | description = Ability to specify (or remove) geotag using an OpenStreetMap widget | priority = 3 - low | difficulty = 3 - low | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Picture annotation|Picture annotation]] | category = [[Multimedia:Editing|Editing]] | description = Ability to annotate pictures | priority = 3 - low | difficulty = 3 - low | design = | development = | release = | notes = Isn't this already done? }} {{Multimedia:Specifications/line | name = [[Multimedia:Basic image editing|Basic image editing]] | category = [[Multimedia:Editing|Editing]] | description = Ability to rotate & crop pictures | priority = 2 - medium | difficulty = 2 - medium | design = | development = | release = | notes = not so hard to do in code, just need to set up server to do it in production }} {{Multimedia:Specifications/line | name = [[Multimedia:Structured data|Structured data]] | category = [[Multimedia:Maintenance|Maintenance]] | description = | priority = 1 - high | difficulty = 1 - high | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Filtered search|Filtered search]] | category = [[Multimedia:Using and reusing content|Using and reusing content]] | description = Ability to use search filters based on categories or structured data | priority = 2 - medium | difficulty = 1 - high | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:IPTC support|IPTC support]] | category = [[Multimedia:Back-end|Back-end]] | description = Ability to extract IPTC metadata | priority = 2 - medium | difficulty = 2 - medium | design = | development = [[:n:user:bawolff|Brian Wolff]] | release = | notes = [http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/wikimedia/t127230774186 GSoC] }} {{Multimedia:Specifications/line | name = [[Multimedia:XMP support|XMP support]] | category = [[Multimedia:Back-end|Back-end]] | description = Ability to extract XMP metadata | priority = 2 - medium | difficulty = 2 - medium | design = | development = [[:n:user:bawolff|Brian Wolff]] | release = | notes = [http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/wikimedia/t127230774186 GSoC] }} {{Multimedia:Specifications/line | name = [[Multimedia:User gallery|User gallery]] | category = [[Multimedia:Navigation|Navigation]] | description = Special gallery page for users | priority = 3 - low | difficulty = 3 - low | design = | development = | release = | notes = exists already as extension? }} {{Multimedia:Specifications/line | name = [[Multimedia:Slideshow|Slideshow]] | category = [[Multimedia:Navigation|Navigation]] | description = Ability to watch a slideshow of pictures in a category or a list | priority = 3 - low | difficulty = 3 - low | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Tags / category intersect / flattening|Tags / category intersect / flattening]] | category = [[Multimedia:Navigation|Navigation]] | description = | priority = 1 - high | difficulty = 1 - high | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Push metadata|Push metadata]] | category = [[Multimedia:Using and reusing content|Using and reusing content]] | description = Ability to save page metadata to files | priority = 2 - medium | difficulty = 2 - medium | design = | development = | release = | notes = I question the utility here -- NeilK }} {{Multimedia:Specifications/line | name = [[Multimedia:Queriable metadata|Queriable metadata]] | category = [[Multimedia:Using and reusing content|Using and reusing content]] | description = Ability to query asset metadata from the API | priority = 2 - medium | difficulty = 2 - medium | design = | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:File fingerprint|File fingerprint]] | category = [[Multimedia:Back-end|Back-end]] | description = Feature to calculate fingerprints of files to allow fuzzy search | priority = 3 - low | difficulty = 1 - high | design = | development = | release = | notes = unsolved problems in AI should probably not be on our agenda -- NeilK }} {{Multimedia:Specifications/line | name = [[Multimedia:Upload from third-party desktop applications|Upload from third-party desktop applications]] | category = [[Multimedia:Upload|Upload]] | description = Plugins to upload from desktop applications | priority = 3 - low | difficulty = 1 - high | design = [[user:guillom|Guillaume Paumier]] | development = [[user:guillom|Guillaume Paumier]] (digiKam) | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:Batch asset metadata editing|Batch asset metadata editing]] | category = [[Multimedia:Maintenance|Maintenance]] | description = Ability to make batch modifications of descriptions, categories, etc. | priority = 3 - low | difficulty = 1 - high | design = [[user:guillom|Guillaume Paumier]] | development = | release = }} {{Multimedia:Specifications/line | name = [[Multimedia:User preferences for upload|User preferences for upload]] | category = [[Multimedia:Upload|Upload]] | description = Interface to specify default licenses, user template, categories etc. in user preferences | priority = 2 - medium | difficulty = 3 - low | design = [[user:guillom|Guillaume Paumier]] | development = [[:mw:user:NeilK|Neil Kandalgaonkar]] | release = }} |} </div> [[Category:Multimedia usability - Specifications]] onc4gccs2cr6a2joor4ue4frvn4tuln 6 937 5661 2010-02-04T18:56:56Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 938 5662 2010-02-04T18:58:05Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 939 5665 2010-02-04T19:06:16Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 100 942 5693 2010-02-05T23:39:37Z Guillom 13 |- | {{{question}}} || {{{implementation}}} || {{{notes}}} wikitext text/x-wiki |- | {{{question}}} || {{{implementation}}} || {{{notes}}} thm3kvoyagbfodllpazeeq3g9l5cvdd 100 946 6522 5784 2010-04-09T16:21:58Z Guillom 13 redirect wikitext text/x-wiki #REDIRECT [[Multimedia:Flows]] et6syf7u0kjylcw6qow3vjx8dbyckn9 100 947 9350 9349 2011-01-05T01:27:08Z 216.38.130.166 wikitext text/x-wiki |- | {{{name}}} || {{{category}}} || {{{description}}} || {{{priority}}} || {{{difficulty|}}} || {{{design}}} || {{{development}}} || {{{release}}} || {{{notes|}}} qe4mn930n49h2qzisrqoebht4agopja 100 948 5751 2010-02-09T18:52:00Z Guillom 13 moved [[Multimedia:Uploading]] to [[Multimedia:Upload]]: hop wikitext text/x-wiki #REDIRECT [[Multimedia:Upload]] gpt6e9mr414jj0mzfeiygbmzg70msvl 0 951 5824 5822 2010-02-12T19:32:00Z Juxn~usabilitywiki 176 /* Icons */ wikitext text/x-wiki {{Internal}} This is a tutorial on how to create icons for our toolbar. Take a look at icons that have already been created before you start to create one yourself. When you have succeeded to create a new icon please contribute it to [http://commons.wikimedia.org/wiki/Vector_toolbar Wikimedia Commons].<br /> Textformatting icons are treated seperatly, read how to create Texformatting icons [[Text format icons| here]]. ==Icons== [[File:Toolbaricon_strike.png|Strike]]<br /> [[File:Toolbaricon_quote.png|Insert block quote]]<br /> [[File:Toolbaricon_hiddencomment.png|Insert hidden comment]]<br /> [[File:Toolbaricon_lock.png|Read only mode]]<br /> [[Toolbar icons Wishlist| Wishlist]] ==Style== The vector toolbar icons make use of the free [http://commons.wikimedia.org/wiki/GNOME_Desktop_icons GNOME Desktop Icons]. Any of these icons can easily be turned into an icon for our toolbar by following the guidelines: [[#Turning GNOME Icons into a vector icon| Turning GNOME Icons into a vector icon]]. If you need to create a new icon, which is not in the GNOME Icon-set, please follow the [http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Tango Icon Style Guide Lines]. ===Turning GNOME Icons into a vector icon=== If you want to use a GNOME Icon in the vector toolbar you have to do some graphical adjustments. Please follow these steps: * Download the icon of your choice from [http://commons.wikimedia.org/wiki/GNOME_Desktop_icons| Wikimedia Commons] as a 200px PNG file. * Open the file in a programm like Adobe Photoshop or Gimp. * Delete all shadows (that the icon-object casts on the virtual platform). * Crop the file to be excactly as hight and wide as the icon is (no white space around it). * Change the image size to be not more than 20px high and wide. The perfect size may be a bit smaller than 20px, this depends on the characteristics of the specific icon. Make sure "Constrain Proportions" and "Resample Image" are checked. Choose "Bicubic (sharper)". * Often it is necessary to add dark outlines. Depending in the complexity of the logo there are many ways to do that. If you have a simple icon you can do it as follows: :*Duplicate the Layer :*Turn layer Opacity to 0% :*Open the layer properties (right click on the Layer) :*Add a 1px innern stroke, with black and 20% Opacity. (You can vary with the opacity until you get a nice looking result). *Go to "Canvas Size" (not "Image Size"!) and edit the size to be 22*22px. *Save this file as a png(-24). Please note the Namings Guide Lines and upload your Icon to [http://commons.wikimedia.org Wikimedia Commons]. ==Specifications== *size *file *color ==Recommendations== {| class="wikitable" |- ! Do !! Don't t |- | aprox. 1px thick lines|| thiner, thicker lines |- | visible icon-elements|| thin, small icon-elements |- | metaphors, anologies to real life|| abstract icons |- | intuitivly understandable|| insider |} ==Naming Guide Lines== Please upload your Icon to [http://commons.wikimedia.org/wiki/Vector_edit_toolbar Wikimedia Commons] and name your file like this:<br /> "toolbaricon_" + description of the icon + fileformat (".png")<br /> Please describe what the icon symbolizes rather than what function it represents. '''Example''': For the lock icon, which can be used to switch to a readonly mode, the file would be named:<br /> "''toolbaricon_lock.png''" fbycwptgw6s4ll2546jjo53o9e09qf2 6 952 5792 2010-02-11T10:18:11Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 953 5793 2010-02-11T10:18:21Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 954 5794 2010-02-11T10:18:29Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 955 9129 9128 2010-10-25T13:05:40Z 75.81.147.30 wikitext text/x-wiki This page represents a wishlist of toolbar icons for the new vector toolbar. Feel free to add your favorite icons and drop a comment on the discussion page. ==Formatting Bundle== [[File:Button hr.png]] horizontal line [[File:Toolbaricon_strike.png|Strike]] [[File:Button strike.png]] strike [[File:Button underline.png]] underline [[File:Toolbaricon_quote.png|Insert block quote]] [[File:Button_blockquote.png]] blockquote [[File:Ref-button-bg.png]] reference footer *appendices sections [[File:Button_Anführung.png]] German Anführungsstriche (German quotation marks) [[File:Button center.png]] centered paragraph [[File:Button definition list.png]] definition list [[File:Button nbsp.png]] non-breaking space [[File:Button pre.png]] Pre formatted text [[File:Button code.png]] Insert Code ==Math Bundle== [[File:Button math.png]] math ==Wiki Bundle== [[File:Toolbaricon_hiddencomment.png|Insert hidden comment]] [[File:Button comment.png]] hidden comment [[File:Toolbaricon_lock.png|Read only mode]] locked, read only [[File:Button category plus.png]] [[File:Button category03.png]] [[File:Button category link.png]] [[File:Button category.png]] add category [[File:Button_P_template.png]] [[File:Button template.gif]] [[File:Button templatelink.png]] insert template [[File:Button copy vio plagio.png]] Copyright [[File:Button see also.png]] See also [[File:Button sub link.png]] Link to a sub page ==common use template== [http://commons.wikimedia.org/wiki/MediaWiki_edit_toolbar/commonusetemplate Common use template] from Wikimedia Commons: ===Standpoint=== [[File:Button support.png]] support<br /> [[File:Button partial support.png]] partial support<br /> [[File:Button oppose.png]] oppose<br /> [[File:Button neutral.png]] neutral<br /> [[File:Button delete.png]] delete<br /> [[File:Button keep.png]] keep<br /> [[File:Button comment vote.png]] comment vote<br /> [[File:Button opinion.png]] opinion<br /> [[File:Button question2.png]] question 2<br /> [[File:Button wait.png]] wait<br /> [[File:Button comment.png]] comment<br /> [[File:Button check.png]] check<br /> [[File:Button fait.png]] fait<br /> [[File:Button question.png]] question 1<br /> [[File:Button aviso.png]] aviso<br /> [[File:Button aviso borrado.png]] aviso burrado<br /> [[File:Button done.png]] done<br /> [[File:Button not done.png]] not done<br /> ===Warn and Ban=== [[File:Deletewarn1.png]] delete warn 1 [[File:Deletewarn2.png]] delete warn 2 [[File:Deletewarn3.png]] delete warn 3 [[File:Deletewarn4.png]] delete warn 4 [[File:Spam1.png]] Spam 1 [[File:Spam2.png]] Spam 2 [[File:Spam3.png]] Spam 3 [[File:Spam4.png]] Spam 4 [[File:Testwarn1.png]] testwarn 1 [[File:Testwarn2.png]] testwarn 2 [[File:Testwarn3.png]] testwarn 3 [[File:Testwarn4.png]] testwarn 4 [[File:Warn1.png]] warn 1 [[File:Warn2.png]] warn 2 [[File:Warn3.png]] warn 3 [[File:Warn4.png]] warn 4 [[File:Warncreate1.png]] warncreate 1 [[File:Warncreate2.png]] warncreate 2 [[File:Warncreate3.png]] warncreate 3 [[File:Warncreate4.png]] warncreate 4 d4u79hb06zwcfgtfk1y6l6wfko21143 0 956 9318 9316 2010-12-16T13:31:50Z 68.51.63.60 /* Modifying things */ adopted changes from "working" example to reduce warning wikitext text/x-wiki If you're just here to get some quick code that you can copypaste into your user JS and will just work out of the box, see the [[/Library|customizations library]]. The rest of this article explains the technical details of customizing the toolbar and requires a basic level of understanding of JavaScript. == Configuration structure == The toolbar widget is defined by a [http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/WikiEditor/modules/jquery.wikiEditor.js?view=markup configuration object]. You can look at the configuration for the [http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/WikiEditor/modules/ext.wikiEditor.toolbar.js?view=markup default toolbar] to see how you can modify the toolbar. Complete documentation is to be written shortly. You can modify the toolbar even after it's been built by calling the <code>.wikiEditor()</code> function on the textarea. You will need to do this inside an <code>$(document).ready(function() {});</code> call, though. == Adding things == <source lang="JavaScript"> // Check that the toolbar is available if ( typeof $j != 'undefined' && typeof $j.fn.wikiEditor != 'undefined' ) { // Execute on load $j( function() { // General format: // $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { configuration object here } ); // To add a toolbar section: $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'sections': { 'emoticons': { 'type': 'toolbar', // Can also be 'booklet' 'label': 'Emoticons' // or 'labelMsg': 'section-emoticons-label' for a localized label } } } ); // To add a group to an existing toolbar section: $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'emoticons', 'groups': { 'faces': { 'label': 'Faces' // or use labelMsg for a localized label, see above } } } ); // To add a button to an existing toolbar group: $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'emoticons', 'group': 'faces', 'tools': { 'smile': { label: 'Smile!', // or use labelMsg for a localized label, see above type: 'button', icon: 'http://upload.wikimedia.org/wikipedia/commons/thumb/a/a4/Gnome-face-smile.svg/22px-Gnome-face-smile.svg.png', action: { type: 'encapsulate', options: { pre: ":)" // text to be inserted } } } } } ); // To add a booklet section: $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'sections': { 'info': { 'type': 'booklet', 'label': 'Info' } } } ); // To add a page to an existing booklet section $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'info', 'pages': { 'colors': { 'layout': 'table', 'label': 'Colors', 'headings': [ { text: 'Name' }, // or use textMsg for localization, see also above { text: 'Temperature' }, { text: 'Swatch' } ], 'rows': [ { 'name': { text: 'Red' }, 'temp': { text: 'Warm' }, 'swatch': { html: '<div style="width:10px;height:10px;background-color:red;">' } }, { 'name': { text: 'Blue' }, 'temp': { text: 'Cold' }, 'swatch': { html: '<div style="width:10px;height:10px;background-color:blue;">' } }, { 'name': { text: 'Silver' }, 'temp': { text: 'Neutral' }, 'swatch': { html: '<div style="width:10px;height:10px;background-color:silver;">' } } ] } } } ); // To add a special characters page $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'info', 'pages': { 'emoticons': { 'layout': 'characters', 'label': 'Emoticons', 'characters': [ ':)', ':))', ':(', '<3', ';)' ] } } } ); } ); } </source> === Existing sections === The default WikiEditor toolbar has the following sections: *The ''main'' section which is always visible, with the groups ''format'' and ''insert''. *The ''advanced'' section, with the groups ''heading'', ''format'', ''size'', ''insert'' and ''search''. *The ''characters'' section, with pages ''latin'', ''latinextended'', ''ipa'', ''symbols'', ''greek'', ''cyrillic'', ''arabic'', ''hebrew'', ''bangla'', ''telugu'', ''sinhala'' and ''gujarati'' *The ''help'' section, with pages ''format'', ''link'', ''heading'', ''list'', ''file'', ''reference'' and ''discussion''. == Removing things == TODO == Modifying things == <div style="border:1px solid red; padding:5px"> '''Warning''': Binding doesn't seem to work with <code>$j()</code> but does work if called with addOnloadHook. A working example could be found at the bottom of [http://ru.wikipedia.org/w/index.php?title=MediaWiki:ToolbarNew.js&oldid=25331363 ru:MediaWiki:ToolbarNew.js] </div> We don't really have a nice API to modify things, unfortunately. The best we have is a hook to change the configuration of a section just before it's being built: <source lang="JavaScript"> // Check that jQuery is defined if ( typeof $j != 'undefined' ) { $j( function() { $j( '#wpTextbox1' ).bind( 'wikiEditor-toolbar-buildSection-sectionname', function( event, section ) { // Do stuff with section } ); } ); } </source> === Example: adding localized icons === <source lang="JavaScript"> // Check that jQuery is available if ( typeof $j != 'undefined' ) { $j( function() { $j( '#wpTextbox1' ).bind( 'wikiEditor-toolbar-buildSection-main', function( event, section ) { // Add icons for bold (F) and italic (L) for Swedish (sv) // Don't overwrite them if they're already defined, so this hack can safely be removed once the // usability team incorporates these icons in the software if ( !( 'sv' in section.groups.format.tools.bold.icon ) ) { // There's already a bold F icon for German, use that one section.groups.format.tools.bold.icon['sv'] = 'format-bold-F.png'; section.groups.format.tools.bold.offset['sv'] = [2, -214]; } if ( !( 'sv' in section.groups.format.tools.italic.icon ) ) { // Use an icon from Commons for L section.groups.format.tools.italic.icon['sv'] = 'http://upload.wikimedia.org/wikipedia/commons/3/32/Toolbaricon_italic_L.png'; section.groups.format.tools.italic.offset['sv'] = [2, -214]; } } ); } ); } </source> kh695pfktf3c2qviwejy20vteyib1vf 6 961 5823 2010-02-12T19:30:52Z Juxn~usabilitywiki 176 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 966 5865 2010-02-16T19:35:12Z Trevor Parscal (WMF) 3 moved [[Babaco Designs/Icon Localization]] to [[Text format icons]]: Don't want it here anymore. wikitext text/x-wiki #REDIRECT [[Text format icons]] rq1yziw74rep2932lbce047jbudtsw4 6 968 5871 2010-02-17T01:04:31Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 969 5872 2010-02-17T01:04:52Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 970 9295 9294 2010-11-23T22:27:06Z JanPaul123 2199 Undo revision 9294 by [[Special:Contributions/67.159.44.51|67.159.44.51]] ([[User talk:67.159.44.51|talk]]) wikitext text/x-wiki ''Related usability studies:'' [[Usability and Experience Study|March 2009]], [[Usability, Experience, and Progress Study|September 2009]] == Methodology == In March 2010, the Wikimedia Foundation Stanton Usability Team partnered with [http://www.gotomedia.com gotomedia] to conduct a third and final evaluative study of the Wikipedia editing experience. This consisted of ten one-on-one in-person interviews and eight remote interviews. Sessions began with a brief interview about participants’ computer use in general, and their past experience with Wikipedia. In this usability testing, participants from a representative sample of website users were observed as they performed a set of predetermined tasks from a script. The 75-minute sessions were led and moderated by an experienced Usability Specialist. Throughout the session, the UX Specialist asked additional questions to clarify and expand on participant responses. This process helped to create an understanding of how users interact with the website and illuminates potential usability problems. The primary research goals were to: * evaluate the progress/improvements made by the stanton team in reducing the obstacles that novice users encounter in editing a Wikipedia article, including—but not limited to—adding personal content, fixing a typo, adding a reference, formatting content, and creating an article. * evaluate the new prototype interaction with templates * evaluate the effects of template collapsing. === Target audience === Participants were chosen based on the segmentation agreed on by gotomedia and Wikipedia, focusing on Wikipedia users who had limited or no editing experience. {| class="wikitable" style="text-align:center;" |- ! Participant No. ! Has not edited, but is willing to ! Has not edited, doesn't see themselves editing ! Has made < 25 contributions ! Male ! Female ! Under 18 ! 19&ndash;34 ! 35&ndash;54 ! 55+ ! Uses WP everyday ! Uses WP > Once a week ! Uses WP Once every few weeks |- | 01 || X || X || X || X || X || X || X || X || X || X || X || X |- | 02 || X || X || X || X || X || X || X || X || X || X || X || X |- | 03 || X || X || X || X || X || X || X || X || X || X || X || X |- | 04 || X || X || X || X || X || X || X || X || X || X || X || X |- | 05 || X || X || X || X || X || X || X || X || X || X || X || X |- | 06 || X || X || X || X || X || X || X || X || X || X || X || X |- | 07 || X || X || X || X || X || X || X || X || X || X || X || X |- | 08 || X || X || X || X || X || X || X || X || X || X || X || X |- | 09 || X || X || X || X || X || X || X || X || X || X || X || X |- | 10 || X || X || X || X || X || X || X || X || X || X || X || X |} === Recruiting === As in past studies, we recruited over 2,000 San Francisco residents for the in person testing and over 1,000 US residents for the remote testing. A banner/alert was placed and displayed at the top of every 1 in 100 Wikipedia pages for the duration of 3 days. When users viewed our message by clicking, they were forwarded to ethnio recruiting system where we asked them a series of questions. Specifically, users were asked about what they were doing on Wikipedia, how often they used Wikipedia, if they had ever contributed to Wikipedia (and in what manner), their age, gender, location, and availability. Based on these criteria, the 3,000+ users who responded to our survey were filtered down to 500 viable subjects based on their answers to these questions. The team and gotomedia worked with Fleischman Field Research to contact, filter, and schedule these participants based on a further phone conversation covering their Wikipedia usage patterns, reasons for not contributing, talkative and o === Study Participants === ==== Remote Testing ==== {| class="wikitable" |- ! Participant No. ! Age ! Gender ! Wikipedia Editing History ! Wikipedia Usage ! Occupation |- | 01 "Phil" | 22 | Male | Has not contributed, but is willing to. | Every day | Freelance writer |- | 02 "Keith" | 41 | Male | Has not contributed, but is willing to. | Every day | Technician |- | 03 "Bianca" | 22 | Female | Has not contributed, but is willing to. | Every day | Intern |- | 04 "Adam" | 21 | Male | Has not contributed, but is willing to. | Every day | Student |- | 05 "Charles" | 46 | Male | Yes. Fewer than 25 edits. | More than once a week | Court Clerk |- | 06 "Nicholas" | 31 | Male | Has contributed. 1 article. | Every day | Account Manager |- | 07 "Meghan" | 19 | Female | Has contributed once. | Every day | Homemaker |- | 08 "Lisa" | 52 | Female | Has edited. ~10 contributions | Every day | Homemaker |} === Scripting === The moderator script was drafted by the Wikipedia Usability Team and gotomedia, based on [[Moderator Script | the script originally developed and used last year]]. An almost identical script was used for the lab subjects and the remote subjects, the discrepancies being entirely related to the difference in set up. The script aimed to see how users would attempt to and feel about a collection of tasks or objectives that first time and early Wikipedians frequently encounter in their editing process including, but not limited to: * Finding and using the various modes of editing ("edit this page" vs. section edits) * Adding personal content or information to an existing article * Looking at Discussion Pages * Adding comment/thread to a discussion page. * Adding or using content from an external source (website, paper, etc) * Adding a reference to content * Adding an external link to a list or section of links * Editing an article that uses a template * Editing an infobox through wikisyntax and pop ups * Formatting content (Headers, bold, italics, linking, tables) * Creating a table and new article * Fixing a typo <br> Though the script was generally task based, the questions were open ended and left room for interpretation, encouraging subjects to not try to complete the tasks in any "correct" way, but rather to go about them naturally, if they had felt the motivation to do so on their own. Open-ended interview questions including "How did you find that process?" regularly follow every "task". The script was piloted on one staff member of gotomedia, a reader (but not editor) of Wikipedia prior to any official testing. * View the actual Moderator Script [[Moderator Script III | here]]. === Lab Interviews === === Remote Interviews === == Summary of Results (by gotomedia) == === Overview === As a part of the Wikipedia Usability Initiative, the Wikimedia Foundation asked gotomedia to conduct a series of usability tests to evaluate progress toward the Initiative’s overall goal of “measurably increase(ing) the usability of Wikipedia for new contributors.” In previous rounds of testing, Wikipedia and Bolt | Peters uncovered and documented many usability issues that exist in Wikipedia generally, and in the editing process specifically. Our research reaffirmed these previously documented issues such as: * People love Wikipedia. Wikipedia is extremely popular with users. All of the participants we spoke to use the site at least several times a week, and many use it several times a day. * People don’t think they have anything to add. Nearly everyone we interviewed reported that they are reticent to add to Wikipedia because they are not confident in the quality or validity of their own potential contribution. *Wikitext is easy ...and hard. Users are able to make simple text changes to a Wikipedia article with relative ease, but more advanced editing tasks such as creating links, footnotes, and tables proved to be more challenging. * Users learn by example. When confronted with a task that they did not immediately understand, most users looked for examples in the Wikitext and attempted to mimic what other editors had done. * Users are not able to create a new article. Only one of our participants was able to figure out how to start a new article on Wikipedia. These issues are well documented. We did not find anything in our research that significantly contradicts any of the findings of the previous studies. We will focus our comments on more specific editing issues, new functionality that was introduced since the previous tests were conducted, and additional observations not previously documented. === General Editing Issues === Wikitext presents significant barriers to editing. The best way to really open up the editing process to all users would be to hide Wikitext from users altogether. Wikipedia participation will only be truly open to everyone when a true WYSIWYG interface can be developed. There are many technical, cultural, and financial reasons why a true WYSIWYG interface probably won’t be implemented at Wikipedia any time soon, and there are legitimate arguments about whether or not making editing that easy would ultimately be good for Wikipedia. However, if the goal is to truly open up editing to all users, a true WYSIWYG interface would be the best way to accomplish that goal.<br /> <span style="color: gray;">“I am not a technical person so I have no idea (how to do this).” -Carrie, 32, Account Manager</span><br/> <span style="color: gray;">“...seems like that would be so much easier than dealing with code. The way it’s doing it now, it seems to be keeping some people out. It seems exclusionary.” – Phil, 22, Freelance Writer<br /></span> <span style="color: gray;">“I know my mother couldn’t use this!” – Oliver, 48, Business Analyst<br /></span> New editors need more help. Several users expressed a desire for a short video or tutorial that would give them a basic understanding of the editing process. Many users were observed looking for help in the left hand column of the page, and those that did so expected to find edit-specific information under the Toolbox menu in that left column. <span style="color: gray;">“Some of the things aren’t actually intuitive. So either they could make it more obvious for a novice or lay people, or make a tutorial. (And) make that tutorial really, really obvious for when features are just rolled out.” – Bianca, 22, Intern<br /></span> <span style="color: gray;">“I think they should highlight the Help and how to contribute. It should be super obvious on the front page. I had no idea and had never tried, but I think if it were more obvious (how easy editing is) then more people like myself would.” – Adam, 21, Student<br /></span> <span style="color: gray;">“I would likely look at a video. I know Google does that for their suite of apps...” – Clayton, 22, Tutor<br /></span> === Editing Toolbar === The editing toolbar definitely represents an improvement for editors over the tools previously available to them, and the changes made to the toolbar since the previous rounds of testing do appear to facilitate easier editing. Toolbar visibility was improved over the previous design. Some participants still overlooked the toolbar, but most users did eventually find the toolbar on their own. '''Internal links confused many users'''. In the first round of testing by Bolt | Peters, Internal Links and External Links were accomplished using two different tools in the Toolbar. In that scenario, users tended to find one of the link tools, and ignore the other. So in the second round of testing by Bolt | Peters, the two tools were collapsed into a single link tool, and users were expected to choose an Internal vs. External link by selecting a tab at the top of the overlay. But in this scenario, users tended to overlook the tabs. So in this third round of testing by gotomedia, the Internal and External tabs were eliminated, and the overlay would automatically determine which kind of link the user wanted to make, based on what they entered into the “Target page or URL:” field. This was an elegant solution, but still confused many users. Many participants assumed that they would need to enter the full URL of the Wikipedia page they wanted to link to. So they would open a new tab or window, navigate to the target Wikipedia page, copy the URL, and paste it into the Target page or URL field in the overlay. The overlay would then treat the link as external, inserting the full URL into the Wikitext, resulting in a working internal link that displayed as an external link. That is the functionality that in-person participants encountered, but this functionality was changed before the remote interviews were conducted. If remote participants entered a full URL at Wikipedia.org, they were shown a second overlay that said, “The URL you specified looks like it was intended as a link to another wiki page. Do you want to make it an internal link?” With this dialog implemented, participants did end up with the correct link format in their edits. The progression of the Link tool over the course of the usability initiative has grown more and more successful, but there is still some room for improvement. '''The Reference tool''' proved very challenging. None of the participants recognized the tool as “Reference” unless they discovered the mouseover tooltip. Two participants mentioned that they would have expected that icon to mean “bookmark.” When users found the Reference tool and tried to use it to add a citation, they universally failed to accomplish the task correctly. If they highlighted text in the article before clicking the Reference tool, then they were surprised to find that the text “disappeared” from the article when they previewed or published their edits. Few users ever found the text where it had been relocated in the References section of the page. When participants attempted to add a reference without using the Reference tool, they were similarly perplexed by the process. Many users expected to add their reference directly to the References section of the article. So they would use the inline “edit’ link for the References section, and then be completely lost when they found only the {{Reflist}} tag there and none of the actual references they expected to see. Even when users found the Reference entry in Help and tried to mimic it, they still were not sure what information should go where, or how their references would appear on the page.<br /> <span style="color: gray;">“That picture does not look like a reference picture to me at all.” – Rob, 30, Student<br /></span> <span style="color: gray;">“If you clicked reference and a box showed up, like a popup, that let you put in the title and URL of your reference, that seems to me like it would be so much easier than trying to deal with code.” - Phil, 22, Freelance Writer <br /></span> There seemed to be a general confusion about the expected function for the reference tool and the linking tools. For the latter, highlighting is proper. For the former, it is not. Yet, users tended to conflate these two processes together. While these two processes are not, strictly speaking, connected with each other, users do seem to see them as somewhat analogous when it comes to highlighting. Therefore, some exploration should be done to consider how these two processes can be better aligned. '''The term “Advanced”''' scared some users away. The Advanced label intimidated some users. Those that were already feeling overwhelmed by the editing tasks said that they were already in over their heads, and did not want to add anything that was “advanced.” In previous testing, participants expressed that they were overwhelmed by the large number of tools in the toolbar. The Advanced section was implemented to hide the less-often used tools until they were needed. This was a good direction to take, but the labeling should be reconsidered. <span style="color: gray;">“Advanced should be called something different like formatting because advanced scares people.” – Caroline, 25, Project Manager <br /></span> '''Help is indeed helpful''', but could be expanded. Users appreciated the presence of the Help ‘cheat sheet’ embedded in the editing interface. The embedded placement represents a significant improvement over previous designs in which users had to interrupt their editing tasks to go find the cheat sheet on their own. However, the cheat sheet does not include the new tools in the toolbar. Several users went to the Help section to investigate how to make a reference for example, but the cheat sheet does not direct them to use the Reference tool.<br /> <span style="color: gray;">(Clayton was asked to add a Reference) “I am trying to find a help button. (He opens Help module.) I like this and I can look at it and edit at the same time. I like it a lot. ...I am trying to add this reference. I don’t know what “test” in quotations means. I guess this is the link outside, ...additional text...and reference. I would just try it.” (Then after struggling with the Wikitext for several minutes): ...Oh I guess I overlooked this. (He finds the Reference button.)” – Clayton, 22, Tutor<br /></span> Participants did not understand the '''Embedded File tool'''. Participants were not asked to complete a task using the Embedded File tool, but several of them commented on the tool. Nearly all users who commented on the tool said that they expected the tool to insert a picture. But the mouseover tooltip “Embedded File” confused them. If they clicked the tool, then they found that the markup that was inserted included “.jpg”. This confirmed their first thought that the tool was for inserting a picture, but left them wondering why the tooltip didn’t simply say “Insert Picture.” The Insert Picture Gallery tool added to the confusion. Both icons were read as “Insert Picture”, but users did not understand why there would be two tools, and why the tooltips were different. <span style="color: gray;">“This embedded file is not well-named. Should be embedded photo because I don’t know the difference between photos and files.” – Caroline, 25, Project Manager<br /></span> === Navigable Table of Contents === Participants universally liked the [[Navigable Table of Contents]] (NTOC). Not all participants noticed the NTOC without prompting, but once they did, they seemed to understand it quickly. Some did not experiment with clicking the NTOC. Those that did understood its function immediately. <span style="color: gray;">“The table of contents is also very helpful because this is a very long article. The table of contents is helpful, a nice little map.” – Caroline, 25, Project Manager<br /></span> <span style="color: gray;">“The right hand navigational part... It makes sense and it’s a lot more useful than what Wikipedia usually has.” – Bianca, 22, Intern<br /></span> Participants were pleasantly surprised to see a new section appear in the NTOC immediately. Users were asked to create a new section in an article. Many users stumbled a bit on this task. Some assumed that they would need to edit the TOC directly, and so began looking for an inline ‘edit’ link for the TOC. Others looked for a tool to help them create a new section. But once participants began examining the Wikitext, most found the existing headings and were successfully able to mimic them. Once they did, nearly all of them were surprised to see the new section appear immediately in the NTOC. Participants found this immediate feedback to be very reassuring. This is perhaps the only example in the editing interface where users get instant confirmation that their edits are being made successfully.<br /> <span style="color: gray;">“It’s nice that the headlines are automatic. That they automatically create a table of contents.” – Caroline, 25, Project Manager<br /></span> === Preview === The Preview state needs clear visual cues. Participants often confused the Preview state with the Read state. Users would make an edit in Wikitext, click Preview to confirm the edit, and then forget that they were in Edit mode. They would click links in the article and not understand why the links did not work, or they would click an inline ‘edit’ link to try to make another edit and find that the edit link simply did not respond. Particularly for new editors, this could lead to a feeling that they had broken the page or done something wrong.<br /> <span style="color: gray;">“I didn’t like the fact that when I was on a Read page that it just didn’t look any different from the Edit page.” – Tram, 30, Student<br /></span> Some users were reluctant to use Preview. Some participants went immediately to Publish rather than to Preview after making an edit in Wikitext. In most cases they simply did not notice the Preview option. But in some cases participants continued to use Publish rather than Preview, even after Preview was pointed out to them. This may have been due to the special circumstances of the testing setting. During testing, participants were encouraged not to worry too much about the accuracy of their edits, so that we could concentrate on the editing process. This may have led participants to be more comfortable with publishing than they would have been in a natural editing scenario.<br /> <span style="color: gray;">“I usually just publish it and make changes after. I’m usually scared of losing my edits even in Word Press. It’s really easy to navigate out of page and it rarely saves itself. I usually publish first.” – Bianca, 22, Intern<br /></span> <span style="color: gray;">“Preview: I didn’t see it at first, probably because I wasn’t looking for it. ...you automatically want to go with pushing the (Publish) button next. So maybe moving the Preview over here (near Publish on the right side).” – Caroline, 25, Project Manager<br /></span> Link behavior in Previewmode needs more attention. Currently, most links do not work in Preview mode. Links to References do work when the full article is being edited. These same reference links do not work when a single section of an article is being edited. Study participants frequently tried to use links in Preview mode. One commonly observed scenario proceeded this way: # Use the Edit tab to display Wikitext for an entire page # Make an edit # Click the Preview tab # Scroll down to find and confirm the edit # Realize that the edit was incorrect or that another edit was needed. # Click the inline ‘edit’ link to correct the edit # Nothing happens. The inline ‘edit’ link doesn’t work and the user does not understand why. If the Preview pane is to remain within the primary editing window, then a consistent, predictable behavior must be developed to handle links within Preview mode. That behavior could be enabling all links, enabling certain kinds of links, or disabling all links. For any links that are disabled, users should receive clear consistent feedback about why the link does not work as expected. If a user clicks a link that is disabled, a dialog should instruct the user, “You are previewing this article. Links do not work in Preview mode. Return to the full article to enable links.“ Our recommendation is that at least some kinds of links should work in Preview, including newly-added links, links to references, and inline ‘edit’ links. Inline ‘edit’ links provide a more immediate way for the editor to correct their edits. If for some reason inline ‘edit’ links cannot be enabled in Preview, then they should be hidden in Preview mode. Preview behavior should be consistent. The behavior of the Preview tab at the top of the page differed from the behavior of the Show Preview button at the bottom of the page. The Preview tab would replace the Wikitext pane with the Preview pane, while the Show Preview button would display the Preview pane above the Wikitext pane. If a user used one method to access Preview mode and then used the other, they were frequently confused by this inconsistent behavior. === Publish === Users do not understand the meaning of “Minor edit.” During the publishing process, editors are presented with the option to check a box indicating that their edit is a “Minor edit”. Nearly all participants checked this box, assuming that because the changes that they had made were relatively small, that they would be classified as “minor.” In fact, Wikipedia would have classified the majority of edits made during the study as ‘major’.<br /> <span style="color: gray;">“I’ve never figured out what minor edit means. I usually click on it since all my edits are small so I would assume that’s what it is.” – Bianca, 22, Intern<br /></span> Links in the Publish overlay are not recognizable. When users click the Publish button, this overlay displays: Many participants mentioned that they did not understand all of the items mentioned in this overlay, particularly the license information. But none of our participants discovered that this overlay contains links that lead to more information. None of the links on this overlay display as such. === Infobox Editing === Several users expressed an affinity for the infobox. They look to the infobox for relevant statistics and “hard information.” They appreciate the immediacy of the infobox and the way that it “surfaces” important information for easy access. When participants were asked to edit information in the infobox, many expressed surprise or even doubt that the information there was editable. Some believed that the information in infoboxes was automatically populated from external sources, and/or that there would be additional barriers to editing this content. Users expressed more confidence in the accuracy of content in the infobox, as compared to content in the main article.<br /> <span style="color: gray;">“In the past couple of years they have added this right hand window with key facts and I love it. It’s very easy. It’s easy to get all the key info on the right.” – Caroline, 25, Project Manager<br /></span> Users had a hard time figuring out how to edit the Infobox. When prompted to edit information in the infobox, most users looked for a corresponding inline ‘edit’ link. They often clicked an inline ‘edit’ link that happened to display near the infobox. When that did not work, they then used the Edit tab to display Wikitext for the full page, and looked for something that would correspond to the infobox in the NTOC. Very few participants recognized the infobox settlement template capsule as the place to edit the infobox without prompting. (More on the template capsule below). Participants also struggled to name the infobox. When looking for a way to edit it, they didn’t know what the infobox was called, and so didn’t know exactly what they were looking for. “The infobox could be named something else. I don’t know, but I can’t think of another clever name. But it’s not obvious that’s what this is. I’d say “the side bar” maybe. ...I don’t know.” – Caroline, 25, Project Manger<br /> <span style="color: gray;">“Well there are lots of these little things (templates). So it just looked like everything else here. Its because of the name. We don’t know what to call it.” – Oliver, 48, Business Analyst<br /></span> === Template Capsules === Templates were introduced to the editing interface in an effort to further hide markup, and increase the readability of Wikitext. They are largely successful in that effort, but the design and implementation of the template capsules need refinement to improve understanding of their use and function. Some users couldn’t see past the triangle. Template capsules offered two primary means of editing the markup they represent. Editors could expand the capsule to show the full markup by clicking the triangle icon on the left of the capsule, or they could click the capsule title to open up an editing wizard. About half of our participants clicked the arrow first, and assumed that was the only way they could interact with the capsule. They had to be prompted to click elsewhere on the capsule to discover the wizard. The opposite was also true. There was, however, no correlation between the function discovered and the user’s comfortableness with editing Wikitext directly. Therefore, a code-anxious user may click the expand arrow, and be stuck, or a code-friendly user might pop the overlay, and be frustrated. So, rather than providing options to two types of users, the UI has the potential of confounding both while serving neither. Given that the test participants were inexperienced editors, we found that once these participants had seen both the wizard and the direct Wikitext for the infobox, they universally preferred using the wizard overlay to make edits. <span style="color: gray;">“It’s not clear that this is a pop down for easy editing vs. a drop down for wiki(text) editing” – Caroline, 25, Project Manager</span> Blue text in capsules indicated to some users that they were external links. Half of the participants in the study were shown template capsules with black text, and half were shown template capsules with blue underlined text. Some of the participants who saw blue text assumed that the blue text indicated a regular hyperlink. They were therefore reluctant to click the capsule for fear of being taken away from the editing task at hand. On the other hand, with black text on the gray background, there is some concern that the capsules blend in to the code too much and do not invite editors to explore them.<br /> <span style="color: gray;">“OK. It scared me for a sec that it looks like they were going to hyperlink. Usually when they are blue and underlined... but no, they just go down.” – Bianca, 22, Intern<br /></span> <span style="color: gray;">“You can tell its going to link you to somewhere else because we saw that the links are like that, and the references are like that, so we know that you’re going somewhere else...” – Sara, 21, Student<br /></span> The wizard icon on template capsules had no meaning to users. None of the users who mentioned the icon had any idea what it might signify. Recommendations: Consider dropping the icon in favor of the word “edit”. The word “edit” will invite editors to click, and will do a better job of conveying the outcome of a click. “Edit” should be displayed in a different style than the title of the template (a different color, font and/or weight) to help distinguish it from the title and increase “clickability.” Text in templates needs to be searchable. When participants were asked to edit the population of a city displayed in the infobox, one of the primary strategies they employed to find the correct place to edit was to use Firefox’s Find function to search for the word “population”. But unless template capsules were expanded, then the word population did not appear on the page , and so was not found in the search. This completely flummoxed participants. They knew that the word “population” must be present in the Wikitext because they could see it in the Read version of the page, and yet Find couldn’t find it. === Future Work === Overall, we found that the Wikipedia Usability Initiative was successful in the endeavors we tackled to improve the editing process. Namely, the cleaner skin and tabbed navigation made for simpler and faster navigation; the simpler and more graphic toolbar offers more intuitive controls to enter wikitext than the old toolbar; the dialogs proved valuable in generating wikitext; the navigable table of contents both helps people navigate large articles and provides a snippet of real time updates; the integrated help proviced quick and easy access to common tasks (and avoided verbose help pages and navigation to another page); and templates improve the readability of wikitext. From where we started, we have improved the ease of the editing process, however it is still somewhat beyond the reach of an "average user" and there is still much to be done. The first of our work will include iterating on the features that didn't fully solve the problems we were trying to address. '''Templates''': As mentioned above, template "capsules" proved very effective and hiding the complex wiki syntax, providing easier access to an article's body content. However, the interaction to access this template syntax needs to be improved. The "pop up" mode was universally preferred for new users, and though we did not test with advanced users, we know through feedback that they still require direct access to this code. We will be working on a solution that hides this wiki syntax while still providing access to the breadth of users that needs to edit it. '''Preview and Publish''': Users interactions illustrate the need for side-by-side or in page preview. The preview tab that we added worked well, but users struggled to differentiate between the editing and previewing states. We additionally need to refine the flow to not cause the confusion mentioned above to bring users to save their content. '''Navigable Table of Contents''': The navigable table of contents, as a feature, proved its value in our study and is ready for deployment. However, more QA and browser/os compatibility work needs to be completed before this can happen. As we move forward, we will also continue to bring the Wikipedia/Mediawiki editor closer to the publishing tools (read: rich text editing tools) that users expect. Additionally, we will also begin to look at the broader user experience and many of the issues we surfaced last March that we could not address in the editing experience alone. In carrying out this work, we have developed and improved the organizational processes, testing, and tools as well as the volunteer community involvement necessary to forge ahead. == Video Highlights == * [http://commons.wikimedia.org/wiki/File:WIK-P_EditingTools.ogv Editing Tools] * [http://commons.wikimedia.org/wiki/File:WIK-P_Impressions.ogv Progress Impressions] * [http://commons.wikimedia.org/wiki/File:WIK-P_WorkToDo.ogv Still More Work Ahead] == Notes == * The team's rough notes from the interviews are [[Usability, Experience, and Evaluation Study/Notes|here]]. * gotomedia's Notes [[Category:Usability studies]] bmuphfjjg39v8x4y5292l986i396nzr 0 971 5876 2010-02-17T19:26:04Z Juxn~usabilitywiki 176 moved [[Toolbar icons Wishlist]] to [[Additionally Vector Toolbar Icons]] wikitext text/x-wiki #REDIRECT [[Additionally Vector Toolbar Icons]] phhs5iwj9gbftjveolr60sfateotmxe 6 973 5881 2010-02-18T00:38:30Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 0 974 5892 5891 2010-02-18T19:18:34Z Howief (WMF) 1286 wikitext text/x-wiki Please follow these 4 steps to turn off the Beta Features '''1. Log into your account''' '''2. Click on the "My Preferences" link in the upper right corner:''' [[File: My_preferences.jpg | 600px]] '''3. Under "Experimental Features", uncheck all of the following:''' * Enable navigable table of contents * Enable enhanced editing toolbar * Enable dialogs for inserting links, tables, and more [[File: Experimental_Features.jpg | 600px]] '''4. Click "Save"''' 4dg85ad214nks2en38orxzohodacwl3 6 975 5889 2010-02-18T19:15:14Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 976 5890 2010-02-18T19:16:08Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 978 5926 2010-02-23T19:22:55Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 982 5946 2010-03-02T00:29:44Z Howief (WMF) 1286 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 983 5952 5949 2010-03-02T00:55:48Z Howief (WMF) 1286 uploaded a new version of &quot;[[File:Beta february 2010 incremental.jpg]]&quot; wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 988 5996 2010-03-05T13:35:48Z Clytie 1072 Screenshot (tab drawer not included) of Omniweb 5.10.2 showing the editing window in the Beta. Note the complete lack of toolbar or TOC. wikitext text/x-wiki Screenshot (tab drawer not included) of Omniweb 5.10.2 showing the editing window in the Beta. Note the complete lack of toolbar or TOC. bhf1v6g3godstokqvuiqchfpehnsrqy 0 997 8619 6040 2010-07-29T13:11:49Z Nemo bis 9 cat wikitext text/x-wiki == Citron Phase I Overview == Citron Phase I is the mid-March release from the Usability Initiative. The team is targeting the following features for the release: '''Dialogues:''' We are introducing dialoges with Citron. These features were originally released under Babaco, but were disabled due to issues with the iFrame. :*'''Links:''' The new [[:Image:Babaco_link_dialog_example.jpg | link dialog]] allows users to more easily create links, both links to pages within the wiki (“internal links”) as well as link to other pages on the web (“external links”). When creating links, the link suggest feature automatically suggest internal pages based on what you’ve entered. :*'''Tables:''' The [[:Image:Babaco_table_dialog.jpg| table dialog]] automatically generates wiki-text for tables based on a given width and height and lets you add a header row with one check of a box. :*'''Search and replace:''' Also new in this release is the [[:Image:Babaco_search_replace.jpg | search and replace tool]] which enables users to search for text and replace while editing. '''Toolbar Reorganization: ''' The toolbar layout will be revised based on click-tracking data from our users. '''Page Clean-up:''' We are simplifying the edit page by cleaning up the footer and licensing information. '''Side-by-Side Preview''' ''(under My Preferences):'' We are introducing a simpler method of viewing previewing changes by allowing users to preview their changes within the same editing window. This feature is available under the Editing tab in "My Preferences". '''Template Collapsing and Editing''' ''(For Usability Testing Only):'' Templates have long been a source of confusion for our editors, particularly novice ones. We are making template editing easier by providing the following features. For the upcoming release, these features will be available for Firefox 3, though we plan on expanding browser coverage shortly. :* '''Collapsing:''' In the editor, templates will be collapsed into a "capsule." Templates are often difficult for novice users to understand and can be a distraction to their editing. Collapsing the templates into capsules cleans up the editing space so that the template wikitext is less of a distraction. These capsules may be expanded into either the original wikitext or a user-friendly form. :* '''Form-based editing:''' The form-based template editor will enable users unfamiliar with wikitext to edit the content of a template with an easy to use web form. [[Category:Releases]] 9h8525ykcbyjy0efdsst2lv6h1xs01z 100 998 6461 6353 2010-04-06T00:15:00Z Guillom 13 sort key wikitext text/x-wiki {{draft}} This page discusses a generic workflow system that could serve as a possible implementation of the [[Multimedia:Incomplete uploads]]. Workflows we've identified on Wikimedia projects are basically of three types: * '''issues''' that needs to be resolved * '''tasks''' that should be done * community '''processes'''. We use the word "'''ticket'''" to refer to any of these types. == Issue management == ;Applicable workflows * Incomplete uploads (only for user-specific view) * Copyright issues (including obvious and suspected copyright violations) * Inappropriate personally identifiable information (not a priority at the moment; maybe at some point an integrated system can be used to replace OTRS / mailing lists requests) * Offensive content, nonsense * Factual error * Typography, grammar, spelling, conjugation deletion & maintenance * speedy deletion : common reasons and/or custom message * RfD: same, longer rationale * skim through [[:commons:Category:User_scripts|Category:User_scripts]] and gadgets in [[:commons:Special:Preferences|Preferences]] * Report an issue: [[Multimedia:"Report an issue" wizard]] / Create a ticket manually == Tasks == ;Applicable workflows * tasks, todo lists ; assignment of tasks * patrol of new pages (and new edits?) * tasks: target date * edit protected page * double redirects * links to disambiguation pages * etc. == Processes == ;Applicable workflows * content promotion (FP, QI; VP) * OTRS confirmation == Commonalities & Interface == Commonalities * rationale * discussions * link(s) to the page, preview of the file * list / queue of items * notification of the uploader / the creator of the page / people who edited the page the most / people watching the page * expiry date / deadline; possibility to extend / renew * batch actions? Actions * add / remove a template * change a template's parameter * add / remove a category * change visibility settings * send e-mail / e-mail reminder * possible linked to [[:mw:Manual:User rights|permission keys]] List / queue: * aggregation of different Flows * filtering (default options & customizability) * sorting, filtering; lil icons * blackboard of pending issues * static vs custom flows * Ticket creation * Actions * Queue / list == Raw notes from sketches == Actions (based on user rights) * send e-mail * add/remove template * add/remove category * add new message / section * create new LQT thred Todo: administration interface to add more flows Filters * default filters * ability to create custom filters based on a set of criteria; e.g. "new articles in topic X", etc. * Group by categories (content, links, users, categories, etc.) * Add new ticket type (specify family / class / group) * Add new group * Add field (type, label) == Interface == === Navigation menu === * sidebar or tabs (1 model, 2 views?) === User view === * Special:MyIssues * subscribe to new tickets matching a set of criteria (e.g. new Deletion requests related to History) === Global view === * filtering by ticket type (issue, task, process) * filtering by group (copyright, classification, links, etc.) * filtering by topic (wikiproject or more general -- Arts, Science, etc.) === Administrative interface === * Administrative interface to create new ticket types, new groups, etc. * new ticket type: should it be showed by default or rather added manually? == Sketches == <gallery> File:Flows - Initial assessment.svg|Initial assessment File:Flows - My issues list.svg|List of issues (user view) File:Flows - Incomplete uploads.svg|Incomplete uploads (user view) File:Flows - Incomplete uploads list with batch changes.svg|Incomplete uploads list, with batch changes (user view) File:Flows - Issues list by type.svg|Issues list by type File:Flows - Issues list by topic or WikiProject.svg|Issues list by topic or WikiProject File:Flows - Menu bar for issues.svg|Navigation menu for issues (tabs) File:Flows - Menu sidebar for issues.svg|Navigation menu for issues (sidebar) File:Flows - Menu bar & sidebar for tasks.svg|Navigation menus for tasks (tabs & sidebar) File:Flows - Menu bar & sidebar for processes.svg|Navigation menus for processes (tabs & sidebar) File:Flows - Speedy and regular deletion requests - General view.svg|Speedy and regular deletion requests - General view File:Flows - Speedy and regular deletion requests - Discussion view.svg|Speedy and regular deletion requests - Discussion view File:Flows - Speedy and regular deletion requests - Closing.svg|Speedy and regular deletion requests - Closing File:Flows - New item patrolling.svg|Patrol of new items File:Flows - New item patrolling with batch changes.svg|Patrol of new items, with batch changes </gallery> [[Category:Multimedia usability - Specifications|Flows]] jgnurxjcayhpginsuvq3e5tkuvmsx8c 100 1006 8454 8453 2010-07-13T22:15:14Z NeilK 1629 /* Compatibility */ wikitext text/x-wiki == Features / TODO == See [[Multimedia:Upload wizard/Features]] == Compatibility == See [[Multimedia:Upload wizard/Compatibility]] == Current Commons behavior == Some behavior is important to replicate; others we are deliberately changing anyway... === Descriptions === Commons form uses standard FUBAR-sort for languages (based on language code, which is roughly ISO 639). We are using unicode sort, which groups related langs together. Should move to the planned universal language typeahead widget Uses languages to group like so: lang = English , description = "foobar", you get <nowiki>{en|1=foobar}</nowiki>. And so on for each language. It is permissible to have a description in "unknown language". Or multiple descriptions. In that case the form simply doesn't wrap it in a language template. If you have multiple "unknown language" you get them all concatted together and mixed in with actual lang-template-wrapped descriptions. This seems bogus to me, under what circumstances do you not know the language you're entering? (editing is different). We should make 'unknown language' an error. === Licensing === ====Own work + CC-BY-SA-3.0 + GFDL==== * Information template: <nowiki><h2>{{int:filedesc}}</h2> {{Information |Description={{en|1=This is my description of what it all is}} |Source={{own}} |Author=[[User:NeilK|NeilK]] |Date= |Permission= |other_versions= }} </nowiki> * License template: <nowiki>{{self|cc-by-sa-3.0|GFDL}}</nowiki> * added immediately to categories (server-side; we don't have to do anything); request paran pprop=text|categories to see :CC-BY-SA-3.0 :License_migration_redundant :GFDL :Self-published_work ====Third party ==== I do not know the license: <nowiki>{{subst:nld}}</nowiki> Strangely, we are allowed to assert "ownwork" here. Ownwork, copyleft, attribution required (CC all versions): <nowiki>{{self|GFDL|cc-by-sa-all|migration=redundant}}</nowiki> Own work, self: <nowiki>{{PD-self}}</nowiki> Own work, self, cc-by (no sa): <nowiki>{{self|GFDL|cc-by-3.0|migration=redundant}}</nowiki> Third party licenses don't have the "self" template. Creative Commons Zero: <nowiki>{{cc-zero}}</nowiki> Creative Commons by sa 3.0 <nowiki>{{cc-by-sa-3.0}}</nowiki> Free Art License <nowiki>{{FAL}}</nowiki> (not one of our preferred licenses) etc. From Flickr and I do not know the license: <nowiki>{{subst:template 2|flickrreview|subst:nld}}</nowiki> From Flickr and I do know the license (for example, cc-by-sa-2.0) {{subst:template 2|cc-by-sa-2.0|flickrreview}} === Categories === Uses HotCats to prefill as you type. Then during posting, simply emits category wikitext, e.g. :<nowiki>[[Category:Foo]][[Category:Bar]]</nowiki> HotCats recently added up arrows and down arrows to select supercategories or subcategories of the currently-selected category. You can only do this after you've added the category already. However, once you're in super- or sub- browsing mode, you can keep going in that direction. When you finally make a selection, that replaces the current category. This seems like a very difficult feature to explain to new users, and also overlaps with the question of how to create a new subcategory on the fly. If I'm looking for Animalia, Felix, Felix domesticus, and then there's no Felix domesticus canhazcheeseburger then what? Why can't I just make it, with the appropriate parentage? This is why tags are soooo much easier than categories. Why do we keep trying to make this work? According to Lupo (author of HotCats) expert users have requested it. We should find out what the real use cases are. ==Feature implementations== It is considered desirable to automatically "fix" filenames; that is, when there is a file naming conflict, to immediately rename the file to something like "conflict title 2". There are some issues with that: * Discovering a title which is not in conflict is an O(n) operation from the client side. What if there are 12 or more such files? We will be waiting for 12 API calls. * Adding random letters or numbers to a title is not helpful to people using the repository * What if the user really did want to replace a file? We have to defer to a more convoluted interface later... Had a chat with RobLa on this and we came up with another idea: when a conflict is discovered, offer them semantically meaningful options, derived from other metadata. For instance, a message like: --------- There already is a media file with the title 'Nicolas Sarkozy' in Wikimedia Commons. { Preview } If your file has *exactly* the same content except with better quality, you should replace it. { Replace it } Otherwise, please make your title meaningfully unique: :* Nicolas Sarkozy at 2010-04-22 in Toulouse, France (Data derived from EXIF) :* Nicolas Sarkozy in Toulouse, France :* Nicolas Sarkozy, 2010-04-22 19:59:00 :* Nicolas Sarkozy viewed from ( FILL IN BLANK ) :* Nicolas Sarkozy wearing ( FILL IN BLANK ) :* Nicolas Sarkozy at ( FILL IN BLANK ) :* Nicolas Sarkozy with ( FILL IN BLANK ) :* Nicolas Sarkozy at 2010-04-22 19:59:00 by UserName" :* Nicolas Sarkozy ( FILL IN BLANK ) --------- Some suggested titles are more appropriate for people, others for buildings or objects. Advantage here is we will not have to make O(n) API calls to find unique suggestions, even client side. And if we build the feature server side we can make it even better. dvkdnuc87d8gt4v5vw0j2tdzpi0u5p8 100 1008 6054 2010-03-12T00:07:14Z Guillom 13 moved [[Multimedia:NewUpload]] to [[Multimedia:Upload wizard]]: reorg wikitext text/x-wiki #REDIRECT [[Multimedia:Upload wizard]] 6h8l6b7tji32aoi6zw4zqyfbxcd6kgv 0 1025 8614 6118 2010-07-29T13:01:34Z Nemo bis 9 cat wikitext text/x-wiki == Stuff we definitely want == * Toolbar (sans reorg) * Dialogues (links, tables, Search and Replace) * Templates * NTOC * Preview (sans changes tab) == Stuff we maybe want == * Publish button+dialog * Footer cleanup == Stuff we have to hack up == * Change caption of Save button to "Publish" with user JS [[Category:Usability studies]] 7wvz8yry9uqojyl2avknhz1s0hpt86h 6 1026 6124 2010-03-17T22:31:09Z Shuhari 4 New link dialog enabled on March 17, 2010 wikitext text/x-wiki New link dialog enabled on March 17, 2010 e9r4wsdfw2g4k92jfexkxcnnnv566pi 0 1028 6515 6502 2010-04-08T21:11:36Z 216.38.133.254 wikitext text/x-wiki == IN PERSON == [[Usability,_Experience,_and_Evaluation_Study/Notes/DryRun | "Dry Run"]] - @ 9am <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Victoria | "Victoria"]] - Thurs @ 9am <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Clayton | "Clayton"]] - Thurs @ 10:30am <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Sara | "Sara S"]] - Thurs @ 12:00pm <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Carrie | "Carrie O"]] - Thurs @ 3:00pm <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Tram | "Tram"]] - Thurs @ 4:30pm <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Erin | "Erin"]] - Fri @ 9:00am <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Oliver | "Oliver"]] - Fri @ 10:30am <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Caroline | "Caroline"]] - Fri @ 1:30pm <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Rob | "Rob"]] - Fri @ 3:00pm <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Joaquin | "Joaquin"]] - Fri @ 4:30pm <br /> == REMOTE == [[Usability,_Experience,_and_Evaluation_Study/Notes/Phil | "Phil"]] - Thurs @ 6:00am PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Keith | "Keith"]] - Thurs @ 9:00am PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Bianca | "Bianca"]] - Thurs @ 11:30am PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Adam | "Adam"]] - Thurs @ 1:00pm PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Charles | "Charles"]] - Fri @ 6:00am PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Nicholas | "Nicholas"]] - Fri @ 7:30am PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Meghan | "Meghan"]] - Fri @ 10:00am PDT <br /> [[Usability,_Experience,_and_Evaluation_Study/Notes/Lisa | "Lisa"]] - Fri @ 11:30am PDT <br /> == General Comments/Notes == * == Bugs we've found == * publish button does not work with captcha * once you edit info within the link box, we should not auto update fields * "what you type" should be in courier, lost its formatting * "loading" message for preview * consider changing table example in dialog to sketch (see my sketch) * our table example does not match the default values * Publish dialog does not have "Briefly describe the changes you've made here" * include infobox with icon in TOC * does ctrl-f work inside a pop up? * ctrl-v makes the templates explode. * preview tab from within "preview mode" - deal with it better! * preview pages aren't distinguishable from actual wiki pages - run the risk of people not committing their edits (in some cases because the preview is a false confirmation of their edits * dialogs + minor edit + etc are missing suggestive text * edit links visible in preview tab mode * take heading level 1 out of the dropdown menu == Brain Dump == * icon in the cheat sheet * showing inserted text better * showing article changes better * explore lightbox/gray/inplace help * can't be agnostic about what kind of template it is. put burden on template writers - provide guidlines (template info extension) * minor edit/formatting edit? * ref wizard - including different citation templates fte7vwyt40vhr3mfmtmx903wbhzkgoh 0 1030 6140 2010-03-18T12:25:04Z Praveenp 998 ++ wikitext text/x-wiki '''Current script for Malayalam transliteration given below. This script is limited to some predefined text areas :(''' <source lang="javascript"> /* <nowiki><pre> This script is a modified version of Alex benenson's cyrillic translitarator and this version was created by [[User:Peringz|Peringz]] */ var consonants = {"ക":"ക","ഖ":"ഖ","ഗ":"ഗ","ഘ":"ഘ","ങ":"ങ","ച":"ച","ഛ":"ഛ","ജ":"ജ","ഝ":"ഝ","ഞ":"ഞ","ട":"ട","ഠ":"ഠ","ഡ":"ഡ","ഢ":"ഢ","ണ":"ണ","ത":"ത","ഥ":"ഥ","ദ":"ദ","ധ":"ധ","ന":"ന","പ":"പ","ഫ":"ഫ","ബ":"ബ","ഭ":"ഭ","മ":"മ","യ":"യ","ര":"ര","ല":"ല","വ":"വ","ശ":"ശ","ഷ":"ഷ","സ":"സ","ഹ":"ഹ","ള":"ള","ഴ":"ഴ","റ":"റ","റ്റ":"റ്റ"}; var chillaksharam = {"ൺ":"ണ","ൻ":"ന","ം":"മ","ർ":"ര","ൽ":"ല","ൾ":"ള","്\\u200D":""}; var vowels = '"്a":"","്e":"െ","്i":"ി","്o":"ൊ","്u":"ു","്A":"ാ","്E":"േ","്I":"ീ","്O":"ോ","്U":"ൂ","്Y":"ൈ","െe":"ീ","ൊo":"ൂ","ിi":"ീ","ിe":"ീ","ുu":"ൂ","ുo":"ൂ","്r":"്ര്",'; var roman = '"k":"ക്","ക്h":"ഖ്","g":"ഗ്","ഗ്h":"ഘ്","ൻg":"ങ്","c":"ക്\\u200D","ക്\\u200Dh":"ച്","ച്h":"ഛ്","j":"ജ്","ജ്h":"ഝ്","ൻj":"ഞ്","ൻh":"ഞ്","T":"ട്","ട്h":"ഠ്","D":"ഡ്","ഡ്h":"ഢ്","റ്റ്h":"ത്","ത്h":"ഥ്","d":"ദ്","ദ്h":"ധ്","p":"പ്","പ്h":"ഫ്","f":"ഫ്","b":"ബ്","ബ്h":"ഭ്","y":"യ്","v":"വ്","w":"വ്","z":"ശ്","S":"ശ്","സ്h":"ഷ്","s":"സ്","h":"ഹ്","ശ്h":"ഴ്","x":"ക്ഷ്","R":"റ്","t":"റ്റ്",'; var chill = '"N":"ൺ","n":"ൻ","m":"ം","r":"ർ","l":"ൽ","L":"ൾ",'; var swaram = '"a":"അ","അa":"ആ","A":"ആ","e":"എ","E":"ഏ","എe":"ഈ","i":"ഇ","ഇi":"ഈ","ഇe":"ഈ","അi":"ഐ","I":"ഐ","o":"ഒ","ഒo":"ഊ","O":"ഓ","അu":"ഔ","ഒu":"ഔ","u":"ഉ","ഉu":"ഊ","U":"ഊ","H":"ഃ","റ്h":"ഋ","ർ^":"ഋ","ഋ^":"ൠ","ൽ^":"ഌ","ഌ^":"ൡ",'; //var numerals = '"1":"൧","2":"൨","3":"൩","4":"൪","5":"൫","6":"൬","7":"൭","8":"൮","9":"൯","0":"൦",'; var conjuncts = '"ൻt":"ന്റ്","ന്റ്h":"ന്ത്","ൻk":"ങ്ക്","ൻn":"ന്ന്","ൺN":"ണ്ണ്","ൾL":"ള്ള്","ൽl":"ല്ല്","ംm":"മ്മ്","ൻm":"ന്മ്","ന്ന്g":"ങ്ങ്","ൻd":"ന്ദ്","ൺm":"ണ്മ്","ൽp":"ല്പ്","ംp":"മ്പ്","റ്റ്t":"ട്ട്","ൻT":"ണ്ട്","ൺT":"ണ്ട്","്ര്^":"ൃ","ൻc":"ൻ\\u200D","ൻ\\u200Dh":"ഞ്ച്","ൺD":"ണ്ഡ്",'; var others = '"്L":"്ല്","~":"്\\u200C","്~":"\\u200C", "\\u200C~":"\\u200C", "\\u200D\\u200C":"\\u200D", "\\u200C_":"__", "___":"___","~":"്","ക്\\u200Dc":"ക്ക്\\u200D","ക്ക്\\u200Dh":"ച്ച്","q":"ക്യൂ",'; var caps = '"B":"ബ്ബ്","C":"ക്ക്\\u200D","F":"ഫ്","G":"ഗ്ഗ്","J":"ജ്ജ്","K":"ക്ക്","M":"മ്മ്","P":"പ്പ്","Q":"ക്യൂ","V":"വ്വ്","W":"വ്വ്","X":"ക്ഷ്","Y":"യ്യ്","Z":"ശ്ശ്",'; var ZWNJ = '"_":"\\u200C"'; // for compatibility with bookmarklets function cyr_translit(src) { return to_cyrillic(src); } var conversionHash = undefined; var maxcyrlength = 0; function getConversionHash() { if (conversionHash == undefined) { // TODO var opr = "{" + vowels + roman + chill + swaram + conjuncts + caps + others; for (var consonant in consonants) { opr += '"' + consonant + 'a":"' + consonant + 'ാ",'; opr += '"' + consonant + 'e":"' + consonant + 'േ",'; opr += '"' + consonant + 'i":"' + consonant + 'ൈ",'; opr += '"' + consonant + 'o":"' + consonant + 'ോ",'; opr += '"' + consonant + 'u":"' + consonant + 'ൗ",'; } for (var chk in chillaksharam) { opr += '"' + chk + 'a":"' + chillaksharam[chk] + '",'; opr += '"' + chk + 'e":"' + chillaksharam[chk] + 'െ",'; opr += '"' + chk + 'i":"' + chillaksharam[chk] + 'ി",'; opr += '"' + chk + 'o":"' + chillaksharam[chk] + 'ൊ",'; opr += '"' + chk + 'u":"' + chillaksharam[chk] + 'ു",'; opr += '"' + chk + 'A":"' + chillaksharam[chk] + 'ാ",'; opr += '"' + chk + 'E":"' + chillaksharam[chk] + 'േ",'; opr += '"' + chk + 'I":"' + chillaksharam[chk] + 'ീ",'; opr += '"' + chk + 'O":"' + chillaksharam[chk] + 'ോ",'; opr += '"' + chk + 'U":"' + chillaksharam[chk] + 'ൂ",'; opr += '"' + chk + 'Y":"' + chillaksharam[chk] + 'ൈ",'; opr += '"' + chk + 'r":"' + chillaksharam[chk] + '്ര്",'; opr += '"' + chk + 'y":"' + chillaksharam[chk] + '്യ്",'; opr += '"' + chk + 'v":"' + chillaksharam[chk] + '്വ്",'; opr += '"' + chk + 'w":"' + chillaksharam[chk] + '്വ്",'; opr += '"' + chk + '~":"' + chillaksharam[chk] + '്\\u200C",'; } opr += ZWNJ + "}"; // var tb = document.getElementById('wpTextbox1'); // tb.value = opr; conversionHash = eval("("+opr+")"); maxcyrlength=6; } return conversionHash; } function to_cyrillic(src, output, chunks) { if (src == undefined || src == "" || src == null) return src; if (output == undefined) output = new String(); var hash = getConversionHash(); var location = 0; while (location < src.length) { var len = Math.min(maxcyrlength, src.length - location); var arr = undefined; var sub; while (len > 0) { sub = src.substr(location, len); arr = hash[sub]; if (arr != undefined) break; else len--; } // need this for translit on the fly if (chunks != undefined) chunks[chunks.length] = sub; if (arr == undefined) { output += sub; location ++; } else { // case analysis var newChar = arr; if (sub.toLowerCase() == sub.toUpperCase() && arr.length > 1 && arr[1] && (newChar.toUpperCase() != newChar.toLowerCase())) { // need translit hash to determine if previous character (and possibly the one before it) // were converted and are in upper case // set prevDud to true previous is not a translated character or simply a blank // set prevCap to true if previous was translated and was upper case var prevCh = output.length == 0 ? null : output.substr(output.length - 1, 1); var prevDud = !prevCh || !getTranslitString(prevCh); var prevCap = (!prevDud && prevCh == prevCh.toUpperCase()); // sub is caseless but result isn't. case will depend on lookbehind and lookahead if (prevDud || !prevCap) { output += newChar.toLowerCase(); prevCap = false; } else { var next = " "; if (location + len < src.length) next = src.substr(location + len, 1); if (next != next.toUpperCase() && next == next.toLowerCase() ) { //next is lowercase (and not caseless) output += newChar.toLowerCase(); } else if (next == next.toUpperCase() && next != next.toLowerCase() ) { // next is uppercase (and not caseless) output += newChar.toUpperCase(); } else { // next is caseless. output case determined by the case of output[length - 2] var pprevCh = output.length == 1 ? null : output.substr(output.length - 2, 1); var pprevDud = !pprevCh || !getTranslitString(pprevCh); if (!pprevDud && (pprevCh == pprevCh.toUpperCase())) { //pre-prev is in upper case. output is also uppercase output += newChar.toUpperCase(); } else { output += newChar.toLowerCase(); } } } } else if ((sub.toLowerCase() == sub.toUpperCase()) && (arr.length < 2 || !arr[1])) { // literal treatment of newChar output += newChar; } else if (sub != sub.toLowerCase()) { // sub not all-lowercase output += newChar.toUpperCase(); } else { // sub is lowercase output += newChar.toLowerCase(); } location += len; } } return output; } function convertIt(src,converter){ var resultbuffer=""; for(var i=0;i<src.length;i++){ resultbuffer=converter(resultbuffer+src[i]); } return converter(resultbuffer); } var translitHash = undefined; function initTranslit() { if (translitHash == undefined) { translitHash = new Array(); for (var i = 0; i < conversionHash.length; i++) { var ch = conversionHash[i][1]; // if the translit string is not caseless, convert cyr string to upper case // otherwise maintain its case if (conversionHash[i][0].toUpperCase() != conversionHash[i][0].toLowerCase()) ch = ch.toUpperCase(); if (translitHash[ch] == undefined) translitHash[ch] = conversionHash[i][0]; } } } //-- translit on-the-fly -- function replaceValue(node, value, stepback) { if (stepback == undefined) stepback = 0; if (isExplorer()) { var range = document.selection.createRange(); range.moveStart("character", -stepback); range.text = value; range.collapse(false); range.select(); } else { var scrollTop = node.scrollTop; var cursorLoc = node.selectionStart; node.value = node.value.substring(0, node.selectionStart - stepback) + value + node.value.substring(node.selectionEnd, node.value.length); node.scrollTop = scrollTop; node.selectionStart = cursorLoc + value.length - stepback; node.selectionEnd = cursorLoc + value.length - stepback; } } // compare positions function positionIsEqual(other) { if (isExplorer()) return this.position.isEqual(other.position); else return this.position == other.position; } function Position(node) { if (node.selectionStart != undefined) this.position = node.selectionStart; else if (document.selection && document.selection.createRange()) this.position = document.selection.createRange(); this.isEqual = positionIsEqual; } function resetState() { this.position = new Position(this.node); this.transBuffer = ""; this.cyrBuffer = ""; } function StateObject(node) { this.node = node; this.reset = resetState; this.cyrBuffer = ""; this.transBuffer = ""; this.position = new Position(node); } var stateHash = new Array(); function isExplorer() { return (document.selection != undefined && document.selection.createRange().isEqual != undefined); } function pressedKey(event) { if (isExplorer()) return event.keyCode; else return event.which; } function transliterateKey(event) { /* if ((event.keyCode == 255 && event.charCode > 0) || event.keyCode == 8) { return; } */ if (event == undefined) event = window.event; var node = null; if (event.target) { node = event.target; } else if (event.srcElement) { node = event.srcElement; } // initialize state var state = stateHash[node]; if (state == null) { state = new StateObject(node); stateHash[node] = state; } if ( (pressedKey(event) > 20) && !event.ctrlKey && !event.altKey && !event.metaKey) { var c = String.fromCharCode(pressedKey(event)); // process input var result = process_translit(state, c); // finish up if (c != result.out || result.replace != 0) { if (isExplorer()) event.returnValue = false; else event.preventDefault(); replaceValue(node, result.out, result.replace); state.position = new Position(node); } } } function TranslitResult() { this.out = ""; this.replace = 0; } function process_translit(state, c) { // reset state if position changed if (!state.position.isEqual(new Position(state.node))) state.reset(); var result = new TranslitResult(); // initial backbuffer. Add to it as characters are converted var backbuffer = getBackBuffer(state.node, state.cyrBuffer.length, 2); var chunks = new Array(); state.transBuffer = state.transBuffer+ c var str = to_cyrillic(state.cyrBuffer+c, backbuffer, chunks); // remove backbuffer from output str = str.substr(backbuffer.length); result.out = str; /* str is now left alone - it has the output matching contents of chunks and will be used to reinitialize backbuffers, along with chunks and state.transBuffer */ // get the difference between state.cyrBuffer and output for (var i = 0; i < Math.min(state.cyrBuffer.length, result.out.length); i++) { if (state.cyrBuffer.substr(i, 1) != result.out.substr(i, 1)) { result.replace = state.cyrBuffer.length - i; result.out = result.out.substr(i); break; } } if (result.replace == 0) { if(result.out.length<state.cyrBuffer.length) result.replace=state.cyrBuffer.length- result.out.length; result.out = result.out.substr(Math.min(state.cyrBuffer.length, result.out.length)); // result.out+="\u0008" } // update state: backbuffer, bufferArray if (chunks.length > 0 && chunks[chunks.length - 1] == result.out.substr(result.out.length - 1)) { // no convertion took place, reset state state.reset(); } else { while (state.transBuffer.length > maxcyrlength) { state.transBuffer = state.transBuffer.substr(chunks[0].length); chunks.shift(); str = str.substr(1); } state.cyrBuffer = str; } return result; } function getBackBuffer(node, offset, count) { if (isExplorer()) { //.tagName.toUpperCase() == "EDITOR") { var range = document.selection.createRange(); range.moveStart("character", -offset); var result = range.text.substr(-count); if (!result) result = ""; return result; } else { return node.value.substring(0, node.selectionStart - offset).substr(-count); } } // need this for bookmarklets function getSelectedNode() { if (document.activeElement) return document.activeElement; else if (window.getSelection && window.getSelection() && window.getSelection().rangeCount > 0) { var range = window.getSelection().getRangeAt(0); if (range.startContainer && range.startContainer.childNodes && range.startContainer.childNodes.length > range.startOffset) return range.startContainer.childNodes[range.startOffset] } return null; } function toggleCyrMode() { var node = getSelectedNode(); if (node) { if (stateHash[node]) { if (removeKeyEventListener(node)) delete stateHash[node]; } else { if (addKeyEventListener(node)) stateHash[node] = new StateObject(node); } } } function addKeyEventListener(node) { if (node.addEventListener) node.addEventListener("keypress", transliterateKey, false); else if (node.attachEvent) node.attachEvent("onkeypress", transliterateKey); else return false; return true; } function removeKeyEventListener(node) { if (node.removeEventListener) node.removeEventListener("keypress", transliterateKey, false); else if (node.detachEvent) node.detachEvent("onkeypress", transliterateKey); else return false; return true; } function getSelectedText() { if (isExplorer()) { return document.selection.createRange().text; } else { var node = getSelectedNode(); if (node && node.value && node.selectionStart != undefined && node.selectionEnd != undefined) return node.value.substring(node.selectionStart, node.selectionEnd); } return ""; } /* calling functions */ function addLoadEvent(func) { if (window.addEventListener) window.addEventListener("load", func, false); else if (window.attachEvent) window.attachEvent("onload", func); } function addTranslit(editForm,textBox) { checkrt(editForm); // check for translit support if (textBox.addEventListener) textBox.addEventListener("keypress", processKeys, false); else if (textBox.attachEvent) textBox.attachEvent("onkeypress", processKeys); } function addTextEvent() { /////// if(lija_getCookie('mlWikiTranslit')!=null && lija_getCookie('mlWikiTranslit')!="") realTime=(lija_getCookie('mlWikiTranslit')=="true")?true:false; ////// var editForm =document.getElementById('editform'); if(editForm != null) { var textBox=document.getElementById('wpTextbox1'); var textSummary = document.getElementById('wpSummary'); addTranslit(editForm,textBox); addCheckbox(editForm,textBox ); if(textSummary) { addTranslit(editForm,textSummary); } } // add transliteration feature to search form also var searchForm = document.getElementById('searchform'); if( searchForm != null ) { try { var searchBox = document.getElementById('searchInput'); // add IME checkbox control to searchForm if (searchBox != null || searchForm != null) { var element = document.createElement("input"); element.setAttribute("type","checkbox"); element.setAttribute("id","sbrealtime"); if (element.addEventListener) element.addEventListener("click", rtClick, false); else if (element.attachEvent) element.attachEvent("onclick", rtClick); // var labelcheckBox = document.createTextNode('മലയാളത്തിലെഴുതുക'); var chkSpan = document.createElement("span"); chkSpan.setAttribute("id","spnRealtime"); var searchBody = document.getElementById('searchBody'); searchBody.appendChild(element); searchBody.appendChild(chkSpan); // searchForm.insertBefore(element,searchBox); document.getElementById("sbrealtime").checked = realTime; document.getElementById('spnRealtime').innerHTML = '<a href="http://ml.wikipedia.org/wiki/സഹായം:ടൈപ്പിംഗ്‌" title="Switches keyboard between Malayalam and English">മലയാളത്തിലെഴുതുക</a>'; // searchForm.insertBefore(chkSpan,searchBox); // var p = document.createElement("p"); // p.setAttribute("style","width:100%;height:1px;"); // searchForm.insertBefore(p,searchBox); } } catch(ex) { //എററിനെ ഓടിക്കുക. } if(searchBox) { addTranslit(searchForm,searchBox); } } //മലയാളം ടൈപ്പിങ് താളുകളിൽ സാധ്യമാക്കാനുള്ള സ്ക്രിപ്റ്റുകൾ | scripts to avail Malayalam transliteration //തിരയല്‍ താള്‍ | Search page var simpleSearchForm = document.getElementById('search'); if( simpleSearchForm != null) { var simpleSearchBox = document.getElementById('searchText'); if( simpleSearchBox ) { addTranslit(simpleSearchForm, simpleSearchBox );} } var powerSearchForm = document.getElementById('powersearch'); if( powerSearchForm != null) { var powerSearchBox = document.getElementById('powerSearchText'); if( powerSearchBox ) { addTranslit(powerSearchForm, powerSearchBox );} } // തലക്കെട്ട് മാറ്റല്‍ താള്‍. | Move page var movePageForm = document.getElementById('movepage'); if( movePageForm != null ) { var newTitleBox = document.getElementById('wpNewTitle'); if( newTitleBox ) {addTranslit(movePageForm, newTitleBox);} var reasonBox = document.getElementById('wpReason'); if( reasonBox ) {addTranslit(movePageForm, reasonBox ); } } //വിക്കിപീഡിയ:കളരി var kalariForm = document.getElementById('createbox'); if( kalariForm != null ) { var kalariText = document.getElementsByName('title')[0]; if( kalariText ) {addTranslit(kalariForm, kalariText);} } //അപ്‌ലോഡ് താള്‍ //******************** var upForm=document.getElementById('mw-upload-form'); if(upForm)//ഈ ഫോം ഇല്ലെങ്കില്‍ പിന്നെ മുന്നോട്ട് പോകണ്ട. { var upName=document.getElementById('wpDestFile'); var upComment=document.getElementById('wpUploadDescription'); if(upName) addTranslit(upForm,upName); if(upComment) addTranslit(upForm,upComment); } //************** } function addCheckbox(editform,textBox) { if(editform==null||textBox==null) return; try { var element = document.createElement("input"); element.setAttribute("type","checkbox"); element.setAttribute("id","realtime"); if (element.addEventListener) element.addEventListener("click", rtClick, false); else if (element.attachEvent) element.attachEvent("onclick", rtClick); var labelcheckBox = document.createTextNode(' മലയാളം എഴുതുവാന്‍ ഈ ഉപാധി സ്വീകരിക്കുക - Use Ctrl + M to Toggle.'); editform.insertBefore(element,textBox); document.getElementById("realtime").checked = realTime; editform.insertBefore(labelcheckBox,textBox); var p = document.createElement("p"); p.setAttribute("style","width:100%;height:1px;"); editform.insertBefore(p,textBox); } catch(ex) { //എററിനെ ഓടിക്കുക. } } var imeStatus = false; function processKeys(event) { if (rtsupported) { e = event || window.event; var myKeyCode = 0; var myShiftKey = false; if( document.all ) { //IE myKeycode = e.keyCode; myShiftKey = e.shiftKey; } else if ( document.getElementById || document.layers ) { myKeyCode = e.which; myShiftKey = (myKeyCode == 16)?true:false; } if ((e.keyCode == 13 && e.ctrlKey) || (e.which == 109 && e.ctrlKey)) { realTime = !realTime; lija_setCookie('mlWikiTranslit',realTime,1);//save in cookie var chk = document.getElementById('realtime'); var chkSb = document.getElementById('sbrealtime'); if (chk) { chk.checked = realTime; } if (chkSb) { chkSb.checked = realTime; } return false; } else if ((e.keyCode >= 3328 && e.keyCode <= 3455) || (e.which >= 3328 && e.which <= 3455)) { var chk = document.getElementById('realtime'); var spanSb = document.getElementById('spnRealtime'); var chkSb = document.getElementById('sbrealtime'); if (imeStatus == false || realTime) { realTime = false; if (chk) { chk.checked = realTime; chkSb.checked = realTime; spanSb.innerText = chkSb.checked } imeStatus = true; //alert('A Malayalam input tool was detected. Disabling in-built transliteration. To turn it On again use Ctrl+M'); window.status='A Malayalam input tool was detected. Disabling in-built transliteration. To turn it On again use Ctrl+M';//FF failure // return false; } } else if (realTime) { imeStatus = false; transliterateKey(event); // call transliteration function } } } var realTime=false; function rtClick(event) { realTime = !realTime; lija_setCookie('mlWikiTranslit',realTime,1);//save in cookie } var rtsupported = false; var error; function checkrt(editform) { try { /* var nav = navigator.userAgent.toUpperCase(); rtsupported = (nav.indexOf("GECKO") >= 0 || nav.indexOf("OPERA") >= 0 || nav.indexOf("SAFARI") >= 0); */ rtsupported = (document.selection != undefined) if (!rtsupported) { var element = document.createElement("TEXTAREA"); editform.appendChild(element); if (element.selectionStart != undefined) rtsupported = true; editform.removeChild(element); } } catch (error) {} } //************************************ // ട്രാന്‍സ്‌ലിറ്ററേഷന്‍ സ്ക്രിപ്റ്റില്‍ കൂക്കി സപ്പോര്‍ട്ട് ചേര്‍ക്കാനുള്ള ശ്രമം function lija_getCookie(cookieName) { if (document.cookie.length>0) { cookieStart=document.cookie.indexOf(cookieName + "="); if (cookieStart!=-1) { cookieStart=cookieStart + cookieName.length+1; cookieEnd=document.cookie.indexOf(";",cookieStart); if (cookieEnd==-1) cookieEnd=document.cookie.length; return unescape(document.cookie.substring(cookieStart,cookieEnd)); } } return ""; } function lija_setCookie(cookieName,value,expiredays) { var exdate=new Date(); exdate.setDate(exdate.getDate()+expiredays); document.cookie=cookieName+ "=" +escape(value)+"; path=/"+ ((expiredays==null) ? "" : "; expires="+exdate.toGMTString()); } //************************************ // add this line to your monobook.js to disable in-built transliteration - thanks to Sadik Khalid for this quick tip // var userIMEEnabled = false; // paste this line to user monobook.js and remove // from the begining of this line // check for user preference and load in-built transliteration tool if(typeof(window.userIMEEnabled) == 'undefined') { addLoadEvent(addTextEvent); } /* </pre></nowiki> */ </source> ---- '''Once we added one more function to avail transliteration to all text areas. But someday it started to display some error in internet explorer. So reverted. Here it is:''' <source lang="javascript"> var isForm = document.getElementsByTagName('form'); // താളിൽ ഫോം വല്ലതുമുണ്ടോ?? if (isForm != null) { addTranslitToForms(); } //ഉണ്ടേൽ തുടങ്ങുക function addTranslitToForms(){ var fno = document.forms.length; //എത്ര ഫോം?? for (var i=0; i<fno; i++){ var curForm = document.forms[i]; // അതിലൊരു ഫോം //alert(curForm.length); for(var j=0; j<curForm.length; j++){ var curElement = curForm.elements[j]; //ആ ഫോമിലെ ഒരു എലിമെന്റ് if(curElement.type && (curElement.type == 'text' || curElement.type == 'textarea')) { // അതിൽ ടൈപ്പ് സാധ്യമെങ്കിൽ //alert("got a text"); addTranslit(curForm, curElement); // ലിപിമാറ്റുക } } } } </source> l2a9pe9874dfoaa1mfobtuple82vj2q 0 1036 6182 6181 2010-03-23T23:10:59Z 216.38.133.254 wikitext text/x-wiki If a feature is not available for a given Usability N account but is for Usability M, the following causes are possible: * User JS/CSS out of sync ** Make sure [[User:Usability N/vector.js]] and [[User:Usability N/vector.css]] are in sync with their M counterparts ** Purge client cache (Shift+Refresh) * Preference has disappeared ** Check values of wgWikiEditorEnabledModules and wgVectorEnabledModules in Firebug console. If the modules you're interested in are set to true, preferences are not the problem ** Fire up <code>sql enwiki</code> on fenari and run <code>SELECT up_user, up_property, up_value FROM user, user_properties WHERE up_user=user_id AND user_name='Usability N';</code> to get a list of all preferences for that user. If the preference you're looking for isn't in the list, add it with <code>INSERT INTO user_properties (up_user, up_property, up_value) VALUES (12345, 'prefname', 1);</code> ** Fire up <code>php /home/wikipedia/common/wmf-deployment/maintenance/eval.php --wiki=enwiki</code> and type <code>User::newFromName('Usability N')->invalidateCache();</code> ** If it still doesn't work, log the user out and back in. It's possible that the preferences row has disappeared again, in which case you'll need to add it again. If possible, do that when the user is logged out $user->invalidateCache(); In eval.php 7p8kzwv564nzeb3hzyqsj3g6sm6i6g5 0 1038 6188 2010-03-25T15:50:18Z 69.105.154.137 Created page with '===Hannes' notes=== ====About the Test itself==== * Start with a more simple task * When the "leave-Edit warning message" appears: let her read! Don't say "it's ok, we don't need...' wikitext text/x-wiki ===Hannes' notes=== ====About the Test itself==== * Start with a more simple task * When the "leave-Edit warning message" appears: let her read! Don't say "it's ok, we don't need that". * Why do we ask to create a new page? I think this can be left out, since we didn't improve anything on that process. ====Usability Notes about Denise==== * She did not find the edit-tab and searched left nav for it * In the editor: had a big problem scrolling down, was confused by douple scrollbar? (browser + edit-window) * clicked portal in left nav. left nav in general seems to take lots of her attention :his confused her. she had to be guided back. * doesn't find preview (did not scoll down, because of her scrolling-problem) * Sean helped: from now on she always finds the preview. '''Toolbar''' * recognizes the reference icon immediatly. Is confused wheather she should click it. "no that just shows me..", "not sure", "this might take me to a reference" (not insert) * recognizes inserlink icon immediatly * Insert Link Dialog: wants to insert the whole URL of the LA Wiki Page * Inserts bold several times (so there are many marks) '''Save''' * finds save-button fast * want to use preview and save it afterwards * doesn't see/use Edit Summary and minor-Edit * when she leave the editor without saving she didn't read the warning-message (Sean told her not to care about it) '''Insert Table''' * recognizes table icon immediatly * uses the dialog without problems * not confused/ intimidated by the code that gets inserted * messed up the code a bit without noticing (which evokes an display error of the table) * previews --> see the error --> wants to go back to correct her error --> click edit --> confused, got lost, (also lost her data), because she is not in her section and her edits are gone '''Templates''' * searches the template box (in read mode) for a section-edit link * doesn't recognize the capsule "infobox settlement" as the San Francisco Infobox * uses form-popup pretty well * seaches for population * thinks "population...footnotes" is what she s looking for. --> confused, unclear about the variables names fb4naxu9xjlond0i4uro9rnfda1n3ib 0 1039 6191 2010-03-25T15:56:51Z 69.105.154.137 Created page with '===Hannes' notes=== ====About the Test itself==== * Start with a more simple task * When the "leave-Edit warning message" appears: let her read! Don't say "it's ok, we don't need...' wikitext text/x-wiki ===Hannes' notes=== ====About the Test itself==== * Start with a more simple task * When the "leave-Edit warning message" appears: let her read! Don't say "it's ok, we don't need that". * Why do we ask to create a new page? I think this can be left out, since we didn't improve anything on that process. ====Usability Notes about Denise==== * She did not find the edit-tab and searched left nav for it * In the editor: had a big problem scrolling down, was confused by douple scrollbar? (browser + edit-window) * clicked portal in left nav. left nav in general seems to take lots of her attention :his confused her. she had to be guided back. * doesn't find preview (did not scoll down, because of her scrolling-problem) * Sean helped: from now on she always finds the preview. '''Toolbar''' * recognizes the reference icon immediatly. Is confused wheather she should click it. "no that just shows me..", "not sure", "this might take me to a reference" (not insert) * recognizes inserlink icon immediatly * Insert Link Dialog: wants to insert the whole URL of the LA Wiki Page * Inserts bold several times (so there are many marks) '''Save''' * finds save-button fast * want to use preview and save it afterwards * doesn't see/use Edit Summary and minor-Edit * when she leave the editor without saving she didn't read the warning-message (Sean told her not to care about it) '''Insert Table''' * recognizes table icon immediatly * uses the dialog without problems * not confused/ intimidated by the code that gets inserted * messed up the code a bit without noticing (which evokes an display error of the table) * previews --> see the error --> wants to go back to correct her error --> click edit --> confused, got lost, (also lost her data), because she is not in her section and her edits are gone '''Templates''' * searches the template box (in read mode) for a section-edit link * doesn't recognize the capsule "infobox settlement" as the San Francisco Infobox * uses form-popup pretty well * seaches for population * thinks "population...footnotes" is what she s looking for. --> confused, unclear about the variables names fb4naxu9xjlond0i4uro9rnfda1n3ib 0 1040 10280 6196 2019-03-14T18:02:43Z Krinkle 709 /* = wrap up */ wikitext text/x-wiki == Parul's Notes == * Finds edit tab immediately * [NASH] capital U * [NASH] lets give people more time to make an edit * [NASH] need you to have your computer/chat * Next step "I guess I could preview it" * Would hit publish - then the sentence I wrote would appear on the main * Recognizes NTOC as the subheadings, especially useful for an article that has a lot of information * Doesn't see that they are clickable. Clicks - "Wow, that's a lot easier" 11:00 - VIDEO * [NASH] "not lets assume there's a page to alex chilton.com" * Uses the link button and paste, adds links, doesn't look as expected. Would expect to see the HTML - the href and stuff * Would expect a plain hyperlink * [NASH] lets do the internal link first * noticed the separate section for internal/external link but did not know the difference * types in page, sees suggestions, notices page exists. "I didn't know what to expect". it's different from the external link. * through exercise, understands the difference between * refference, uses section edit link, sees "reflist" * 16:48 - do you want a reference or a footnote? does it matter? * copies formatting that's above, add an asterisk. COPY AND PASTE * [NASH] worried about video quality - lets check it * stumped on references * checks advanced tab in toolbar. looking for reflist button? not ref button? * looks in the text to figure out where existing references are. finds a reference link. does not copy and paste. scrolls up and down to find ref. gets crazy with it - linking to an html page with an internal wiki link. madness. uses preview. * i'm lloking at what's been previously entered in mimic format that's been done. so what i'm doing will look the same and work the same 22:50. * eventually gets it! * i would possibly add a reference if i felt like it was something no one would do. a lot of people are more knowledgeable. * if it was a subject that i felt strongly about. 25:23 * i think references are important. i think being in grad school it's important. it's something that wikipedia gets criticized for. * 26:08 - similar to most blog sites - looks like rich text editing/online email. looks familiar to me. * looks easy enough to do. takes a little bit of time. * i didn't even look at the help section. 27:08 * i'm seeing putting in the help for references. oh ok - so this is all that. * i guess this is where a lot of people would start. i like to figure things out on my own. these are all examples. this would be a good cheat sheet without having to go back and forth in preview. i'd probably do a mixture. * i would hit publish * reads all of the information. understands minor edit and watch this page. * captcha! ack! * victoria deals with it well "makes sure i'm a human user". * our publish button doesn't work with captcha. * [NASH] warn about publish on captcah * setting up a user account and having the time or desire. * has looked at discussion before. just out of curiosity. * i'm seeing lots of long entries. they're discussing how to/what kind of contents should be on the page. some of it looks kind of....not as important as i would think. that seems very involved and not something i'd be interested in at all. apparently there are people that feel strongly about those things. 32:31 * vandalism. not surprising that people use whatever article to express their political point of view on the page. * seemed like a lot of discussion that i didn't have the time to sort through. * uses navigation easily read/discussion === Advanced tasks === * has never really looked at her hometown page * uses help menu - under headings. uses NTOC to get to attractions * adds sports heading with one '=' * do we want first level heading in the help? * adds sections, makes sure they show up in NTOC * in adding table, looks in help. nothing there. * [NASH] can probe on other places for help if "cheat sheet" doesn't cut it * it's got the code for the table. need to add the information. i feel like '''41:01''' i am doing something wrong because there should be an easier way to do it. * let me see what happens when i highlight header text and put something in. does it. previews. sees what that looks like. * i guess i have to manually put in the information. * looks like i added an extra row, so i'm going to delete that. * i just did something with the format - not quite sure what i did. * [NASH] separate table and template task? * thinks infobox is as a table. looks. finds infobox. * [NASH] refresh. * fins template, uses expansion * poor performance on long articles * need proper mouse over behavior for capsules. * 53:23 (YAY) * first inclination to click the arrow. * [NASH] probe about left navigation * uses left navigation with ease * i'm looking for something that says create entry. === wrap up === *1:01:26 "it's a lot easier than i expected * i thought there were more steps to take to edit * i like that there is some tracking of information and the changes, so it would be easy to go back and figure out where something got changed and how to correct that. if something got lost it would be easy to retreive. * if i screw something up - it's ok. (makes her feel more comfortable editing?) * view history and discussions seem unclear - hard to understand the abbreviations. * if there was a subject that i felt i had more knowledge about that i would want to take the time to commit to. need to be a bit of a time commitment. * [NASH] are we getting their email addresses? * [NASH] call backs? * being able to look at previous articles and subject. * "Make sure that the language for using it is understandable to non-computer people" "people that do a lot of code updating" 1:05 * It could be a little intimidating. I have a fair bit of html - i've been doing my own blog for 8 years. I just tweak the code, I don't write much. == Guillaume's and Nimish's Notes == * Wikipedia = starting point; looks for sources at the bottom * never took the time to edit; knew she could edit * has explored the tabs (talk, history) * has experience with HTML * * "Not quite the HTML format, but similar" * -Doesn't use wikipedia as a definitive source, checks references * "Never took the time to figure out (editing)" * PREVIEW, YAY * Got distracted with the bottom clutter (esp the show preview button on the bottom) * NTOC - understood what it is "alot easier" (wasn't first instinct to click) * -Insert Link (flashing not prominent enough) * WE SO NEED TO RELEASE THE PREVIEW TAB * --Ref-- * tried to find tool, then looked in the text (used link dialog) * Uses wikitext as an example like before * "Tend not to look at Help for instructions" * -Actually reading the publish information, a bit verbose but did go through the whole thing * Publish dialog not work with capcha * No Help for tables =( "This should be easier" * -"Special Link" thinks template is a link, doesn't entice click * -Thinks the form button is the button for forms * * Confused infobox with table (looks sort of like a table and table task close to template task) * * New page: something ovious I'm not seeing * Editing->subject matter expertice * Fair amt of HTML experience/blogging * expected the HTML code for external link * or hyperlink (wysiwyg) * chose an article already quite complete, doesn't know what to add * when looking for the list of references, thinks it's the external links * to add a "reference" (really an external link), would copy/paste the format of an existing line * can't find the references * found the ref tag in the wikitext * uses the syntax to enter a reference manually (!) * personal note from g.: why is the "what you type" column in the Help menu in a regular font, and not in a fixed-width font like the wikitext? * doesn't have the time, energy or will to dive into the long discussions * such discussions are for people who are passionate about this topic * when asked to create a new section : does directly to the help menu in edit mode, now that she knows it exists (she discovered it while playing around earlier) * chose the 1st level heading (which is h1 i.e. for page titles) * then saw the code (with only one equal sign) was different from section levels already in the wikitext * so used two equal signs instead * personal note from g: I don't think we need the 1st level heading in the help menu; this level is used for page title only * if it's confusing to start with a "2nd level", we can use the LaTeX vocabulary (section, subsection, subsubsection) * imho the help menu should be more prominent for new users, so it's easier for them to understand it actually exists * 1:00:20: is looking for something that says "create entry", "add article" or something like that * 1:01:40 "it's a lot easier than I expected" * likes: the tracking of the information, so it'll be easy to go back == Naoko's Notes == == Howie's Notes == qnq6cg6xu4hs6ra79yhna4zk1s71h8k 0 1041 7822 6258 2010-06-16T00:50:14Z 217.171.129.73 /* Parul's Notes */ wikitext text/x-wiki == Parul's Notes == * Graduated from UCSD last year - bouncing around. Studying for my MCATS, applying to med school. Self employed as a tutor * Supplement my studies * I always go to google first to get to Wikipedia - first link on the page. * It's a big part of what the internet offers. Hold in high regard in accuracy - very accurate form of providing information. Gotten more popular and I stuck with it. * I take from, I don't feel like I'm in a position to give my input on a lot of thing because I don't have the expertise to edit. I work in biological sciences - no mistakes. Have been thinking about adding things about where I live. * Had a class project on a wiki - used webping like editing a some html not a lot - add pictures, text, hyperlinks. Other people are doing it at the same time. Edit it, submit it, approved in some way. Or not approved * Uses a table of contents to navigate the article. * 09:32 previews - that's pretty cool * RAINBOW BALLS * internal link - changes text * 15:00 would rather do it in the edit box * learns wikitext from having seen and used it from the dialog - deterred from dialog because of changing text. * googles for help * i tend not to go for help - usually google stuff out of habit * 21:20 cheatsheet - this is pretty neat, this helps me do different things. alright. i like this because i can look at it and edit at the same time. * uses external links because reflist is unintelligible. * i would keep playing around with it until i got it right * wouldn't really think to much about adding a reference unless i was doing scientific stuff * 35:55 had a knack for glancing over things. if i had to, an assignment to edit a wiki entry, i would like a video. i know google does that for it's suite of applications. (SEND THIS CLIP TO FRANK/OUTREACH). get me started kind of video - those couple things we did. * 37:00 one introduction! * now that i'm playing around with it, i'm interested in what else we can do. * 39:00 do good stuff * not sure how the verifcation process works. * 41:00 that would be a cool video too * the process made it easy, but i go to wikipedia to get information. this is kind of an eye opener for me. it's not hard at all. * talk: would talk about the process, but don't know who would mediate. this could be a magical land where everyone agrees. * what's to stop.....i'm familiar with vandalism. wikipedia police? this is neat, i might start going to the discussion part of an article. chat board. * everything above this ball....i don't even really look at. * opens up another page to look at that. * doesn't see the need for 1st level heading * maybe flip flop these? * edit template is more in the same them of what i'm doing in this wiki text. * lost on making a new article. * everyone looks in left navigation for it. * navigates left navigation with ease. * slightly confusing interaction on dialogs * table of contents on the right and how i can skip to things really quick. the markup was really easy. * once i feel like i have more confidence in having expertise in an area! * ctrl-v * play around with things * 1:15 need to have copy * part of our language. no one edits. i've never seen anyone edit. i think one time we were debating (someone) was dead. * 1:16 i'm glad that wikipedia is getting people to edit. would blow my mind. i like wikipedia because i feel like there is truth in the voices of the masses. this is a good way for all of those voices to come together. reality is seen to wikipedia. more people editing = greater accuracy. * ==Group notes== Search: 2:40 Google -> Wikipedia Doesn't go to wp first and search from wp to find out how to add sources to wikipedia, he googled "how to add references to wikipedia" Thinks wikipedia is very accurate "wp is something i take from" doesn't feel he has expertise to contribute; "all that stuff is pretty solid, don't see many mistakes"; may edit local stuff has experience with wikis via class project (wetpaint). editing is "almost like html, but not quite" "approved in some way, or not approved" (thoughts on how the wikipedia article approval process works) /me lets howie write things down NTOC: "this is nifty" found it immediately use to get alot of information "Link" symbol automatically recognized Link dialog doesn't grab "closest link" if in a link Link default text change->not a feature? --Discouraged because the text "randomly changed" "That's pretty convenient." using the wiki link feature Selected text and hit link icon. Link to external page - doesn't like it when text to display = url - since text to display changes, would rather use wikitext to create external links The label, "Wikitext" is understood. "Citation help would be nice." Google searched for Wikipedia "help" Likes the "cheat sheet" in the toolbar, "I can look and type at the same time." - but on most websites, tends not to use help Spending quite a bit of time on adding references... - couldn't figure out syntax, so tried to copy the text from help menu and got something crazy - puzzled how extenal links show up in references, "I just keep playing around it until I get it right." like Victoria, was looking for references in the External links section why haven't we converted all in-text references to out-of-text references? it is now technically possible Compare the existing syntax and his intention, "what I was doing was right." "Pretty easy" (Really? it looked struggle to me. NK) « how would I put a link in my reference? » 31:30 "I only got a number." (implying the number in the references) 34:00 he's confused by the fact that when he wants to display the URL with the URL as label, the code is simply « http://truc.org » instead of « [http://truc.org http://truc.org] » (syntax for other links where the label is different from the URL) "I would like a video, if I am asked to edit Wikipedia." (Getting started, overall sujet would be good.) "Reference icon makes sense, but I'm not familiar with it" he's more familiar with icons from other applications (like Word) License agreement dialog gives a long pause "watch this page" -> email notification? or my edit is verified? "I don't know how Wikipedia is verified." (Thinking there is a body who verifies the content.) Would you edit in the future? "The process made it really easy, and that is not obstacles any more. Yeah." "I don't know where to go.", looking for "discussion" tab "all the information on a wikipedia page is down". First thing he does on a page is to scroll down thinks talk page is where you would discuss conflicts, but is uncertain who mediates. (calls it "chat board" or "message board") "This is neat." (looking at the discussion page) Task: add section --> Goes to hometown (Millbrae) adding section: - opened up a tab with Millbrae (BUT he went to wp home page and entered "millbrae" in wp search box) Opened "help" from the toolbar instead of expanding the toolbar to get advanced option confustion with "1st level heading" and what he sees (second level headings) (same as Victoria -- see also comments there) Task: add table Found the table icon without problems Made connection of rows and columns by looking at the cells in the wikisyntax Task: Templates Goes to the second browser tab to view the article, instead of using the "Read" tab Wants template to be part of NTOC Clicked on expand to wikitext first Rolls up and down and found the infobox capsule Expanded the template using inline expansion (not dialog) "Not as easy as I had hoped for." "drop down menu is safe" since he doesn't think he's gonna go anywhere else with the expand icon Template Dialog: Should it be alphabetized? right now in order of display, but might be disconnect Thinks it's a link Thinks the form icon does something completely different Wants ability to jump to specific part of form eachtime he previews his changes, he has to scroll back up to the top ofthe page to switch to the wikitext view again. It may make sense tohave a continuous view switcher bar on the left of the page orsomething. "I don't want to click links, because it takes me somewhere else" (pointing to the blue underlined capsule names) 59:45 "the drop-down menu is safe" "This is pretty neat too." (looking at the "View History" page) Wishes "Add a page" tab on the top Suggests a wizard Likes: the NTOC on the right reference was easier than i thought What would make you contribute? "One I feel like I have more expertise in an area" In the future, a biography of a colleague that becomes famous stuff that he's passionate about -- he either agrees with or trusts the information Says he would edit small errors (e.g., spelling) Task: Adding images Chose image gallery, inserted a link into a capiton -> does not work "Wikipedia is part of our language, but..." None of his friends would edit, unless it was just for kicks "believes there is truth in voices of the masses" "reality is seen through wikipedia" "(as) more people edit, it(wp) would be more accurate." q264ice5hyaegercyv55dgul615bxss 0 1042 6480 6221 2010-04-07T00:14:31Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * student, 5 days a week. * skeptical because you can edit it yourself - but it seems pretty accurate * be like a word document? fix it? has to be approved somewhere so people aren't doing this all day long. i feel like there should be [an approval process] * looks like a word document kind of thing * click click click * fast to publish * copy and pasting - sees in examples from the external links * hits show preview to see if it worked. * editing from within preview mode? * accomplishes it with the *[NASH] rephrase the reference question. *[NASH] mac for tomorrow * confusion about "insert reference text here" * everything but the last minute touches is easy 29:35 * 41:11 what's going on here: ALOT * sees history and viewing history, not editing history * has the correct assumptions about searching for a new page!? * no reason for me to take the time to learn. more advertisement that you can change this. or it's not that hard. == Group Notes == On speech team, so constantly looking things up Uses ~5 days/week a little skeptical since you can edit yourself, but seems pretty accurate why not edit? hasn't seen anything which needs editing "that was very easy to do. . .i'm not sure. . ." Expects word doc stuff realized the 'show preview' preview is a preview 11:36 -"I don't know how to edit it" References => People continuously try to add links in the 'references' section at the bottom, to an external web page - found help, trying to figure out syntax - says she'd be pretty likely to reference "if i could figure it out" Would you be more likely to edit in the future? "yeah, probably" "they're discussing" Who? "<username>" Do they work for wikipeida or are they just people out in the world? "They're just people out in the world" Task: add section this was easy for her. she looked at the wikitext and copied the "==" syntax Task: add table Brought up dialogue for table, changed rows/columns, started editing inserted wikitext "oh that's beautiful" when she finished the table Task: decrease population of castro valley by one Clicks on expand template first Moderator had to probe to get her to click form link thinks form icon will take her somewhere else view history page; what's going on here? "A lot. I'm not sure" Figures out it's "people who are changing things" after she sees the diff Viewing history is something she probably won't do why not edit? Doesn't occur to her/doesn't want to take time to learn e8qm164wwukqmxk3re7r3zm12eydv6w 0 1043 6481 6244 2010-04-07T00:15:41Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * 32 year old female, account manager, lives in the city, single, with roommates, no kids. * looking someone up on wikipedia - it feels stalkerish but i look up their bio and see where else i might have seen them, follow links * uses almost everyday, has not edited. * looking to find information, do not necessarily have the information. i can't think of anything where i've seen it and thought it was incorrect and thought i should update it. * i don't see that anything is happening. i'm clicking on things to find out what they do and they're not doing anything or i'm not seeing it * general confusion. * nothing to loose with turbo tax * what's this - not two pages of gobbley gook. * gobbley gook * gobbley gook ==Group Notes == Looks up people a lot Why not edit? Looking for information about people; not knowledgeable enough - can't think of instance where she's seen something incorrect - remembers seeing stub for adding more information, just never did - "dont consider myself a source" Recurring theme of "not knowlegdable enough" Colbert is awesome Wasn't aware of user accounts "i'm not a technical person" doesn't have the patience to figure it out Mentioned that the statement that she added "wasn't particularly profound" Task: Citation Looooong pause... Reference icon is not recognized Trying to figure out from help "I'm not technical enough (and not willing) to do this Help was not helpful "i'm clicking on them to find out what they do, but nothing seems to be happening" --> this is where she says she'd stop Help not interactive enough (We could make it fun and pretty) struggles to identify what syntax makes links NTOC is easy to be recognized and interacted She says it's pretty unlikely that she'll edit again (unless there is a burning desire to edit something) - small errors (e.g., spelling) - is there anything WP can do? She says there are a lot of click-throughs, not user-friendly, "legalese stuff" wasn't user friendly --> reduce number of steps - she uses turbotax, wants the equivalent of turbotax too many click through before publishing Task: adding a new section - quickly used section header tool - excited to see what she did worked Task: ceate a table - took 10-15 seconds to find a table icon - looks proud after creating a table successfully Task: Edit population Expanded the infobox using the dialog Recurring theme: Looking for Infobox by the TOC because that's where it appears in the page Name makes *huge* difference did not notice the scroll bar at first, but noticed later and started scrolling View History - I will *never* take time to review this - Thinks user talk page is where the discussion of the article takes place Recurring theme: look at left Nav to create article (because we're asking them to do something like File-> new article...fix that) How to find help? "I never look at help, even using MS word." I slightly feel I had accomplished something. Slightly empowered by learning how to edit. "I don't find it super user friendly. I'm visual person, and this code thing.." "turns to code" Liked: She likes the help after all. Finds the toolbar layout easy. Has experience in web publising Yelp: considered contributing; but then heard it was a scam so doesn't contribute turbotax: used to use accountant, friend told her about it, thought it was hard; hook was could do return online, get your return online; nothing to lose; "a 15 year old should be able to understand this"; "line 46 -> line 46, simplicity", feels like wikipedia takes her back to wordperfect days "a 15 yr old should be able to understand what this is" Short, simple statements t49hwqegylkwlc9kg6iv9zxntbap6em 6 1044 6224 2010-03-25T20:18:21Z Shuhari 4 == Summary == == Summary == wikitext text/x-wiki == Summary == == Summary == jqetmo861tdwj37yx60et3afhxaees2 0 1046 8023 7776 2010-06-21T21:46:21Z Az1568 8 /* How do I turn off the new features? */ "New!"..? Should be "New features" wikitext text/x-wiki {{FAQLang}} ==What's changed?== We're making several changes to the user interface. First, we are introducing a new skin named "Vector". This new skin should make common functions easier to find. We've also introduced a number of improvements to the editing interface, including an improved editing toolbar, dialogs to help with tasks such as inserting links and tables, and a built-in "cheatsheet" to help users access the most commonly used functions. Finally, we've changed the site layout by simplifying the overall navigation and moving the search box to a more intuitive location (see the blog post [http://techblog.wikimedia.org/2010/06/usability-why-did-we-move-the-search-box/ "Why did we move the search box?"] for a more detailed explanation of this change). We hope our users will find the changes helpful. For those who want to continue using the original features, there will be a 'Take me back' link at the top of the page. ==Why are you making these changes?== Wikipedia and the other projects operated by the Wikimedia Foundation are written and edited by volunteers. When knowledgeable people cannot participate in editing Wikipedia because they find it too confusing or difficult to edit articles, it is a serious problem that undermines the potential quality, breadth and depth of the content that we can offer to you. In other words, even if you don't contribute content, the easier we can make it for knowledgeable people to join our projects, the more useful our resources become to you. When it was first developed, the software running Wikipedia was considered reasonably user-friendly. By today's standards, it is not as streamlined nor user-friendly as other software. That's why we're making a series of important changes, beginning with the first release of new software in April, to make Wikipedia better. ==How was it decided that these changes would be implemented?== Starting in January 2009, we built a small team to assess and improve the usability and user experience of Wikipedia and its sister projects. The first Usability and Experience Study took place in March 2009. We've shared all [[UX Study|documentations and videos]] from the study. Based on the findings of the study, we implemented a series of improvements that have been made available for public testing starting in August 2009. This was followed by further iterations and fixes based on user feedback, culminating in a second user study which took place in October 2009 ([[Usability, Experience, and Progress Study|documentation]]), which have validated some of our changes, and led us to making further improvements. The release that we're deploying in April represents the set of changes that are well-tested and have been used by more than 500,000 users through our beta program. An average of 80% of users who tried the beta program stayed in it, and we've collected extensive feedback from other users on their reasons for leaving the program. This feedback was used to make further changes, many of which were related to language-specific issues. We've shared full documentation of our [[Beta_Feedback_Survey|beta retention data and user feedback]].) ==Why aren't you making bigger changes to the user interface?== This is just the beginning. We've made a set of additional changes that are still undergoing active testing and development. You can see these changes on our [http://prototype.wikimedia.org/ prototype site]. After validating these changes through user research, we'll be making further tweaks, pushing towards a second release later this year. We've made user experience a permanent effort at the Wikimedia Foundation. From now on, regular changes and improvements to the interface, not just aimed at first-time editors, but also at readers and experienced editors, are business-as-usual. Specifically, we will assess the best strategy to implement rich-text editing on Wikipedia and its sister projects. ==Will this change be deployed in all languages?== This change was initially be deployed to Wikimedia Commons early April. The English Wikipedia will followup on May 13 starting at 5:00am UTC, and Wikipedia in all languages and other Wikimedia Foundation projects will update at a later period of time. Our international volunteer community, working through translatewiki.net, is still working hard to make sure that we have the best possible localization coverage for the launch. If you want to help, please see the step-by-step guide on [http://translatewiki.net/ translatewiki.net]. == Where did the watch tab go? == You can watch/unwatch a page by clicking the star in the toolbar where the "Read", "Edit" and "View History" buttons are. ==How can users make sure their user scripts, user styles, gadgets and external tools will still work?== By testing them with the new settings, you will be able to verify compatibility and resolve any issues. By clicking the “Try Beta” link at the top of any page, and then opting into the beta, you will have turned on the same settings which will be made default. Another way to test skin compatibility is to append “?useskin=vector” to the end of the URL of a page. For example, the URL http://en.wikipedia.org/wiki/Wikimedia_Foundation would become http://en.wikipedia.org/wiki/Wikimedia_Foundation?useskin=vector to see how the page would look using the Vector skin. ==How do I turn off the new features?== If you'd like to turn off the new features, please follow these steps: # Log into your account # Click on the "New features" link in the upper right portion of the page (next to your username) # Go to the "Take Me Back" section of the "New features" page and click on the link to turn off the new features You may always turn the new features back on by visiting the "New features" page again. ==Why don't the scripts (monobook.js) and styles (monobook.css) work any more?== If you would like to continue to use your custom code in the [[m:vector|vector skin]], you will need to move and/or adapt your [[Special:Mypage/monobook.js|monobook.js]] to your [[Special:Mypage/vector.js|vector.js]] and [[Special:Mypage/monobook.css|monobook.css]] to [[Special:Mypage/vector.css|vector.css]] accordingly. ==Vector customization tips== Here's [http://meta.wikimedia.org/wiki/Vector the good resource] on customization of Vector. s2k876myj7m5j8f8skjvh7op86k8zm3 100 1050 6462 6352 2010-04-06T00:15:16Z Guillom 13 sort key wikitext text/x-wiki {{draft}} * facilitate reporting of issues * Customer service / scaling up OTRS Request for help / issue reporting * your message will be publicly viewable (preferred); faster, the whole community can help * your message will remain private (→ OTRS) logged-in users → identified by their username logged-out users → e-mail? reminder sent by e-mail when the state of the page/issue/process changes (new, resolved, deleted, promoted, etc.) <gallery> File:Report an issue wizard - Initial assessment.svg|Initial assessment File:Report an issue wizard - Copyright.svg|Report copyright issue File:Report an issue wizard - Privacy.svg|Report privacy issue File:Report an issue wizard - Factual error (generic).svg|Report generic factual error File:Report an issue wizard - Factual error (BLP).svg|Report own BLP factual error </gallery> [[Category:Multimedia usability - Specifications|Report an issue wizard]] a5246970ncazx83vmv6wsg7m38zyvjg 0 1051 6482 6257 2010-04-07T00:16:33Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * Grad school at UPENN * at my computer during my waking hours for half the day, personal stuff, facebook, stuff i'm interested in * use a mac, but more familiar with a pc. * has a blog, use yelp, craigslist, transactional thing. i use blogspot * visits wikipedia several times a day, has edited three times * editing process was suprisingly easy to edit. open process - anyone can edit. actual interface not that easy. * familiarizes herself with cosmetics page - straightforward. interesting that i was redirected. * looking for contents in the same place it is in the article. wish it were (where i expected it to). not that easy to find - not the same numbering scheme that was on the prior page. looking for an "add section" in the NTOC * moves instead to edit content instead of "adding" content. * successfully edits content - previews, and finds editor at the bottom of the preview page. * test clicks all lead to internal wiki pages. forms understanding that you can only link to wiki pages within the body of the text. * "sorry it's kind of a kludgy way to do it. i don't really understand" * {reflist} identified as the start of a reference section * uses link dialog - believes she's done it right.......previews. links inactive. feels like it's wrong or not allowed or violated some policy. * copy and pasted from a previous example of reference. * 35:48 when i hit preview i'm scared because i don't know if it's going to save my changes * looks for edit on infobox in read mode * ctrl f - for content collapsed in a template. == Group Notes == [1-2 edits] + blogger Edited for fun for the first time Editing experience was surprisingly easy to edit (open process), but actual editing process was not easy although she considers herself tech-savvy does not have an account goes to cosmetics page pleasntly surprised that "make up" page is redirected to "cosmetics" "interesting photo collecitons" Redirects -> reasoning (assumes topic deficiency) Add something to the page use "read" tab to go back to the page "interesting" interface (puzzled) wants to add a section, but can't figure out Looks for TOC where the TOC was in the page (similar to finding Infobox in earlier participants) Expects TOC to have "add section" button since sections are already present Doesn't use 'section edit'... Wants to add a section directly to NTOC Trys out the link on the left navigation bar Familiar with old "save" interface, thrown off by "publish" "can't link to external links in the body" ->assumption of how wikipedia works? Back button to get back to read mode Thiks that she can copy the link syntax from the links in the text (did not work as she wanted to add external link) Never noticed the toolbar Goes to the left nav when she was asked something useful Finally found the link icon (expects it to be blue. "link is always in blue") (syntax highlighting for links?) Tries to copy internal link syntax for external links Didn't know she was in the preview mode (thought she was in the article page) Recurring Theme: Preview mode not clear References: copy+paste reference example Figuring out how to add citation is difficult, try and error does not work Wants to "save" first (meaning locally for previewing) ' Recurring theme: needing to undo (not readily visible or known that it's possible) Templates as "buttons" not "links" Expects help in the left navigation bar No idea about templates without multiple parameters and values In discussion page: Look at boxes at the top and thinks the page is for announcement Task: adding a section - wants to add a section in NTOC - figures out the heading syntax by clicking one of the section header from NTOC - There is no "UNDO" (after making a mistake with table creation) "Preview" tab is found without any wondering around, but the preview itself takes a long time for a long article like "San Francisco" "those gray boxes must be some kind of templates" likes the temlate inline expansion as she can see te whole thing View history (have been there before, thinking it is discusion page) Likes: Hyperlinks to the section Didn't like: No page differentiation (did not know where she was at) Participation: If there is an indication about "help" in the search result page, i will edit. eekf7g7qs741mbm3sjd1v7qzt374c3s 6 1052 6259 2010-03-26T05:58:53Z Shuhari 4 == Summary == The trend of account creation for English Wikipedia in 2009. wikitext text/x-wiki == Summary == The trend of account creation for English Wikipedia in 2009. 43yluvskvnylhxhrpkbbdnk7wg2bng6 6 1053 6262 2010-03-26T10:28:48Z Notafish 299 == Summary == Screenshot of how target page URL field and Text to Diplay field are linked and probably should not. wikitext text/x-wiki == Summary == Screenshot of how target page URL field and Text to Diplay field are linked and probably should not. 2kyqzh6jrsac3ptdz23y5gynddvufz7 0 1056 6485 6285 2010-04-07T00:19:43Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * has done user research of sorts before * user message * i'm usually looking for things i want to know about. * had never paid attention to the navigation before, i usually go straight to the content of the article. * search bar is where people are expecting it to be. * loves the disambiguation * i don't get the "go" and "search" * 40:00 * has not looked at discussion pages * goes to "evil" heavy topic * you can add your non-factual thoughts * i would call that "pretty information" almanac * no simple edit link, but i suppose we can just edit the article * contents: main organizations of the article. * i don't see something....it doesn't have that almanac listed * 52:55 "are you telling me it's called an infobox??" * again, infobox on article should have edit link and template pop up should look like infobox itself. * consider multiple orderings for infoboxes * form design sux * messy user process - preview, publish - no clear idea when/where he's at * would be easier if this was part of my login. do we reallly need this everytime i edit? * someone might disagree with that? * 58:00 these were the funny characters i was looking at * i am not familiar with that. * it expands. it's a preview.....so i can't edit here. it's a gray background. * 1:02 - laughing at the idea of doing a table. "where's the help?" * 1:03:14 - are you gonna tell me i can just type there? * those special icons - i'm not sure those were the way to do something before * want a link that goes something to more substantial * i don't remember any tools to skipping over or knowing the widgets * for a person that blogs, a lot of this feels familiar * what do you do? how do you start this? * seeing some graphic support for doing this. (favorite) * the monitor - and scroll within scroll within scroll * what do you do? all of these articles have to have something. do you want infotext or not. at least something that describes something that you're about to do....[wants a "template" for a new article? wants a tutorial or some beginner info before creating a new article?] * INTERESTED IN SEEING THE VIDEO. == Group Notes == Search bar moved, "where people expect it" (used it before he noticed it) -> go and search is confusing "used show preview" time to preview/response too slow "can I open a new tab? do I have to wait for it?" copied url to sf wiki page (http://en.wikipedia.org/wiki/San_Francisco_Bay_Area), pasted in link dialog, checked "wiki page"; "external link" icon in upper right corner didn't change, created a new wiki page named the url (expressly said 'this is a wiki page' while creating the external URL) PREVIEW NOT CLEAR ENOUGH, people test links in preview to make sure they internally/externally link right "can't see controls all the time" size of scroll area "blogging tools don't have tabs at the top' --> how do blogging tools do preview? Understood the "discussion" tab, but was unsure when he got to the page. He eventually seemed to figure it out. task: template editing struggled to find collapsed template since i don't know the order, i expect alphabetical larger infoboxes a problem, in display order, need some sort of categorization chooses to preview after making change then clicks on publish Thinks "minor edit" flags it for someone to look at Templates "there are lots of these little things, looked like everything else here", Infobox "we don't know wht to call it" (we need to differentitate) TEMPLATES HAVE DIFFERENT USES, 1 SOLUTION FOR THEM DOESN'T WORK! "doesn't look editable" SCREEN SCROLL: as to guillom's comment:people always scroll to a certain position as a 'comfortable editing position'...how can we change that? Task: create table started laughing, then went immediately to help Tried to type within the example Once table is inserted, he figured out how to edit What do you think about the editing process? "I know my mother couldn't use this" if he wanted to do something more advance, wants to go to help Liked the graphical support "if i knew what an infobox was, it would have helped" Didn't like Scroll within scroll within scroll When creating new article: Thinks there must be some sort of format New article prepopulated with a style? All this [the toolbar] would be helpful 6m2hydch237h6q727x5xuvrvvq43yhv 0 1057 6486 6287 2010-04-07T00:21:07Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * grants for non-profit organizations, project + special knowledge management * online marketing. more of a bystander in crowdsourcing. * has edited - nobel prize winners - bill o'reilly. * "i don't think i have very much to say" if i was very knowledgeable on some subject. and having the time for it. * "little wiki language" * i would rather use the pop out - less overwhelming. very overwhelming - esp for people that aren't familiar with this kind of thing. * i like the two different ways for people to get into it. wiki text or whatever. it's not clear what these two things mean. * assuming i can edit here * intuitive understanding. * i'm one of wikipedia's biggest fans.....even though there is the crazy corruption going on. * hesitant to do it so we don't have the need. == Group Notes == More of a consumer of info than a contributor for ugc stuff (e.g., amazon, yelp) Task: add link Used double brackets Added [[kevin thompson]] knows that red = no article, and her expectation is that "Kevin Thompson" would be in red She doesn't want the link to go to a disambiguation page tried to paste wikipedia url into link dialog when creating an internal link Motivated and finds relevant text Very error-tolerant ieoytorzstz2j9e9c2ysq30sqcx81fr 0 1058 6487 6292 2010-04-07T00:22:22Z 216.38.133.254 wikitext text/x-wiki == Parul's Notes == * i'm kind of scared about that - i don't know if i know enough about one subject to know what i should * never seen those before 'cause we've never logged in. * editing a section, in preview, opens new tabs to get examples from elsewhere in the page * 35:30 it's a lot harder than i thought it would be - referencing via section. * once you use a tool a lot, it's easier. doing it for the first time it was a little intense. * pretty straightforward * my note taking skills have slipped. * thinks templates are "embed file" result. * show this part to guillame 54:00 * 55:00 updated by the census - higher powers that me - i'll give it a shot i guess. * looks to see if the infobox on the article had that title "infobox" * why have both? as someone that's new to this thing......they do the same thing * though maybe you could edit the table dialog....but maybe next phase. 1:11:something * reference button - looks like bookmark * demo - this is how we do the edit. this is how * great job and change that button == Nimish's Notes == "reference" icon not clear Recurring theme: no one's really using the 'reference' button Need only one interaction with template ("why have both?") 'get rid of arrow' expects table in table dialog to be editable "Demo on how to edit" (tutorial, clip, etc) "Change the reference button" kft96vtcuhrfyrqthhbq1xtoqzdh6yo 0 1064 6308 2010-03-27T18:39:47Z Nihiltres 78 moved [[Whats new questions and answers]] to [[What's new, questions and answers]]: Grammar fix; this has been bothering me for a while. :p Change is minor. wikitext text/x-wiki #REDIRECT [[What's new, questions and answers]] 40y16csx91hu3gbj16dvh4xifum4lob 0 1071 8873 6471 2010-09-10T07:30:55Z 71.141.96.194 wikitext text/x-wiki To use these snippets, paste them into the <code>User:Yourusername/vector.js</code> or <code>User:Yourusername/monobook.js</code> page (depending on whether your skin is Vector, Monobook or something else). You can use multiple snippets by simply pasting them below each other. == Snippets requiring no customization == === Strikethrough button === This puts the button in the "Advanced" section of the toolbar. To put it in the top section of the toolbar instead, replace <code>'advanced'</code> with <code>'main'</code>. The button uses the old toolbar's strikethrough image; to change this, change the URL after <code>icon:</code>. <source lang="JavaScript"> if ( typeof $j != 'undefined' && typeof $j.fn.wikiEditor != 'undefined' ) { $j( function() { $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'advanced', 'group': 'format', 'tools': { 'strikethrough': { label: 'Strike', type: 'button', icon: 'http://upload.wikimedia.org/wikipedia/commons/3/30/Btn_toolbar_rayer.png', action: { type: 'encapsulate', options: { pre: "<s>", post: "</s>" } } } } } ); } ); } </source> === Horizontal line button === This puts the button in the "Advanced" section of the toolbar. To put it in the top section of the toolbar instead, replace <code>'advanced'</code> with <code>'main'</code>. The button uses the old toolbar's horizontal line image; to change this, change the URL after <code>icon:</code>. <source lang="JavaScript"> if ( typeof $j != 'undefined' && typeof $j.fn.wikiEditor != 'undefined' ) { $j( function() { $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'advanced', 'group': 'format', 'tools': { 'hline': { label: 'Horizontal line', type: 'button', icon: 'http://bits.wikimedia.org/skins-1.5/common/images/button_hr.png', action: { type: 'encapsulate', options: { pre: "----", ownline: true } } } } } ); } ); } </source> === Comment button === <source lang="JavaScript"> if ( typeof $j != 'undefined' && typeof $j.fn.wikiEditor != 'undefined' ) { $j( function() { $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'advanced', 'group': 'format', 'tools': { 'comment': { label: 'Comment', type: 'button', icon: 'http://upload.wikimedia.org/wikipedia/commons/3/37/Btn_toolbar_commentaire.png', action: { type: 'encapsulate', options: { pre: "<!-- ", post: " -->" } } } } } ); } ); } </source> === Math button === <source lang="JavaScript"> if ( typeof $j != 'undefined' && typeof $j.fn.wikiEditor != 'undefined' ) { $j( function() { $j( '#wpTextbox1' ).wikiEditor( 'addToToolbar', { 'section': 'advanced', 'group': 'format', 'tools': { 'math': { label: 'Math', type: 'button', icon: 'http://bits.wikimedia.org/skins-1.5/common/images/button_math.png', action: { type: 'encapsulate', options: { pre: "<math>", post: "</math>" } } } } } ); } ); } </source> == Snippets requiring trivial customization == q7rzx0ke6fuqur2pdj9fcdwbeimdb7j 0 1072 8615 6357 2010-07-29T13:02:11Z Nemo bis 9 cat (given it's orphan) wikitext text/x-wiki == Victoria == moved to http://usability.wikimedia.org/wiki/Usability,_Experience,_and_Evaluation_Study/Notes/Victoria == Clayton == Search: 2:40 Google -> Wikipedia Doesn't go to wp first and search from wp to find out how to add sources to wikipedia, he googled "how to add references to wikipedia" Thinks wikipedia is very accurate "wp is something i take from" doesn't feel he has expertise to contribute; "all that stuff is pretty solid, don't see many mistakes"; may edit local stuff has experience with wikis via class project (wetpaint). editing is "almost like html, but not quite" "approved in some way, or not approved" (thoughts on how the wikipedia article approval process works) /me lets howie write things down NTOC: "this is nifty" found it immediately use to get alot of information "Link" symbol automatically recognized Link dialog doesn't grab "closest link" if in a link Link default text change->not a feature? --Discouraged because the text "randomly changed" "That's pretty convenient." using the wiki link feature Selected text and hit link icon. Link to external page - doesn't like it when text to display = url - since text to display changes, would rather use wikitext to create external links The label, "Wikitext" is understood. "Citation help would be nice." Google searched for Wikipedia "help" Likes the "cheat sheet" in the toolbar, "I can look and type at the same time." - but on most websites, tends not to use help Spending quite a bit of time on adding references... - couldn't figure out syntax, so tried to copy the text from help menu and got something crazy - puzzled how extenal links show up in references, "I just keep playing around it until I get it right." like Victoria, was looking for references in the External links section why haven't we converted all in-text references to out-of-text references? it is now technically possible Compare the existing syntax and his intention, "what I was doing was right." "Pretty easy" (Really? it looked struggle to me. NK) ¬´ how would I put a link in my reference? ¬ª 31:30 "I only got a number." (implying the number in the references) 34:00 he's confused by the fact that when he wants to display the URL with the URL as label, the code is simply ¬´ http://truc.org ¬ª instead of ¬´ [http://truc.org http://truc.org] ¬ª (syntax for other links where the label is different from the URL) "I would like a video, if I am asked to edit Wikipedia." (Getting started, overall sujet would be good.) "Reference icon makes sense, but I'm not familiar with it" he's more familiar with icons from other applications (like Word) License agreement dialog gives a long pause "watch this page" -> email notification? or my edit is verified? "I don't know how Wikipedia is verified." (Thinking there is a body who verifies the content.) Would you edit in the future? "The process made it really easy, and that is not obstacles any more. Yeah." "I don't know where to go.", looking for "discussion" tab "all the information on a wikipedia page is down". First thing he does on a page is to scroll down thinks talk page is where you would discuss conflicts, but is uncertain who mediates. (calls it "chat board" or "message board") "This is neat." (looking at the discussion page) Task: add section --> Goes to hometown (Millbrae) adding section: - opened up a tab with Millbrae (BUT he went to wp home page and entered "millbrae" in wp search box) Opened "help" from the toolbar instead of expanding the toolbar to get advanced option confustion with "1st level heading" and what he sees (second level headings) (same as Victoria -- see also comments there) Task: add table Found the table icon without problems Made connection of rows and columns by looking at the cells in the wikisyntax Task: Templates Goes to the second browser tab to view the article, instead of using the "Read" tab Wants template to be part of NTOC Clicked on expand to wikitext first Rolls up and down and found the infobox capsule Expanded the template using inline expansion (not dialog) "Not as easy as I had hoped for." "drop down menu is safe" since he doesn't think he's gonna go anywhere else with the expand icon Template Dialog: Should it be alphabetized? right now in order of display, but might be disconnect Thinks it's a link Thinks the form icon does something completely different Wants ability to jump to specific part of form each time he previews his changes, he has to scroll back up to the top of the page to switch to the wikitext view again. It may make sense to have a continuous view switcher bar on the left of the page or something. "I don't want to click links, because it takes me somewhere else" (pointing to the blue underlined capsule names) 59:45 "the drop-down menu is safe" "This is pretty neat too." (looking at the "View History" page) Wishes "Add a page" tab on the top Suggests a wizard Likes: the NTOC on the right reference was easier than i thought What would make you contribute? "One I feel like I have more expertise in an area" In the future, a biography of a colleague that becomes famous stuff that he's passionate about -- he either agrees with or trusts the information Says he would edit small errors (e.g., spelling) Task: Adding images Chose image gallery, inserted a link into a capiton -> does not work "Wikipedia is part of our language, but..." None of his friends would edit, unless it was just for kicks "believes there is truth in voices of the masses" "reality is seen through wikipedia" "(as) more people edit, it(wp) would be more accurate." == Sarah == On speech team, so constantly looking things up Uses ~5 days/week a little skeptical since you can edit yourself, but seems pretty accurate why not edit? hasn't seen anything which needs editing "that was very easy to do. . .i'm not sure. . ." Expects word doc stuff realized the 'show preview' preview is a preview 11:36 -"I don't know how to edit it" References => People continuously try to add links in the 'references' section at the bottom, to an external web page - found help, trying to figure out syntax - says she'd be pretty likely to reference "if i could figure it out" Would you be more likely to edit in the future? "yeah, probably" "they're discussing" Who? "<username>" Do they work for wikipeida or are they just people out in the world? "They're just people out in the world" Task: add section this was easy for her. she looked at the wikitext and copied the "==" syntax Task: add table Brought up dialogue for table, changed rows/columns, started editing inserted wikitext "oh that's beautiful" when she finished the table Task: decrease population of castro valley by one Clicks on expand template first Moderator had to probe to get her to click form link thinks form icon will take her somewhere else view history page; what's going on here? "A lot. I'm not sure" Figures out it's "people who are changing things" after she sees the diff Viewing history is something she probably won't do why not edit? Doesn't occur to her/doesn't want to take time to learn == Carrie == Looks up people a lot Why not edit? Looking for information about people; not knowledgeable enough - can't think of instance where she's seen something incorrect - remembers seeing stub for adding more information, just never did - "dont consider myself a source" Recurring theme of "not knowlegdable enough" Colbert is awesome Wasn't aware of user accounts "i'm not a technical person" doesn't have the patience to figure it out Mentioned that the statement that she added "wasn't particularly profound" Task: Citation Looooong pause... Reference icon is not recognized Trying to figure out from help "I'm not technical enough (and not willing) to do this Help was not helpful "i'm clicking on them to find out what they do, but nothing seems to be happening" --> this is where she says she'd stop Help not interactive enough (We could make it fun and pretty) struggles to identify what syntax makes links NTOC is easy to be recognized and interacted She says it's pretty unlikely that she'll edit again (unless there is a burning desire to edit something) - small errors (e.g., spelling) - is there anything WP can do? She says there are a lot of click-throughs, not user-friendly, "legalese stuff" wasn't user friendly --> reduce number of steps - she uses turbotax, wants the equivalent of turbotax too many click through before publishing Task: adding a new section - quickly used section header tool - excited to see what she did worked Task: ceate a table - took 10-15 seconds to find a table icon - looks proud after creating a table successfully Task: Edit population Expanded the infobox using the dialog Recurring theme: Looking for Infobox by the TOC because that's where it appears in the page Name makes *huge* difference did not notice the scroll bar at first, but noticed later and started scrolling View History - I will *never* take time to review this - Thinks user talk page is where the discussion of the article takes place Recurring theme: look at left Nav to create article (because we're asking them to do something like File-> new article...fix that) How to find help? "I never look at help, even using MS word." I slightly feel I had accomplished something. Slightly empowered by learning how to edit. "I don't find it super user friendly. I'm visual person, and this code thing.." "turns to code" Liked: She likes the help after all. Finds the toolbar layout easy. Has experience in web publising Yelp: considered contributing; but then heard it was a scam so doesn't contribute turbotax: used to use accountant, friend told her about it, thought it was hard; hook was could do return online, get your return online; nothing to lose; "a 15 year old should be able to understand this"; "line 46 -> line 46, simplicity", feels like wikipedia takes her back to wordperfect days "a 15 yr old should be able to understand what this is" Short, simple statements == Mrs Howie == [1-2 edits] + blogger Edited for fun for the first time Editing experience was surprisingly easy to edit (open process), but actual editing process was not easy although she considers herself tech-savvy does not have an account goes to cosmetics page pleasntly surprised that "make up" page is redirected to "cosmetics" "interesting photo collecitons" Redirects -> reasoning (assumes topic deficiency) Add something to the page use "read" tab to go back to the page "interesting" interface (puzzled) wants to add a section, but can't figure out Looks for TOC where the TOC was in the page (similar to finding Infobox in earlier participants) Expects TOC to have "add section" button since sections are already present Doesn't use 'section edit'... Wants to add a section directly to NTOC Trys out the link on the left navigation bar Familiar with old "save" interface, thrown off by "publish" "can't link to external links in the body" ->assumption of how wikipedia works? Back button to get back to read mode Thiks that she can copy the link syntax from the links in the text (did not work as she wanted to add external link) Never noticed the toolbar Goes to the left nav when she was asked something useful Finally found the link icon (expects it to be blue. "link is always in blue") (syntax highlighting for links?) Tries to copy internal link syntax for external links Didn't know she was in the preview mode (thought she was in the article page) Recurring Theme: Preview mode not clear References: copy+paste reference example Figuring out how to add citation is difficult, try and error does not work Wants to "save" first (meaning locally for previewing) ' Recurring theme: needing to undo (not readily visible or known that it's possible) Templates as "buttons" not "links" Expects help in the left navigation bar No idea about templates without multiple parameters and values In discussion page: Look at boxes at the top and thinks the page is for announcement Task: adding a section - wants to add a section in NTOC - figures out the heading syntax by clicking one of the section header from NTOC - There is no "UNDO" (after making a mistake with table creation) "Preview" tab is found without any wondering around, but the preview itself takes a long time for a long article like "San Francisco" "those gray boxes must be some kind of templates" likes the temlate inline expansion as she can see te whole thing View history (have been there before, thinking it is discusion page) Likes: Hyperlinks to the section Didn't like: No page differentiation (did not know where she was at) Participation: If there is an indication about "help" in the search result page, i will edit. ==Erin C== References -> tries to make it HTML b/c it looks like HTML tags Gets confused with the template capsule Recognizes need for discussion page so it's not an "edit war" Infoboxes: expect a 'section edit' "really not sure how to get into that" "throws me off that they have 2 ways to view the same thing" "makes me wonder if one way is better than another" "summary saying 'substantial vandalism' helped me" ==Oliver== Search bar moved, "where people expect it" (used it before he noticed it) -> go and search is confusing "used show preview" time to preview/response too slow "can I open a new tab? do I have to wait for it?" copied url to sf wiki page (http://en.wikipedia.org/wiki/San_Francisco_Bay_Area), pasted in link dialog, checked "wiki page"; "external link" icon in upper right corner didn't change, created a new wiki page named the url (expressly said 'this is a wiki page' while creating the external URL) PREVIEW NOT CLEAR ENOUGH, people test links in preview to make sure they internally/externally link right "can't see controls all the time" size of scroll area "blogging tools don't have tabs at the top' --> how do blogging tools do preview? Understood the "discussion" tab, but was unsure when he got to the page. He eventually seemed to figure it out. task: template editing struggled to find collapsed template since i don't know the order, i expect alphabetical larger infoboxes a problem, in display order, need some sort of categorization chooses to preview after making change then clicks on publish Thinks "minor edit" flags it for someone to look at Templates "there are lots of these little things, looked like everything else here", Infobox "we don't know wht to call it" (we need to differentitate) TEMPLATES HAVE DIFFERENT USES, 1 SOLUTION FOR THEM DOESN'T WORK! "doesn't look editable" SCREEN SCROLL: as to guillom's comment:people always scroll to a certain position as a 'comfortable editing position'...how can we change that? Task: create table started laughing, then went immediately to help Tried to type within the example Once table is inserted, he figured out how to edit What do you think about the editing process? "I know my mother couldn't use this" if he wanted to do something more advance, wants to go to help Liked the graphical support "if i knew what an infobox was, it would have helped" Didn't like Scroll within scroll within scroll When creating new article: Thinks there must be some sort of format New article prepopulated with a style? All this [the toolbar] would be helpful == Caroline == More of a consumer of info than a contributor for ugc stuff (e.g., amazon, yelp) Task: add link Used double brackets Added [[kevin thompson]] knows that red = no article, and her expectation is that "Kevin Thompson" would be in red She doesn't want the link to go to a disambiguation page tried to paste wikipedia url into link dialog when creating an internal link Motivated and finds relevant text Very error-tolerant ==Rob M== "reference" icon not clear Recurring theme: no one's really using the 'reference' button Need only one interaction with template ("why have both?") 'get rid of arrow' expects table in table dialog to be editable "Demo on how to edit" (tutorial, clip, etc) "Change the reference button" ==Joaquin D== No experience with HTML All-blacks rugby fan =) "a whole bunch of computery looking things" -> "oh no wait" (after NTOC and stuff showed up) DEF less intimidated after other stuff appeared Added wiki page link and clicked "internal" again...bottom option seems too confusing 'adding section' -> doesn't think it's automatic (thinks headings are a formatting issue) [[Category:Usability studies]] r4i3lsdk3uyqeu5tz7qkcetomw2hwwt 0 1075 6405 6385 2010-04-02T16:04:08Z Juxn~usabilitywiki 176 pasted notes from etherpad wikitext text/x-wiki == Parul's Notes on Bianca == * editing for grammar * haven't made any major edits - added some content, but not nearly as much * blogs * has written yelp reviews * notices article and discussion tabs. * stanford band - changes the caption on a photo. * never really figured out what minor edit is - usually click on it. * copies and pastes from an example link. finds referenced links. * i'm trying to see how to make a piece of text look like (a link?) * look like hyperlink * sean points out link button in toolbar * creates internal link by typing chars- page doesn't exist, red * links to "external" page using dialog * internal link - automatically * not likely to add references * knows how to add a section - just types the chars, looks at toolbar, wouldn't use * shifting in the editor window - distracting * see video markers for template stuff * has never created a page ==Naoko's Notes on Bianca== ===General editing=== * Compares the editing experience with WordPress * Publish the edits without previewing * Knows how to add a link to Wikipedia page * Add internal link using dialog successfully * Creates a table using dialog, but missed how to make a header row ===Templates interaction=== * Looks for an infobox in NTOC * Expands the arrow, instead of using the dialog * Likes the dialog, but did not recognize how to get to it ===Overall impression=== * Interface is not intuitive * Wishes obvious tutorial * Refers to twitter for how to's * Highlights for new features ===One thing you like the most=== * NTOC * Template dialog ===What would make you contribute significantly?=== * Making citation easier (importing references) * Incentives * Something enticing (not sure how to express) ===One message to the UX team=== * Make it obvious ==Nimish's and Hannes's Notes== * "I wish this would be a plain Text Editor" * Uses Preview Tab immediatly (when asked to find the preview) * Thought the Advanced, Speical Page and Help Links are "real" Links that takes you to another page. Therrfor she didn't want to click on the them. * can use the ling dialog very good. "this is pretty intuitiv" ===Insert Reference=== * recognizes ref icon * was very confused by junping effect!!! * does not know how to format a reference, would just select text and click the ref-icon * Would like to have an undo button ===Discussion=== * Expects "moderators to discuss the article" * Clicks on it: see some hints --> is confused, this is not what she expected. * "this is like another wiki" ===Add a section=== * copies the "===" * rather than using the headings from the toolbar (even though she sees them, doesnt know what it is) * thinks the indent-icon could have something todo with a section as well, but she is unsure ===Insert table=== * finds table icon immediatly * gets along with the iserted table code pretty well * (knows where to put what) ===Infobox/ Template Folding=== * looks for a "category" in the ntoc that says infobox * some guide: "scroll back to the top" than finds the capsule, clicks oin the arrow * guide: "click on the hyperlink" * "Oh cool, but I would have figure this out, if you did not tell me." * Calls templates "hyperlinks" * Enjoys editing from forms more * What you like better? "the popup thing, it's easier to find. But I dont like the fact that I cannot change the headings" ===New Page=== * Searches left nav (Communtiy Portal) * searches for "how to create a new page" --> doesnt find help ===Search=== * Searching for help information * Asks for tutorial as well oqltvlsa4x75go18l1k25yu3zioh7df 0 1076 6406 6373 2010-04-02T16:07:05Z Juxn~usabilitywiki 176 pasted notes from etherpad wikitext text/x-wiki == Parul's Notes == * Usability 2 * didn't notice that preview at first * plays with NTOC by editing the section name. "i should have previewed first" let me go do that. 9:28am * copies and pastes a link from above - sees examples and doesn't use the toolbar (not a bad thing) * general impressions - learned new things i didn't know before. * used to be local - tampa,fl, but moved away. * easy to go to brockton and get the facts - more undisputable than alex jones. * find stuff - didn't have any idea where it was * research on research. it's not something that can be undertaken lightly. some kind of reason to make sure it was done right - not just because i care about it. keep myself in business and can't drop everything. need the passion to do the job. * keep expanding the truth. ==Nimish's and Hannes's Notes== * previous experience: facebook,yelp,etc * Didn't see top level edit, assumed section edit "where I'd put it" * trys to login as "user billy 1" * didn't use the preview mode initially, just publish * understood the ntoc intuitively * copy and paste link * doesn't see where the text got inserted...MAKE BRIGHTER * footnotes: "It would be in the references" * expects tools in the toolbox * expects forum * "It isn't my intent to go out and edit everything" * opened form immediately rather than arrow * Leans heavily on section edit * "pretty cool" ===Insert External Link:=== * Inserts Link with Copy/Paste a different Link, than changing ===Insert Intern Link:=== * Searches Left Nav for some help to insert an external link * Clicks on "What links here" expects help there * misinterpretates the ref-tag as "hyperlink" * selects the ref-tag, clicks on insert link icon (gets invalid link) ===Edit and section edit=== * Doesn't see the main edit link * depends on section edit links * therefor he cannot edit the first section g6eo7grewpyfwvmiheum39s29bhq69h 0 1078 6407 6391 2010-04-02T16:08:19Z Juxn~usabilitywiki 176 pasted notes from etherpad wikitext text/x-wiki ==Parul's Notes== ==Naoko's Notes== ===General Editing=== *Creates heading by copying the heading from other parts of the article *Refers to NTOC as subtitles and modules *NTOC makes sense *Adds external link using dialog without any issues *Chooses the next step as "publish" instead of "preview" *Not sure what "minor edit" means *Constant uses publish instead of preview *Uses preview below the editor instead of the preview tab *Finds interface much simpler than expected ===Discussion=== *Expects discussion board and comments from various contributors in "Discussion" *Goes silent looking at two huge templates *Tries again for the Washington DC article ===Template Interaction=== *Goes to Washington DC *Goes to a table instead of the infobox capsule *After guided to the capsule, opens it up using the link, and successfully edits the population *Likes the pop-up over inline expansion ===Creating a table=== *Navigates to the Sports section using NTOC *Does not find the table icon without being guided *Change values easily *Nested tables is created by mistake ===How to get help=== *Selects the cheat sheet from the link next to "Cancel" *Thinks the cheat sheet is very helpful ==Nimish's Notes== * FB but no other online editing * Most freq editing on ms office * uses edit summary* * "MINOR EDIT CONFUSING" hvlg1coze5jhjdoxptrvtddvj498djp 0 1079 6402 6401 2010-04-02T15:54:02Z Juxn~usabilitywiki 176 /* Nimish's and Hannes's Notes */ style changes wikitext text/x-wiki == Parul's Notes == * doesn't see toolbar * comments (like reddit) as reputation ==Nimish's and Hannes's Notes== Contributes reviews '''NTOC:''' *"under the 'hide contents'" *-> maybe the label should be 'contents (hide)'? *understands ntoc immediatly '''Insert External Link''' * tries ref sources (at the bottom of the page) * guide: "scroll up, see the toolbar?" toolbar doesn t attract Nicholas <br /> Assumes the "select text" functionality<br /> <br /> Looks up external page to a wiki page '''Internal Link''' * opens dialog, but seems to think that its worong * --> doesn t see/ read "to a wiki page" * ref icon (mouse overs the ref-icon, while checking the toolbar for a function to add a link) * "this will take me to the bottom" * "doesn't look like I can do it that easily" (refs) '''Insert a reference''' * "no idea" * "Cancel" -> expected undo <br /> * Found preview eventually, preferred it to 'trial and error' * preview confusing -> hit edit in preview to edit '''Discussion page''' * -> no idea what's there '''Infobox''' * Infobox: need section level, definitely! * clicks section edit underneath the infobox (which belopngs to the section noit to the infobox) * finds the capsule, opened it - thinks - and cancled!! (d'oh) * --> didn t recognized the content. "I dont think it was that obvious" * --> would be much better,if the popup uses more vertical space (like 80% of the browser-window) * --> problem of titling and labels(?) <br /> * section edit found immediately '''Add a section''' * did not find/ use "advanced" (naming issue? or visually not atttractive enough?) * guidance to use advanced: doesn t use headings * "I would search a sections that has a subsection and than copy it" * --> succeeds this way <br /> * recurring theme: people keep associating 'section' with the way it looks as opposed to a logical structure (IE try to indent and bold over deliniating subsection) '''Insert table''' * managed pretty well <br /> '''Create New Page''' * searches top navi (mouseovers the watch-star, reads tooltip) * searches for help on the mainpage, find tutorial for editing * clicks his way though several help pages, without success <br /> '''Overall/ Resumee''' * "pretty intimedating at first" * toolbar was helpfull "once that I found it" * would like to "gain reputation" for contributing t0yuskak81j45jt655w6lswst886nh8 0 1080 6403 2010-04-02T15:59:28Z Juxn~usabilitywiki 176 pasted notes from etherpad wikitext text/x-wiki ==Nimish's and Hannes's Notes== * Clerk, occasional posting on review sites ===Publish dialog=== * used edit summary and appreciated it <br /> * Found help page but not think to use the dialog (generational thing? same behavior yesterday) * REF tag: highlighted the text he wanted to reference, then clicked 'ref' button, once he worked out how the link dialog did this, assumed same functionality * READ tab intuitive, to "exit editing" <br /> * Performance is SUPER slow with large pages <br /> * Confused with 'bold' for section heading (also saw this confusion yesterday) * Searched though the available icons, did not click Advanced immediatly * ("advanced" miss naming?) * when he clicked he found "headings" pretty fast and used it right <br /> ===NTOC=== * understood intuitivly * "makes it a lot easier" ===External Link=== * searches left nav * "isn t here add a link or something?" * searches for help at a help-page * guide: "take alook at the top" * --> finds toolbar, clicks on "help" finds external link * '''wants to click the help examples !!!! (which would really make sense )''' * finds link-icon accidently ===Uses Preview Tab=== * wanted to go "back to edit" while he was at the preview * got the warning message --> so he knows that he is still in the editor ===Infobox interactions=== * Scrolled around through the transcluded templates (we should shrink those down) * Expected down arrow to indicate 'this expands down' * Caspsule doesn t attract him * only found with guidance * --> clicked on text: form popup * now, he performed the edit task quickly ===Table=== * While beeing at the preview and wants to go back to the editor to do more editing: * "Publish this or else I'll lose it" <br /> * accidently removed a "!", while adding header text and the first "|" * "screwed it up" and gave up ===Create a new Page=== * first searched for a help page * than tried to search for a page (he had in mind), which doesn t exist, than created it. * "that's pretty easy" ===Overall=== * "the interaction ispretty straight forward" * "easy" 17bj34vqpk4ivteq63rfuhanga4m6k1 0 1082 6408 2010-04-02T16:11:04Z Juxn~usabilitywiki 176 pasted notes from etherpad wikitext text/x-wiki ==Nimish's and Hannes's Notes== * HTML confusing (no templates) * Preview confusing * Intuitive understanding of NTOC * page slow * (Internal external links confusing) * Understood discussion page is *not* a forum * Infobox = "code" * Search box intuitive * Uses examples * General notes: For older machines (like his parents machine) performance is terrible * prefers to google information rather than look in help * blames self for not knowing where things are * Still loves wikipedia despite horrible lag * "if there was a subject I knew about" <br /> * Insert Link: Dialogs not enabled (using IE) * Reference Icon: immediatly recognized * Clicked ref-cion: :* Doesn't know what to do: :* "hmm...I don't know what to do from here" :* "I would like to have an extra, external tool to help me" :* "A Popup, where I can put information in, ...., that would be so much easier." <br /> * Does not know how to edit the infobox * recognizes some of the words from the infobox * but still is confused * finally he made it to increase population by one.. yeah! :) * doesn't use advanced toolbar, did not see it * if you dont know what advanced does you wouldn't click it when you search for insert table * is unsure about the table-code nxi5ujh6n1fwwo42off3eaay58upkcb 10 1083 8652 6415 2010-07-29T13:30:56Z Nemo bis 9 cat wikitext text/x-wiki {{keypress/core| {{{1}}} }}<!-- -->{{#if:{{{2|}}}| +{{keypress/core| {{{2}}} }} }}<!-- -->{{#if:{{{3|}}}| +{{keypress/core| {{{3}}} }} }}<!-- -->{{#if:{{{4|}}}| +{{keypress/core| {{{4}}} }} }}<!-- -->{{#if:{{{5|}}}| +{{keypress/core| {{{5}}} }} }}<!-- -->{{#if:{{{6|}}}| [[w:Category:Wikipedia keypress template parameter needs fixing]] }}<noinclude> [[Category:Templates]] </noinclude> brt9n6bart7rlh7v0vjgaj03anvnpcq 10 1084 6417 6416 2010-04-05T15:48:27Z RW Marloe 1482 wikitext text/x-wiki <span class="keyboard-key" style="border: 0.2em outset #cecbc7; background: #f0ece8; padding: 0 0.4em 0.1em 0.3em; font-size: 0.8em; white-space: nowrap;">{{#switch:{{lc:{{{1}}}}} | shift = {{Unicode|⇧}} Shift | [[w:shift key|shift]] = {{Unicode|⇧}} [[w:Shift key|Shift]] | enter = {{Unicode|↵}} Enter | [[w:enter key|enter]] = {{Unicode|↵}} [[w:Enter key|Enter]] | cmd = {{Unicode|⌘}} Cmd | [[w:cmd key|cmd]] | [[w:command key|cmd]] = {{Unicode|⌘}} [[w:Command key|Cmd]] | opt = {{Unicode|⌥}} Opt | [[w:opt key|opt]] | [[w:option key|opt]] = {{Unicode|⌥}} [[w:Option key|Opt]] | tab = Tab {{Unicode|⇆}} | [[w:tab key|tab]] = [[w:Tab key|Tab]] {{Unicode|⇆}} | backspace = ← Backspace | [[w:backspace]] = ← [[w:Backspace]] | win | [[w:win key|win]] | [[w:windows key|win]] = {{Unicode|⊞}} [[w:Windows key|Win]] | up = ↑ | [[w:arrow keys|up]] = [[w:arrow keys|↑]] | down = ↓ | [[w:arrow keys|down]] = [[w:arrow keys|↓]] | left = ← | [[w:arrow keys|left]] = [[w:arrow keys|←]] | right = → | [[w:arrow keys|right]]= [[w:arrow keys|→]] | #default = {{{1}}} }}</span><noinclude> {{documentation}} <!-- Add categories and interwikis to the /doc subpage, not here! --> </noinclude> aas1jwxe2fkxyprx4jx2xmyv0btzz5t 0 1087 6589 6565 2010-04-22T08:36:43Z Triolan 1798 /* See also */ wikitext text/x-wiki A chronological '''list of proposals and ideas''', for the development of [[w:Wikipedia|Wikipedia]] and other [[w:Wikimedia Foundation#Projects, initiatives and chapters|Wikimedia projects]]. To become involved type your ideas and create an article for it, as a [[w:Wikipedia:Subpages|user subpage]]. Then link it to this list here: {| class="wikitable sortable" |- ! Article !! Notes !! User <!-- Please add new articles at the top --> |- | [[User:RW Marloe/Proposals for Wikimedia Development|Proposals for Wikimedia Development]] || Covering Wikipedia and general Wikimedia topics || [[User:RW Marloe|RW Marloe]] <!-- Please add new articles at the top --> |} ==See also== *[[Talk:Main Page|Main page discussions]] Why I can't download Shtirlitz from program page in Wikipedia? Is this such imporovement like you said in your program of initiative? by08ilrmzl4rhtevqjoaa8l8iblsqaa 10 1088 8657 7054 2010-07-29T13:33:00Z Nemo bis 9 cat wikitext text/x-wiki {| cellspacing="0" cellpadding="0" style="clear: {{{clear|right}}}; margin-bottom: .5em; float: right; padding: .5em 0 .8em 1.4em; background: none; width: {{{width|{{{1|auto}}}}}};" {{#if:{{{limit|}}}|class="toclimit-{{{limit}}}"}} | __TOC__ |}<noinclude> [[category:templates]] </noinclude> b9grhobmsoic01sc1q5slwkowf8njxf 10 1089 8644 6431 2010-07-29T13:29:08Z Nemo bis 9 cat wikitext text/x-wiki <includeonly>{{pp-meta |type={{#switch:{{{demolevel|{{#ifeq:{{PROTECTIONLEVEL:edit}}-{{PROTECTIONLEVEL:move}}|-sysop|move|{{PROTECTIONLEVEL:edit}}}}}}} |semi |autoconfirmed=semi |administrator |full |sysop=indef |move=move |#default=indef<!--fallback value-->}} |small={{{small|yes}}} |demospace={{{demospace|}}} |demolevel={{#ifeq:{{PAGENAME}}/{{NAMESPACE}}|{{SUBPAGENAME}}/{{ns:Template}}|{{{demolevel|undefined}}}|{{#ifeq:{{lc:{{SUBPAGENAME}}}}|sandbox|sysop|{{{demolevel|undefined}}}}}}} |expiry=<!--not applicable--> |dispute=no |icon-text=This {{#ifeq:{{NAMESPACE}}|{{ns:6}}|image, included in a high-risk template or message,|high-risk template}} is indefinitely {{#switch:{{{demolevel|{{#ifeq:{{PROTECTIONLEVEL:edit}}-{{PROTECTIONLEVEL:move}}|-sysop|move|{{PROTECTIONLEVEL:edit}}}}}}} |semi |autoconfirmed=semi-protected from editing |move=move-protected |administrator |full |sysop |#default=<!--fallback value-->protected from editing}} to prevent vandalism. |reason-text=This {{#switch:{{NAMESPACE}} |{{ns:image}}=image, used in one or more [[w:Wikipedia:High-risk templates|high-risk templates]]{{#switch:{{{demolevel|{{PROTECTIONLEVEL:edit}}}}} |semi |autoconfirmed= |administrator |full |sysop=<nowiki> </nowiki>and/or [[w:Special:Allmessages|system messages]], |#default=<!--fallback value-->}} |#default=[[w:Wikipedia:High-risk templates|high-risk template]] }} has been [[w:Wikipedia:This page is protected|{{#switch:{{{demolevel|{{#ifeq:{{PROTECTIONLEVEL:edit}}-{{PROTECTIONLEVEL:move}}|-sysop|move|{{PROTECTIONLEVEL:edit}}}}}}} |semi |autoconfirmed=semi- |move=move- |administrator |full |sysop<!--uses default--> |#default=<!--fallback value-->}}protected]]{{#ifeq:{{PROTECTIONLEVEL:edit}}-{{PROTECTIONLEVEL:move}}|-sysop||<nowiki> </nowiki>from editing}} to prevent [[w:Wikipedia:Vandalism|vandalism]]. {{#switch:{{{demolevel|{{PROTECTIONLEVEL:edit}}}}} |semi |autoconfirmed= |administrator |full |sysop<!--uses default--> |#default={{#switch:{{NAMESPACE}}|{{ns:image}}=<br /><small>'''Do not move this image''' to [[commons:|Wikimedia Commons]].</small>}}}} |categories={{{categories|{{#ifeq:{{NAMESPACE}}|{{ns:10}}|{{#switch:{{{demolevel|{{#ifeq:{{PROTECTIONLEVEL:edit}}-{{PROTECTIONLEVEL:move}}|-sysop|move|{{PROTECTIONLEVEL:edit}}}}}}} |semi |autoconfirmed=[[w:Category:Wikipedia semi-protected templates|{{PAGENAME}}]]{{#ifeq:{{PROTECTIONLEVEL:move}}|sysop|[[w:Category:Wikipedia move-protected templates|{{PAGENAME}}]]}} |move=[[w:Category:Wikipedia move-protected templates|{{PAGENAME}}]] |administrator |full |sysop<!--uses default--> |#default=[[w:Category:Wikipedia protected templates|{{PAGENAME}}]]<!--fallback value-->}}}}{{#ifeq:{{NAMESPACE}}|{{ns:6}}|[[w:Category:{{#switch:{{{demolevel|{{PROTECTIONLEVEL:edit}}}}} |semi |autoconfirmed=Semi-protected |administrator |full |sysop<!--uses default--> |#default=Protected<!--fallback value-->}} images|{{PAGENAME}}]]}}}}}}}</includeonly><noinclude> {{pp-template|categories=no}} <!-- Show the small version --> {{pp-template|small=no}} <!-- Show the large version --> [[category:templates]] </noinclude> l4ppe34hkrxjnn6cr0nndrldfetayhv 10 1090 8663 6432 2010-07-29T13:34:27Z Nemo bis 9 cat wikitext text/x-wiki {{#ifeq:{{#switch:{{lc:{{{type}}}}} |move=<!-- -->{{#ifeq: {{#switch:{{lc:{{{demolevel|undefined}}}}} |semi |autoconfirmed=autoconfirmed |administrator |full |sysop=sysop |undefined={{PROTECTIONLEVEL:move}} |#default=<!--fallback value: null -->}} |sysop|yes|no }} |create=<!-- -->{{#if: {{#switch:{{lc:{{{demolevel|undefined}}}}} |semi |autoconfirmed=autoconfirmed |administrator |full |sysop=sysop |undefined={{PROTECTIONLEVEL:create}} |#default=<!--fallback value: null -->}} |yes|no }} |#default<!--includes all other types-->=<!-- -->{{#if: {{#switch:{{lc:{{{demolevel|undefined}}}}} |semi |autoconfirmed=autoconfirmed |administrator |full |sysop=sysop |undefined={{PROTECTIONLEVEL:edit}} |#default=<!--fallback value: null -->}} |{{#ifeq:{{#switch:{{lc:{{{disallowlevel|}}}}} |semi |autoconfirmed=autoconfirmed |administrator |full |sysop=sysop |#default=<!--fallback value: null-->}} |{{#switch:{{lc:{{{demolevel|undefined}}}}} |semi |autoconfirmed=autoconfirmed |administrator |full |sysop=sysop |undefined={{PROTECTIONLEVEL:edit}} |#default=<!--fallback value: null -->}} |no|yes }} |no}} }}|yes|{{#ifeq:{{lc:{{{small|}}}}}|yes| <div class="metadata topicon" id="protected-icon" style="display:none; right:55px;">[[Image:{{{image|{{#switch:{{lc:{{{type}}}}} |full=Padlock.svg |semi=Padlock-silver-medium.svg |move=Padlock-olive.svg |indef=Padlock-red.svg |office=Padlock-black.svg |create=Padlock-skyblue.svg |#default=Transparent.gif }}}}}|20px|link={{{icon-link|Wikipedia:Protection policy#{{lc:{{{type}}}}}}}}|{{{icon-text|This {{pagetype|subjectspace=yes}} is {{#switch:{{lc:{{{type}}}}} |semi=semi- |move=move- |indef=permanently<nowiki> </nowiki> |create=creation- |office=<!--null, but should this have a special tag?--> |full |#default=<!--null--> }}protected{{#ifeq:{{lc:{{{type}}}}}|indef||{{#if:{{{expiry|}}}|<nowiki> </nowiki>until {{#time:F j, Y|{{{expiry}}}}}}}}}{{#if:{{{icon-reason|}}}|<nowiki> </nowiki>{{{icon-reason}}}}}.}}}]]</div> |<!-- else, not small --> {{mbox | demospace = {{{demospace|}}} | type = protection | image = [[Image:{{{image|{{#switch:{{lc:{{{type}}}}} |full=Padlock.svg |semi=Padlock-silver-medium.svg |move=Padlock-olive.svg |indef=Padlock-red.svg |office=Padlock-black.svg |create=Padlock-skyblue.svg |#default=Transparent.gif }}}}}|40px|{{{icon-text|This page is {{#switch:{{lc:{{{type}}}}} |semi=semi- |move=move- |indef=permanently<nowiki> </nowiki> |create=creation- |office=<!--null, but should this have a special tag?--> |full |#default=<!--null--> }}protected.}}}]] | text = '''{{{reason-text|{{#switch:{{lc:{{{type}}}}} |full=This page is currently [[w:Wikipedia:This page is protected|protected]] from editing |semi=Editing of this {{pagetype|subjectspace=yes}} by [[w:Wikipedia:User access levels#Autoconfirmed_users|new]] or [[w:Wikipedia:User access levels#Anonymous_users|unregistered]] users is currently [[w:Wikipedia:Protection policy|disabled]] |move=This {{pagetype|subjectspace=yes}} is currently [[w:Wikipedia:This page is protected|protected]] from [[w:Help:Moving a page|page moves]] |indef=This page is [[w:Wikipedia:This page is protected|protected]] from editing ''indefinitely'' |office=This {{pagetype|subjectspace=yes}} is currently [[w:Wikipedia:This page is protected|protected]] from editing |create=[[w:Help:Starting a new page|Recreation]] of this {{pagetype|subjectspace=yes}} [[w:Wikipedia:This page is protected|has been disabled]] }}{{#ifeq:{{lc:{{{type}}}}}|indef||{{#if:{{{expiry|}}}|&#32;until {{#time:F j, Y|{{{expiry}}}}}}}}}{{{reason<includeonly>|</includeonly>}}}.}}}'''<br /> {{{explanation-text|{{#ifeq:{{lc:{{{dispute}}}}}|yes|This protection is '''not''' an endorsement of the {{#ifeq:{{{type}}}|move|[{{fullurl:Special:Log|type=move&page={{FULLPAGENAMEE}}}} current title]|[{{fullurl:{{FULLPAGENAMEE}}|action=history}} current version]}}.}} See the [[w:Wikipedia:Protection policy|protection policy]] and [{{fullurl:Special:Log|type=protect&page={{FULLPAGENAMEE}}}} protection log] for more details. {{#switch:{{lc:{{{type}}}}} |full|indef=Please discuss any changes on the [[{{TALKPAGENAME}}|talk page]]; you may use the {{tlx|editprotected}} template to ask an [[w:Wikipedia:Administrator|administrator]] to make the edit if it is supported by [[w:Wikipedia:Consensus|consensus]]. {{#ifeq:{{NAMESPACE}}|{{ns:8}}<!--MediaWiki-->||You may also [[w:Wikipedia:Requests for page protection|request]] that this page be unprotected.}} |semi=If you cannot edit this {{pagetype|subjectspace=yes}} and you wish to make a change, you can {{#ifeq:{{NAMESPACE}}|{{TALKSPACE}}||[[w:Template:Editsemiprotected|request an edit]], [[{{TALKPAGENAME}}|discuss changes on the talk page]],}} [[w:Wikipedia:Requests for page protection#Current requests for unprotection|request unprotection]], [[w:Special:Userlogin|log in]], or <span class="plainlinks">[http://en.wikipedia.org/w/index.php?title=Special:Userlogin&type=signup <span style="color:#002bb8;" title="Sign in / create account">create an account</span>]. |move=The page may still be edited but cannot be moved until unprotected. Please discuss any suggested moves on the [[{{TALKPAGENAME}}|talk page]] or at [[w:Wikipedia:Requested moves]]. You can also [[w:Wikipedia:Requests for page protection|request]] that the page be unprotected. |office=If you are able to edit this page, please discuss all changes and additions on the [[{{TALKPAGENAME}}|talk page]] first. '''Do not remove protection from this article unless you are authorized by the Wikimedia Foundation to do so.''' |create=Please see the {{#if:{{{xfd|}}}|'''[[{{{xfd}}}|deletion discussion]]''' or the}} [{{fullurl:Special:Log|type=delete&page={{FULLPAGENAMEE}}}} deletion log] for details of why this page was deleted. If you would like to create a page at this title, you must first [[w:Wikipedia:Requests for page protection|request]] for it to be unprotected, or contact the administrator who deleted the page for the deleted material to be restored. If unsuccessful, you can use [[w:Wikipedia:Deletion review|deletion review]]. }}}}} }} }}|[[w:Category:Wikipedia pages with incorrect protection templates]]}}<!--End if small--><includeonly>{{#ifeq:{{lc:{{{categories|no}}}}}|no||{{{categories|}}}}}</includeonly><noinclude> [[Category:Templates]] </noinclude> 6zogkbvya6orx4i5oy0ksf0mp2jzn3u 10 1091 6433 2010-04-05T17:16:13Z RW Marloe 1482 Redirected page to [[Template:TOC right]] wikitext text/x-wiki #REDIRECT [[Template:TOC right]] tfpobd5x8b68zq6g7n1kinn14h0dhry 6 1092 6446 2010-04-05T22:15:44Z Howief (WMF) 1286 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 0 1093 6450 6449 2010-04-05T22:42:40Z Howief (WMF) 1286 /* Here's what we've recently launched: */ wikitext text/x-wiki We've been working hard to make things easier for our users. We're excited to share some improvements, including a new look and feel and simplified editing features. Improving the usability of the site is an ongoing effort here at Wikimedia and we'll be sharing more updates in the future. ==Here's what we've recently launched:== [[File:UsabilityNavigation.png|thumb|250px|Navigation]] *'''Navigation:''' We've improved the navigation for reading and editing articles. Now, the tabs at the top of each page more clearly define whether you're viewing the article page or discussion page, and whether you're reading or editing an article. <br style="clear: both;"/> [[File:UsabilityToolbar.png|thumb|250px|New Editing Toolbar]] *'''Editing toolbar improvements:''' We've reorganized the editing toolbar to make easier to use. Now, formatting articles is simpler and more intuitive. <br style="clear: both;"/> [[File:UsabilityDialogs.png|thumb|250px|Link Wizard]] *'''Link wizard:''' An easy-to-use tool allows you to add links to other Wikipedia articles as well as links to external sites. <br style="clear: both;"/> *'''Search improvements:''' We've improved search suggestions to get you to the article you're looking for more quickly. *'''Other new features:''' We've also introduced a table wizard to make creating tables easier and find and a replace feature to simplify article editing. bcgogsd4kxowcwdvg7salgwe4h17p9p 100 1094 6458 6455 2010-04-06T00:13:23Z Guillom 13 sort key wikitext text/x-wiki MediaWiki currently uses a [[:w:SHA-1 hash|SHA-1 hash]] to characterize the content of an uploaded file; such a hash is supposed to be unique for each file, and it allows to identify duplicates. However, this feature only identifies ''exact'' duplicates; it can't identify similar or derivative files. Some applications use identifiers like "fingerprints" or "signatures" based on image identification technology like [[:w:Haar-like features|Haar-like features]] to find and track similar pictures. For example, digiKam uses a "lengthy number using a special technique (Haar algorithm) that make it possible to compare images by comparing this calculated signature. The less numerical difference there is between any two image signatures, the more they resemble each other."<ref>[http://docs.kde.org/development/en/extragear-graphics/digikam/using-kapp.html#fuzzy-searches Using digiKam − Fuzzy Searches/Duplicates], digiKam documentation.</ref> A similar feature for MediaWiki (probably as an extension) would greatly benefit Wikimedia Commons by providing the ability to: * identify derivative works (e.g. an original image and a cropped version) * identify similar pictures (e.g. different pictures of the same object, specifying a threshold of similarity) * provide the basis for powerful search features, including "fuzzy search" (e.g. free hand color sketching) * facilitate the identification of objects and thus help with the classification of multimedia assets [[:w:digiKam|digiKam]] is released under the GPL. It offers a working implementation of image fingerprints in C++/Qt<ref>[http://api.kde.org/extragear-api/graphics-apidocs/digikam/html/namespaceDigikam_1_1Haar.html Digikam::Haar Namespace Reference], KDE 4.5 API Reference.</ref> based on a research article by Jacobs ''et al.''<ref>Charles E. Jacobs, Adam Finkelstein, David H. Salesin. [http://salesin.cs.washington.edu/abstracts.html#MultiresQuery Fast Multiresolution Image Querying]. Proceedings of SIGGRAPH'95, in ''Computer Graphics'' Proceedings, Annual Conference Series, pages 277-286, August 1995.</ref>. It also provides a fuzzy search feature<ref>[http://www.digikam.org/drupal/node/321 digiKam Fuzzy Search Tools Under Construction], digiKam blog, June 2008.</ref>. == Notes and references == <references/> [[Category:Multimedia usability - Specifications|File fingerprint]] 83w0fkipqq1wuu0atyx6oaufsrsc1sx 100 1095 9121 8674 2010-10-24T21:01:40Z 217.88.125.173 The script on commons was revamped completely, might be more interesting for you now wikitext text/x-wiki {{draft}} * [[bugzilla:5383]] - Inline slideshows Features * timer / manual navigation * play / pause * navigation (prev/next, maybe slider) * for lists (inline/full screen), categories & galleries (pop-up/overlay/full screen) * non-JS fallback? (manual navigation) Existing work * [[:commons:MediaWiki:Gadget-GallerySlideshow.js|MediaWiki:Gadget-GallerySlideshow.js]] on Commons * [[:en:n:MediaWiki:Ticker2.js|MediaWiki:Ticker2.js]] on the English-language Wikinews ([[:en:n:User:Bawolff/sandbox/ticker|example]]) * [[:mw:Extension:SmoothGallery|Extension:SmoothGallery]] for MediaWiki; per the author: "not jQuery based and "xml style tags are completely broken - so use parser function style tags"." ([http://ryandlane.com/wiki/SmoothGallery example]) [[Category:Multimedia usability - Specifications|Slideshow]] bt70n3khh1xw0443yyu8nqkeqp1zu5z 6 1096 6465 2010-04-06T02:22:03Z Shuhari 4 == Summary == Updated enhanced toolbar with new icons, created by Hannes Tank wikitext text/x-wiki == Summary == Updated enhanced toolbar with new icons, created by Hannes Tank 6fh320fri6bdw08hj9pz650es88ckvk 0 1099 6479 2010-04-07T00:11:40Z 216.38.133.254 Created page with '==Nimish's Notes== Former blogger uses wikipedia as "dictionary" Search: tries to search for article categories Wikitext bothers her (too much markup) Minor edit confusion s...' wikitext text/x-wiki ==Nimish's Notes== Former blogger uses wikipedia as "dictionary" Search: tries to search for article categories Wikitext bothers her (too much markup) Minor edit confusion selected sentence to put ref tags on it Expects media wizard section edit thinks template is an external link DESPITE styling to not look like a link looks at leftnav for 'create page' mslz38uxohe02bzo1tkahbb9ja2s5fr 0 1100 6483 2010-04-07T00:18:01Z 216.38.133.254 Created page with '== Nimish's Notes == References -> tries to make it HTML b/c it looks like HTML tags Gets confused with the template capsule Recognizes need for discussion page so it's not an ...' wikitext text/x-wiki == Nimish's Notes == References -> tries to make it HTML b/c it looks like HTML tags Gets confused with the template capsule Recognizes need for discussion page so it's not an "edit war" Infoboxes: expect a 'section edit' "really not sure how to get into that" "throws me off that they have 2 ways to view the same thing" "makes me wonder if one way is better than another" "summary saying 'substantial vandalism' helped me" 2b4juepi95dtigkds8d272gziq63zlt 0 1101 6488 2010-04-07T00:24:50Z 216.38.133.254 Created page with '== Nimish's Notes == No experience with HTML All-blacks rugby fan =) "a whole bunch of computery looking things" -> "oh no wait" (after NTOC and stuff showed up) DEF less inti...' wikitext text/x-wiki == Nimish's Notes == No experience with HTML All-blacks rugby fan =) "a whole bunch of computery looking things" -> "oh no wait" (after NTOC and stuff showed up) DEF less intimidated after other stuff appeared Added wiki page link and clicked "internal" again...bottom option seems too confusing 'adding section' -> doesn't think it's automatic (thinks headings are a formatting issue) smtozvp5qg0yg73yojhz8dit21yg6xp 100 1102 6511 6506 2010-04-07T23:04:59Z Guillom 13 draft wikitext text/x-wiki {{draft}} MediaWiki currently provides a way to see the edits of a user using the Special:Contributions page (see for example [[Special:Contributions/guillom]]). File uploads are registered as regular edits and show in the "Contributions" page. However, this system is not appropriate for media files, which would benefit from a more visual approach, especially for media libraries like Wikimedia Commons. Currently, such pages are maintained manually by some users in a subpage of their userpage. The proposed implementation would be a new special page like Special:Gallery/username basically working like Special:Contributions, but displaying thumbnails of the media files uploaded. == Existing work == * [[:mw:Extension:User Image Gallery|Extension:User Image Gallery]] * [http://toolserver.org/~daniel/WikiSense/Gallery.php?wikifam=commons.wikimedia.org&img_user_text=Guillom Gallery tool] on the toolserver [[Category:Multimedia usability - Specifications|User gallery]] 6fe77hsx1s3lkwjg3gon3eaj3lry9fy 100 1103 6510 2010-04-07T22:57:14Z Guillom 13 notes wikitext text/x-wiki {{draft}} * Integrated into MediaWiki (possibly as an extension) * Reusable format (possibly embeddable into XMP file metadata in the future). == Existing work == * [[:commons:Help:Gadget-ImageAnnotator|Help:Gadget-ImageAnnotator]] on Commons ([[:commons:MediaWiki:Gadget-ImageAnnotator.js|code]]) == Reference documents == * [http://www.w3.org/2005/Incubator/mmsem/XGR-interoperability/ Multimedia Annotation Interoperability Framework], W3C Incubator Group Editor's Draft, 14 August 2007 * [http://www.w3.org/2005/Incubator/mmsem/XGR-image-annotation/ Image Annotation on the Semantic Web], W3C Incubator Group Report 14, August 2007 * [http://websvn.kde.org/?revision=1048077&view=revision Document for discussing ideas for image annotation and face recognition.], Michael G. Hansen, 2009-11-12 ([http://websvn.kde.org/*checkout*/trunk/extragear/graphics/digikam/project/ImageAnnotation.odt?revision=1048077&pathrev=1048077 download ODT file)], part of a general discussion about [https://bugs.kde.org/show_bug.cgi?id=146288 Face recognition feature] == Other resources == * [http://code.google.com/p/jquery-image-annotate/ jquery-image-annotate], An Image Annotation plugin for jQuery * [http://www.fotonotes.net/ Fotonotes] * [http://www.fototagger.com FotoTagger] [[Category:Multimedia usability - Specifications]] gbdad4tumvhufmajuxd8e5jet28a1br 0 1105 6517 2010-04-08T23:35:30Z 130.86.196.173 + wikitext text/x-wiki {{softredirect|m:Vector}} jniqg4zhee4sxdk289ale8nm15nvx8r 100 1106 6518 2010-04-09T00:45:22Z Guillom 13 cat wikitext text/x-wiki [[Category:Multimedia usability - Specifications|Location editor]] t4zm2dxn43mx7t888bni2ch0w96mmpb 6 1109 6526 2010-04-10T23:17:09Z Nux 319 bar by me (PD), rest by usability team wikitext text/x-wiki bar by me (PD), rest by usability team 03rmz2setwyo88r2ztpad14y6p2cxgu 100 1111 6540 6538 2010-04-14T22:29:15Z Guillom 13 +1 wikitext text/x-wiki * [http://museum-api.pbworks.com/ Museums and the machine-processable web] ** [http://museum-api.pbworks.com/Science-Museum-linked-data Science Museum linked data] * [http://www.tate.org.uk/research/tateresearch/tatepapers/10spring/stack.shtm Tate Online Strategy 2010–12] * [[:w:en:Wikipedia:Advice for the cultural sector|Wikipedia:Advice for the cultural sector]] * [[:wikia:museums:Wikimedia@MW2010|Wikimedia@MW2010]] on the Museums Wiki * [[:wikia:museums:Wikimedia@MW2010 (Model projects)|Wikimedia@MW2010 (Model projects)]] on the Museums Wiki * [[:w:en:Wikipedia:Culture|Wikipedia Cultural Embassy project]] ** [[w:en:Wikipedia:Culture/NYPL|Wikipedia:Culture/NYPL]] * [[:w:en:User:Ham/250 paintings|User:Ham/250 paintings]] * [http://conference.archimuse.com/biblio/term/mw2010/ Bibliography] of MW2010 [[Category:Multimedia usability]] 1o3k4d97e0djbxjtcbrhie4isyw15uk 6 1113 6543 2010-04-15T02:37:58Z Shuhari 4 == Summary == == Summary == wikitext text/x-wiki == Summary == == Summary == jqetmo861tdwj37yx60et3afhxaees2 0 1116 6548 6547 2010-04-15T23:17:09Z 216.38.133.254 wikitext text/x-wiki We've been playing around with expanding and collapsing templates in our [http://prototype.wikimedia.org/sandbox.6 sandbox], play around with them and leave feedback on [[Talk:Template feedback|this talk page]] qu38apugj7ud574lox5nibd9bgbkp4r 0 1119 7535 6567 2010-06-07T22:55:52Z Node ue 806 wikitext text/x-wiki Some early thoughts: When considering Wikimedia projects, internationalism and cross-cultural issues should not just be "considerations", they should be at the core of the mission. I think most of the people participating here, if they use Wikipedia for something, would feel most comfortable using the English Wikipedia. However, for approximately '''half''' of our users, this does not seem to be the case. We are biased as speakers of English. Imagine if the entire world was ruled by one government, but the decisions were made based on opinion polls conducted only in Iran... Wikimedia is a diverse and inclusive community. Within our community, there are many editors and even more readers who do not speak a word of English. Important first steps: * Research :* There's been some good research done so far for English-speaking Wikipedians. Now how about the other half of our readers and contributors? * Discussion :* Although I'm sure that in principle, contributions here in languages other than English would be welcomed, in practice, this seems unlikely to happen as the interface and all of the pages are written in English. Thus, non-English-speakers are excluded from the process. I realize that it would be extremely difficult to get full involvement from speakers of all 250+ languages used in our community, but we could at least reach out to and find a way to include some of the larger non-English communities. * Consideration :* Non-English-speakers should not be a mere afterthought in this initiative, they should be a core consideration at every step of the way. The multilingual and multicultural nature of our project presents many unique challenges, but it is at the core of our mission and so cannot and should not be treated as a secondary phenomenon. ([[User:Node ue|Node ue]] 22:55, 7 June 2010 (UTC)) bb6nwhz7yjmk6ncvf6j2m92adxkx71j 0 1123 9127 9126 2010-10-25T11:44:26Z Lecartia 870 Undo revision 9056 by [[Special:Contributions/90.214.125.185|90.214.125.185]] ([[User talk:90.214.125.185|talk]]) wikitext text/x-wiki {{Accessibility Initiative navigation}} As the '''Wikimedia Accessibility Initiative''' (WAI) we want to coordinate efforts towards accessibility globally. This page intends to be the point of contact for people interested in the accessibility of Wikimedia projects. As we understand accessibility as a natural part of usability, we have chosen the Usability wiki to host all our upcoming pages related to accessibility. Accessibility still has little significance on the agenda of the Wikimedia Foundation. There is no official project dedicated to accessibility. Accessibility bugs submitted to Bugzilla are often assigned a low importance and, thus, are never fixed. From our past experiences we have learnt that local efforts only don’t have the desired impact. The few accessibility advocates are not heard. But if we care about language communities with 10.000 speakers, we definitely must take care about millions of disabled. Therefore, we established the Wikimedia Accessibility Initiative as the global advocate of accessible Wikimedia projects. We want to set up an active group of experts that provides consistent and coordinated recommendations, rather than providing feedback as individuals with occasional and possibly divergent opinions. We want to collect, document and comment on global [[accessibility issues]], i.e. issues within MediaWiki and within common extensions, and of course provide solutions for found problems. We want to learn from successful local projects and provide [[best practices]] for local projects and for developers. We also want to create and then propose a high-level [[accessibility policy]] to the Wikimedia Foundation. The Accessibility Initiative can only be successful, if enough dedicated people participate. Naoko Komura, Head of UX Programs, has once phrased it nicely: We need to build enough momentum. We hope you join our efforts when reading this page. == Importance of accessibility == Why is accessibility of major importance to Wikimedia? Let us give you some statistics. According to the WHO report there are 161 million visually impaired world-wide including 37 million blind. In Germany alone we have 80.000 deaf using sign-language. A survery of the German Aktion Mensch found that deaf, people with learning disabilities, with mental disabilities or with dyslexia use wikis much less than people with other impairments. Collaboration is even lesser. Wikis are too complicated for them, because they don’t find information in the form they need, e.g. simple sentences or sign-language videos. The fact is: We know too little about what prevents people with disabilities to use Wikimedia projects, and, even more important, to participate. Even more overlooked are disabled people in the third world. Typically having no AT products at all, they need special support, e.g. a self-voicing Wikipedia (see discussion “[[Talk:Releases/Acai#Speak_to_the_blind.3F|Speak to the blind]]”). Wikipedia was the third most favorite website for screen reader users in early 2009 (see [http://www.webaim.org/projects/screenreadersurvey/ WebAIM survey]). == Scope of work == In the following you find the fields in which we want to contribute. If you have other ideas or comments that don’t fit into this classification, please share them nonetheless. === Strategic planning === We want to analyse the current [[accessibility strategy]] within Wikimedia project and within the Wikimedia Foundation, and work out strategic plans for both. This topic was raised during the strategic planning process of the Wikimedia Foundation, see the [[strategy:Proposal:Create_an_accessibility_committee|proposal to create an accessibility committee]] and the lean category on [[strategy:Category:Proposals_for_improving_accessibility|proposals for improving accessibility]]. Eugene, of Blue Oxen, [http://strategy.wikimedia.org/w/index.php?title=Talk:Strategic_Plan/Movement_Priorities&offset=20100511225134#Encourage_Diversity:_For_people_with_disabilities_4987 asks us to] “[…] think at a movement-level. In other words, don’t just think about what the Wikimedia Foundation can do to improve accessibility. Think about what partners, the community at large could do.” === Proposal of accessibility policy === As a concrete goal within developing an [[accessibility strategy]] we want to propose a high-level [[accessibility policy]] for the Wikimedia Foundation. Accessibility must become an accepted and communicated goal of the Foundation. === Best practices === [[Best practices]]: found by local initiatives === Feedback on prototypes === One goal is to provide feedback on the prototypes of the UX team, so we have fairly accessible tools before conducting an accessibility audit. * [[Prototype]] (editing) * http://commons.prototype.wikimedia.org/js2/Special:UploadWizard (upload) === Feedback on accessibility issues === [[Accessibility issues]]: throughout all Wikimedia projects, MediaWiki core code and extensions == What can you do? == '''Join our initiative.'''<br />Let us know you are involved with accessibility. Put your name on the particpants list, or leave a note on the talk page, or visit us in the IRC channel, or get in contact with a trusted particpant. '''Spread the word.'''<br />Advertise the Wikimedia Accessibility Initative so that people become aware and possible join our efforts. You can write blog postings (e.g. [http://blog.wikimedia.fr/focus-sur-laccessibilite-1624 French] and [http://blog.wikimedia.de/2010/04/21/barrierefreiheit-international/ German] Wikimedia blog), write a note at your local initiatives, talk to people you know who are interested in accessibility etc. '''Share your ideas.'''<br />Put down and discuss your ideas either on the (talk) pages or in the IRC channel. You can also send an email to the above stated participants. They will be glad to answer questions or to receive your input. '''Report issues.'''<br />If you are aware of accessibilty issues in Wikimedia projects report them. Only what is known can be fixed. Leave a short explanation on the [[accessibility issues|issue page]] or contact any of the initiative’s participants. '''Fix issues.'''<br />If you are able to fix existing accessibilty issues, do so! '''Get support.''' '''Propose best practices.'''<br />If you have experience from you local accessibility initiatives or from your own efforts, note them down in the [[best practices]] page. '''Improve these pages.'''<br />When you find information gaps, bad wording, poor examples or just wrong spelling or grammar, go ahead and improve our pages. After all, this is a wiki. == Coordination == We have set up the irc channel [irc://chat.freenode.net/wikimedia-accessibility #wikimedia-accessibility] for internal coordination and questions. If you find no one present, do send an email to one of the participants. Other channels like [irc://chat.freenode.net/wikipedia_usability #wikipedia_usability] may be used as well for discussion. === Participants === Of course, you don’t have to put yourself in a list to advocate accessibility. But it could be helpful for others in order to find a contact person, for general enquiries, or for support in local projects. * Danny, user [[User:Danny B.|Danny B.]] * Rodan Bury, user [[user:Dodoïste|Dodoïste]]: Rodan is a member of the French accessibility project. He’s sometimes also working on the English Wikipedia. He is interested in usability, accessibility and web standards in general. * Samuel Klein, user [[User:Sj|sj]] * Maria Schiewe, user [[User:Lecartia|Lecartia]]: Maria is an ordinary board member of Wikimedia Deutschland. In 2009 Wikimedia Deutschland’s board agreed on [[m:Kompass_2020/Usability/Technik|three goals regarding accessibility and usability]] until 2020. (One objective: Wikimedia is a reference example of web accessibility and usability.) These goals were approved by the general assembly in 2010.<br />Maria is an employee of a manufacturer of assistive technology (Braille displays etc.) and currently works as an accessibility consultant for a German public authority. Before that, she was a research associate developing two-dimensional haptic user interfaces. Maria’s expertise and knowledge focuses on blind and visually impaired users. But she also has a strong interest in the needs of deaf users. * User [[User:Reaperman|Reaperman]] === Local initiatives === These are the local initiatives we are currently aware of, grouped by language. Apart from a global Accessibility Initiative we need strong local ones. Often local projects fail because there are too few people involved. So please join and support them, if you are interested. * Czech Wikipedia: [[:cs:Wikipedie:WikiProjekt Přístupnost|WikiProjekt Přístupnost]] * English Wikipedia: [[:en:Wikipedia:WikiProject Accessibility|WikiProject Accessibility]] * French Wikipedia: [[:fr:Wikipédia:Atelier accessibilité|Wikipédia:Atelier accessibilité]] * German Wikipedia: [[:de:WP:BIENE|Wikipedia:BIENE]] * Italian Wikipedia: [[:it:Wikipedia:Accessibilità del contenuto|Wikipedia:Accessibilità del contenuto]] (since 2004) * [[:he:ויקיפדיה:נגישות]] * [[:ja:Wikipedia:アクセシビリティ]] * [[:pt:Wikipedia:Acessibilidade]] == Actions taken == At Wikimania Rodan will gave the [[wm2010:Submissions/First_steps_towards_accessibility|presentation “First steps towards accessibility”]], summarizing the findings of a French accessibility expert regarding MediaWiki and Wikimedia. Complementary, Danny and Maria run the [[wm2010:Submissions/Accessibility_Workshop|hands-on workshop “Hear and feel your MediaWiki code at work”]]. Maria has nominated the German Wikipedia for an [http://www.biene-wettbewerb.de/ accessibility award called BIENE]. The results will be presented in December 2010. Although our chances of winning are low, we will receive an extensive report of accessibility issues found by the expert testers. Wikimedia Germany is in contact with the German Central Library for the Blind (DZB), who have had a look at Vector's accessibility. Some results can be found at [[mw:Accessibility]]. == Resources == === Recommended reading === * Shawn Henry: ''Just Ask: Integrating Accessibility Throughout Design''. ISBN 978-1430319528, also available online at [http://www.uiaccess.com/JustAsk/ www.uiaccess.com/JustAsk/] *: Shawn Henry from W3C explains in detail how to include accessibility into user-centered design and how to include disabled participants into testing. Her guiding principle: “Just ask people with disabilities. They are a key resource for improving accessibility.” A must-read. * Joe Clark: ''Building Accessible Websites''. available online at [http://joeclark.org/book/ joeclark.org/book/] *: from 2002 and, hence, a bit outdated, but still offers good insights into accessibility * WC3 WAI: ''[http://www.w3.org/WAI/eval/ Evaluating Web Sites for Accessibility]''. * [http://www.d.umn.edu/itss/support/Training/Online/webdesign/accessibility.html#useaccess extensive link list compiled by the University of Minnesota Duluth], has an informative link on almost every accessibility topic * [http://www.iit.cnr.it/en/node/1982 Editing Wikipedia Content via Screen Reader: Easier Interaction with ARIA], Marina Buzzi. And related user testing [http://www.iit.cnr.it/en/node/2307 Enhancing Wikipedia Editing with WAI-ARIA], Caterina Senette, Maria Claudia Buzzi, Marina Buzzi. === Personas === Personas allow you to understand the needs of users better and keep them in mind throughout the whole design process. Instead of refering to a dubious “user” you have one or several specific characters. * [http://www.aegis-project.eu/index.php?option=com_content&view=article&id=63&Itemid=53 13 personas covering a wide range of disabilities] provided by the Ægis project, licensed under CC-SA 3.0 * [http://diveintoaccessibility.org/table_of_contents.html 5 personas with different disabilities] by Mark Pilgrim from his book “Dive into Accessibility”, licensed under GNU FDL 1.1+ === Assistive technology === It’s a good idea to test with assistive technology (AT) on a virtual machine (VM). Most AT products offer a “demo mode”, i.e. they run fully functional for a specified time, but you need to re-boot your system after this time has elapsed. Therefore, VM come in handy. Don’t install various AT products alongside as they can interfere. Better use one VM for one product. The article ''[http://yuiblog.com/blog/2008/12/30/configuring-screen-readers/ Configuring Your Machine For Testing With A Screen Reader]'' explains how to set up your VM and how to configure JAWS, Window-Eyes, and NVDA for your testing. ==== Screen reader ==== Screen readers are great to get an idea on how blind users navigate through a page. It's great for demonstration. Be aware however that their implementation vary, and they can't be used to accurately measure the accessibility of a page. Use W3C's guidelines instead. * JAWS: JAWS is the most widely used screen reader in North America and Western Europe. It’s current version 11 is available from [http://www.freedomscientific.com/products/fs/jaws-product-page.asp Freedom Scientific]. Without an authorisation code JAWS runs as a 40 minute demo. Be sure to run the “Braille Viewer” alongside to see the Braille display’s output in normal script. * NVDA: article by WebAIM [http://www.webaim.org/articles/nvda/ Using NVDA to Evaluate Web Accessibility] * Supernova * Window-Eyes * [http://www.apple.com/accessibility/voiceover/ VoiceOver], built into Mac OS X and iPhoneOS (iOS). * … ==== Screen magnifier ==== * Lunar (or Supernova) * ZoomText * … === Testing tools === * [https://addons.mozilla.org/de/firefox/addon/402 Fangs] for Firefox: Fangs is a screen reader emulation that basically mimics the popular screen reader Jaws. It shows the typical speech output of a page as text and also provides a list of headings and a list of links. A very light-weight, easy-to-use tool for basic inspection. * [https://addons.mozilla.org/de/firefox/addon/5809 Firefox Accessibility Extension] for Firefox: includes useful lists for navigation, list of text equivalents etc. * [http://www.visionaustralia.org.au/info.aspx?page=614 Web Accessibility Toolbar] for IE5+ * [http://www.vischeck.com/ Vischeck] allows to simulate how the page or picture is seen by people with specified kind of color blindness. ==See also== *[[w:en:Wikipedia:Manual of Style (accessibility)]] (and interwikis) [[Category:Accessibility]] ofme94zt6omgrhwuoaj6d1y5fyyotzu 14 1124 8789 8667 2010-08-16T04:10:56Z Nemo bis 9 strategy wikitext text/x-wiki This category hosts all pages related to accessibility. See also [[strategy:Category:Accessibility]]. [[Category:Root]] 6lobfqtr2wbip56hhh9sz9fn0mcruvi 0 1125 8748 8747 2010-08-09T11:07:25Z Lecartia 870 /* Vector Issues */ typography wikitext text/x-wiki {{Accessibility Initiative navigation}} This page should contain an overview of our collected issues regarding [[accessibility]]. Our plan: # We add separate pages for each accessibility issue with a detailed description and possibly a possible patches. (Bugzilla is not the best place for doing this, because possibilities and participants are limited.). # We sort or group the issues regularly and prioritize them according their impact. # We then point the UX team or responsible developers to the issues in order of the chosen priority. (Then we will probably add the issues in Bugzilla to keep track of the fixes.) Even though there are already a couple of accessibility bugs submitted to Bugzilla, they are often assigned a low importance and, thus, are never fixed. Maybe we can have an ''Issue of the Week'' we focus on and that we discuss in the chat. == Report template == A page reporting an issue may contain the following: * short description * long description * documentation of failure (screenshot, speech output…) * links to resources from accessibility professionals, or guidelines ([[:en:WCAG 2.0|WCAG 2.0]], [http://www.webaim.org/standards/508/checklist WebAIM's cheklist], [http://www.dhs.state.il.us/page.aspx?item=32765 IITAA] and their [http://www.dhs.state.il.us/IITAA/IITAAWebImplementationGuidelines.html accessibility guidelines]...) * working example: an example of similar functionality elsewhere that is accessible * … == Vector Issues == *Search button not accessible (background image without alt text), see [http://www.w3.org/TR/WCAG20-HTML-TECHS/H36.html H36: Using alt attributes on images used as submit buttons] and [http://www.w3.org/TR/WCAG20-HTML-TECHS/G196.html G196: Using a text alternative on one item within a group of images that describes all items in the group]. Seems to be partially fixed by Danny B in [[Bugzilla:24401]]. The name of the button could be improved by setting it to “search” instead of the generic and unhelpful “button” (replace <code>name="button"</code> by <code>name="search"</code>). * Vector edit toolbar: “heading” listbox tabindex not as expected * ([[bugzilla:24298|bug 24298]]) Vector – tabs: drop-down menu is keyboard inaccessible or at least not accessible as expected, Maria: can’t open menu via keyboard at all * Edit toolbar can't be used without pointing device. See details on talk page : [[Talk:Accessibility issues#Accessibility of the toolbar|Accessibility of the toolbar]]. * Enhanced edit toolbar has menus accessible via keyboard but all buttons are inaccessible without pointing device. == MediaWiki Core == === Captcha === http://en.wikipedia.org/wiki/User_talk:Jimbo_Wales/Archive_37#Wikipedia_and_Captcha === Structure === * [[/WAI-ARIA landmarks]] * <nowiki>:</nowiki> generate a <code>dd</code> list, but <nowiki>:</nowiki> are not used for definitions but for indentation of the text, <code>dd</code> is misused here, better to use nested or intended paragraphs ([[bugzilla:4521|bug 4521]]) ==== Headings ==== * all navigation headings are level 5 for no good reason ([[bugzilla:457|bug 457]]) * [edit] should not be part of any h (see screenshot for effect on list of links) ([[bugzilla:1629|bug 1629]]) * … ==== Labels ==== * firstHeading labelfor editing field (editform) === Keyboard interaction === * Expand button <code>[+]</code> inserted by CategoryTree extension is inaccessible with keyboard. === Other / unsorted === * ([[bugzilla:23595|bug 23595]]) Suggest window expands outside the screen, it should have fixed right position and expand to the left, reported by Danny B. * ([[bugzilla:24544|bug 24544]]) Completely inaccessible watchlist tab == MediaWiki Extensions == == Upload tool == * buttons for interaction, not links == Success stories == [[mw:Special:Code/MediaWiki/tag/accessibility|All accessibility related patches to MediaWiki]] Fixed problems we reported. * [[bugzilla:23428|Bug 23428: Headers of collapsible (sub)menus in sidebar not accesible via keyboard]], reported by Danny B. ** <small>However, sidebar still doesn't have expected focus order.</small> * [[/“From Wikipedia …” is no heading|“From Wikipedia …” is no heading]] - fixed in [[rev:69545]], [http://de.wikipedia.org/w/index.php?title=Wikipedia:Projektneuheiten&curid=3180504&diff=76958376&oldid=76951191 thanks to Danny B.] for the patch. [[Category:Accessibility]] cikvb7j3oah04ggy0nvj122enfwxiwq 0 1126 7961 6667 2010-06-20T10:19:40Z Lecartia 870 user-generated content wikitext text/x-wiki Here we want to work on the [[accessibility]] policy that should be proposed to the Wikimedia Foundation. In a nutshell the policy should say: The Wikimedia Foundation takes care of accessibility seriously. Any action towards better accessibility is supported e.g. meeting Section 508 or WCAG 2.0. Any action against accessibility is e.g. something like you’d break one of the five pillars. == Preamble == * MediaWiki pretty accessible because mostly plain text and some images used * … user-generated content: has to follow guidelines for … [[Category:Accessibility]] jobvu3qonhs217fs52wv0kq4c1a242i 0 1129 6769 6768 2010-05-01T16:49:53Z Mephiles602 621 /* Suggestion */ wikitext text/x-wiki == Short description == “From Wikipedia, the free encyclopedia” is tagged as <code><nowiki><h3></nowiki></code>, but it does not serve as a heading. Hence, the <code><nowiki><h></nowiki></code> element is misused. The [https://bugzilla.wikimedia.org/show_bug.cgi?id=457 bug 457] from 2004 is directly related to this issue. == Resulting problem == Headings are used for quick navigation and for list navigation by blind users. … The list will look like this: * Article name 1 * From Wikipedia, the free encyclopedia 3 * … * References 2 * External Links 2 * … ==Suggestion== Either replace the <code><nowiki><h3></nowiki></code> around “From Wikipedia, the free encyclopedia” with a <code><nowiki><span></nowiki></code> or put it at another place altogether. Another possibility is to use the HTML5 solution. <code><nowiki><hgroup><h1>Accessibility</h1><h2>From Wikipedia, the free encyclopedia</h2></hgroup></nowiki></code>. --[[User:Mephiles602|Mephiles602]] 16:49, 1 May 2010 (UTC) == Step-by-step instruction == * go to http://en.wikipedia.org/wiki/WAI-ARIA or any other article * with Fangs ** right click on the page, select “View Fangs” ** go to the tab “Headings List” * with Jaws ** … [[Category:Accessibility]] fxn88bmy4i8v6kyv4wuxxsn23kdoie8 0 1131 6658 2010-04-24T09:32:05Z Lecartia 870 moved [[Accessibility]] to [[Accessibility Initiative]]: name of our movement wikitext text/x-wiki #REDIRECT [[Accessibility Initiative]] t5m8tnibvv6av4vupft4vqhfjm6z9n0 0 1133 8592 8411 2010-07-28T11:25:17Z Dodoïste 287 {{Accessibility Initiative navigation}} wikitext text/x-wiki {{Accessibility Initiative navigation}} The proposals for best practices are not rated yet, so they are by no means official recommendations by us. We will first collect proposals and discuss them. * Let people generate accessible content without knowing about it. That means: accessible templates, accessible tables generated from the toolbar’s dialog etc. * Enforce accessibility. Many people do not care about accessibility unless it’s somehow enforced, either by law, rules, or other kind of agreements. Otherwise they commonly behave like: “Look that article also has blue on blue text, why can’t mine have it so?” * List common accessibility sins. Name them, and explain why they are sins. Also provide common ways how to fix them. It do is some kind of propaganda. People need to hear and see everywhere that blue on blue is evil. proposal by WereSpielChequers on Wikimania: make accessibility criterion for Featured Articles, not by adding them to criteria list but by participating in the commenting on/voting of the nominated articles [[Category:Accessibility]] p8r1xk1alpi2g3tn84s6wadsyxcbpyv 100 1141 6742 6741 2010-04-29T22:45:34Z Guillom 13 not doing that right now, see office wiki for details wikitext text/x-wiki ==Upload Wizard== ===Present=== [[User:Shuhari|Naoko Komura]], [[User:Guillom|Guillaume Paumier]], [[User:NeilK|Neil Kandalgaonkar]] ===Splitting up licensing and upload details=== NeilK argued that the current licensing interface is too complicated. He argued that licensing should not be combined with all the other information, nor should there be licensing "overrides" where some uploads on the page use the deed chooser at the top of the page, and others are set individually. Demonstrated current interface which implements desired behaviour and argued was too complicated. NeilK suggested another interface where licensing is optionally set for all uploads in a separate step. This also means that the anticipated "Incomplete Uploads" page would not be exactly identical to step 2 of the Upload Wizard, but NeilK & Guillaume have worked out an alternative batch interface (just mockups so far). With demos, argument accepted tentatively by Naoko & Guillaume, but everyone would like to see the 4 step process ASAP before we do anything else to see if our intuitions are correct. NeilK estimates this will take 1-2 days. ===Validation and Help=== All agree the form needs some help or other examples, as well as corrective messages when the user does incorrect input. For the most part, we prevent the user from even being able to input anything incorrectly, but for the cases where we do, we will use the following principles: * Tooltips and errors take the form of a floating "post-it note" with a small triangle sticking out of one edge, pointing at the field in question. Tooltips will be a neutral color, errors will be reddish. * When a field has focus, show a tooltip with an example or other helpful information about how to fill out the form. (Deferred: It should be possible for expert users to indicate that they don't want to see these any more.) * When content can be analyzed for errors, give instant or near-instant feedback upon entering data (such as the filename field, which automatically checks for uniqueness) * If field is blank, give error feedback upon the user trying to submit, with a similar tooltip * When an error is caught, outline the field in red and show an error "post-it". Do not wait for user to give the field focus to show this. If the "post-it" is longer than one line, show some interface widget to expand it (do not allow these error post-its to "overlap"). These messages should be brief. If we want to get discursive, we may also include a button in the tooltip to pop up a modal dialog to explain further. * If errors are not caught somehow before submission, be ready to populate the form with errors detected server-side. What needs tooltip help? * Title * Description * Source * Author * License (?) * Date (explain that it should be date photo was taken, picture painted, etc.) * Location * Categories * Other information What kinds of error messages might occur? * Title too short * Title too long (or truncated) * Title is not acceptable (common autogenerated filename, not descriptive -- viz. feature on Commons today) * Title is already taken by another filename (show interface similar to Add Media Wizard; thumbnail with option to overwrite that image). :* n.b. we will always allow uploading of an image, even if it has a title which is the same as another. Currently accomplished by secretly uploading the file with an autogenerated filename, then changing the name to the desired one later on in the wizard; this approach may not be suitable for final version of app * Need at least one description, of a reasonable length * Description too short * Description too long (or truncated) * Date in improper format * Other information... ?? bad wikitext? * Source too short * Source too long (or truncated) * ?? Source bad URL (if appears to be an inaccessible or broken URL?) * Author too short * Author too long (or truncated) * Failed to select license * Signature too short * Signature too long * ... probably others Guillaume suggested that the title could sometimes be derived from description, but no one could agree on the semantics of when this would occur, so the idea was shelved for now. ===Category Widget=== Nice to have. This is already available in AMW. ==Next steps== NeilK * get a four-step process working (ASAP, by Tuesday) * work on remaining TODOs in Multimedia Wizard tech notes, such as links from the thank you page, other layout issues * work on other features discussed above: validation, help tooltips [[Category:Multimedia usability - Meetings]] gdwj31rxvqdvigsu4n7pmb62zk4nf7v 0 1145 6771 6770 2010-05-02T12:34:09Z Lecartia 870 + [[Category:Accessibility]] wikitext text/x-wiki == Universal accessibility and Wikipedia, same goal? == <blockquote cite="http://www.w3.org/Consortium/mission">"The social value of the Web is that it enables human communication, commerce, and opportunities to share knowledge. One of W3C's primary goals is to make these benefits available to all people, whatever their hardware, software, network infrastructure, native language, culture, geographical location, or physical or mental ability."</blockquote> <p style="margin: -1em 0 1em 60px;">—&#160;Tim Berners-Lee, W3C</p> <blockquote cite="http://interviews.slashdot.org/article.pl?sid=04/07/28/1351230">"Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge. That's what we're doing."</blockquote> <p style="margin: -1em 0 1em 60px;">—&#160;Jimmy Wales</p> (temporary diagram) Content ----------X----------> Visitors Content -----> Machines -----> Visitors ^ Web browser Screen reader [http://www.google.com/support/webmasters/bin/answer.py?hl=en-uk&answer=70897 Robots] [http://translate.google.fr/translate?prev=hp&hl=fr&js=y&u=http://en.wikipedia.org/wiki/Web_accessibility&sl=en&tl=fr&history_state0= Translators] Etc. There is more to Accessibility than being usable by people with disabilities. Accessibility is an occasion (lever?) to improve a website's global quality. Through better semantics and standards, the website's content becomes understandable by machines. It eases the reuse of the content, indexation by googlebot and the likes, usage of the website through various devices (mobiles...)... *Reduces the bandwidth (saves money!), *Useful for elders too, *People using low bandwidth *... http://openweb.eu.org/articles/accessibilite_numerique_pourquoi/ http://openweb.eu.org/articles/fructifions_donnees http://blog.temesis.com/post/2006/10/31/193-vulgariser-l-accessibilite [[Category:Accessibility]] 0l1j3chy13o5unsx53dpoys4skv5j9c 0 1147 9358 9357 2011-01-12T12:16:29Z Wutsje 166 Undo revision 9357 by [[Special:Contributions/82.114.188.11|82.114.188.11]] ([[User talk:82.114.188.11|talk]]) wikitext text/x-wiki =What's New?= We have been working hard to make things easier for our users. We are excited to share some improvements, including a new look and feel and simplified editing features. Improving the usability of our projects is a priority of the Wikimedia Foundation and we will be sharing more updates in the future. [[File:UsabilityNavigation.png]] [[File:UsabilityToolbar.png]] <br /> <center>[[File:UsabilityDialogs.png]]</center> ==List of the upcoming changes== Here's a brief summary of the changes we'll be rolling out over the next several weeks: *'''Navigation:''' We have improved the navigation for reading and editing pages. Now, the tabs at the top of each page more clearly define whether you are viewing the page or discussion page, and whether you are reading or editing a page. *'''Editing toolbar improvements:''' We have reorganized the editing toolbar to make easier to use. Now, formatting pages is simpler and more intuitive. *'''Link wizard:''' An easy-to-use tool allows you to add links to other wiki pages as well as links to external sites. *'''Search improvements''': We have improved search suggestions to get you to the page you are looking for more quickly. *'''Other new features:''' We have also introduced a table wizard to make creating tables easier and find and a replace feature to simplify page editing. Please visit the [[What's new, questions and answers|FAQ]] page for more information about the changes. iod4zpqb2mha0gr0vxibvsu7kp25gr2 0 1152 7951 7856 2010-06-20T06:05:56Z Nemo bis 9 moved [[English Wikipedia Default Links]] to [[Releases/Default Switch/English Wikipedia Default Links]] wikitext text/x-wiki Here is a list of links to help people who are monitoring progress on the English Wikipedia Default: '''Feedback pages:''' * '''[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback English Wikipedia Feedback Page]''': This is the one place we're trying to direct all feedback, so please try to send users here in communications. * [http://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Upcoming_Changes_to_the_User_Interface Village Pump Post] * [http://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/Archive213#Upcoming_Changes_to_the_User_Interfacee Administrators' Noticeboard Post (archived)] * [http://usability.wikimedia.org/wiki/Talk:What%27s_new,_questions_and_answers FAQ Talk Page] * [[Opinion:_Language_Links|Language Links]] '''Other pages:''' * [http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers FAQ page] * [[Releases/NewFeatures|Release page]] 7qzchxszih801oeo0v0kgv7pqsijie2 6 1153 6883 2010-05-08T14:26:22Z Juxn~usabilitywiki 176 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1155 6887 6885 2010-05-08T15:20:30Z Juxn~usabilitywiki 176 uploaded a new version of &quot;[[File:RuLogo.jpg]]&quot;: == Summary == == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1163 6940 6936 2010-05-11T19:45:26Z Juxn~usabilitywiki 176 uploaded a new version of &quot;[[File:Wikipedia-logo-v2-ru italic.png]]&quot;: == Summary == == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1164 6943 2010-05-11T19:52:09Z Juxn~usabilitywiki 176 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1165 6947 2010-05-11T19:59:11Z Juxn~usabilitywiki 176 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1172 6978 2010-05-12T09:36:41Z Juxn~usabilitywiki 176 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1184 7053 2010-05-16T22:54:01Z Husky 35 == Summary == Nice wireframe rendering of [[:File:Commons main page project Paris 2009.jpg]]. CC-BY-SA 3.0 wikitext text/x-wiki == Summary == Nice wireframe rendering of [[:File:Commons main page project Paris 2009.jpg]]. CC-BY-SA 3.0 oluldp4pbkntu8cj127m1ww3yhlb1pv 6 1194 7142 2010-05-24T22:17:16Z NeilK 1629 == Summary == Commons language selection for media file descriptions, early 2010 wikitext text/x-wiki == Summary == Commons language selection for media file descriptions, early 2010 7dpit06fmw9nh51s19tqy07rf8il6be 6 1195 7143 2010-05-24T22:18:00Z NeilK 1629 == Summary == Predictive typing on multiple fields; contact searching on Flickr wikitext text/x-wiki == Summary == Predictive typing on multiple fields; contact searching on Flickr 2i82s64bynv2t9yf9ewrqz2l2kod2p9 100 1196 9300 9299 2010-11-27T01:59:22Z Purodha 113 /* Approaches taken by other sites */ wikitext text/x-wiki We need a usable way to select languages on Wikimedia projects. ==Current system== [[Image:Language-select.png|thumb]] The current system provides a menu listing many languages, displayed in their preferred name in that language if available, but ordered by the ISO 639 code. Good points: * sorting by ISO codes will naturally group language variants together, such as Chinese Traditional (zh-tw) and Chinese Simplified (zh-cn). * Speakers of the language see the name of the language in the most common form. * Each language is treated equally Bad points: * The ordering is very unintuitive, since the ISO codes aren't even shown and sometimes bear no relationship to what the user is searching for. Users may assume that they should be looking for the name in English, or in the interface language. In some informal usability testing, we've seen users confused why "Fijian Hindi" is listed in English but Hindi is listed in Devanagari script. ** (Response: All names are listed in the interface language currently, '''including''' Fiji Hindi. The reason it appears in Latin alphabet is that the Fiji Hindi Wikipedia uses almost exclusively Latin alphabet.) --[[User:Node ue|Node ue]] 22:13, 7 June 2010 (UTC) * The very long number of options is time-consuming to scroll, even if you know what you're looking for. ==Requirements?== * Treat every language fairly. :* (Unclear) do not privilege languages just for being popular. (?) There may be ways to speed up the interface for common languages without impeding uncommon languages. * Include every reasonable language and subgroup (although, Wikimedia has significantly departed from ISO standards...) :* As far as I am aware, we have only departed from ISO standards in a handful of very limited cases which are now "grandfathered in", can you please elaborate? --[[User:Node ue|Node ue]] 22:15, 7 June 2010 (UTC) ::* FYI: We currently have roughly 20 out of 300+ cases of abbreviations for languages which, or the uses of which, are not 100% conforming to the standard BCP47. About a dozen aof those are planned to be changed to standard ones sooner or later, Some of those are only used at specific places and do not appear elsewhere. --[[User:Purodha|Purodha]] 01:40, 27 November 2010 (UTC) * Support, where necessary, bilingual users. Should be easy to switch between your preferred languages. ==Use cases== * '''Input''' Wikimedia Commons is inherently multilingual. All media items have a description field that may be split into multiple languages. The only time a "switch" between languages is necessary is when entering such descriptions. * '''Linking -- this might not be relevant to the question of how to input data?''' The Wikipedias each cover just one language. However, there are cross-language-wiki links maintained between articles that are deemed to be about the same thing. In the past this has just been a list of links in the left-hand column, ordered in the traditional (bad) ISO 639 code manner. ==Approaches taken by other sites== * [[Image:Facebook-lang-select.png|thumb]] '''Show every language offered, in its own script and language'''. Many sites offer a drop-down list like this. However it is difficult to scale. Facebook takes it the furthest by showing every language they offer in a large grid. : Facebook (circa mid 2010) offers the site internationalized to about 80 languages, some of which are in beta. Their interface selection widget pops up a matrix of choices, which show the name of the language localized to that language. This has the advantage that users can scan the entire list all at once. Multiple ordering approaches seem to be used, with most European languages sorted lexicographically, the Chinese variants grouped together, Japanese off by itself, and the others consigned to a column of miscellaneous languages. :: A better explanation of that: Korean, Chinese, Thai and Japanese are sorted according to English alphabetical order by their native name (Hangukmal, Zhongwen, Thai and Nihongo respectively) --[[User:Node ue|Node ue]] 22:16, 7 June 2010 (UTC) * '''Show every language offered, in the current user interface language AND in its own script and language'''. Google does this when setting language preferences in certain places. It's probably the most usable. :Most sites comparable to Wikimedia Commons typically only offer translations in ten or perhaps twenty languages. At the time of writing Wikimedia Commons has 356. So this common solution is not going to work for us. While we could probably get what Spanish is in English and vice versa, discovering the Quechua name for Japanese may be flat out impossible. : [http://www.unilang.org/ Unilang] -- has a drop down menu with English name of language, followed by name of language localized in that language. Sorted by English name of major language family, but then dialects and subgroups are sorted beneath that no matter what their English name is. Although the rest of the site has a localizable interface this menu is ''always'' displayed in English. (wisely avoiding the n**2 problem of translating every language in every language). However, we don't have the option of privileging English. :: This is probably not an acceptable solution for us. This gives English a favored status, which may be acceptable for Unilang as an organization but is not for us. Accusations of attempted imposition of Anglocentric cultural hegemony will arise very quickly if people on the French Wikipedia see English names for all languages. --[[User:Node ue|Node ue]] 22:19, 7 June 2010 (UTC) :::<s>Node ue, what about "in the current user interface language" seems anglocentric to you? [[User:NeilK|NeilK]] 00:18, 8 June 2010 (UTC)</s> :::Node ue: never mind, I see you're reacting to the Unilang example. That was just the closest thing I could find to what I'm describing. I agree it's not acceptable for us. [[User:NeilK|NeilK]] 00:22, 8 June 2010 (UTC) :::: The n**2 problem is basically being solved by the UNICODE CLDR [http://cldr.unicode.org/], and http://translatewiki.net/ is using a language picker inside MediaWiki that uses its data. A drawback may be that the CLDR data is not very complete yet, and it has a ''very'' slow update cycle at the moment between half a year and three years. I believe that upgrading the language picker to show additional infor mation, such as the language code and/or the language names in the interface language would be pretty straightforward. [[wikipedia:ksh:User talk:Purodha|Tell me]] if you want me to investigate that further, or make it. --[[User:Purodha|Purodha]] 01:59, 27 November 2010 (UTC) ===Other resources=== * [http://imagexmedia.com/support/faqs/general-questions/how-should-language-selection-be-displayed-web ImageXMedia] has a good resource on approaches taken by various sites, what to do, and what not to do. ==Ideas== ===Predictive text input=== [[Image:Flickr-contact-search.png|thumb]] Guillaume proposed a predictive typing interface that matches on all the strings we know of, plus the ISO 639 code. So one could find the Chinese language by typing "ch" to find its English name, "zh" for its language code, or by typing 中文. Facebook and Flickr use similar interfaces to quickly search for contacts, and this approach has been proven to scale to hundreds of entries. This is a clever solution since it allows us to make the best use of incomplete information. If we don't have the Swahili translation of Japanese, we don't include it as a possible input. If we *do* happen to have it, great. This is a largish subproject with uses outside Multimedia usability (or even Wikimedia generally) which may need its own scoping, probably its own extension. However, we don't have to code this from scratch. There exist some standard widgets for predictive search, or remote AJAX search from text entry. ===Geographically-oriented input=== The idea here is to offer users a way to navigate through languages in a value-neutral manner. 1) We would divide up the world into hierarchical regions, and obtain translated names for that short list of regions, in as many languages as possible. 2) Then, we offer a hierarchical menu, starting with the continents, and then show the user languages which are common in that region. Here's an example of looking for Spanish while browsing with an English interface. * South America :* Portuguese (Brazilian)''' :* '''Spanish''' OR * Europe :* Spain ::* Catalan ::* '''Spanish''' While this is possibly a convenient way to pick a language, another solution must be devised to show the user's choices (particularly if they make multiple selections, as when setting preferences). == Problems with many of the proposals on this page == It seems that many of these proposals presuppose that all users looking for a language have some degree of proficiency in English, which is not necessarily the case. If I only speak Quechua, how am I going to know to look under English-language labels like "South America" to find it? For a reverse example... if you're looking for English, would you know to choose between the labels "ევროპის", "აფრიკა", "აზია", "ჩრდილოეთი ამერიკა" and "სამხრეთ ამერიკა" (the names of the continents in [[:w:Georgian language|Georgian]]) to find your language? '''Any solution must take into account the fact that there are many, many people on this planet who are monolingual in languages other than English and cannot understand even one single short word of the language'''. --[[User:Node ue|Node ue]] 22:24, 7 June 2010 (UTC) :We are trying to craft proposals which aren't English-specific. I see your point, which is actually orthogonal to geography or English -- you're saying that the current interface language may not be a language that the user speaks, so they can't navigate a menu, of any kind, unless they see some string of characters they understand. If we can't put every language on the screen, they have to be able to guess that there is such a widget, and intuit how to use it without words. But, if we assume we have to have a language-interface-switcher on every page, the only solution is to have every language on every page, in some way, as a menu, popup, predictive text input, or paragraph of 356 links. Is there an elegant solution to this? An icon with little word balloons coming off of a globe, that pops up some sort of widget? [[User:NeilK|NeilK]] 00:02, 8 June 2010 (UTC) ::Well, my example was merely written from the point of view of a non-English speaker who visits a page on the English Wikipedia, but it could be applied to anybody at a site in a language they don't understand. As far as an elegant solution, any solution has to be very, very easy to figure out, which icons might not necessarily be. Another possible downside to anything that is hidden is that it takes an extra click to find out if a version in your language is available... say I prefer Swahili, I'm at the page [[:w:Baby boomer]]... I want to view the article in my language, but it's not there. With a language like Swahili, in which it's relatively uncommon to find Interwiki links from en.wp (sw.wp has 18K articles compared to millions on en.wp), users would probably not even bother. Having the language name there, announcing itself, is like stumbling upon buried treasure for many people. ::As far as having 356 links, that could be a problem in the future, but it isn't right now. See [http://toolserver.org/~mzmcbride/count-langlinks.txt] - at the English Wikipedia, only about 3% of articles have more than 13 interwikis, and only a couple thousand articles have more than 50. I agree that a better solution should be found than having 250+ links, but we have to try to do that without sacrificing ease-of-use. --[[User:Node ue|Node ue]] 00:12, 11 June 2010 (UTC) mvvkuftfhpyg4i99ezpjox2xxi2xcpz 6 1197 7157 2010-05-24T23:02:40Z NeilK 1629 == Summary == How Facebook allows the user to select interface language -- a modal popup showing a matrix of all available languages (about 80). This link is prominent at the bottom of the page, but not intended to be invoked very frequently. wikitext text/x-wiki == Summary == How Facebook allows the user to select interface language -- a modal popup showing a matrix of all available languages (about 80). This link is prominent at the bottom of the page, but not intended to be invoked very frequently. e8sb55aj38bnh10ydyn5qn7exaipwsu 0 1198 9221 9220 2010-10-30T04:27:57Z Guillom 13 Reverted edits by [[Special:Contributions/72.181.166.201|72.181.166.201]] ([[User talk:72.181.166.201|talk]]) to last revision by [[User:Hoo man|Hoo man]] wikitext text/x-wiki == Greeting == Hi, I’m [MODERATOR NAME], thanks so much for coming in today! == Permission == '''For In-Person Sessions''': Before we get started let’s get these consent forms filled out. Basically we’re going to be recording both your computer screen, and your face through that camera, and then our audio conversation. Those recordings are going to be posted on the internet under Creative Commons licensing, so they’ll be available for anyone who’s interested in this research to view at least part of them. By signing here, you’re agreeing that’s okay. Also, if you initial down below, we’ll label the video with your first name. If you’d rather we didn’t, we’ll label it with a made- up name instead. In either case, your face will be visible and your voice audible. Do you have any questions? '''For Remote Sessions''': Prior to today, you should have received and returned a consent form for recording of this session. Basically we’re going to be recording both your computer screen and our audio conversation. Those recordings are going to be posted on the internet under Creative Commons licensing, so they’ll be available for anyone who’s interested in this research to view at least part of them. You will not be personally identified but your voice will be audible. Depending on what you’ve checked on your consent form, we’ll either label the video with just your first name, or make up a name. Do you have any questions? == Overview + Setup == Great, let’s talk a little about what were going to be doing here today. We’re collecting feedback on Wikipedia.org. Basically, I’ll ask you some questions and then watch you use the web site. The whole thing will take about 75 minutes. Your job is really easy: you just have to be yourself and act as you naturally would. I did not design this website, and I don’t actually work directly for Wikipedia, I’m just collecting feedback, so I promise, nothing you say could hurt my feelings! As you use the site, please be honest with your positive and negative thoughts. There are no right or wrong answers. You are not being tested; the Wikipedia webpage is being tested. == Background Questions == So let’s get started with a few quick background questions.<br /> 1. Please tell me a little about yourself. What do you do? Where are you from?<br /> 1.5. Tell me about how computers fit into your day. How much time do you spend online? Do you publish a website or blog? Contribute reviews on Amazon or Yelp? What kinds of software do you use<br /> 2. What was it you were doing on Wikipedia when you filled out the survey a few weeks ago?<br /> 3. You said you come to Wikipedia [INSERT] often. What are you usually looking up/doing?<br /> 4. How has your experience been in the past?<br /> 4a. Non-Editors Only: You mentioned that you haven’t edited Wikipedia before, but you’d be willing to. What are the reasons that you haven’t in the past?<br /> 4b. Non-Editors Only: Can you tell me what you know now about the process of editing?<br /> 4c. Editors Only: You mentioned that you have contributed to Wikipedia before. What are your impressions of the contribution and editing process?<br /> == Tasks + Testing == Next I’d like to have you go on Wikipedia to do a couple of tasks. As we do this, there’s one thing that I would like you to keep in mind. Please “think aloud” as you use the web site today. For example, if you are reading something, read it out loud and feel free to say anything that comes to your mind as you read - for example that’s interesting or what in the world are they talking about? Also, think out loud while you’re doing a task, so I can understand what you are thinking and doing. (e.g.: Now I’m going to try to use the search engine) And, if you get to a point where you would naturally stop working, let me know. I’ll let you decide when your task is complete, whether you find what you are looking for or not. Just tell me when you’re finished.<br /> <br /> Do you have any questions before we continue?<br /> <br /> Today, we’re going to be focusing on navigating through the website and making changes to Wikipedia entries. Let’s go to the Wikipedia website. In your browser, please go to www.wikipedia.org and then click ENGLISH === Basic Editing === 1. Do you have a Wikipedia account? Note, moderator will provide them with preset credentials. <br/><br/> 2. Let’s take a look at an article on Wikipedia on something that you know a lot about. If participant can’t remember or declines, suggest: Hometown; Favorite sports team, movie, singer, actor; last meal you had/book you read; College or University you attended. First I’d like for you to just spend some time on the page, look around, and talk to me about the different features you see here. <br/><br/> 3. Ok, let’s say you wanted to add some information to this page. What would you do first? <br/><br/> 4. After user discovers the editing interface: Take a moment to look around the page here. Talk to me about the tools that you see here and how you might use them. 5. Ok, so let’s go ahead and add some information to this page. The information can be anything you want. How would you do that? If participant cannot think of text to add, suggest “Free knowledge for everyone on the planet.” <br/><br/> 6. What do you think about that list of links to the right hand side of the edit box (TOC)? What do you think is going on there. Skip if no TOC on chosen page. <br/><br/> 7. What about linking the information you added to a page somewhere else on the internet? How would you do that? <br/><br/> 8. Let’s say you want to link the information you added to the page to another page on Wikipedia. How would you do that? <br/><br/> 9. Let’s say you want to add a reference to this page, like a footnote, which will appear at the bottom of the page in the References. Add the reference to something that you have added to the page. How would you do that? <br/><br/> 10. How likely would you be to do this? <br/><br/> 11. Now that you’ve used the editing interface a bit, is there anything that strikes you as confusing? Prompt about navigation & other elements of the toolbar <br/><br/> 12. Is there anything missing that you’d normally expect to see? <br/><br/> 13. Let’s say you’re satisfied with the changes you’ve made and want to add them to Wikipedia. How would you go about doing that? Note: Explore Save & Preview choices. <br/><br/> 14. Now that you’ve done this, how likely is it that you would do it again or more often? <br/><br/> 15. Please go to the discussion page for this article. Have you ever read, used or contributed to a discussion page for a Wikipedia article? If so, please tell me about that. <br/><br/> === Advanced Editing === Next we’re going to try some other editing tasks. If user is already on entry for a location, then we can remain on this page. If not, direct the user to call up their Hometown page. If Hometown page does not have Template, then direct user to San Francisco, CA page, 1. First, take a look at the long box of information that runs down the right-hand side of the page. Please take a minute to scan it. Now, let’s say you just moved to this city / town and wanted to change the population info to be one greater. How would you do that? <br/><br/> 3a. If the participant doesn’t use the Infobox, then: Let’s take a look at the item in the edit area labeled: “Infobox settlement:” ... Please take a minute to interact with it and give me your thoughts. What do you think this is for? <br/><br/> 2. Does the Infobox item work generally as you’d expect? If participant has only discovered Expansion feature, then prompt for Overlay, and vice versa. <br/><br/> 3. Next, I’d like you to create a new section on this page. If this location page has a Sports section, add new subsection titled “Rivalries” ... If this location page does not have a Sports Section, then ask the user to add one ... Note that the user should make text Bold and increase Font Size <br/><br/> 2. Ok, next I’d like you to enter some information under this new section. I’d like you to add a simple table. This table should show the different sports rivalries with this town. The table should look something like this: In person interviews hand the following to the participant. Remote users will be given a link to a web page with this diagram. <br/><br/> {| class="wikitable" |- ! Sport !! Hometown Team !! Rival Team |- | Baseball || Team || Team |- | Football || Team || Team |- | Basketball || Team || Team |} === Optional Questions – Time Permitting === 1. What about the View History page? <br/><br/> 2. If you wanted to create a completely new article entry, how would you do that? Suggest using a completely made up historical figure. <br/><br/> 3. Let’s say you wanted help during this process. Where would you go? Prompt to explore toolbar help. <br/><br/> == Final Questions + Wrap up == 1. Looking back, what do you think of everything you've seen and used? 2. What did you like the most? 3. The least? 4. What might encourage or increase your participation on Wikipedia.org? 5. If there was one comment that you would want to make sure that everyone at Wikipedia working on this project heard, what would it be? 6.Would it be okay for us to contact you if we have any follow up questions or information? 3mkfmmvz0c00fnqz0p695w3iwo0zusq 0 1199 8944 8941 2010-09-26T18:03:12Z Cbrown1023 7 /* Phase IV Deployment */ new CentralNotices were already published on Meta. wikitext text/x-wiki {{TOCright}} The User Experience Team and other Wikimedians are currently in [[Releases/Default_Switch#Phase_V_Deployment|Phase V]] and getting ready to roll-out the default interface called "Vector" along with other usability improvements to the remaining Wikimedia projects. :''Note: PR = pre-release and PO = post-release.'' == Phase I Deployment == * [[commons:|Wikimedia Commons]], completed on April 5, 2010 == Phase II Deployment == * [[:en:|English Wikipedia]], completed on May 13, 2010 ([[English Wikipedia Default Links]]) == Phase III Deployment == * <span class="plainlinks">[http://wikipedia.org/ Top 10 Wikipedias]</span>, 5:30 UTC/07:30 CEST, Thursday, June 10 / 22:30 PDT, June 9. {| class="wikitable plainlinks" |- ! lang ! Announcement<ref name="Announcement">It's important that these default changes are widely announced on the Foundation blog, local village pumps, local news mediums, chapter blogs/press releases, social media outlets, and many other places. Please list the announcement venues here.</ref> ! <span title="Pre-release page">[http://meta.wikimedia.org/w/index.php?title=Special:NoticeTemplate/view&template=VectorNewLook PR CentralNotice]</span><ref name="PhaseIII-CN-PR">To be enabled on June 6 (72 hours before the switch).</ref> ! <span title="Pre-release Page">PR</span><ref name="PhaseIII-PR">CentralNotice links to this page, so this page must also be enabled by June 6.</ref> ! <span title="Post-release Page">[http://meta.wikimedia.org/w/index.php?title=Special:NoticeTemplate/view&template=VectorChanged PO CentralNotice]</span> ! FAQ ! Ambassador<ref name="Ambassadors">"User Experience Ambassadors" &ndash; The collaboration with the translation community is crucial to make sure that support materials, such as announcements, FAQ, feedback page, site notice, and OTRS templates, are available in local languages, but it is also important that there are group of folks from the each language community who can make sure that announcements are reaching to the language community and the feedback is escalated back to the user experience team before and after the release. These advocates will be "user experience ambassadors" who will help coordinate the translation of support materials in the local language, help communicate information about "the switch", and help escalate feedback back to the Usability team. If you're interested in volunteering, see [[Talk:Releases/Default Switch|the talk page]]!</ref> ! <span title="Feedback Page">FBack</span> ! [[translatewiki:User:GerardM/usability-stats|MW]] <span id="en" /> |- valign="top" | [[w:|en]] | {{status|done}}[http://blog.wikimedia.org/2010/a-new-look-for-wikipedia/ WMF blog] | {{status|done}}Wikipedia's getting a new look. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features Learn more.] | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features] | {{status|done}}Notice something different? We've made a few improvements to Wikipedia. Learn more. | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}&mdash; | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}} <span id="ja" /> |- valign="top" | [[w:ja:|ja]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[[:w:ja:Wikipedia:お知らせ#ウィキペディアのインターフェースが新しくなります|Noticeboard]]<ref>for contributors (Village Pump Annoucement)</ref><br />{{status|done}}[[:w:ja:Template:メインページお知らせ/本文|Main Page]]<ref>for readers (Main Page notice)</ref> | {{status|done}}ウィキペディアのインターフェイスが新しくなります / [[:w:ja:Wikipedia:使用性改善/新機能紹介|詳細]] | {{status|done}}[http://ja.wikipedia.org/wiki/WP:UX/New] | {{status|done}}変更にお気づきですか？ウィキペディアにいくつかの改善が加えられました（[[:w:ja:Wikipedia:使用姿勢改善/新機能紹介|詳細]]）。 | {{status|done}}[http://ja.wikipedia.org/wiki/WP:UX/FAQ] | {{status|done}}[[:w:ja:Wikipedia:使用性改善/支援チーム|JAWP Support Team]] ([[w:ja:User:青子守歌|Aokomoriuta]]) | {{status|done}}[http://ja.wikipedia.org/wiki/WP:WUI/F] | {{status|done}} <span id="es" /> |- valign="top" | [[w:es:|es]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[http://wikimedia.org.ar/wiki/Prensa/Wikipedia_renueva_su_apariencia WMAR PR]<br />{{status|done}}[http://wikimedia-es.blogspot.com/2010/06/wikipedia-renueva-su-apariencia.html WMES blog]<br />{{status|done}}[[w:es:Wikipedia:Café/Portal/Archivo/Noticias/Actual#¡Vector!|Café]] | {{status|published}}Wikipedia está cambiando su aspecto. [[:es:Wikipedia:Feedback_de_experiencia_de_usuario/Nuevas_funcionalidades|Ver más.]] | {{status|done}}[http://es.wikipedia.org/wiki/Wikipedia:Feedback_de_experiencia_de_usuario/Nuevas_funcionalidades] | {{status|published}}¿Has notado algo diferente? Hemos hecho algunas mejoras en Wikipedia. [[:es:Wikipedia:Feedback_de_experiencia_de_usuario/Nuevas_funcionalidades|Ver más.]] | {{status|done}}[http://es.wikipedia.org/wiki/Wikipedia:Feedback_de_experiencia_de_usuario/Nuevas_funciones,_preguntas_y_respuestas] | {{status|done}}[[w:es:User:Rayis|Rayis]] | {{status|done}}[http://es.wikipedia.org/wiki/Wikipedia:Feedback_de_experiencia_de_usuario] | {{status|done}} <span id="de" /> |- valign="top" | [[w:de:|de]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[http://blog.wikimedia.de/2010/06/10/vector-mediawiki-skin/ WMDE blog]<br />{{status|done}}[[w:de:Wikipedia:Kurier|Kurier]]<br />{{status|missing}}VP? | {{status|done}}Wikipedia bekommt ein neues Aussehen. Mehr Informationen... | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Neue_Funktionen] | {{status|done}}Hast du unsere Änderungen bemerkt? Wir haben Wikipedia verbessert. Mehr Informationen... | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/FAQ] | {{status|done}}[[w:de:User:Church of emacs|Church of emacs]] | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Feedback] | {{status|done}} <span id="fr" /> |- valign="top" | [[w:fr:|fr]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|missing}}WMFR blog<br />{{status|done}}[[w:fr:Wikipédia:Wikimag|Wikimag]]<br />{{status|missing}}[[w:fr:Wikipédia:Le Bistro|Le Bistro]] | {{status|done}}Wikipédia change d'apparence. En savoir plus... | {{status|done}}[http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Retours_d'exp%C3%A9rience_sur_l'utilisabilit%C3%A9/Nouvelles_fonctionnalit%C3%A9s] | {{status|done}}Quelque chose a changé ? Wikipédia s'améliore ! En savoir plus... | {{status|done}}[http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Retours_d'exp%C3%A9rience_sur_l'utilisabilit%C3%A9/FAQ] | {{status|done}}[[w:fr:user:Kyro|Kyro]] | {{status|done}}[http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Retours_d'exp%C3%A9rience_sur_l'utilisabilit%C3%A9] | {{status|done}} <span id="gsw" /> |- valign="top" | [[w:als:|als]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[http://blog.wikimedia.de/2010/06/10/vector-mediawiki-skin/ WMDE blog]<br />{{status|done}} | {{status|done}}Wikipedia chunnt e nej Uusäh iber. Meh Informatione... | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Neue_Funktionen] | {{status|done}}Hesch unsri Ämderige gmerkt? Mir hän d Wikipedia verbesseret. Meh Informatione ... | {{status|done}}[http://als.wikipedia.org/wiki/Wikipedia:Usability-Initiative/FAQ] | {{status|done}}[[w:als:User:Holder|Holder]] | {{status|done}}[http://als.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Feedback] | {{status|done}} <span id="fr" /> <span id="it" /> |- valign="top" | [[w:it:|it]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|published}}[[User:Marco 27/Blog announcement|WMIT blog]][http://www.frontieredigitali.it/online/?p=1703]<br />{{status|done}}[[w:it:Wikipedia:Bar/Discussioni/Vector anche su it.wiki|Bar]]<br />{{status|done}}[[w:it:Wikipedia:Wikipediano|Wikipediano]] | {{status|done}}Wikipedia sta per cambiare aspetto. [[:it:Progetto:Coordinamento/Usabilità/Nuove funzionalità|Scopri come]]. | {{status|done}}[http://it.wikipedia.org/wiki/Progetto:Coordinamento/Usabilità/Nuove_funzionalità] | {{status|published}}Noti qualcosa di diverso? Abbiamo apportato diversi miglioramenti a Wikipedia. Scopri quali. | {{status|done}}[http://it.wikipedia.org/wiki/Progetto:Coordinamento/Usabilità/FAQ] | {{status|done}}[[w:it:User:Marco 27|Marco 27]] | {{status|done}}[http://it.wikipedia.org/wiki/Progetto:Coordinamento/Usabilità] | {{status|done}} <span id="ru" /> |- valign="top" | [[w:ru:|ru]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[[w:ru:Википедия:Форум/Новости#Usability|Форум (ФН)]] | {{status|done}}Википедия обретает новый вид. [http://ru.wikipedia.org/wiki/Википедия:Отклики_о_пользовании/Новые_возможности Подробнее.] | {{status|done}}[http://ru.wikipedia.org/wiki/Википедия:Отклики_о_пользовании/Новые_возможности] | {{status|done}} Заметили что-то новое? Мы немного улучшили Википедию. Подробнее. | {{status|done}}[http://ru.wikipedia.org/wiki/Википедия:Отклики_о_пользовании/ЧаВо] | {{status|done}}[[:ru:User:VasilievVV|VasilievVV]] | {{status|done}}[http://ru.wikipedia.org/wiki/Википедия:Отклики_о_пользовании] | {{status|done}} <span id="pl" /> |- valign="top" | [[w:pl:|pl]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[http://pl.wikipedia.org/wiki/Wikipedia:TO#4_czerwca Noticeboard]<br />{{status|done}}press [http://www.dobreprogramy.pl/Polska-Wikipedia-wkrotce-w-nowej-szacie-graficznej,Aktualnosc,18646.html] [http://www.heise-online.pl/newsticker/news/item/Wikipedia-na-wakacje-zmienia-skore-1017618.html] | {{status|done}}Wikipedia się zmienia. [http://pl.wikipedia.org/wiki/Pomoc:Nowa_sk%C3%B3rka_%E2%80%93_wektor Dowiedz się więcej]. | {{status|done}}[http://pl.wikipedia.org/wiki/Pomoc:Nowa_sk%C3%B3rka_%E2%80%93_wektor] | {{status|done}}Zauważyłeś/aś jakieś zmiany? Wprowadziliśmy parę usprawnień w Wikipedii. Dowiedz się więcej. | {{status|done}}[http://pl.wikipedia.org/wiki/Pomoc:Nowa_sk%C3%B3rka_%E2%80%93_wektor] | {{status|done}}[[:pl:User:Nux|Nux]] | {{status|done}}[http://pl.wikipedia.org/wiki/Wikipedia:U%C5%BCyteczno%C5%9B%C4%87_%E2%80%93_ksi%C4%99ga_skarg,_za%C5%BCale%C5%84_i_pomys%C5%82%C3%B3w] | {{status|done}} <span id="pt" /> |- valign="top" | [[w:pt:|pt]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[[w:pt:Wikipedia:Esplanada/anúncios#Nova_interface_na_Wikip.C3.A9dia_lus.C3.B3fona|Esplanda (EA)]] | {{status|published}}A Wikipédia está a mudar de aparência. [[:pt:Wikipedia:Feedback de experiência de usuário/Novas funcionalidades|Saiba mais]]. | {{status|done}}[http://pt.wikipedia.org/wiki/Wikipedia:Feedback_de_experiência_de_usuário/Novas_funcionalidades] | {{status|done}}Notou algo diferente? Fizemos algumas melhorias na Wikipédia. [[:pt:Wikipedia:Feedback de experiência de usuário/Novas funcionalidades|Saiba mais]]. | {{status|done}}[http://pt.wikipedia.org/wiki/Wikipedia:Feedback_de_experiência_de_usuário/FAQ] | {{status|missing}} | {{status|done}}[http://pt.wikipedia.org/wiki/Wikipedia:Feedback_de_experiência_de_usuário] | {{status|done}} <span id="nl" /> |- valign="top" | [[w:nl:|nl]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[[w:nl:Wikipedia:De_kroeg#In de week van 7 juni zal de nieuwe interface gelanceerd worden voor de Nederlandse Wikipedia|De kroeg]] | {{status|done}}Wikipedia krijgt een nieuw uiterlijk. [http://nl.wikipedia.org/wiki/Wikipedia:Feedback_voor_het_User_Experience_Team/Nieuwe_functionaliteiten Lees meer.] | {{status|done}}[http://nl.wikipedia.org/wiki/Wikipedia:Feedback_voor_het_User_Experience_Team/Nieuwe_functionaliteiten] | {{status|done}}Iets opgevallen? We hebben een paar verbeteringen doorgevoerd op Wikipedia. [http://nl.wikipedia.org/wiki/Wikipedia:Feedback_voor_het_User_Experience_Team/Nieuwe_functionaliteiten Lees meer.] | {{status|done}}[http://nl.wikipedia.org/wiki/Wikipedia:Feedback_voor_het_User_Experience_Team/FAQ] | {{status|done}}[[w:nl:User:Romaine|Romaine]] | {{status|done}}[http://nl.wikipedia.org/wiki/Wikipedia:Feedback_voor_het_User_Experience_Team] | {{status|done}} |} == Phase IV Deployment == '''Update:''' * On June 30, 2010, we completed Phase IV of the Usability Initiative Deployment. The list of projects may be found [[Releases/Default_Switch/Phase_IV_projects|here]]. * We still need help translating the Post-Release Central Notice and other items in the table below. '''Please check the list of Wikipedia Projects for [[Releases/Default_Switch/Phase_IV_projects|Phase IV Deployment]]''' * <span class="plainlinks">[http://www.wikipedia.org/ Wikipedias] with over [http://translatewiki.net/wiki/User:GerardM/usability-stats 80% of the interface localized]</span>, target date: '''''10am PDT/5pm UTC, June 30, 2010'''. *If your local Wikipedia project meets the criteria above, feel free to add it to this list and translate the information listed in the (en) row, into your own language. ---- *The deadline for the ''Translation and Bug help CentralNotice'' (as it is going live on this date) is on '''June 21, 2010'''. *The deadline for the translation of [http://translatewiki.net/wiki/User:GerardM/usability-stats system messages] is '''4pm PDT/11pm UTC, June 28, 2010'''. * If you create a localized feedback page, please direct English language feedback to [[m:2010 Wikimedia design and feature change/Feedback]], and help us to translate or summarize feedback in your language. *If you have any questions regarding the translation process or need help, please contact [[User:Az1568|Az1568]] (azariv[[File:At_sign.svg|{{{1|17px}}}| at ]]wikimedia.org) or any member of the Usability Initiative. {| class="wikitable plainlinks sortable" |- ! lang ! Announcement<ref name="Announcement" /> ! <span title="Translation and Bug help notice">Trans/Bug Help CN</span> ! <span title="Pre-release Notice">PR CentralNotice</span><ref name="PhaseIII-CN-PR" /> ! <span title="Pre-release Page">PR</span><ref name="PhaseIII-PR" /> ! <span title="Post-release Notice">PO CentralNotice</span> ! FAQ ! Ambassador<ref name="Ambassadors" /> ! <span title="Feedback Page">FBack</span> ! [[translatewiki:User:GerardM/usability-stats|MW]] <span id="de" /> |- valign="top" | [[w:|de]] | {{status|missing}}Local Village pump, Mailing list, etc. | {{status|done}}Wikipedia bekommt ein neues Aussehen. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Hilf uns bei der Fehlerbehebung und Übersetzung!] | {{status|done}}Wikipedia bekommt ein neues Aussehen. [http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Neue_Funktionen Mehr Informationen...] | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Neue_Funktionen] | {{status|done}}Hast du unsere Änderungen bemerkt? Wir haben Wikipedia verbessert. [http://de.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Mehr Informationen...] | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/FAQ] | {{status|missing}}&mdash; | {{status|done}}[http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Feedback] | {{status|done}} <span id="el" /> |- valign="top" | [[w:el:|el]] | {{status|done}}[http://el.wikipedia.org/wiki/%CE%92%CE%B9%CE%BA%CE%B9%CF%80%CE%B1%CE%AF%CE%B4%CE%B5%CE%B9%CE%B1:%CE%91%CE%B3%CE%BF%CF%81%CE%AC#.CE.9D.CE.AD.CE.B1_.CF.87.CE.B1.CF.81.CE.B1.CE.BA.CF.84.CE.B7.CF.81.CE.B9.CF.83.CF.84.CE.B9.CE.BA.CE.AC Αγορά (Local Village pump)] | {{status|done}} Το εγχείρημα <nowiki>{{SITENAME}}</nowiki> παίρνει μια νέα όψη. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Βοηθήστε μας να βρούμε προβλήματα και να συμπληρώσουμε τις μεταφράσεις του περιβάλλοντος.] | {{status|published}} Η Βικιπαίδεια παίρνει μια νέα όψη. [http://el.wikipedia.org/wiki/Βικιπαίδεια:Πρωτοβουλία_Χρηστικότητας/Νέα_χαρακτηριστικά Μάθετε περισσότερα] | {{status|done}}[http://el.wikipedia.org/wiki/Βικιπαίδεια:Πρωτοβουλία_Χρηστικότητας/Νέα_χαρακτηριστικά] | {{status|done}}Βλέπετε κάτι διαφορετικό; Κάναμε μερικές βελτιώσεις στην Βικιπαίδεια. [http://el.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Μάθετε περισσότερα.] | {{status|missing}} | {{status|done}}[[w:el:User:Geraki|Geraki]] | {{status|done}}[http://el.wikipedia.org/wiki/Βικιπαίδεια:Πρωτοβουλία_Χρηστικότητας/Ανατροφοδότηση] | {{status|done}} <span id="en" /> |- valign="top" | [[w:|en]] | {{status|done}}Local Village pump, Mailing list, etc. | {{status|done}}<nowiki>{{SITENAME}}</nowiki> is getting a new look. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Help us find bugs and complete user interface translations.] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> is getting a new look. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features Learn more] | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features] | {{status|done}}Notice something different? We've made a few improvements to <nowiki>{{SITENAME}}</nowiki>. [http://en.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Learn more.] | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}&mdash; | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}} <span id="als" /> |- valign="top" | [[w:als:|als]] | {{status|done}}[[:w:als:Wikipedia:Stammtisch|Stammtisch (Village pump)]] | {{status|done}}D'Wikipedia griegt e neus Usseh. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Hilf uns bim Fehler süeche un Übbersetze!] | {{status|done}}D'Wikipedia griegt e neus Usseh. [http://de.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Neue_Funktionen Meh Informatione...] | {{status|done}}[http://als.wikipedia.org/w/index.php?title=Spezial:UsabilityInitiativePrefSwitch&from=Wikipedia%3AUsability-Initiative%2FNeue_Funktionen] | {{status|done}}Häsch unseri Änderige gseh? Mr hän d'Wikipedia verbessert. [http://als.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Meh Informatione...] | {{status|done}}[http://als.wikipedia.org/wiki/Wikipedia:Usability-Initiative/FAQ] | {{status|done}}[[:w:als:Benutzer:Holder|Holder]] | {{status|done}}[http://als.wikipedia.org/wiki/Wikipedia:Usability-Initiative/Feedback] | {{status|done}} <span id="be-x-old" /> |- valign="top" | [[w:be-x-old:|be-x-old]] | {{status|done}}[[w:be-x-old:Вікіпэдыя:Форум#Пераключэньне інтэрфэйсу|Форум (Village Pump)]] | {{status|published}}Вікіпэдыя зьмяняе свой выгляд. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Дапамажыце знайсьці памылкі і скончыць пераклад інтэрфэйсу]. | {{status|published}}Вікіпэдыя зьмяняе свой выгляд. [http://be-x-old.wikipedia.org/wiki/Вікіпэдыя:Водгукі_ўдзельнікаў/Новыя_магчымасьці Даведайцеся болей]. | {{status|done}}[http://be-x-old.wikipedia.org/wiki/Вікіпэдыя:Водгукі_ўдзельнікаў/Новыя_магчымасьці] | {{status|published}}Заўважылі нейкія зьмены? Мы крыху палепшылі Вікіпэдыю. [http://be-x-old.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Даведайцеся болей]. | {{status|done}}[http://be-x-old.wikipedia.org/wiki/Вікіпэдыя:Водгукі_ўдзельнікаў/Пытаньні_і_адказы] | {{status|done}}[[User:Wizardist|Wizardist]] | {{status|done}}[http://be-x-old.wikipedia.org/wiki/Вікіпэдыя:Водгукі_ўдзельнікаў] | {{status|done}} <span id="br" /> |- valign="top" | [[w:br:|br]] | {{status|done}}[[:br:Wikipedia:Kumuniezh/An_davarn|An davarn]] | {{status|published}}Emañ Wikipedia o cheñch tres. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Ro dorn da glokaat ha da c'hwennat troidigezhioù an etrefas implijer.] | {{status|done}}Emañ wikipedia o cheñch tres. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features Titouroù all.] | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features] | {{status|done}}Merzet un dra bennak disheñvel? Tammoù gwellaennoù zo bet degaset da wikipedia. [http://en.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Titouroù all.] | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}&mdash; | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}} <span id="ca" /> |- valign="top" | [[w:ca:|ca]] | {{status|published}}[http://www.viquimedia.cat/viqui/Premsa/La_Viquip%C3%A8dia_renova_l%27aspecte WMCAT]<br />{{status|done}}[[:ca:Viquipèdia:La taverna/Arxius/Propostes/Recent#Entrem a l'aparença vector (de la Beta)|Village pump]]<br />{{status|done}}[http://lists.wikimedia.org/pipermail/wikica-l/2010-June/000102.html Mailing list] | {{status|published}}La Viquipèdia està canviant d'aspecte. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Ajudeu-nos a trobar-hi errors i a completar les traduccions de la interfície.] | {{status|published}}La Viquipèdia està canviant d'aspecte. [http://ca.wikipedia.org/wiki/Viquip%C3%A8dia:Comentaris_sobre_l%27experi%C3%A8ncia_d%27usuari/Noves_caracter%C3%ADstiques Més informació.] | {{status|done}}[http://ca.wikipedia.org/wiki/Viquip%C3%A8dia:Comentaris_sobre_l%27experi%C3%A8ncia_d%27usuari/Noves_caracter%C3%ADstiques] | {{status|done}}Noteu alguna cosa diferent? Hem fet algunes millores a la Viquipèdia. [http://ca.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Més informació.] | {{status|done}}[http://ca.wikipedia.org/wiki/Viquip%C3%A8dia:Aparen%C3%A7a_Vector] | {{status|missing}} | {{status|done}}[http://ca.wikipedia.org/wiki/Viquip%C3%A8dia:Comentaris_sobre_l%27experi%C3%A8ncia_d%27usuari] | {{status|done}} <span id="cs" /> |- valign="top" | [[w:cs:|cs]] | {{status|published}}[http://cs.wikipedia.org/wiki/Wikipedie:Pod_lípou_(oznámení)#Zm.C4.9Bna_vzhledu Village pump] | {{status|published}}Wikipedie získá novou podobu. [http://cs.wikipedia.org/wiki/Wikipedie:Iniciativa_použitelnosti Pomozte nám s testováním.] | {{status|published}}Wikipedie získá novou podobu. [http://cs.wikipedia.org/wiki/Wikipedie:Iniciativa_použitelnosti/Nové_funkce Chcete vědět víc?] | {{status|done}}[http://cs.wikipedia.org/wiki/Wikipedie:Iniciativa_použitelnosti/Nové_funkce] | {{status|published}}Všimli jste si něčeho? Trochu jsme Wikipedii vylepšili. [http://cs.wikipedia.org/wiki/Wikipedie:Iniciativa_použitelnosti/Nové_funkce Chcete vědět víc?] | {{status|done}}[http://cs.wikipedia.org/wiki/Wikipedie:Iniciativa_použitelnosti/FAQ] | {{status|missing}} | {{status|done}}[http://cs.wikipedia.org/wiki/Wikipedie:Iniciativa_použitelnosti/Reakce] | {{status|done}} |- valign="top" | [[w:|cy]] | {{status|done}}[[:cy:Wikipedia:Y_Caffi|Y Caffi]] | {{status|done}}Mae <nowiki>{{SITENAME}}</nowiki> ar fin ymddangos ar ei newydd wedd. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Awn ati i ddod o hyd i'r bygiau ac i gwblhau cyfieithu'r rhyngwyneb.] | {{status|done}}Mae <nowiki>{{SITENAME}}</nowiki> ar fin ymddangos ar ei newydd wedd. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features Darllenwch rhagor] | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features] | {{status|done}}Wedi sylwi bod rhywbeth yn wahanol i arfer yma? Rydym wedi bod wrthi'n gwella <nowiki>{{SITENAME}}</nowiki>. [http://en.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Darllenwch rhagor.] | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|missing}} | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}} <span id="dsb" /> |- valign="top" | [[w:dsb:|dsb]] | {{status|done}}[http://dsb.wikipedia.org/wiki/Wikipedija:Portal Village pump] | {{status|progress}}Wikipedija dostanjo nowy naglěd. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Pomóž nam pśi testowanju a pśełožowanju.] | {{status|progress}}Wikipedija dostanjo nowy naglěd. [http://dsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužywajobnosći/Nowe_funkcije Dalšne informacije...] | {{status|progress}}[http://dsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužywajobnosći/Nowe_funkcije] | {{status|progress}}Sy změny zawupytnuł? Smy <nowiki>{{GRAMMAR:akuzatiw|{{SITENAME}}}}</nowiki> pólěpšyli. [http://dsb.wikipedia.org/wiki/Specialne:UsabilityInitiativePrefSwitch/Nowe_funkcije Dalšne informacije...] | {{status|progress}}[http://dsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužywajobnosći/FAQ] | {{status|missing}} | {{status|progress}}[http://dsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužywajobnosći/Měnjenja] | {{status|progress}} <span id="eo" /> |- valign="top" | [[w:eo:|eo]] | {{status|done}}[[:eo:Vikipedio:Diskutejo#Vector-etoso|Diskutejo]] | {{status|done}}La aspekto de Vikipedio ŝanĝiĝas. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Helpu nin trovi cimojn kaj fintraduki la uzantointerfacon.] | {{status|published}}La aspekto de Vikipedio ŝanĝiĝas. [http://eo.wikipedia.org/wiki/Vikipedio:Novaj_funkcioj Pli pri la temo.] | {{status|done}}[http://eo.wikipedia.org/wiki/Vikipedio:Novaj_funkcioj] | {{status|published}}Ĉu vi rimarkis ion malsaman? Ni faris plibonigojn al Vikipedio. [http://eo.wikipedia.org/wiki/Vikipedio:Novaj_funkcioj Pli pri la temo]. | {{status|missing}}[http://eo.wikipedia.org/wiki/Vikipedio:Novaj_funkcioj/Vector] | {{status|missing}} | {{status|missing}} | {{status|done}} <span id="eu" /> |- valign="top" | [[w:eu:|eu]] | {{status|done}}[[w:eu:Wikipedia:Txokoa/Eskariak#Itxura lehenetsia aldatzea|Txokoa (Village pump)]] | {{status|done}}Wikipediaren itxura aldatzen ari da. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Lagun gaitzazu akatsak bilatzen eta interfazeko itzulpenak amaitzen.] | {{status|done}}Wikipediaren itxura aldatzen ari da. [http://eu.wikipedia.org/wiki/Wikipedia:Lankideen_esperientziari_buruzko_iruzkinak/Ezaugarri_berriak Informazio gehiago] | {{status|done}}[http://eu.wikipedia.org/wiki/Wikipedia:Lankideen_esperientziari_buruzko_iruzkinak/Ezaugarri_berriak] | {{status|done}}Zerbait ezberdin nabaritzen duzu? Wikipedian hobekuntza batzuk egin ditugu. [http://eu.wikipedia.org/wiki/Berezi:UsabilityInitiativePrefSwitch Informazio gehiago.] | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}— | {{status|done}}[http://eu.wikipedia.org/wiki/Wikipedia:Lankideen_esperientziari_buruzko_iruzkinak] | {{status|done}} <span id="fa" /> |- valign="top" | [[w:fa:|fa]] | {{status|missing}}[[w:fa:وپ:ق|Village pump]] | {{status|done}}ویکی‌پدیا به سوی شمایلی جدید می‌رود[http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D9%85%DA%A9%D8%A7%D9%86%D8%A7%D8%AA_%D8%AC%D8%AF%DB%8C%D8%AF/%D8%A8%D8%A7%D8%B2%D8%AE%D9%88%D8%B1%D8%AF به ما در اشکال‌زدایی کمک کنید] | {{status|done}}ویکی‌پدیا به سوی شمایلی جدید می‌رود[http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D9%85%DA%A9%D8%A7%D9%86%D8%A7%D8%AA_%D8%AC%D8%AF%DB%8C%D8%AF اطلاعات بیشتر] | {{status|done}}[http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D9%85%DA%A9%D8%A7%D9%86%D8%A7%D8%AA_%D8%AC%D8%AF%DB%8C%D8%AF] |{{status|done}}چیزی عوض شده؟ ما ویکی‌پدیا را کمی تغییر داده‌ایم [http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%98%D9%87:UsabilityInitiativePrefSwitch اطلاعات بیشتر] | {{status|done}}[http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D9%85%DA%A9%D8%A7%D9%86%D8%A7%D8%AA_%D8%AC%D8%AF%DB%8C%D8%AF/%D8%B3%D9%88%D8%A7%D9%84%D8%A7%D8%AA_%D9%85%D8%AA%D8%AF%D8%A7%D9%88%D9%84] | {{status|missing}}[[w:fa:User:Ladsgroup|Amir]] | {{status|done}}[http://fa.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%E2%80%8C%D9%BE%D8%AF%DB%8C%D8%A7:%D8%A7%D9%85%DA%A9%D8%A7%D9%86%D8%A7%D8%AA_%D8%AC%D8%AF%DB%8C%D8%AF/%D8%A8%D8%A7%D8%B2%D8%AE%D9%88%D8%B1%D8%AF] | {{status|done}} <span id="fi" /> |- valign="top" | [[w:fi:|fi]] | {{status|done}}[[:fi:Wikipedia:Kahvihuone (tekniikka)|Village pump]] | {{status|published}}<nowiki>{{SITENAME}}</nowiki> saa uuden ilmeen. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Auta meitä löytämään virheet ja täydentämään käännökset]. | {{status|done}}<nowiki>{{SITENAME}}</nowiki> saa uuden ilmeen. [http://fi.wikipedia.org/wiki/Wikipedia:K%C3%A4ytt%C3%A4j%C3%A4kokemuspalaute/Uudet_ominaisuudet Lisätietoja]. | {{status|done}}[http://fi.wikipedia.org/wiki/Wikipedia:K%C3%A4ytt%C3%A4j%C3%A4kokemuspalaute/Uudet_ominaisuudet] | {{status|published}}Huomaatko jotakin erilaista? Olemme tehneet parannuksia <nowiki>{{GRAMMAR:illative|{{SITENAME}}}}</nowiki>. [http://fi.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Lisätietoja]. | {{status|missing}} | {{status|missing}} | {{status|done}}[http://fi.wikipedia.org/wiki/Wikipedia:K%C3%A4ytt%C3%A4j%C3%A4kokemuspalaute] | {{status|done}} <span id="fr" /> |- valign="top" | [[w:|fr]] | {{status|done}}Bistro, list de discussion, etc. | {{status|done}}<nowiki>{{SITENAME}}</nowiki> se donne une nouvelle allure. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Aidez-nous à éradiquer les bogues et à compléter les traductions d’interface.] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> se donne une nouvelle allure. [http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Retours_d%27exp%C3%A9rience_sur_l%27utilisabilit%C3%A9/Nouvelles_fonctionnalit%C3%A9s En savoir plus] | {{status|done}}[http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Retours_d%27exp%C3%A9rience_sur_l%27utilisabilit%C3%A9/Nouvelles_fonctionnalit%C3%A9s] | {{status|done}}Avez-vous remarqué les différences ? Nous avons apporté quelques améliorations à/au <nowiki>{{SITENAME}}</nowiki>. [http://fr.wikipedia.org/wiki/Sp%C3%A9cial:UsabilityInitiativePrefSwitch En savoir plus.] | {{status|done}}[http://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Retours_d%27exp%C3%A9rience_sur_l%27utilisabilit%C3%A9/FAQ] | {{status|done}}&mdash; | {{status|done}}[http://fr.wikipedia.org/wiki/Wikipédia:Retours_d'expérience_sur_l'utilisabilité] | {{status|done}} <span id="gl" /> |- valign="top" | [[w:gl:|gl]] | {{status|done}}[[w:gl:Wikipedia:A Taberna (novas)#Nova interface|A Taberna]] | {{status|published}}A Wikipedia renova a súa imaxe. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Axúdanos a atopar erros e completar as traducións da interface.] | {{status|published}}A Wikipedia renova a súa imaxe. [http://gl.wikipedia.org/wiki/Wikipedia:Comentarios_dos_usuarios/Novas_características Máis información] | {{status|done}}[http://gl.wikipedia.org/wiki/Wikipedia:Comentarios_dos_usuarios/Novas_características] | {{status|published}}Notaches algo diferente? Fixemos algunhas melloras na Wikipedia. [http://gl.wikipedia.org/wiki/Especial:UsabilityInitiativePrefSwitch Máis información.] | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|missing}} | {{status|done}}[http://gl.wikipedia.org/wiki/Wikipedia:Comentarios_dos_usuarios] | {{status|done}} <span id="he" /> |- valign="top" | [[w:|he]] | {{status|done}} [[:he:ויקיפדיה:לוח מודעות]] (noticeboard) | {{status|done}}ויקיפדיה מקבלת מראה חדש. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change עזרו לנו למצוא טעויות ולהשלים את תרגום ממשק המשתמש]. | {{status|done}}ויקיפדיה מקבלת מראה חדש. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features למידע נוסף]. | {{status|done}}[http://he.wikipedia.org/wiki/%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%A4%D7%99%D7%AA%D7%95%D7%97_%D7%94%D7%AA%D7%A9%D7%AA%D7%99%D7%AA/%D7%95%D7%A7%D7%98%D7%95%D7%A8/%D7%AA%D7%9B%D7%95%D7%A0%D7%95%D7%AA_%D7%97%D7%93%D7%A9%D7%95%D7%AA] | {{status|done}}הבחנתם בשינוי? שיפרנו את השמישות של ויקיפדיה. [http://en.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch למידע נוסף]. | {{status|done}}[http://he.wikipedia.org/wiki/%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%A4%D7%99%D7%AA%D7%95%D7%97_%D7%94%D7%AA%D7%A9%D7%AA%D7%99%D7%AA/%D7%95%D7%A7%D7%98%D7%95%D7%A8/%D7%A9%D7%90%D7%9C%D7%95%D7%AA_%D7%95%D7%AA%D7%A9%D7%95%D7%91%D7%95%D7%AA] | {{status|done}}[[:en:User:Amire80|Amir E. Aharoni]] | {{status|done}}[http://he.wikipedia.org/wiki/%D7%95%D7%99%D7%A7%D7%99%D7%A4%D7%93%D7%99%D7%94:%D7%A4%D7%99%D7%AA%D7%95%D7%97_%D7%94%D7%AA%D7%A9%D7%AA%D7%99%D7%AA/%D7%95%D7%A7%D7%98%D7%95%D7%A8] | {{status|done}} <span id="hsb" /> |- valign="top" | [[w:hsb:|hsb]] | {{status|done}}[http://hsb.wikipedia.org/wiki/Wikipedija:Korčma Village pump] | {{status|progress}}Wikipedija dóstanje nowy napohlad. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Pomhaj nam při testowanju a přełožowanju.] | {{status|progress}}Wikipedija dóstanje nowy napohlad. [http://hsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužiwajomnosće/Nowe_funkcije Dalše informacije...] | {{status|progress}}[http://hsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužiwajomnosće/Nowe_funkcije] | {{status|progress}}Sy změny spytnył? Smy <nowiki>{{GRAMMAR:akuzatiw|{{SITENAME}}}}</nowiki> polěpšili. [http://hsb.wikipedia.org/wiki/Specialne:UsabilityInitiativePrefSwitch/Nowe_funkcije Dalše informacije...] | {{status|progress}}[http://hsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužiwajomnosće/FAQ] | {{status|missing}} | {{status|progress}}[http://hsb.wikipedia.org/wiki/Wikipedija:Iniciatiwa_wužiwajomnosće/Měnjenja] | {{status|progress}} <span id="hu" /> |- valign="top" | [[w:hu:|hu]] | {{status|done}} [http://hu.wikipedia.org/wiki/Wikip%C3%A9dia:Sajt%C3%B3k%C3%B6zlem%C3%A9nyek/%C3%9Aj_kin%C3%A9zetet_kap_a_magyar_Wikip%C3%A9dia press release], mailing list/village pump announcements earlier | {{status|done}}A Wikipédia új kinézetet kap. [http://hu.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%81t%C3%A1ll%C3%A1s_Vectorra Segíts megtalálni a hibákat és javítani a fordításokat!] | {{status|done}}A Wikipédia új kinézetet kap. [http://hu.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%81t%C3%A1ll%C3%A1s_Vectorra Tudj meg többet!] | {{status|done}}[http://hu.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%81t%C3%A1ll%C3%A1s_Vectorra] | {{status|done}}Valami szokatlan? Egy kis ráncfelvarrást végeztünk a Wikipédián. [http://hu.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Tudj meg többet!] | {{status|done}}[http://hu.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%81t%C3%A1ll%C3%A1s_Vectorra/GyIK] | {{status|done}}[[:hu:User:Tgr|Tgr]] | {{status|done}}[http://hu.wikipedia.org/wiki/Wikip%C3%A9dia:%C3%81t%C3%A1ll%C3%A1s_Vectorra/visszajelz%C3%A9s] | {{status|done}} <span id="ka" /> |- valign="top" | [[w:ka:|ka]] | {{status|done}}[[w:ka:ვიკიპედია:ყავახანა#Usability|ფორუმი]] [[:w:ka:%E1%83%97%E1%83%90%E1%83%A0%E1%83%92%E1%83%98:%E1%83%92%E1%83%90%E1%83%9C%E1%83%AA%E1%83%AE%E1%83%90%E1%83%93%E1%83%94%E1%83%91%E1%83%94%E1%83%91%E1%83%98|თარგი:განცხადებები]] | {{status|done}}ვიკიპედია სახეს იცვლის. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change დაგვეხმარეთ შეცდომების პოვნაში და ინტერფეისის თარგმნაში.] | {{status|done}}ვიკიპედია სახეს იცვლის. [http://ka.wikipedia.org/wiki/ვიკიპედია:ბეტა/ახალი_შესაძლებლობები გაიგეთ მეტი.] | {{status|done}}[http://ka.wikipedia.org/wiki/ვიკიპედია:ბეტა/ახალი_შესაძლებლობები] | {{status|reday}}ჩვენ ოდნავ გავაუმჯობესეთ ვიკიპედია. შეიტყვეთ მეტი. | {{status|done}}[http://ka.wikipedia.org/wiki/ვიკიპედია:ბეტა/ახალი_შესაძლებლობები/FAQ] | {{status|done}}[[:ka:User:Gaeser|Gaeser]] | {{status|done}}[http://ka.wikipedia.org/wiki/ვიკიპედია:ბეტა/ახალი_შესაძლებლობები/გამოხმაურებები] | {{status|done}} <span id="ko" /> |- valign="top" | [[w:ko:|ko]] | {{status|done}} [[:w:ko:위키백과토론:위키프로젝트 시스템/벡터 스킨|관련 토론란 (Related discussion)]] | {{status|done}} <nowiki>{{SITENAME}}</nowiki>(이)가 새롭게 바뀝니다. 문제점이나 개선할 점이 있다면 [[:w:ko:위키백과토론:위키프로젝트 시스템/벡터 스킨|여기]]에 알려 주세요. | {{status|done}} <nowiki>{{SITENAME}}</nowiki>(이)가 새롭게 바뀝니다. [http://ko.wikipedia.org/wiki/%ED%8A%B9%EC%88%98%EA%B8%B0%EB%8A%A5:UsabilityInitiativePrefSwitch 자세히 알아보기] | {{status|done}} [http://ko.wikipedia.org/wiki/%ED%8A%B9%EC%88%98%EA%B8%B0%EB%8A%A5:UsabilityInitiativePrefSwitch] | {{status|done}} 더 사용하기 편리해진 <nowiki>{{SITENAME}}</nowiki>, 조금 바뀐 것이 느껴지시나요? [http://ko.wikipedia.org/wiki/%ED%8A%B9%EC%88%98%EA%B8%B0%EB%8A%A5:UsabilityInitiativePrefSwitch 자세히 알아보기] | {{status|done}} | {{status|done}} [[:ko:User:Klutzy|Klutzy]] | {{status|done}} [http://ko.wikipedia.org/wiki/%EC%9C%84%ED%82%A4%EB%B0%B1%EA%B3%BC%ED%86%A0%EB%A1%A0:%EC%9C%84%ED%82%A4%ED%94%84%EB%A1%9C%EC%A0%9D%ED%8A%B8_%EC%8B%9C%EC%8A%A4%ED%85%9C/%EB%B2%A1%ED%84%B0_%EC%8A%A4%ED%82%A8] | {{status|done}} <span id="be-x-old" /> |- valign="top" | [[w:mk:|mk]] | {{status|done}} Notice on the [http://mk.wikipedia.org/w/index.php?title=%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%98%D0%B0:%D0%A1%D0%B5%D0%BB%D1%81%D0%BA%D0%B0_%D1%87%D0%B5%D1%88%D0%BC%D0%B0&oldid=1113556 local village pump (Селска чешма)] + on the mk.wiki mailing list | {{status|done}}Википедија добива нов изглед. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Помогнете ни да ги пронајдеме грешките и да го завршиме преводот за посредничкиот елемент.] | {{status|published}} Википедија добива нов изглед. [http://mk.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%98%D0%B0:%D0%9A%D0%BE%D0%BC%D0%B5%D0%BD%D1%82%D0%B0%D1%80%D0%B8_%D0%B7%D0%B0_%D0%BA%D0%BE%D1%80%D0%B8%D1%81%D0%BD%D0%B8%D1%87%D0%BA%D0%BE%D1%82%D0%BE_%D0%B8%D1%81%D0%BA%D1%83%D1%81%D1%82%D0%B2%D0%BE/%D0%9D%D0%BE%D0%B2%D0%B8_%D0%BC%D0%BE%D0%B6%D0%BD%D0%BE%D1%81%D1%82%D0%B8 Дознајте повеќе.] | {{status|done}}[http://mk.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%98%D0%B0:%D0%9A%D0%BE%D0%BC%D0%B5%D0%BD%D1%82%D0%B0%D1%80%D0%B8_%D0%B7%D0%B0_%D0%BA%D0%BE%D1%80%D0%B8%D1%81%D0%BD%D0%B8%D1%87%D0%BA%D0%BE%D1%82%D0%BE_%D0%B8%D1%81%D0%BA%D1%83%D1%81%D1%82%D0%B2%D0%BE/%D0%9D%D0%BE%D0%B2%D0%B8_%D0%BC%D0%BE%D0%B6%D0%BD%D0%BE%D1%81%D1%82%D0%B8] | {{status|published}}Забележувате нешто различно? Направивме некои подобрувања на Википедија. [http://mk.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Дознајте повеќе.] |{{status|done}}[http://usability.wikimedia.org/wiki/%D0%A8%D1%82%D0%BE_%D0%B5_%D0%BD%D0%BE%D0%B2%D0%BE,_%D0%BF%D1%80%D0%B0%D1%88%D0%B0%D1%9A%D0%B0_%D0%B8_%D0%BE%D0%B4%D0%B3%D0%BE%D0%B2%D0%BE%D1%80%D0%B8] | {{status|done}} [[w:mk:Корисник:Brainmachine|Brainmachine]] |{{status|done}}[http://mk.wikipedia.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D0%B5%D0%B4%D0%B8%D1%98%D0%B0:%D0%9A%D0%BE%D0%BC%D0%B5%D0%BD%D1%82%D0%B0%D1%80%D0%B8_%D0%B7%D0%B0_%D0%BA%D0%BE%D1%80%D0%B8%D1%81%D0%BD%D0%B8%D1%87%D0%BA%D0%BE%D1%82%D0%BE_%D0%B8%D1%81%D0%BA%D1%83%D1%81%D1%82%D0%B2%D0%BE] | {{status|done}} <span id="ml" /> |- valign="top" | [[w:ml:|ml]] | {{status|done}}[[:ml:വിക്കിപീഡിയ:പഞ്ചായത്ത് (നയരൂപീകരണം)#Changing to new interface|Village pump]]<br /> {{status|done}}[http://lists.wikimedia.org/pipermail/wikiml-l/2010-May/001215.html Mailing list]<br /> {{status|done}}[[:ml:മീഡിയവിക്കി:Sitenotice|Site Notice]] | {{status|done}}വിക്കിപീഡിയയ്ക്ക് പുതിയ മുഖം. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change ബഗുകൾ കണ്ടെത്താനും സമ്പർക്കമുഖത്തിന്റെ മലയാള പരിഭാഷ പൂർണ്ണമാക്കുവാനും ഞങ്ങളെ സഹായിക്കുമല്ലോ.] | {{status|done}}വിക്കിപീഡിയയ്ക്ക് പുതിയ മുഖം. [[:ml:വിക്കിപീഡിയ:ഉപയോക്തൃ_അനുഭവ_അഭിപ്രായങ്ങൾ/പുതിയ_സവിശേഷതകൾ|കൂടുതൽ അറിയുക.]] | {{status|done}}[http://ml.wikipedia.org/wiki/വിക്കിപീഡിയ:ഉപയോക്തൃ_അനുഭവ_അഭിപ്രായങ്ങൾ/പുതിയ_സവിശേഷതകൾ] | {{status|done}}വ്യത്യാസമെന്തെങ്കിലും തോന്നുന്നുണ്ടോ? ഞങ്ങൾ കുറച്ചു മാറ്റങ്ങൾ വരുത്തിയിട്ടുണ്ട്. [http://ml.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch കൂടുതൽ അറിയുക]. | {{status|done}}[http://ml.wikipedia.org/wiki/വിക്കിപീഡിയ:ഉപയോക്തൃ_അനുഭവ_അഭിപ്രായങ്ങൾ/പതിവു_ചോദ്യങ്ങൾ] | {{status|done}}[[w:User:Shijualex|Shijualex]] | {{status|done}}[http://ml.wikipedia.org/wiki/വിക്കിപീഡിയ:ഉപയോക്തൃ_അനുഭവ_അഭിപ്രായങ്ങൾ] | {{status|done}} <span id="ms" /> |- valign="top" | [[w:ms:|ms]] | {{status|done}}[http://ms.wikipedia.org/wiki/Wikipedia:Kedai_Kopi_(teknikal) Village pump] | {{status|done}}Wikipedia akan berubah kepada muka baru. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Bantulah kami mengesan kesilapan dan menlengkapkan penterjemahan.] | {{status|done}}Wikipedia akan berubah kepada muka baru. [[:ms:Wikipedia:Pendapat_dan_cadangan_pengguna/Ciri-ciri_baru|Ketahui lebih lanjut.]] | {{status|done}}[http://ms.wikipedia.org/wiki/Wikipedia:Pendapat_dan_cadangan_pengguna/Ciri-ciri_baru] | {{status|done}}Adakah laman ini berlainan daripada biasa? Kami telah memperbaharui Wikipedia. [[:ms:Wikipedia:Pendapat_dan_cadangan pengguna/Ciri-ciri_baru|Ketahui lebih lanjut.]] | {{status|done}}[http://en.wikipedia.org/wiki/Wikipedia:Vector] | {{status|done}}[[w:User:Diagramma Della Verita|Diagramma Della Verita]] | {{status|done}}[http://ms.wikipedia.org/wiki/Wikipedia:Pendapat_dan_cadangan_pengguna] | {{status|done}} <span id="nn" /> |- valign="top" | [[w:nn:|nn]] | {{status|missing}} | {{status|done}}Wikipedia får snart ny utsjånad. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Hjelp oss med å finne feil og gjere ferdig omsetjinga …] | {{status|done}}Wikipedia får snart ny utsjånad. [http://nn.wikipedia.org/wiki/Wikipedia:Nytt_grensesnitt Finn ut meir …] | {{status|missing}}[http://nn.wikipedia.org/wiki/Wikipedia:Nytt_grensesnitt] | {{status|done}}Ser du noko nytt? Vi har gjort nokre forbetringar på Wikipedia. [http://nn.wikipedia.org/wiki/Wikipedia:Nytt_grensesnitt Finn ut meir …] | {{status|missing}}[http://nn.wikipedia.org/wiki/Wikipedia:Nytt_grensesnitt/Spørsmål_og_svar] | {{status|done}}&mdash; | {{status|done}}[http://nn.wikipedia.org/wiki/Wikipedia:Nytt_grensesnitt/Tilbakemeldingar] | {{status|missing}} <span id="no"> |-valign="top" | [[w:no|no]] | | <nowiki>{{SITENAME}}</nowiki> får snart nytt utseende. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Hjelp oss med å finne feil, og å oversette ferdig ...] | <nowiki>{{SITENAME}}</nowiki> får snart nytt utseende. [[:en:Special:UsabilityInitiativePrefSwitch|Les mer]]... | {{status|missing}} [http://no.wikipedia.org/wiki/Wikipedia:Nytt_grensesnitt] | Legger du merke til noe nytt? Vi har gjort noen forbedringer på Wikipedia. [[:w:en:Special:UsabilityInitiativePrefSwitch|Les mer]]. | {{status|missing}} | | {{status|missing}} | <span id="vi" /> |- valign="top" | [[w:|vi]] | {{status|done}}Local Village pump, Admin notice board | {{status|done}}Wikipedia sắp có một dáng vẻ hoàn toàn mới. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Hãy giúp chúng tôi tìm lỗi và hoàn thiện các bản dịch giao diện.] | {{status|done}}Wikipedia sắp có một dáng vẻ hoàn toàn mới. [http://vi.wikipedia.org/wiki/Wikipedia:Phản_hồi_trải_nghiệm_của_người_dùng/Tính_năng_mới Tìm hiểu thêm] | {{status|done}}[http://en.wikipedia.org/wiki/Phản_hồi_trải_nghiệm_của_người_dùng/Tính_năng_mới] | {{status|done}}Bạn cảm thấy có gì khang khác phải không? Chúng tôi đã thực hiện vài cải tiến cho Wikipedia. [http://vi.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Tìm hiểu thêm.] | {{status|done}} [http://vi.wikipedia.org/wiki/Wikipedia:Ph%E1%BA%A3n_h%E1%BB%93i_tr%E1%BA%A3i_nghi%E1%BB%87m_c%E1%BB%A7a_ng%C6%B0%E1%BB%9Di_d%C3%B9ng/H%E1%BB%8Fi_%C4%91%C3%A1p] | [[:vi:User:Vinhtantran|Vinhtantran]] | {{status|done}}[http://vi.wikipedia.org/wiki/Wikipedia:Ph%E1%BA%A3n_h%E1%BB%93i_tr%E1%BA%A3i_nghi%E1%BB%87m_c%E1%BB%A7a_ng%C6%B0%E1%BB%9Di_d%C3%B9ng] | {{status|done}} <span id="zh" /> |- valign="top" | [[w:zh:|zh]] | {{status|done}}[[:zh:维基百科:互助客栈/消息#九個語言維基百科於6月10日啟用新介面|Village pump]]<br/> {{status|done}}{{[[:zh:Template:Bulletin|Bulletin]]}}<ref>in [[Special:Recentchanges|Recent Changes]] for contributors</ref><br/>{{status|done}}[http://lists.wikimedia.org/pipermail/wikizh-l/2010-June/000494.html Mailing List]<br/>{{status|done}}[[:zh:|<span title="Main Page notice">Main Page</span>]]<ref>Notice on the [[:zh:|Chinese Wikipedia Main Page]] for all users</ref><br/>{{status|done}}[[:zh:維基百科:雙周提示/2010年6月26日|TOTD]]<ref>Similar to the tips of a day in English Wikipedia. This tips will display to Chinese Wikipedia Editors on 26-06-2010 to 09-07-2010.</ref> | {{status|published}}(hans): 维基百科将更换新的界面。[http://zh.wikipedia.org/wiki/Wikipedia:用戶體驗反饋 帮助我们寻找程序错误并完成用户界面翻译。]<br /> {{status|published}}(hant): 維基百科將更換新的介面。[http://zh.wikipedia.org/wiki/Wikipedia:用戶體驗反饋 幫助我們尋找程式錯誤並完成使用者介面翻譯。] | {{status|published}}(hans): 维基百科将更换新的界面。[http://zh.wikipedia.org/wiki/Wikipedia:用户体验反馈/新功能 到此了解详情。]<!--zh-hans, zh-cn, zh-my, zh-sg--><br /> {{status|published}}(hant): 維基百科將更換新的介面。[http://zh.wikipedia.org/wiki/Wikipedia:用户体验反馈/新功能 到此了解詳情。]<!--zh-hant, zh, zh-hk, zh-mo, zh-tw--> | {{status|done}}[http://zh.wikipedia.org/wiki/Wikipedia:用户体验反馈/新功能]<br/>{{status|done}}[http://zh.wikipedia.org/wiki/Wikipedia:%E5%8F%8C%E5%91%A8%E6%8F%90%E7%A4%BA/2010%E5%B9%B48%E6%9C%887%E6%97%A5] | {{status|published}}(hans): 注意到有什么变化了吗？维基百科作了一些改进。[http://zh.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch 到此了解详情。]<!--zh-hans, zh-cn, zh-my, zh-sg--><br /> {{status|published}}(hant): 注意到有什麼變化了嗎？維基百科作了一些改進。[http://zh.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch 到此了解詳情。]<!--zh-hant, zh, zh-hk, zh-mo, zh-tw--> | {{status|done}}[http://zh.wikipedia.org/wiki/Wikipedia:%E7%94%A8%E6%88%B6%E9%AB%94%E9%A9%97%E5%8F%8D%E9%A5%8B/FAQ] | {{status|done}}[http://zh.wikipedia.org/wiki/Wikipedia:%E5%8F%AF%E7%94%A8%E6%80%A7%E5%B0%88%E9%A1%8C Usability WikiProject] | {{status|done}}[http://zh.wikipedia.org/wiki/Wikipedia:%E7%94%A8%E6%88%B6%E9%AB%94%E9%A9%97%E5%8F%8D%E9%A5%8B] | {{status|done}} <span id="zh-yue" /><span id="yue" /> |- valign="top" | [[w:zh-yue:|yue]] | {{status|done}}[[:zh-yue:Wikipedia:城市論壇 (雜項)#Vector|Village pump]] | {{status|published}}維基百科將換新界面。[http://zh-yue.wikipedia.org/wiki/Wikipedia:%E7%94%A8%E6%88%B6%E6%84%8F%E8%A6%8B 幫我地搵臭蟲同翻譯。] | {{status|published}}維基百科將換新界面。[http://zh-yue.wikipedia.org/wiki/Wikipedia:用戶意見/新功能 了解詳情。] | {{status|published}}[http://zh-yue.wikipedia.org/wiki/Wikipedia:%E7%94%A8%E6%88%B6%E6%84%8F%E8%A6%8B/%E6%96%B0%E5%8A%9F%E8%83%BD] | {{status|done}}係埋唔同咗呢？維基百科改進咗喇。[http://zh-yue.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch 睇下知多啲啦]。 | {{status|done}}[http://zh-yue.wikipedia.org/wiki/%E7%B6%AD%E5%9F%BA%E7%99%BE%E7%A7%91:%E7%94%A8%E6%88%B6%E6%84%8F%E8%A6%8B/FAQ] | {{status|missing}} | {{status|done}}[http://zh-yue.wikipedia.org/wiki/Wikipedia:%E7%94%A8%E6%88%B6%E6%84%8F%E8%A6%8B] | {{status|done}} <span id="bn" /> |- valign="top" | [[w:bn:|bn]] | {{status|done}}[[:w:bn:উইকিপিডিয়া:প্রশাসকদের আলোচনাসভা#নতুন চেহারায় উইকিপিডিয়া|Admin notice board]] | {{status|done}}নতুন চেহারায় <nowiki>{{SITENAME}}</nowiki>। [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change বাগ খুঁজে বের করতে ও ব্যবহারকারী ইন্টারফেস অনুবাদে আমাদের সাহায্য করুন]। | {{status|done}}<nowiki>{{SITENAME}}</nowiki> এখন নতুন চেহারায়। [http://bn.wikipedia.org/wiki/%E0%A6%89%E0%A6%87%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE:%E0%A6%AC%E0%A7%8D%E0%A6%AF%E0%A6%AC%E0%A6%B9%E0%A6%BE%E0%A6%B0%E0%A6%95%E0%A6%BE%E0%A6%B0%E0%A7%80%E0%A6%B0_%E0%A6%85%E0%A6%AD%E0%A6%BF%E0%A6%9C%E0%A7%8D%E0%A6%9E%E0%A6%A4%E0%A6%BE%E0%A6%B2%E0%A6%AC%E0%A7%8D%E0%A6%A7_%E0%A6%AE%E0%A6%A4%E0%A6%BE%E0%A6%AE%E0%A6%A4/%E0%A6%A8%E0%A6%A4%E0%A7%81%E0%A6%A8_%E0%A6%AC%E0%A7%88%E0%A6%B6%E0%A6%BF%E0%A6%B7%E0%A7%8D%E0%A6%9F%E0%A7%8D%E0%A6%AF%E0%A6%BE%E0%A6%AC%E0%A6%B2%E0%A7%80 বিস্তারিত জানুন]। | {{status|progress}}[http://bn.wikipedia.org/wiki/%E0%A6%89%E0%A6%87%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE:%E0%A6%AC%E0%A7%8D%E0%A6%AF%E0%A6%AC%E0%A6%B9%E0%A6%BE%E0%A6%B0%E0%A6%95%E0%A6%BE%E0%A6%B0%E0%A7%80%E0%A6%B0_%E0%A6%85%E0%A6%AD%E0%A6%BF%E0%A6%9C%E0%A7%8D%E0%A6%9E%E0%A6%A4%E0%A6%BE%E0%A6%B2%E0%A6%AC%E0%A7%8D%E0%A6%A7_%E0%A6%AE%E0%A6%A4%E0%A6%BE%E0%A6%AE%E0%A6%A4/%E0%A6%A8%E0%A6%A4%E0%A7%81%E0%A6%A8_%E0%A6%AC%E0%A7%88%E0%A6%B6%E0%A6%BF%E0%A6%B7%E0%A7%8D%E0%A6%9F%E0%A7%8D%E0%A6%AF%E0%A6%BE%E0%A6%AC%E0%A6%B2%E0%A7%80] | {{status|done}}নতুন কিছু খেয়াল করেছেন? আমরা <nowiki>{{SITENAME}}</nowiki> এর কিছু উন্নয়ন সাধন করেছি। [http://bn.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch বিস্তারিত জানুন]। | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}&mdash; | {{status|progress}}[http://bn.wikipedia.org/wiki/%E0%A6%89%E0%A6%87%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE:%E0%A6%AC%E0%A7%8D%E0%A6%AF%E0%A6%AC%E0%A6%B9%E0%A6%BE%E0%A6%B0%E0%A6%95%E0%A6%BE%E0%A6%B0%E0%A7%80%E0%A6%B0_%E0%A6%85%E0%A6%AD%E0%A6%BF%E0%A6%9C%E0%A7%8D%E0%A6%9E%E0%A6%A4%E0%A6%BE%E0%A6%B2%E0%A6%AC%E0%A7%8D%E0%A6%A7_%E0%A6%AE%E0%A6%A4%E0%A6%BE%E0%A6%AE%E0%A6%A4] | {{status|done}} <span id="pt" /> |- valign="top" | [[w:pt:|pt]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog]<br />{{status|done}}[[w:pt:Wikipedia:Esplanada/anúncios#Nova_interface_na_Wikip.C3.A9dia_lus.C3.B3fona|Esplanada (EA)]] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> está a mudar de aparência. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Ajude-nos a encontrar problemas e a completar as traduções da interface de utilizador.] | {{status|missing}} | {{status|done}}[http://pt.wikipedia.org/wiki/Wikipedia:Feedback_de_experiência_de_usuário/Novas_funcionalidades] | {{status|done}}Notou algo diferente? Fizemos algumas melhorias em <nowiki>{{SITENAME}}</nowiki>. [[:pt:Wikipedia:Feedback de experiência de usuário/Novas funcionalidades|Saiba mais]]. | {{status|done}}[http://pt.wikipedia.org/wiki/Wikipedia:Feedback_de_experiência_de_usuário/FAQ] | {{status|missing}} | {{status|done}}[http://pt.wikipedia.org/wiki/Wikipedia:Feedback_de_experiência_de_usuário] | {{status|done}} <span id="io" /> |- valign="top" | [[w:io:|io]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog] | {{status|published}}<nowiki>{{SITENAME}}</nowiki> obtenos nova semblo balde [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Helpez ni trovar erori e kompletigar la sistemala tradukuri] | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} <span id="vo" /> |- valign="top" | [[w:vo:|vo]] | {{status|done}}[http://blog.wikimedia.org/2010/new-wikipedia-interface-to-nine-more-languages/ WMF blog] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> dageton selogami nulik. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Yufolös obes ad tüvön pölis e ad tradutön sitanunis.] | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} | {{status|missing}} <span id="ckb" /> |- valign="top" | [[:ckb:|ckb]] | {{status|done}}[[:ckb:ویکیپیدیا:دیوەخان (تەکنیکی)|Local Village pump]] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> خەریکە دیمەنێکی نوێ لە خۆ دەگرێت. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change یارمەتیمان بدە ھەڵەکان بدۆزینەوە و وەرگێڕانی ڕووکارەکەی دوایی بێنین.] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> خەریکە دیمەنێکی نوێ لە خۆ دەگرێت. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features زانیاریی زۆرتر] | {{status|done}}[http://ckb.wikipedia.org/wiki/%D9%88%DB%8C%DA%A9%DB%8C%D9%BE%DB%8C%D8%AF%DB%8C%D8%A7:%D8%AA%D8%A7%DB%8C%D8%A8%DB%95%D8%AA%D9%85%DB%95%D9%86%D8%AF%DB%8C%DB%8C%DB%95_%D9%86%D9%88%DB%8E%DA%A9%D8%A7%D9%86] | {{status|done}}ھەستت کردووە شتێک گۆڕدراوە؟ چەند چاکسازیمان کردووە بۆ <nowiki>{{SITENAME}}</nowiki>. [http://en.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch زانیاریی زۆرتر.] | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}} [[:ckb:user:ئاسۆ|ئاسۆ]] | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|missing}} <span id="ar" /> |- valign="top" | [[:ar:|ar]] | {{status|done}}[[:ar:ويكيبيديا:الميدان/أرشيف/أخبار/05/2010|Local Village pump]] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> ستأخذ حلة جديدة. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change اقرأ المزيد.] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> .أصبح لويكيبيديا واجهة جديدة [http://ar.wikipedia.org/wiki/ويكيبيديا:واجهة_المستخدم_الجديدة/مزايا_جديدة اقرأ المزيد] | {{status|done}}[http://ar.wikipedia.org/wiki/ويكيبيديا:واجهة_المستخدم_الجديدة/أكثر_الأسئلة_شيوعا] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> هل لاحظت شيئا مختلفا؟ لقد أجرينا تحسينات على واجهة ويكيبيديا [http://ar.wikipedia.org/wiki/ويكيبيديا:واجهة_المستخدم_الجديدة/مزايا_جديدة اقرأ المزيد]. | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}} | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|missing}} <span id="yo" /> |- valign="top" | [[w:yo:|yo]] | {{status|missing}} | {{status|published}}<nowiki>{{SITENAME}}</nowiki> úngba ìwòojú tuntun. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Ẹ ràn wá lọ́wọ́ láti wá àsìṣe àti láti parí àwọn ìyédèpadà ojúiṣẹ́ oníṣe.] | {{status|published}}<nowiki>{{SITENAME}}</nowiki> úngba ìwòojú tuntun. [http://yo.wikipedia.org/wiki/Wikipedia:Ìdáhùn_ìrírí_oníṣe/Àwọn_ìní_tuntun Ẹ̀kúnrẹ́rẹ́] | {{status|missing}}[http://yo.wikipedia.org/wiki/Wikipedia:Ìdáhùn_ìrírí_oníṣe/Àwọn_ìní_tuntun] | {{status|published}}Ṣé ẹ rí ìyàtọ̀? A ti ṣe àwọn ìmúdára sí <nowiki>{{SITENAME}}</nowiki>. [http://yo.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Ẹ̀kúnrẹ́rẹ́.] | {{status|missing}} | {{status|published}}[[w:yo:User:Demmy|Demmy]] | {{status|missing}}[http://yo.wikipedia.org/wiki/Wikipedia:Ìdáhùn_ìrírí_oníṣe] | {{status|published}} <span id="sv" /> |- valign="top" | [[w:|sv]] | {{status|done}}[http://sv.wikipedia.org/w/index.php?title=Wikipedia:Bybrunnen&oldid=12002455#Vector_kommer_-_Nytt_utseende_p.C3.A5_Wikipedia Local Village pump], Wikimedia Sverige blog | {{status|done}}Wikipedia får ett nytt utseende. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features Mer information.] | {{status|done}}Wikipedia får ett nytt utseende. | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}Märker du skillnaden? Wikipedia har blivit bättre. [[Special:UsabilityInitiativePrefSwitch|Mer information om de nya funktionerna]]. | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}}[http://sv.wikipedia.org/wiki/User:Hannibal Hannibal] | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|missing}} <span id="yi" /> |- valign="top" | [[w:yi:|yi]] | {{status|done}}[[:yi:וויקיפעדיע:קאווע שטיבל#נייער איבערפלאך|Local Village pump]] | {{status|done}}װיקיפּעדיע באַקומט א נײַע אויסזע. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change העלפֿט אונז טרעפֿן גרײַזן און פֿאַרענדיקן די באַניצער איבערפֿלאַך פֿאַרטײַטשן.] | {{status|published}}װיקיפּעדיע באַקומט א נײַע אויסזע. [http://yi.wikipedia.org/wiki/װיקיפּעדיע:ניצלעכקייט־איניציאטיוו/נייע_אייגנקייטן מער אינפֿארמאַציע …] | {{status|published}}[http://yi.wikipedia.org/wiki/װיקיפּעדיע:ניצלעכקייט־איניציאטיוו/נייע_אייגנקייטן] | {{status|published}}האט איר באַמערקט די ענדערונגען? מיר האבן פֿאַרבעסערט . <nowiki>{{SITENAME}}</nowiki>. [http://yi.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch מער אינפֿארמאַציע …] | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|missing}}&mdash; | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|missing}} |- valign="top" | [[w:|tr]] | {{status|missing}}Local Village pump, Mailing list, etc. | {{status|published}}<nowiki>{{SITENAME}}</nowiki> yeni bir görünüme kavuşuyor. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Kullanıcı arayüzü çevirilerini tamamlamamıza ve hataları bulmamıza yardım edin.] | {{status|missing}}<nowiki>{{SITENAME}}</nowiki> yeni bir görünüme kavuşuyor. [http://tr.wikipedia.org/wiki/Vikipedi:Kullanıcı_deneyim_geribildirimi Daha fazlası için] | {{status|missing}}[http://tr.wikipedia.org/wiki/Vikipedi:Kullanıcı_deneyim_geribildirimi/Yeni_özellikler] | {{status|done}}Değişikliği fark ettiniz mi? <nowiki>{{SITENAME}}</nowiki> üzerinde birkaç geliştirme yaptık. [http://tr.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Daha fazlasını öğren.] | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|missing}}&mdash; | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}} <span id="th" /> |- valign="top" | [[w:|th]] | {{status|missing}} | {{status|done}}<nowiki>{{SITENAME}}</nowiki> ได้หน้าตาใหม่ [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change ช่วยเราหา bugs และแปล] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> ได้หน้าตาใหม่ [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features เพิ่มเติม] | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features] | {{status|done}}เห็นอะไรแปลกไปหรือเปล่า? เราได้ปรับปรุง <nowiki>{{SITENAME}}</nowiki>ใหม่ [http://en.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch เพิ่มเติม] | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|missing}} | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|missing}} <span id="id" /> |- valign="top" | [[w:|id]] | {{status|missing}}Local Village pump, Mailing list, etc. | {{status|missing}}<nowiki>{{SITENAME}}</nowiki> memperoleh tampilan baru. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Bantulah kami menemukan galat dan melengkapi penerjemahan antar-muka pengguna.] | {{status|missing}}<nowiki>{{SITENAME}}</nowiki> memperoleh tampilan baru. [http://id.wikipedia.org/wiki/Wikipedia:Umpan_balik_pengalaman_pengguna/Fitur_baru Pelajari lebih lanjut.] | {{status|missing}}[http://id.wikipedia.org/wiki/Wikipedia:Umpan_balik_pengalaman_pengguna/Fitur_baru] | {{status|missing}}Merasa ada yang berubah? Kami telah melakukan beberapa perbaikan untuk <nowiki>{{SITENAME}}</nowiki>. [http://id.wikipedia.org/wiki/Istimewa:UsabilityInitiativePrefSwitch Pelajari lebih lanjut.] | {{status|done}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|missing}}&mdash; | {{status|missing}}[http://id.wikipedia.org/wiki/Wikipedia:Umpan_balik_pengalaman_pengguna] | {{status|missing}} <span id="bg" /> |- valign="top" | [[w:bg:|bg]] | {{status|done}}Local Village pump | {{status|done}}<nowiki>{{SITENAME}}</nowiki> придобива нов облик. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Помогнете за откриването на бъгове и превод на интерфейсните съобщения.] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> придобива нов облик. [http://bg.wikipedia.org/wiki/Уикипедия:Вектор Научете повече.] | {{status|done}}[http://bg.wikipedia.org/wiki/Уикипедия:Вектор] | {{status|done}} Забелязвате ли нещо различно? В <nowiki>{{SITENAME}}</nowiki> са направени някои подобрения. [http://bg.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Научете повече.] | {{status|done}}[http://bg.wikipedia.org/wiki/Уикипедия:Вектор/Въпроси_и_отговори] | {{status|missing}}&mdash; | {{status|done}}[http://bg.wikipedia.org/wiki/Уикипедия:Вектор/Отзиви] | {{status|done}} <span id="frp" /> |- valign="top" | [[w:frp:|frp]] | {{status|done}}[http://frp.wikipedia.org/wiki/Vouiquip%C3%A8dia:Lo_C%C3%A2f%C3%A8_du_Vel%C3%A2jo Lo Câfè du Velâjo (Local Village pump)] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> change d’aparence. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Édiéd-nos a trovar les cofieries et pués a complètar les traduccions de l’entèrface utilisator.] | {{status|done}}<nowiki>{{SITENAME}}</nowiki> change d’aparence. [http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features Nen savêr més...] | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback/New_features] | {{status|done}}Quârque-ren at changiê ? <nowiki>{{SITENAME}}</nowiki> sè mèlyore ! [http://frp.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Nen savêr més...] | {{status|missing}}[http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers] | {{status|done}}[[w:frp:User:Darbé|Darbé]] | {{status|missing}}[http://en.wikipedia.org/wiki/Wikipedia:User_experience_feedback] | {{status|done}} <span id="lb" /> |- valign="top" | [[w:lb:|lb]] | {{status|missing}}De Staminee, Mailinglëscht, asw. | {{status|done}}Wikipedia kritt een neit Ausgesinn. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Hëlleft eis bei der Verbesserung vu Feeler a bäi der Iiwwersetzung!] | {{status|missing}}Wikipedia kritt een neit Ausgesinn. | {{status|missing}} | {{status|missing}}Hutt Dir eis Ännerunge gemierkt? Mir hu Wikipedia verbessert. | {{status|missing}}FAQ | {{status|missing}}&mdash; | {{status|missing}}Feedback | {{status|done}} <span id="krc" /> |- valign="top" | [[w:krc:|krc]] | {{status|ready}}[[:krc:Википедия:Форум|Local Village pump]]. | {{status|published}}<nowiki>{{SITENAME}}</nowiki> джангы кёрюнюм алады. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Интерфейсни къарачай-малкъар тилге кёчюрюб бошаргъа эмда программаны халатларын ачыкъларгъа болушугъуз.] | {{status|published}}<nowiki>{{SITENAME}}</nowiki> джангы кёрюнюм алады. [http://krc.wikipedia.org/wiki/Википедия:Форум/Джангы_амалла Дагъыда окъугъуз...] | {{status|ready}}[http://krc.wikipedia.org/wiki/Википедия:Форум/Джангы_амалла] | {{status|published}}Джангы джукъ эследигизми? <nowiki>{{SITENAME}}</nowiki>ны бир кесек игилендириб турабыз. [http://krc.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Дагъыда окъугъуз...] | {{status|ready}}[http://krc.wikipedia.org/wiki/Википедия:Форум] | {{status|ready}}[[:krc:Къошулуучу:Iltever|Iltever]] | {{status|ready}}[http://krc.wikipedia.org/wiki/Википедия:Форум] | {{status|ready}} <span id="tt" /> |- valign="top" | [[w:tt:|tt]] | {{status|ready}}[[:tt:Википедия:Форум|Local Village pump]]. | {{status|published}}<nowiki>{{SITENAME}}</nowiki> яңа бизәлеш алды. [http://meta.wikimedia.org/wiki/2010_Wikimedia_design_and_feature_change Зинһар безгә хаталарны һәм кулланучы бизәлешендә киткән ялгыш тәрҗемәләрне табарга ярдәм итегез.] | {{status|published}}<nowiki>{{SITENAME}}</nowiki> яңа бизәлеш алды. [http://tt.wikipedia.org/wiki/Википедия:Яңа_бизәлеш Тулырак мәгълүмат...] | {{status|ready}}[http://tt.wikipedia.org/wiki/Википедия_бәхәсе:Җәмгыять_үзәге] | {{status|published}}Ниндидер яңалык күрдегезме? Без бераз гына <nowiki>{{SITENAME}}</nowiki> проектын бизәдек. [http://tt.wikipedia.org/wiki/Special:UsabilityInitiativePrefSwitch Тулырак мәгълүмат...] | {{status|ready}}[http://tt.wikipedia.org/wiki/Википедия_бәхәсе:Җәмгыять_үзәге] | {{status|ready}}[[:tt:Кулланучы:MalTsilna|Ильнар Шайдуллов]] | {{status|ready}}[http://tt.wikipedia.org/wiki/Википедия_бәхәсе:Җәмгыять_үзәге] | {{status|ready}} |} == Phase V Deployment == * All remaining [[Special:Sitematrix|Wikimedia projects]]: '''Sep 1 at 10am PDT / 5pm UTC''' :* Deadline for bug reports: '''Aug 25''' Projects will be switched regardless of localization status, so this is a critical moment to provide missing localizations. We will not switch projects with critical functionality breakage, so please report such breakage as soon as possible. In order to help with communication, if you're an English speaker, please join the [https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors wikitech-ambassadors] mailing list and introduce yourself. We'll use this list as an interface between the Wikimedia Foundation and the Wikimedia languages/projects. : Before you start switching all remaning projects, please consider fix issue connected with missing translation: https://bugzilla.wikimedia.org/show_bug.cgi?id=24906#c5. Thank you, [[User:Leinad|Leinad]] 00:18, 24 August 2010 (UTC) == Notes == <references /> [[Category:Releases]] 7v864bggdkwbkme1ubvm9y4mcctktn0 10 1200 8646 7332 2010-07-29T13:29:40Z Nemo bis 9 cat wikitext text/x-wiki <includeonly>{{#switch:{{{1|}}} |missing |progress |#default = <span style="border-left:1em solid #E00; padding-left:1px;">&nbsp;</span> |proofreading = <span style="border-left:1em solid #FFBF00; padding-left:1px;" class="plainlinks">&nbsp;</span> |published |done = <span style="border-left:1em solid #AEA; padding-left:1px; color:gray;" class="plainlinks">&nbsp;</span> |ready = <span style="border-left:1em solid #FF0; padding-left:1px; color:gray;" class="plainlinks">&nbsp;</span> }}</includeonly><noinclude> ;Statuses * {{status|missing}} missing/progress * {{status|proofreading}} proofreading * {{status|ready}} ready * {{status|done}} done [[Category:Templates]]</noinclude> pm6ijtyzhnodfi74i492uv4vmqzp8ku 6 1203 7249 2010-05-28T18:33:56Z Guillom 13 == Summary == Upload wizard - Proposed changes for deed and license selection. May 28, 2010 {{PD-ineligible}} wikitext text/x-wiki == Summary == Upload wizard - Proposed changes for deed and license selection. May 28, 2010 {{PD-ineligible}} ao8ipgi6nyuxoqbopj8jqw0mkbx55le 6 1204 7250 2010-05-28T19:24:30Z Guillom 13 == Summary == GPL wikitext text/x-wiki == Summary == GPL nu8o5kbndrf581s7m3b8kzec8d3fgg4 100 1213 7314 2010-06-02T00:25:01Z Guillom 13 moved [[Multimedia:Licensing tutorial/CfP]] to [[Multimedia:Licensing tutorial]]: moving it back wikitext text/x-wiki #REDIRECT [[Multimedia:Licensing tutorial]] d5lfewddd6grc2runyhgr8ukng3plqa 10 1218 8641 8167 2010-07-29T13:28:08Z Nemo bis 9 cat wikitext text/x-wiki [[w:bg:Уикипедия:Вектор/Въпроси и отговори|Български]] | [[w:ca:Viquipèdia:Aparença Vector|Català]] | [[w:cs:Wikipedie:Iniciativa použitelnosti/FAQ|Česky]] | [[w:de:Wikipedia:Usability-Initiative/FAQ|Deutsch]] | [[What's new, questions and answers|English]] | [[w:es:Wikipedia:Feedback de experiencia de usuario/Nuevas funciones, preguntas y respuestas|Español]] | [[w:fr:Wikipédia:Retours d'expérience sur l'utilisabilité/FAQ|Français]] | [[w:he:ויקיפדיה:פיתוח התשתית/וקטור/שאלות ותשובות|עברית]] | [[w:it:Progetto:Coordinamento/Usabilità/FAQ|Italiano]] | [[w:ja:Wikipedia:使用性改善/よくある質問と回答|日本語]] | [[w:ka:ვიკიპედია:ბეტა/ახალი შესაძლებლობები/FAQ|{{#language:ka}}]] | [[w:meta:위키백과:성능개선/빈문답|한국어]] | [[w:hu:Wikipédia:Átállás Vectorra/GyIK|Magyar]] | [[Што е ново, прашања и одговори|Македонски]] | [[w:ml:വിക്കിപീഡിയ:ഉപയോക്തൃ അനുഭവ അഭിപ്രായങ്ങൾ/പതിവു ചോദ്യങ്ങൾ|മലയാളം]] | [[w:nl:Wikipedia:Feedback voor het User Experience Team/FAQ|Nederlands]] | [[w:pl:Pomoc:Nowa skórka – wektor|Polski]] | [[w:pt:Wikipedia:Feedback de experiência de usuário/FAQ|Português]] | [[w:ru:Википедия:Отклики о пользовании/ЧаВо|Русский]] | [[w:zh:Wikipedia:用戶體驗反饋/FAQ|中文]]<noinclude> [[Category:Language templates]]</noinclude> 5likquukhsnpbvrtqlz0r7iw3zfjz4k 0 1222 8857 8854 2010-09-02T13:59:31Z Andrew Dalby 2254 wikitext text/x-wiki On May 13, the Usability Initiative changed the left navigation on the English Wikipedia as part of the [http://blog.wikimedia.org/2010/a-new-look-for-wikipedia/ new interface rollout]. The goal was to reduce clutter in the left navigation. Frequently accessed links were kept exposed while infrequently used links would be collapsed by default, and then exposable upon click. Once a user exposes a set of links, they will remain exposed until the links are collapsed. Since launching this change, there has been feedback from the Wikipedia community regarding the hiding of the Language links. Most of the feedback centers around the following two issues: # Multi-lingualism/culturalism is an important aspect of Wikipedia. When users come view article, the exposed language links let the user know that the article is available in other languages. Hiding the links gives this important aspect of Wikipedia much less visibility. # For users that go back and forth between different language versions of the same article, collapsing the languages presents a usability issue as we require users an additional click to access the different languages. Regarding issue #2, there was a bug by which the cookie expiration date which determines the expand/collapse state of the Language links was set too short. The result is that the Language section may collapse even after a user has expanded it. This issue has been resolved, so users should no longer see this issue. Because of browser-specific bugs, this feature was broken in older versions of Opera (before 9.8) and Konqueror (before 4.0) and has been disabled in those browsers. Regarding issue #1, the Usability Team is working on the following compromise [updated 00:22, 5 June 2010 (UTC)]: * By default, show a list of languages based on the user's most likely languages. These language(s) will probably be based on the browser's language setting. We will also have a link to "see other languages." With this type of control, we show the most likely languages while avoiding the clutter of languages that would probably not interest the user. * Change the wording of the "Language" link to be more descriptive (e.g., "See article in other languages" or "View in other languages"). The word "Languages" is probably not adequately descriptive. Please let us know what you think of this proposal. [[User:Howief|Howief]] 00:23, 5 June 2010 (UTC) :The response must have been unanimous, because [[User:Romaine]] wrote (on a different page of this wiki) on 16 June: "As of the beginning of last week, the default for inter-language links in the sidebar is to show them". No one bothered to say so here, so I've copied the information in now. [[User:Andrew Dalby|Andrew Dalby]] 13:59, 2 September 2010 (UTC) == Update == Here are mockups of the interwiki links in [http://upload.wikimedia.org/wikipedia/usability/7/71/Interlanguage_collapsed.png collapsed] and [http://upload.wikimedia.org/wikipedia/usability/4/48/Interlanguage_expanded.png expanded] state (assuming auto-detection of other languages). :Are these two options mutually exclusive? While the renaming sounds good, I am quite skeptical about the first option (choosing the « most likely languages » on behalf of the user). Exactly how would you guess which languages the user is interested in? [[User:Guillom|guillom]] 16:51, 4 June 2010 (UTC) ::No, the options are not mutually exclusive. We're looking at both. Re: the default languages, we may consider short term and long term solutions. Short term, we could base the default languages based on browser language and/or geo-coordinates where available. There are also a number of interesting ideas that have been suggested (e.g., enabling users to select a preference, taking into account the nature of the article) which are slightly more involved, but definitely worth looking into more closely. [[User:Howief|Howief]] 18:55, 4 June 2010 (UTC) :::Until a long-term solution is agreed upon, the appropriate short-term solution is to display the interwiki links by default. It's unfortunate that this fix was reverted, let alone in the name of "usability." —[[:en:User:David Levy|David Levy]] 19:27, 4 June 2010 (UTC) :I regard "Languages" as sufficiently descriptive. The suggested wordings are problematic for the following reasons: :1. They incorrectly imply that all of the articles on a particular topic are direct translations of the same material. The English Wikipedia has intentionally avoided similar wording specifically to counter this misconception. :2. They overcomplicate the label for someone with little understanding of English (likely arriving at the article via a web search), for whom "languages" is the only relevant word. :3. The [[:simple:|simple English Wikipedia]] is not written in another language, so it's inaccurate to refer to it in this manner. —[[:en:User:David Levy|David Levy]] 17:28, 4 June 2010 (UTC) ::While I don't think "Languages" is sufficiently descriptive, I do share your concern that other phrases listed above may be misleading. This may be a case where we have to choose the least-bad option. I do think whatever word we use should aid understanding of the links and right now I'm not sure if it does. [[User:Howief|Howief]] 18:55, 4 June 2010 (UTC) :::I don't believe that ''any'' description can compensate for the clarity lost by hiding the interwiki links; the readers for whom they're most useful are among the least likely to comprehend English in general. :::Mark Williamson wrote an excellent analogy on the Wikimedia Foundation mailing list. In the hypothetical scenario, a reader of English reaches an article at the Georgian Wikipedia. And instead of seeing a link labeled "English," he/she must comprehend that it's hidden under the label "ენები" (Georgian for "languages"). For someone who cannot read Georgian, expanding this to the Georgian translation of "View this topic in another language" or similar would not be the least bit helpful. —[[:en:User:David Levy|David Levy]] 19:27, 4 June 2010 (UTC) I don't think the way forward as suggested at the head of this page is actually a sensible option for several reasons - #I have never understood the attitude that regards the toolbox, languages, list, etc as "clutter". They do not take up any screenspace that is used for anything more useful - indeed now the search box has been marginalised to the top right, there is even less pressure on this area of the screen. Having them expanded by default but collapsible allows those who disagree with me the ability to see all the (imho wasted) blank space the vector designers seem to adore. #I don't understand why the very complicated first option is even being considered - show all languages that are available by default (which seems to be what everyone not involved in the decision to hide them in the first place wants), or show none of the languages that are available by default. Speaking personally, the languages links that I find most useful vary based on many factors, including the topic of the article concerned. For example the Dutch article on a municipality in the Netherlands is more likely to be useful to me than the Russian article, but the exact opposite is true for e.g. Russian politicians. Other important factors are not at all predictable without reading my mind. #I echo everything David Levy says above about the label "Languages". The only thing that could accurately replace it is "(This topic in) other Wikipedia editions", which is far too long and far too complicated. #It isn't just Opera for which the collapsed menus are not available - comments suggest Konqueror, PlayStation 3 and possibly others. [[Special:Contributions/88.107.46.47|88.107.46.47]] 17:48, 4 June 2010 (UTC) :Interesting that this discussion is in English, neatly hidden away from many of the people for whom it matters most: monolingual non English speakers... == Rationale == Slightly rewording stuff on the top of this page: Clutter on a page makes it more difficult to find useful things on the page, especially useful things you might not know about. If a person sees a giant mess of words or symbols, they'll tend to ignore or skim over most of it. We want people to know what the links are on the sidebar and actually '''read''' them, so we need to keep it relatively small. At the same time, the fact that there are multiple language versions of articles is awesome, and it'd be a great thing to make people aware of, but if we make people aware of it by just expanding it out, you get clutter again. As it stands, it's not completely clear '''to an average user''' that expanding the "Language" bar will get them different language versions of the page. One way to give users a "hint" to this functionality is to try and "guess" a language they'd find interesting and expand out on that language and give them a 'more languages' option. Another option is to make the label more clear, and in some concise way say "if you click on this, you'll find multiple language versions of this page" as opposed to "if you click on this, we'll switch your UI to another language" or something. [[User:Nimish Gautam|Nimish Gautam]] 18:56, 4 June 2010 (UTC) :Again, the links do '''not''' lead to "different language versions of the page." This is a common misconception that we've tried very hard to avoid reinforcing. —[[:en:User:David Levy|David Levy]] 19:27, 4 June 2010 (UTC) First, there are not so much interwikis to make it intrusive in most pages (Main Page seems to be an exception, but there full interwikis are usually moved to a different page). Second, the interwiki links have a big disadvantage over other interface items which are easily customizable, since interwikis are used when fall on a foreign wiki, and use them to "go home", so you don't have any cookie set. You also need them expanded in case you are fixing interwikis or translating an article from several languages. Then you will need to expand it on every wiki. Not a big deal, but needing more clicks hurts usability. I also wonder about the change of perception of an article experienced users have depending on how many interwikis [normal, good, featured...] they see. Some ideas I find worth from the [http://thread.gmane.org/gmane.org.wikimedia.foundation/45758 foundation-l thread], which you should really follow: It shows the multilingual nature of wiki*edia, it raises awareness of other wikipedias, just by being shown. You can't correctly guess the right languages, which will lead to frustration, and a worse perception since it depends on too many factors, which will not be easily understood. They are useful as a translation (even if not clicked). The data may skewed due to (a) personal usability tests done with English, (b) the way the clicks were measured in the live site (clicks vs sessions, differences between languages...). As a conclusion, we would like having more data about all of this. [[User:Platonides|Platonides]] 22:03, 4 June 2010 (UTC) :Without knowing exactly what data you are wanting, here is the ordered list (most to least frequent) of how often I click the various links in the sidebar on Wikipedia (other wikis differ, e.g. I almost never upload files to Wikipedia, but that is the most frequently used link on Commons): :#Permanent link :#Main page :#Recent changes :#What links here :#Interwiki links :#Related changes :#Random article :#Featured content :#Cite this page :The other links I don't use often at all. However I like them there so I know what is available for when I do want to use them. Almost (but not all) design changes in the name of usability with vector have actually made it less user friendly which seems to have been sacrificed to some people's opinion of what looks prettier (I disagree but realise this is subjective). I've also lost count of the number of places where I've left feedback, almost all of which has been completely ignored, and that which hasn't has been rejected with basically "you're wrong", even when large numbers of people have the same opnion as me. [[Special:Contributions/88.107.46.47|88.107.46.47]] 01:55, 5 June 2010 (UTC) :: Interesting comment. I also feel that some of my feedback has been lost in the noise (say, on the Main Page talk here). It would be nice to develop a description of the user model that is being supported by Vector -- no skin will make everyone's life equally easy -- and to consider variants that make the use that you describe easier. (and I note that you've been devoiced again - by the lack of SUL on this wiki? - please come back and resign!) [[User:Sj|Sj]] 00:09, 6 June 2010 (UTC) ==Foundation-l mailing list post== ''[reproduced below]'' The Usability team discussed this issue at length this afternoon. We listened closely to the feedback and have come up with solution which we hope will work for everyone. It's not a perfect solution, but we think it's a reasonable compromise. First, some background on the problem we're addressing and the design principle that we used. Every situation is unique, but in the case of the interwikilinks, we believe the sheer number of language links, especially within the context of an information-heavy page, makes users "numb" to the list. When people see large collections of things, they tend to group them all together as one object and not identify the individual parts that make the whole. As the number of items in the list decreases the likelihood of a person identifying the individual items increases. This is similar to how viewing a traffic jam appears as a long line of generic vehicles, while seeing just a few cars driving down the road might be comprehended in more granular detail (a motorcycle, a truck and a sports car). While we did not explicitly test for this during our usability studies (e.g., it wasn't included as a major design question), we did exercise judgement in identifying this as a problem, based partly on the applying the above design principle to the site, partly on the data. Regarding the data behind the decision. First, let me apologize for the tardiness. The engineer who implemented the clicktracking of the left nav recently returned from vacation, so you can probably imagine how things might be a little difficult to find after being away for a while. Please see [[Left Nav Click Data]] for more details, but a quick summary is that we measured the click behavior for two groups of English Wikipedia users, Monobook and Vector (Vector users are primarily those who participated in the beta). Of Monobook and Vector users, 0.95% and 0.28% clicked on the language links (out of 126,180 and 180,873 total clicks), respectively. We felt that fewer than 1% of Monobook clicks was a reasonable threshold for hiding the Language links, especially when taken in the context of the above design principle and the implementation (state persists after expanding). We do, however, recognize the concern that was voiced by a number of our community members. When the language links are in a collapsed state however, there is not enough information to explain what the list will be if you were to expand it. In all likelihood, we won't be able to get the verbiage to the point where it's sufficiently descriptive of the inter-language links. A list of languages is probably more effective as it *shows* the user that there are other languages available (rather than *telling* the user via a "Language", "In other languages" etc. link). However, exposing all of the languages can potentially be just as ineffectual as showing none of them. A more effective approach would be to balance the two, by showing just enough links to clearly illustrate the meaning of the list. So our proposal is to show a list of, say, 5 languages with a "more" link. We think that a list of 5 languages should be sufficient to communicate to the user that there are other language versions available. If the language they want is not on the list, they may click "more" to see the full list. There are numerous ways we can populate the list of 5. The simplest way is to populate based on the current order, but we can also do it based on size of the wiki, browser language, geo IP, etc. Our proposal is to go with something simple for now, and then continue to explore options for greater customization. We hope this compromise addresses the most pressing concerns that have been raised. I will update the page on the usability wiki with the above information. Please direct discussion/feedback to that page. Thank you for your input. Howie, on behalf of the User Experience Team at WMF :<font color="green">''First, some background on the problem we're addressing and the design principle that we used. Every situation is unique, but in the case of the interwikilinks, we believe the sheer number of language links, especially within the context of an information-heavy page, makes users "numb" to the list.''</span> ::I regard this as an unreasonable assumption. ::In my experience/observation, readers saw the links and recognized them as a list of articles in various languages. Most didn't wish to view such articles, so they paid no further attention to the list until such time as they did. (No harm done.) Meanwhile, users wishing to view articles in other languages (a small percentage, but a large number in absolute terms) knew exactly where to look. ::To equate this unusual type of list with large blocks of text in general (without any data to demonstrate the principle's applicability) is to completely ignore context. :::* I agree with this. NB: Erik posted a nice short suggestion to the mailing list recently. --[[User:Sj|Sj]] :::* +1 --[[User:Amire80|Amir E. Aharoni]] 08:04, 6 June 2010 (UTC) :<font color="green">''When people see large collections of things, they tend to group them all together as one object and not identify the individual parts that make the whole. As the number of items in the list decreases the likelihood of a person identifying the individual items increases. This is similar to how viewing a traffic jam appears as a long line of generic vehicles, while seeing just a few cars driving down the road might be comprehended in more granular detail (a motorcycle, a truck and a sports car).''</span> ::This analogy fails to consider a very important distinction. ::Unlike the motor vehicles, one (or a small number) of the links on the list are meaningfully different from the user's perspective. To a reader of Japanese, the [[:ja:|日本語]] link stands out in much the same way that an ice cream van would stand out in the aforementioned traffic jam. The other links, being foreign to this particular user, do not compete for attention (and therefore are less of a distraction than the random cars surrounding the ice cream van are). :::* +1 --[[User:Amire80|Amir E. Aharoni]] 08:04, 6 June 2010 (UTC) :<font color="green">''While we did not explicitly test for this during our usability studies (e.g., it wasn't included as a major design question), we did exercise judgement in identifying this as a problem, based partly on the applying the above design principle to the site, partly on the data.''</span> :: Said data indicated only that the interwiki links were used relatively infrequently. Apparently, there is absolutely no data suggesting that the full list's display posed a problem. Rather, this is a hunch based upon the application of a general design principle whose relevance has not been established. ::: Right. And even a frequent browser of multiple projects who relies heavily on interlanguage links is likely to use other links on a page much more often. I am pleasantly surprised that 1% of all clicks were to interlanguage links -- that suggests that they are more useful to the general read than I had expected. [[User:Sj|Sj]] :<font color="green">''A more effective approach would be to balance the two, by showing just enough links to clearly illustrate the meaning of the list. So our proposal is to show a list of, say, 5 languages with a "more" link. We think that a list of 5 languages should be sufficient to communicate to the user that there are other language versions available. If the language they want is not on the list, they may click "more" to see the full list.''</span> ::If the language that the user seeks is not visible, why do you assume that he/she will recognize the list's nature? ::Imagine seeing the following on a page full of similarly unintelligible text: :::[[Main Page|Ectbadi]] :::[[Main Page|Feskanalic]] :::[[Main Page|Ibsterglit]] :::[[Main Page|Kreviodeil]] :::[[Main Page|Tionevere]] :::[[Main Page|▷ Straknaj 6 tak]] ::Would you recognize the first five items as languages and the last as "Show 6 more"? ::Compare the above to this: :::[[Main Page|Bacruhy]] :::[[Main Page|Ectbadi]] :::[[Main Page|English]] :::[[Main Page|Feskanalic]] :::[[Main Page|Ibsterglit]] :::[[Main Page|Kreviodeil]] :::[[Main Page|Nuprevnu]] :::[[Main Page|Ootredi]] :::[[Main Page|Rozlovatom]] :::[[Main Page|Tionevere]] :::[[Main Page|Zidentranou]] ::And keep in mind that the above allows for the use of Ctrl-F to find "English" on the page. ::: +1. Using browser's Accept-Language and Geolocation may be good for some sites, but for Wikipedia it is way, way too simplistic. Wikipedia supports many languages which common browsers don't, for example Sakha (code sah). Furthermore, a lot of people don't bother to configure their browser to support their language. In Israel, for example, many people use English Windows, even though they don't necessarily know English well. Finally, for multilingual countries such as Russia, Indonesia, Israel, China, Belgium, Spain and many others, Geolocation is a potentially offensive joke. --[[User:Amire80|Amir E. Aharoni]] 08:04, 6 June 2010 (UTC) ::: If you go with an option like this, please consider using article size or the language of the article topic as factors in addition to the notoriously unreliable and incorrect geolocation. There are many of us who have enough grasp of a large number of languages to be able to interpret at least hard facts from articles in many languages (e.g. most Germanic or Latin ones). Interwiki links to the largest and likely most recently updated article on a topic without several clicks would be far more useful than links to stubs in languages that geolocation might suggest I understand./[[User:Coffeeshivers|Coffeeshivers]] 17:43, 9 June 2010 (UTC) :<font color="green">''There are numerous ways we can populate the list of 5. The simplest way is to populate based on the current order, but we can also do it based on size of the wiki, browser language, geo IP, etc.''</span> ::Browser language and location detection are the best of the above options, but they're far from flawless. It's been explained on the mailing list that there are reasons for speakers of some languages to set their browsers to other languages. Location detection is not entirely reliable and only enables an educated guess as to the language that someone speaks. ::To me, all of this comes across as a manufactured problem in search of a solution (while the initial change was a solution in search of a problem). :::My thoughts exactly. --[[User:Amire80|Amir E. Aharoni]] 08:04, 6 June 2010 (UTC) :<font color="green">''Our proposal is to go with something simple for now, and then continue to explore options for greater customization.''</span> ::Or you could simply restore the one-line code modification that provided the default behavior requested by the community (pending evidence that an alternative setup is beneficial). ::—[[:en:User:David Levy|David Levy]] 05:30, 5 June 2010 (UTC) ::: Yes. Do it, please, now. It is really not my intention to offend anyone, but i really fail to understand why a questionable decision of a small group of developers is more important than the opinion of the community. Please restore the old functionality until the community agrees to change it. --08:04, 6 June 2010 (UTC) ::I also find it extremely troubling that the team has interpreted interwiki link usage data from the English Wikipedia as applicable to all Wikimedia wikis (given the intention to deploy this setup across the board). I would be shocked to learn that the interwiki links don't receive substantially more use within other Wikipedias (particularly the smaller ones, whose articles often contain less information). —[[:en:User:David Levy|David Levy]] 19:10, 5 June 2010 (UTC) ::: I find it troubling that the developers felt this was a problem that needed to be fixed from the top down. As pointed out above, the vast majority of pages have only a handful of -- if any -- interwiki links. The pages with a distracting number of such links could be handled with a template which would put all of them in a box that would hide them, which could be added by users. That would be the optimal solution: the pages which users felt had too many interwiki links could be fixed ''by the users'', & the rest would be left alone. (And if this template is applied to too many pages, then the current change would be justified.) This is a bottom-up approach, which has served all of the Wikimedia projects quite well in the past. -- [[Special:Contributions/216.20.149.168|216.20.149.168]] 17:14, 9 June 2010 (UTC) (llywrch on en.wikipedia) == Thoughts on the usage data == : "''Of Monobook and Vector users, 0.95% and 0.28% clicked on the language links (out of 126,180 and 180,873 total clicks), respectively." <s>A 66% reduction in the use of one of the more unique and irreplacable elements of Wikipedia sounds like a powerful reason to return to the previous interface.</s> As David notes above, use on smaller wikis will naturally be more significant. It would be nice to see more multilingual and targeted research before making a change to the default behavior (of that earlier interface). [[User:Sj|Sj]] 00:01, 6 June 2010 (UTC) :To clarify, no current statistics have been released. The "0.28%" figure refers to use of Vector before the official roll-out (when the interwiki links became collapsed by default, if I'm not mistaken). The disparity is attributable to the fact that most Vector users were participants in an opt-in, English-language beta test. —[[:en:User:David Levy|David Levy]] 01:21, 6 June 2010 (UTC) :: Thanks for the clarification. So there is no before/after data, then? It would be interesting to gather some on a small sample, whatever happens to the default for most readers. [[User:Sj|Sj]] 08:18, 6 June 2010 (UTC) Does click tracking data works here at all? # They give undue weight to the people who speak only English (which are significant part of overall Wikipedia traffic). If Wikipedia is smaller (and hence is more outweighted by enwiki audience), more people use language links to get the information they want. # Many people don't actually click those links, they just look at where do they point. Finally, does it really help? Is there any actual proof that they distract users? I believe there should be a better way of improving our sidebar than hiding things. [[User:VasilievVV|VasilievVV]] 20:25, 6 June 2010 (UTC) :: If I understand right, part of the reason to collapse the interlanguage links was they weren't used often in monobook. Well, I remember distinctly the time when monobook came out (2004). Before monobook, we had the interlanguage links horizontally at the very top of the page. Then monobook moved them down left, hidden unless you had a big screen or scrolled down. One of the very first things I did was devise some JS/CSS hacks for me to put the interlanguage links back to the top ([[:meta:File:Wp-lupo-vp-screenshot.png]]). That's where they still are for me: the multi-linguality of the WMF projects is for me a key feature, and I never understood why the interlanguage links were moved down-left in monobook. :: Now, I don't want to suggest the interlanguage links be moved back to the top again. That placement is just my personal, perhaps highly unusual, preference. However, when it comes to click counting, I very much would like to suggest that the low counts in monobook are a result of the decision made in the monobook rollout to move them to a place where they are less prominent. Hiding them even more in vector would just be a continuation of that (in my personal view, wrong) decision made back in 2004 with monobook to de-emphasize the multi-lingual nature of WMF projects. :: [[User:Lupo|Lupo]] 09:54, 7 June 2010 (UTC) Out of all left-hand navigation links (excluding search), the interwiki-links are the ones I use most often. Generally at least looking what's available in other languages for each article. My usage of other left-navigation approaches zero. --[[Special:Contributions/88.130.177.138|88.130.177.138]] 21:09, 8 June 2010 (UTC) :::I don't see any comparison with how many people click on ''other'' links at the top, left and bottom of the page. If the change was made based on a statistical ceiling, as is claimed above -- to summarize, "over 1% we would have been interested, below 1% we weren't" -- then other links must have been evaluated in the same way. Where are the statistics? [[User:Andrew Dalby|Andrew Dalby]] 11:52, 6 July 2010 (UTC) ::::Since there was never any reply to this, and the version of the Vector skin that I now see on en:wiki and la:wiki ''does'' display the language links, should I take it that the idea of hiding these links has been dropped? [[User:Andrew Dalby|Andrew Dalby]] 13:33, 2 September 2010 (UTC) ::::Answering myself: yes, it seems it was dropped. See my note near the top of the page. [[User:Andrew Dalby|Andrew Dalby]] 13:59, 2 September 2010 (UTC) [[Category:Feedback]] hogesb0amehsih6i4xuk0pjtmybsc97 0 1223 7387 2010-06-04T11:21:46Z Nemo bis 9 looks like this is the description wikitext text/x-wiki #REDIRECT[[Releases/Babaco]] 3gsob8fi0min8w8ecedxj1n9id3oxd1 0 1224 7388 2010-06-04T11:22:34Z Nemo bis 9 Redirected page to [[Releases/Babaco]] wikitext text/x-wiki #REDIRECT[[Releases/Babaco]] 3gsob8fi0min8w8ecedxj1n9id3oxd1 0 1225 7389 2010-06-04T11:22:49Z Nemo bis 9 Redirected page to [[Releases/Babaco]] wikitext text/x-wiki #REDIRECT[[Releases/Babaco]] 3gsob8fi0min8w8ecedxj1n9id3oxd1 0 1226 7390 2010-06-04T11:23:04Z Nemo bis 9 Redirected page to [[Releases/Babaco]] wikitext text/x-wiki #REDIRECT[[Releases/Babaco]] 3gsob8fi0min8w8ecedxj1n9id3oxd1 0 1228 7398 2010-06-04T16:52:05Z Trevor Parscal (WMF) 3 moved [[Opinion: Language Links]] to [[Opinion Language Links]] wikitext text/x-wiki #REDIRECT [[Opinion Language Links]] 30zwk8a0l5ff5q0rxmk2wmf2f30ltc6 6 1232 7417 2010-06-04T20:27:33Z Howief (WMF) 1286 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1233 7418 2010-06-04T20:28:18Z Howief (WMF) 1286 Interlanguage links collapsed wikitext text/x-wiki Interlanguage links collapsed 4562j0fs0cf4h3yzdysexmtc426m7iz 0 1234 9209 8598 2010-10-28T07:38:46Z 89.189.74.235 wikitext text/x-wiki [http://aro3.sbilya.com/GnooN%20hacker.htm Hacked By Bassam mad hacker life when I was asked his friend to me you are Fjaoptni when you break a companion But our religion and we do not play Rcolona Booze Beware that we are coming, we had not been engaged Valmrsad each act were done Evkroni some people treat them like human beings .. Know what Anne Humane duty] 9mcy7w3xvp8wxttmgyffgs6yb3yb2w5 6 1237 7473 2010-06-06T14:38:08Z Teofilo~usabilitywiki 173 Wikipedia screenshot. See [[:Commons:Talk:Wikipedia/2.0]] wikitext text/x-wiki Wikipedia screenshot. See [[:Commons:Talk:Wikipedia/2.0]] 16lb7dri4tdmk6rnyggui6qxti0119g 6 1238 7474 2010-06-06T14:39:17Z Teofilo~usabilitywiki 173 Wikipedia screenshot. See [[:Commons:Talk:Wikipedia/2.0]] wikitext text/x-wiki Wikipedia screenshot. See [[:Commons:Talk:Wikipedia/2.0]] 16lb7dri4tdmk6rnyggui6qxti0119g 0 1242 7525 7524 2010-06-07T21:33:42Z Amire80 1559 /* See also */ more links wikitext text/x-wiki This is a page to capture proposals for new approaches to the inter-wiki links. ==See also== * [[:strategy:Proposal:A central wiki for interlanguage links]] * [[:meta:A newer look at the interlanguage link]] * [[:en:Wikipedia:WikiProject Interlanguage Links/Ideas from the Hebrew Wikipedia]] * [http://www.gossamer-threads.com/lists/wiki/foundation/198093?do=post_view_threaded The thread on Foundation-l mailing list that prompted the creating of this page] * [[Opinion Language Links]] 9vyngbava764tuupor5r7u2umgjd1sd 0 1243 7670 7619 2010-06-11T15:39:56Z Nemo bis 9 soft-redirect wikitext text/x-wiki #REDIRECT[[m:Product Development Process Ideas]] mzrp2efvzwpradm1yjyrjjy499dkh5b 6 1249 7612 7597 2010-06-10T00:42:01Z Howief (WMF) 1286 uploaded a new version of &quot;[[File:Usability retention apr 2010.jpg]]&quot;: == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 0 1250 7728 7727 2010-06-13T07:52:58Z Shijualex 2060 wikitext text/x-wiki {{FAQLang}} <table style="border-top:solid 1px #AAA;border-bottom:solid 1px #AAA;border-left:solid 1px #AAA;border-right:solid 1px #AAA;background:#FFFFCC;" cellpadding="5" cellspacing="0" align="center"> <tr> <td>[[Image:Gtk-dialog-info.svg|48px]]</td> <td colspan=3 style="background:#FFFFCC; color:black" > '''Kindly DONOT Delete. Translation is in progress''' </td> </tr> </table> ==എന്തൊക്കെ മാറി?== ഉപയോക്തൃ സമ്പർക്കമുഖത്തിന് നിരവധി മാറ്റങ്ങൾ ഞങ്ങൾ വരുത്തിയിട്ടുണ്ട്. പ്രധാനമായി, "വെക്റ്റർ" എന്ന പേരിൽ പുതിയൊരു ദൃശ്യരൂപം അവതരിപ്പിച്ചിരിക്കുന്നു. ഈ പുതിയ ദൃശ്യരൂപത്തിൽ സാധാരണ പ്രവർത്തനങ്ങൾ ലളിതമായിരിക്കും. കൂടെ താൾ തിരുത്തുന്നതിനുള്ള സൗകര്യത്തിനായി മെച്ചപ്പെടുത്തിയ തിരുത്തൽ ടൂൾബാർ, കണ്ണികളും പട്ടികകളും ഉൾപ്പെടുത്താൻ സഹായിക്കുന്ന ഡയലോഗുകൾ, സർവ്വസാധാരണമായി ഉപയോഗിക്കുന്ന പ്രവർത്തനങ്ങൾ എളുപ്പത്തിൽ ചെയ്യാൻ സഹായിക്കുന്ന "ചീറ്റ്ഷീറ്റ്" തുടങ്ങിയവ ഉൾപ്പെടെ നിരവധി മെച്ചപ്പെടുത്തലുകൾ വരുത്തിയിരിക്കുന്നു. സൈറ്റിൽ ആകമാനം കയറിയിറങ്ങാൻ സഹായകമാകും വിധം രൂപഘടനയിലും വരുത്തിയ മാറ്റവും, കൂടുതൽ അർത്ഥവത്തായ സ്ഥലത്തേയ്ക്ക് തിരയാനുള്ള പെട്ടി മാറ്റിയതുമാണ് ഒടുവിൽ പറയാനുള്ളത്. ഈ മാറ്റങ്ങൾ സഹായകരമാണെന്ന് ഉപയോക്താക്കൾ കണ്ടെത്തുമെന്നാണ് ഞങ്ങളുടെ പ്രതീക്ഷ. മുൻപുണ്ടായിരുന്ന ദൃശ്യരൂപം തുടർന്നും ഉപയോഗിക്കാനാഗ്രഹിക്കുന്നവർക്ക് താളിന്റെ മുകളിലായി "എനിക്കിതു വേണ്ട" എന്ന കണ്ണി ഉപയൊഗിച്ച് പഴയ രൂപത്തിലേക്കു് തിരിച്ചു് പോകാവുന്നതാണു്. ==എന്തുകൊണ്ട് ഈ മാറ്റങ്ങൾ?== വിക്കിമീഡിയ ഫൗണ്ടേഷൻ പരിപാലിക്കുന്ന വിക്കിപീഡിയയും മറ്റ് സംരംഭങ്ങളും സന്നദ്ധ പ്രവർത്തകരാണ് എഴുതുകയും തിരുത്തുകയും ചെയ്യുന്നത്. അവരിൽ പലരും വിക്കിപീഡിയ തിരുത്തുന്നത് ആശയകുഴപ്പമുള്ള കാര്യമാണെന്നും ബുദ്ധിമുട്ടാണെന്നും ഒക്കെ പറയാറുണ്ട്. ഞങ്ങൾക്കു നൽകാൻ കഴിയുന്ന വാഗ്ദാനമായ ലേഖനങ്ങളുടെ ഗുണമേന്മയും വ്യാപ്തിയും ആഴവും ഈ ഗുരുതരമായ പ്രശ്നം മൂലം കുറഞ്ഞു പോയേക്കാം. മറ്റൊരു വിധത്തിൽ പറഞ്ഞാൽ ഇപ്പോൾ താങ്കൾക്കു സംഭാവന ചെയ്യാൻ കഴിയുന്നുണ്ടെങ്കിൽ പോലും മറ്റുള്ളവരേയും ലളിതമായി നമ്മുടെ പദ്ധതികളിൽ പങ്കെടുപ്പിക്കാനുള്ള ശ്രമമാണിത്, ഇതുവഴി താങ്കൾക്കും കൂടുതൽ വിവരസ്രോതസ്സുകൾ ലഭിക്കുന്നതാണ്. വിക്കിപീഡിയ പ്രവർത്തിക്കുന്ന സോഫ്റ്റ്‌‌വേർ ആദ്യം വികസിപ്പിച്ച കാലഘട്ടത്തിൽ, അത് ഉപയോക്തൃസൗഹൃദ സ്വഭാവമുള്ളതായി കണക്കാക്കിയിരുന്നു. എന്നാൽ ഇന്നത്തെ മാനദണ്ഡങ്ങളനുസരിച്ച്, മറ്റ് സോഫ്റ്റ്‌‌വേറുകളുമായി താരതമ്യപ്പെടുത്തുമ്പോൾ അതത്ര ലളിതമല്ല. ഇതുകൊണ്ടാണ്, മെച്ചപ്പെട്ട വിക്കിപീഡിയയ്ക്കു വേണ്ടി ഞങ്ങൾ ഗൗരവമേറിയ മാറ്റങ്ങൾ സൃഷ്ടിച്ചുകൊണ്ടിരിക്കുന്നത്. == ഈ മാറ്റങ്ങൾ നടപ്പിൽ വരുത്തണമെന്ന് എങ്ങനെയാണ് തീരുമാനിച്ചത്? == വിക്കിപീഡിയയുടേയും സഹോദര സംരംഭങ്ങളുടേയും ഉപയോഗക്ഷമതയും ഉപയോക്തൃ അനുഭവവും അന്വേഷിക്കാനും മെച്ചപ്പെടുത്താനും 2009 ജനുവരിയിൽ ഞങ്ങൾ ചെറിയൊരു സംഘം രൂപീകരിച്ചു. ഇക്കാര്യത്തിൽ ആദ്യ പഠനം 2009 മാർച്ച് മാസം നടന്നു. പഠനത്തിൽ നിന്നും ലഭ്യമായ [[UX Study|എല്ലാ വിവരങ്ങളും പങ്ക് വെച്ചിട്ടുണ്ട്]]. ഈ പഠനത്തെ ആസ്പദമാക്കി മെച്ചപ്പെടുത്തലുകളുടെ ഒരു പരമ്പര ഞങ്ങൾ ഉണ്ടാക്കുകയും 2009 ഓഗസ്റ്റ് മുതൽ പൊതുജനങ്ങൾക്ക് പരീക്ഷണത്തിനായി പങ്ക് വെയ്ക്കുകയും ചെയ്തു. ഉപയോക്താക്കളുടെ അഭിപ്രായങ്ങൾ കൂടെ കണക്കിലെടുത്ത് ഇതിൽ വീണ്ടും മെച്ചപ്പെടുത്തലുകളും ശരിപ്പെടുത്തലുകളുമുണ്ടായി. രണ്ടാമത്തെ പഠനം 2009 ഒക്ടോബറിലാണുണ്ടായത് ([[Usability, Experience, and Progress Study|രേഖകൾ]]). ഈ പഠനത്തിൽ ഞങ്ങൾ വരുത്തിയ ചിലമാറ്റങ്ങൾ പഠനവിധേയമാക്കപ്പെടുകയും കൂടുതൽ മെച്ചപ്പെടുത്തലുകളിലേയ്ക്ക് ഞങ്ങളെ നയിക്കുകയും ചെയ്തു. അതിന്റെ പരീക്ഷണ കാലഘട്ടത്തിൽ 5,00,000 ഉപയോക്താക്കൾ പരീക്ഷിച്ച, നന്നായി പരിശോധിച്ച മാറ്റങ്ങളുടെ ഒരു ഗണമാണ് 2010 ഏപ്രിൽ മാസം മുതൽ സ്ഥാപിച്ചു വരുന്നത്. ഉപയോഗിച്ചവരിൽ ശരാശരി 80% ആളുകൾ ഈ പരീക്ഷണ മാറ്റങ്ങളിൽ ഉറച്ചു നിന്നു. വിട്ടുപോകുന്നവരിൽ നിന്ന് വിശദമായ അഭിപ്രായങ്ങൾ സ്വീകരിക്കുകയും, അവ കൂടുതൽ മെച്ചപ്പെടുത്തലുകൾക്ക് ഉപയോഗിക്കുകയും ചെയ്തു. പലകാരണങ്ങളും പ്രത്യേക ഭാഷകളുമായി ബന്ധപ്പെട്ടതായിരുന്നു. പരീക്ഷണ കാലത്ത് ലഭിച്ച [[Beta_Feedback_Survey|അഭിപ്രായങ്ങളും പൊതുജനങ്ങൾക്ക് പങ്ക് വെച്ചിട്ടുണ്ട്]]. ==ഉപയോക്തൃ സമ്പർക്കമുഖത്തിന് എന്തുകൊണ്ട് വലിയ മാറ്റങ്ങളില്ല? == ഇതൊരു തുടക്കം മാത്രം. ഞങ്ങൾ സൃഷ്ടിച്ച ഒരുകൂട്ടം മാറ്റങ്ങൾ ഇപ്പോഴും പരീക്ഷണ അല്ലെങ്കിൽ വികസന ഘട്ടത്തിലുണ്ട്. താങ്കൾക്കിവ ഞങ്ങളുടെ [http://prototype.wikimedia.org/ പരീക്ഷണ സൈറ്റിൽ കാണാവുന്നതാണ്]. ഉപയോക്താക്കൾക്ക് ഇവ എങ്ങനെ അനുഭവപ്പെടുന്നു എന്നു പരിശോധിച്ച ശേഷം ഞങ്ങൾ മാറ്റങ്ങളുടെ രണ്ടാംഘട്ടം ഈ വർഷമൊടുവിലായി തരുന്നതാണ്. ഉപയോക്തൃ അനുഭവം മെച്ചപ്പെടുത്തൽ വിക്കിമീഡിയ ഫൗണ്ടേഷൻ ഗൗരവമായി എടുത്തിട്ടുണ്ട്. ഇപ്പോൾ മുതൽ സമ്പർക്ക മുഖത്തിന് സ്ഥിരമായി മാറ്റങ്ങളുണ്ടാകും. പുതിയ ഉപയോക്താക്കൾക്കും, പഴയ ഉപയോക്താക്കൾക്കും കാര്യങ്ങൾ ലഘൂകരിച്ചു നൽകുക എന്നത് സാധാരണ കാര്യമാകും. വിക്കിപീഡിയയിലും സഹോദരസംരംഭങ്ങളിലും റിച്ച്-ടെക്സ്റ്റ് തിരുത്തൽ കൈവരിക്കുകയാണ് ആത്യന്തിക ലക്ഷ്യം. == ഇതു് എല്ലാ ഭാഷകൾക്കും ബാധകമാണോ? == 2010 ഏപ്രിൽ ആദ്യം വിക്കിമീഡിയ കോമൺസിലാണ് ഈ മാറ്റം ആദ്യം വരുത്തിയത്. ഇംഗ്ലീഷ് വിക്കിപീഡിയയിൽ 2010 മെയ് 13 മുതൽ പ്രാവർത്തികമായി. ഇനി മറ്റ് ഭാഷകളിലേയ്ക്ക് വന്നുകൊണ്ടിരിക്കുന്നു. നമ്മുടെ അന്താരാഷ്ട്ര സന്നദ്ധ സേവകസംഘം ട്രാൻസ്‌‌ലേറ്റ്‌‌വിക്കി.നെറ്റ് ഉപയോഗിച്ച് സാദ്ധ്യമായ ഏറ്റവും നല്ല പ്രാദേശിക പതിപ്പിനായി പ്രയത്നിക്കുന്നു. താങ്കൾക്ക് ഭാഗഭാക്കാനാഗ്രഹമുണ്ടെങ്കിൽ [http://translatewiki.net/ translatewiki.net] സൈറ്റിലെ ഘട്ടം ഘട്ടമായുള്ള വഴികാട്ടി കാണുക. == ശ്രദ്ധിക്കുക എന്ന റ്റാബ് എവിടെ പോയി? == "വായിക്കുക", "തിരുത്തുക", "നാൾവഴി കാണുക" തുടങ്ങിയ ബട്ടണുകളുള്ള നിരയിലെ നക്ഷത്രം ഞെക്കുന്നതു വഴി താങ്കൾക്ക് താൾ ശ്രദ്ധിക്കുന്നവയുടെ പട്ടികയിലേക്ക് ചേർക്കാനോ, അതിൽ നിന്ന് നീക്കാനോ സാധിക്കുന്നതാണ്. ==തങ്ങളുടെ യൂസർ സ്ക്രിപ്റ്റുകൾ, യൂസർ സ്റ്റൈലുകൾ, ഗാഡ്ജറ്റുകൾ, മറ്റുപകരണങ്ങൾ ഒക്കെ പ്രവർത്തിക്കുമോ എന്നു് ഉപയോക്താക്കൾക്ക് എങ്ങനെ ഉറപ്പിക്കാനാവും?== പുതിയ ക്രമീകരണങ്ങളിൽ ഇവ ചേർത്ത് ചേർത്ത് പരീക്ഷിക്കുക. ഒത്തുപോകാത്തവ പരിശോധിച്ചറിയാനും പല പ്രശ്നങ്ങളും പരിഹരിക്കാനും താങ്കൾക്ക് കഴിയും. താളിന്റെ ഏറ്റവും മുകളിലുള്ള "ബീറ്റ പരീക്ഷിക്കുക" എന്ന കണ്ണി ഞെക്കി, ബീറ്റ തിരഞ്ഞെടുത്തു് സ്വതവേ ആകുന്നതിനു മുമ്പ് തന്നെ മാറ്റങ്ങൾ താങ്കൾക്ക് പരിശോധിക്കാനാകും. യൂ.ആർ.എല്ലിനു അവസാനം “?useskin=vector” എന്നു കൂട്ടിച്ചേർത്തു നോക്കുകയാണ് മറ്റൊരു മാർഗ്ഗം. ഉദാഹരണത്തിനു്, http://ml.wikipedia.org/wiki/വിക്കിമീഡിയ_ഫൗണ്ടേഷൻ എന്നതാൾ വെക്റ്റർ ദൃശ്യരൂപത്തിൽ എപ്രകാരമായിരിക്കുമെന്നറിയാൻ http://ml.wikipedia.org/wiki/വിക്കിമീഡിയ_ഫൗണ്ടേഷൻ?useskin=vector എന്നു നൽകുക. ==പുതിയ സവിശേഷതകൾ എങ്ങനെ പ്രവർത്തനരഹിതമാക്കാം?== പുതിയ സവിശേഷതകൾ ഉപയോഗിക്കാൻ താങ്കളാഗ്രഹിക്കുന്നില്ലെങ്കിൽ, താഴെ പറയുന്ന പ്രവൃത്തികൾ ചെയ്യുക: #ലോഗിൻ ചെയ്യുക #താളിന്റെ മുകളിലുള്ള "പുതിയ സവിശേഷതകൾ" എന്ന കണ്ണി ഞെക്കുക (താങ്കളുടെ ഉപയോക്തൃനാമത്തിനടുത്തായി ഇത് കാണാം) #"പുതിയ സവിശേഷതകൾ" എന്ന താളിൽ "എനിക്കിത് വേണ്ട" എന്ന കണ്ണി ഞെക്കി പുതിയ സവിശേഷതകൾ ഒഴിവാക്കാം. പുതിയ സവിശേഷതകൾ പ്രവർത്തനസജ്ജമാക്കാനും "പുതിയ സവിശേഷതകൾ" എന്ന താൾ ഉപയോഗിക്കാം. ==എന്തുകൊണ്ട് സ്ക്രിപ്റ്റുകളും (monobook.js) സ്റ്റൈലുകളും (monobook.css) പ്രവർത്തിക്കുന്നില്ല?== [[m:vector|വെക്റ്റർ ദൃശ്യരൂപത്തിലും]] താങ്കളുടെ ഇച്ഛാനുസരണം ക്രമപ്പെടുത്തിയ കോഡ് ഉപയോഗിക്കാനാഗ്രഹിക്കുന്നുവെങ്കിൽ [[Special:Mypage/monobook.js|monobook.js]] താളിലെ സ്ക്രിപ്റ്റുകൾ [[Special:Mypage/vector.js|vector.js]] താളിലേയ്ക്കും, [[Special:Mypage/monobook.css|monobook.css]] താളിൽ നിർവ്വചിച്ചിരിക്കുന്ന സ്റ്റൈലുകൾ [[Special:Mypage/vector.css|vector.css]] താളിലേയ്ക്കും പകർത്തുകയോ/മാറ്റുകയോ ചെയ്യേണ്ടതാണ്. ==വെക്റ്റർ ഇച്ഛാനുസരണമാക്കാനുള്ള വഴികാട്ടി== വെക്റ്റർ ഇച്ഛാനുസരണമാക്കാനുള്ള മാർഗ്ഗങ്ങളുടെ [http://meta.wikimedia.org/wiki/Vector ഒരു ശേഖരം ഇവിടെ] കാണാം. p7itunp7ybxwgp2vhlqvvzq35qo5a4d 6 1253 7686 2010-06-12T00:32:52Z Howief (WMF) 1286 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1254 7687 2010-06-12T00:44:29Z Howief (WMF) 1286 == Summary == wikitext text/x-wiki == Summary == kfgyutht8a6mer1wbxhtidixbj0aafq 6 1264 7768 2010-06-14T22:41:48Z Parul Vora~usabilitywiki 185 == Summary == clip of subject using search wikitext text/x-wiki == Summary == clip of subject using search lvoemmqpp7vzxoy6slcnm6bvd908nwq 8 1265 7773 2010-06-14T23:12:07Z Mdale~usabilitywiki 84 Created page with 'Special Page used as part of the mwEmbed Gadget. Also see [[mw:JS2 Overview#mwEmbed_as_a_Gadget|JS2 Overview]]' wikitext text/x-wiki Special Page used as part of the mwEmbed Gadget. Also see [[mw:JS2 Overview#mwEmbed_as_a_Gadget|JS2 Overview]] l1wbko28fkgj4s4k6bxbsfnrxm8sl9p 6 1266 7808 7786 2010-06-15T21:37:46Z Jorm 2044 wikitext text/x-wiki Screenshot. Here are some more details : Screen size. 800x600 px. Window size is close to the full screen (maybe one or two pixels smaller), although I am not using the full screen (I am not pressing [F11]). Yes the "Salir" link pops up from behind the logo if I reduce the window size (width) (so that I can finally log out) (or I may go to "preferencias" and select "monobook" as my user skin. This is Internet Explorer 6 with javascript turned off. [[User:Teofilo|Teofilo]] 07:54, 15 June 2010 (UTC) : See also what I reported at [[:fr:Wikipédia:Retours_d'expérience sur l'utilisabilité#Remarques diverses en particulier sur l'utilisation a) sur petit écran b) sans javascript]] (screenshot : [[:fr:Fichier:Copie d'ecran nouvelle apparence de Wikipédia.jpg]]). [[User:Teofilo|Teofilo]] 08:02, 15 June 2010 (UTC) Hi! Our team has managed to locate and fix this issue. The fix has been checked into the source repository, but it may be a few days before it gets deployed to the live servers, and you'll se it then. --[[User:Jorm|Jorm]] 21:37, 15 June 2010 (UTC) 8uy9ueulop1cumeh9mbh4z008r5load 6 1269 7814 2010-06-15T23:24:30Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 1270 7818 2010-06-15T23:37:49Z Parul Vora~usabilitywiki 185 wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 1271 8762 8759 2010-08-12T16:36:36Z Avicennasis 1641 Undo revision 8759 by [[Special:Contributions/116.71.184.138|116.71.184.138]] ([[User talk:116.71.184.138|talk]]) - sorry, not the place for this. wikitext text/x-wiki phoiac9h4m842xq45sp7s6u21eteeq1 6 1273 7825 2010-06-16T01:45:44Z Mdale~usabilitywiki 84 test upload wikitext text/x-wiki test upload c6ts649zqs0rchkaexzo1hmarydseat 6 1274 7826 2010-06-16T01:46:36Z Mdale~usabilitywiki 84 test upload wikitext text/x-wiki test upload c6ts649zqs0rchkaexzo1hmarydseat 0 1282 8711 8581 2010-08-06T06:11:22Z 216.130.77.167 wikitext text/x-wiki Here is a list of the Wikipedias we will be going default with during Phase IV. Please add any projects that have been adequately translated to this list. Syntax is project URL followed by database name per [http://noc.wikimedia.org/conf/all.dblist database list]. ; http://af.wikipedia.org : afwiki ; http://als.wikipedia.org : alswiki ; http://ar.wikipedia.org : arwiki ; http://be-x-old.wikipedia.org : be_x_oldwiki ; http://bg.wikipedia.org : bgwiki ; http://bn.wikipedia.org : bnwiki ; http://br.wikipedia.org : brwiki ; http://bs.wikipedia.org : bswiki ; http://ca.wikipedia.org : cawiki ; http://cs.wikipedia.org : cswiki ; http://cy.wikipedia.org : cywiki ; http://da.wikipedia.org : dawiki ; http://diq.wikipedia.org : diqwiki ; http://dsb.wikipedia.org : dsbwiki ; http://el.wikipedia.org : elwiki ; http://eo.wikipedia.org : eowiki ; http://et.wikipedia.org : etwiki ; http://eu.wikipedia.org : euwiki ; http://fa.wikipedia.org : fawiki ; http://fi.wikipedia.org : fiwiki ; http://frp.wikipedia.org : frpwiki ; http://gl.wikipedia.org : glwiki ; http://he.wikipedia.org : hewiki ; http://hsb.wikipedia.org : hsbwiki ; http://hu.wikipedia.org : huwiki ; http://ia.wikipedia.org : iawiki ; http://id.wikipedia.org : idwiki ; http://ka.wikipedia.org : kawiki ; http://ko.wikipedia.org : kowiki ; http://ksh.wikipedia.org : kshwiki ; http://lb.wikipedia.org : lbwiki ; http://mk.wikipedia.org : mkwiki ; http://ml.wikipedia.org : mlwiki ; http://ms.wikipedia.org : mswiki ; http://mt.wikipedia.org : mtwiki ; http://nn.wikipedia.org : nnwiki ; http://no.wikipedia.org : nowiki ; http://oc.wikipedia.org : ocwiki ; http://pms.wikipedia.org : pmswiki ; http://ro.wikipedia.org : rowiki ; http://roa-tara.wikipedia.org : roa_tarawiki ; http://sah.wikipedia.org : sahwiki ; http://sk.wikipedia.org : skwiki ; http://sl.wikipedia.org : slwiki ; http://sq.wikipedia.org : sqwiki ; http://sv.wikipedia.org : svwiki ; http://te.wikipedia.org : tewiki ; http://th.wikipedia.org : thwiki ; http://tl.wikipedia.org : tlwiki ; http://tr.wikipedia.org : trwiki ; http://vi.wikipedia.org : viwiki ; http://yi.wikipedia.org : yiwiki ; http://yo.wikipedia.org : yowiki ; http://zh.wikipedia.org : zhwiki ; http://zh-yue.wikipedia.org : zh_yuewiki ; http://wikimania2010.wikimedia.org : wikimania2010wiki ; http://wikimania2009.wikimedia.org : wikimania2009wiki ; http://wikimania2008.wikimedia.org : wikimania2008wiki ; http://wikimania2007.wikimedia.org : wikimania2007wiki ; http://wikimania2006.wikimedia.org : wikimania2006wiki ; http://wikimania2005.wikimedia.org : wikimania2005wiki ; http://br.wikimedia.org : brwikimedia ; http://dk.wikimedia.org : dkwikimedia ; http://ve.wikimedia.org : vewikimedia ; http://pt.wikimedia.org : ptwikimedia ; http://no.wikimedia.org : nowikimedia ; http://ru.wikimedia.org : ruwikimedia ; http://se.wikimedia.org : sewikimedia ; http://rs.wikimedia.org : rswikimedia ; http://co.wikimedia.org : cowikimedia ; http://pl.wikimedia.org : plwikimedia ; http://ch.wikimedia.org : chwikimedia ; http://il.wikimedia.org : ilwikimedia ; http://nl.wikimedia.org : nlwikimedia ; http://nz.wikimedia.org : nzwikimedia ; http://ua.wikimedia.org : uawikimedia ; http://en.labs.wikimedia.org : en_labswikimedia ; http://de.labs.wikimedia.org : de_labswikimedia ; http://readerfeedback.labs.wikimedia.org : readerfeedback_labswikimedia ; http://meta.wikimedia.org : metawiki ; http://incubator.wikimedia.org : incubatorwiki ; http://www.mediawiki.org : mediawikiwiki 1prqb2yha4exevzelcd4ssdlssqdc3v 0 1283 7882 2010-06-18T09:23:01Z Lecartia 870 Redirected page to [[Accessibility Initiative]] wikitext text/x-wiki #REDIRECT[[Accessibility Initiative]] re5jv8aqgctjjqxp6pbdqfjagf1nqlj 0 1290 7952 2010-06-20T06:05:56Z Nemo bis 9 moved [[English Wikipedia Default Links]] to [[Releases/Default Switch/English Wikipedia Default Links]] wikitext text/x-wiki #REDIRECT [[Releases/Default Switch/English Wikipedia Default Links]] 21nm3kd4bqwm9h2uh42u8dd48y5wsd1 0 1291 8095 7960 2010-06-22T07:40:33Z Lecartia 870 /* US */ +WebAIM wikitext text/x-wiki == Current Strategy == == Proposed Strategy == == Brainstorming == === Possible partnerships === The following is just a list of ideas for possible partnerships for WMF or WAI with companies or organizations, nothing elaborated yet. ==== US ==== * [http://www.afb.org/afbconsulting.asp AFB Consulting], the consulting arm of the [http://www.afb.org/ American Foundation for the Blind] * [http://www.knowbility.org/main/ Knowbility] * [http://webaim.org/ WebAIM] [[Category:Accessibility]] 2rllwd8rop3kpt8x5zab3ca4ya5d1hh 0 1292 7983 7982 2010-06-20T18:00:40Z Brainmachine 449 proofreading; finishing up wikitext text/x-wiki {{FAQLang}} ==Што е променето?== Правиме неколку промени на корисничкиот посреднички елемент. Прво, воведуваме ново руво наречено „Вектор“. Ова ново руво треба да ги направи почестите функции полесни за пронаоѓање. Исто така воведовме бројни подобрувања на посредникот за уредување, вклучувајќи подобрен алатник за уредување, волшебници за помош со вметнување на табели и врски и вградена „помошна табела“ за да се помогне на корисниците да дојдат до пристап до најчесто користените можности. Конечно, го променивме распоредот на мрежното место со поедноставување на општата навигација и поместување на кутијата за пребарување на поинтуитивно место (видете го блог-написот [http://techblog.wikimedia.org/2010/06/usability-why-did-we-move-the-search-box/ "Why did we move the search box?"] за подетални објаснување на оваа промена). Се надеваме дека овие промени ќе им бидат корисни на нашите корисници. За оние коишто сакат да продолжат со оригиналните поставувања, ќе има врска „Врати ме назад“ на врвот на страницата. ==Зошто ги правите овие промени?== Википедија и другите проекти раководени од Фондацијата Викимедија се напишани и уредувани од волонтери. Кога луѓе со знаење не можат да учествуваат во уредувањето на Википедија заради тоа што им е тешко или збунувачки да уредуваат статии, тогаш тоа е сериозен проблем кој го поткопува потенцијалниот квалитет и длабочина на содржината која можеме да Ви ја понудиме. Со други зборови, дури и ако Вие не придонесувате со содржина, колку повеќе им олесниме на луѓето со знаење да се придружат на нашите проекти, толку покорисни ќе станат материјалите за Вас. Кога првпат беше развиен, софтверот кој го раководи Википедија се сметаше за лесен за корисниците. По денешниве стандарди, тој не е толку општ или лесен за корисниците како други софтвери. Затоа правиме серија од важни промени, почнувајќи со првото објавување на новиот софтвер во април за да ја подобриме Википедија. ==Како беше одлучено да се имплементираат овие промени?== Почнувајќи од јануари 2009, направивме мала екипа за проценка и подобрување на употребливоста и корисничкото искуство на Википедија и нејзините братски проекти. Првото истражување за употребливост и искуство се случи во март 2009. Ја споделивме [[UX Study|документацијата и видео-материјалот]] од истражувањето. Според пронаоѓањата од истражувањето, направиме низа на подобрувања кои станаа можни за јавно тестирање во август 2009. Ова беше следено со дополнителни промени и поправки основани на повратни информации од корисниците, кулминирајќи со второ корисничко истражување коешто се случи во октомври 2009 ([[Usability, Experience, and Progress Study|документација]]), кое ги потврди некои од нашите промени и нè наведе кон правење на повеќе подобрувања. Објавувањето на промените коишто ги почнуваме во април ги претставува серијата промени кои се добро тестирани и се искористени од преку 500.000 луѓе преку нашата бета-програма. Во просек, 80% од корисниците коишто ја пробале бета верзијата останале на неа, а собравме и значајни повратни информации од другите кориснци за причините поради кои ја напуштиле бета. Овие повратни информации се искористени за дополнителни промени, од кои многу од нив се проблеми специфични за јазикот. Ја издадовме целата документација од нашите [[Beta_Feedback_Survey|податоци за задржување на бета и корисничките коментари]].) ==Зошто не правите поголеми промени на посредничкиот елемент?== Ова е само почетокот. Ние направивме неколку дополнителни промени кои што сè уште се во фаза на активно тестирање и развиток. Можете да ги видите промените на нашето [http://prototype.wikimedia.org/ прототипно мрежно место]. По одобрувањето на овие промени низ корисничко истражување, ќе се надеваме на второ издание подоцна годинава. Ја направивме употребливоста траен напор на Фондацијата Викимедија. Од сега, вообичаени ќе станат редовни промени и подобрувања на посредничкиот елемент, направени не само за уредувачите-почетници, туку и за читателите и за искусните уредувачи. Поточно, ќе ја процениме најдобрата стратегија за примена на текстуално уредување на Википедија и нејзините братски проекти. ==Дали овие промени ќе бидат достапни на сите јазици?== Оваа промена првобитно беше применета на Ризницата на Викимедија во ран април. Англиската Википедеја следеше на 13 мај, а потоа и десетте најголеми википедии. Нашата меѓународна волонтерска заедница, работејќи преку translatewiki.net, сè уште работи напорно за да бидеме сигурни дека ја имаме најдобрата можна локализациска покриеност за почетокот. Ако сакате да помогнете, видете го овој чекор-по-чекор водич на [http://translatewiki.net/ translatewiki.net]. == Каде отиде јазичето за набљудување? == Можете да набљудувате/престанете со набљудување на страница со кликнување на ѕвездата во алатникот каде што се наоѓаат копчињата „Читај“, „Уреди“ и „Види историја“. ==Како корисниците ќе можат да бидат сигурни дека нивните скрипти, кориснички стилови, додатоци и надворешни алатки ќе работат?== Со тестирање со новите нагодувања, ќе можете да ја проверите компатибилноста и да разрешите било какви проблеми. Со кликнување на врската „Пробај ја Бета“ на врвот од секоја страница и со влез во Бета-верзијата, ќе ги вклучите истите нагодувања кои ќе станат основни. Друг начин да ја тестирате компатибилноста е да додадете „?useskin=vector“ на врвот од URL-то на страницата. На пример, http://mk.wikipedia.org/wiki/Фондација_Викимедија ќе стане http://mk.wikipedia.org/wiki/Фондација_Викимедија?useskin=vector за да видите како ќе изгледа страницата со рувото „вектор“. ==Како да ги исклучам новите можности?== Ако сакате да ги исклучите новите можности, Ве молиме следете ги следниве чекори:: # Најавете се со Вашата сметка # Кликнете на врската „Ново!“ во горниот десен агол на страницата (до Вашето корисничко име) # Одете до пасусот „Врати ме назад“ и кликнете на врската за ди ги исклучите новите можности Секогаш можете пак да ги вклучите новите можности со повторна посета на страницата „Ново!“. ==Зошто скриптите (monobook.js) и стиловите (monobook.css) веќе не функционираат?== Ако сакате да продолжите со Вашиот код во [[m:vector|рувото „Вектор“]], ќе мора да ја преместите и/или промените Вашата [[:mk:Special:Mypage/monobook.js|monobook.js]] страница до [[:mk:Special:Mypage/vector.js|vector.js]] и [[:mk:Special:Mypage/monobook.css|monobook.css]] до [[:mk:Special:Mypage/vector.css|vector.css]], соодветно. ==Совети за промена на вектор== Еве [http://meta.wikimedia.org/wiki/Vector добар материјал] за промени на рувото „вектор“. 4uowl95ahrvwy0yyejndj0h15w240i5 0 1295 8041 2010-06-22T00:16:42Z 216.38.133.254 Created page with ' == Cross Cultural/Global Research == == Article Quality ==' wikitext text/x-wiki == Cross Cultural/Global Research == == Article Quality == rp4gezpfk1loev562pkoq9atqhzd8w8 6 1300 8111 2010-06-22T15:09:07Z Teofilo~usabilitywiki 173 Screenshot showing use of number keys in simple Japanese word processor. For a falk on [[:commons:]] to explain some features concerning a gadget. wikitext text/x-wiki Screenshot showing use of number keys in simple Japanese word processor. For a falk on [[:commons:]] to explain some features concerning a gadget. 4v27jhp42cu3or1790hwb90z7poewt9 0 1308 8163 2010-06-24T05:42:08Z Liangent 235 Redirected page to [[Releases/Default Switch]] wikitext text/x-wiki #REDIRECT [[Releases/Default Switch]] 46q0e2tkbwncwsgtew1jbbvsfcztm1b 0 1311 8177 8176 2010-06-24T19:45:44Z Shuhari 4 /* SVN Commits */ wikitext text/x-wiki This page summarizes the QA automation project of the usability initiative using Selenium. == Environment == Please see [[Resources#Interaction_testing_automation|this page]] for how to set-up the Selenium environment, == Test Cases == === Search === === Watch === === Navigable Table of Contents === === Editor === ==== Dialogs ==== ==== Toolbar ==== == Issues == == SVN Commits == [http://www.mediawiki.org/wiki/Special:Code/MediaWiki/author/bhagya Bhagya's commits] na99ldwqdvrc545bq3sffv79bxqd25x 100 1312 8181 2010-06-24T22:39:34Z Guillom 13 +raw notes wikitext text/x-wiki ; Present : [[User:Guillom|Guillaume Paumier]], [[User:NeilK|Neil Kandalgaonkar]], [[user:eloquence|Erik Möller]], [[user:howief|Howie Fung]] * interwiki upload: nice to have, deferred for now (too many collateral complications) * cross-browser compatibility: ~2 weeks * upload cases:* ** OTRS e-mail magic ~2 weeks ** other cases (paintings, free software screenshots, etc.): nice to have, deferred for now * Incomplete uploads: abandoned for now; may not be the right answer for the issue. Replaced by: resumability of "incomplete" uploads within a given amount of time, deleted when expired + polishing of the upload wizard (categories, etc.) to add more nets to catch errors * deployability: code review: Mark H. + Tim; check with Danese for resource allocation * filetypes compatibility: not actually an issue * upload by URL (e.g. directly from flickr etc.): deferred for now, being taken care of by Add-media-wizard [[Category:Multimedia usability - Meetings]] kvdqinpg8i8k2kcil0mx0r251f1iwyn 6 1317 8230 2010-06-29T06:51:23Z 203.122.26.242 http://www.tolmol.com/bp/tech-tolmol/hp-envy-14-laptop-series-go-for-it-.h wikitext text/x-wiki HP Envy 14 laptop series, go for it HP Envy 14 series is supposed to be one of the world’s smallest and lightest laptops, which it surely is. But in addition to that, it is also a series which has fabulous display, great looks thanks to its metal alloy case, powerful and high performance latest i-core processors from Intel...[[...Read more on tolmol.com http://www.tolmol.com/bp/tech-tolmol/hp-envy-14-laptop-series-go-for-it-.h|...Read more on tolmol.com]] kofewnm1j60i2zn02y1pty81wc0lbdh 0 1340 8412 2010-07-12T08:36:43Z Lecartia 870 Created page with 'Bug of the Week or rather of every two weeks, depending on how fast we are, starting with # … # … [[Category:Accessibility]]' wikitext text/x-wiki Bug of the Week or rather of every two weeks, depending on how fast we are, starting with # … # … [[Category:Accessibility]] ruj7ha80xzna2tp0xe8in48edw6jk7u 100 1347 8449 8448 2010-07-13T21:18:31Z NeilK 1629 /* Detailed compatibility chart */ rough release dates of browsers wikitext text/x-wiki == Summary == {| class="wikitable sortable" border="1" ! Experience ! Percentage of visitors |- | Advanced | |- | Basic | |- | Graceful degradation | |- | Broken | |} == Detailed compatibility chart == {| class="wikitable sortable" border="1" ! Browser ! Version ! Release date ! Usage ! Degrade to simple form ! Basic functionality ! Firefogg uploader ! Drag and drop ! HTML5 uploader ! FileAPI uploader ! Notes |- |Chrome | 1 | 2008-12-01 | 0.02% | | | | | | | |- |Chrome | 2 | 2009-05-01 | 0.06% | | | | | | |- |Chrome | 3 | 2009-09-01 | 3.37% | | | | | | |- |Chrome | 4 | 2010-01-01 | 0.27% | | | | | | | |- |Chrome | 5 | 2010-05-01 | ?? | | | | | | | |- |Firefox | 1 | 2004-11-01 | 0.02% | | | | | | | |- |Firefox | 1.5 | 2005-11-01 | 0.13% | | | | | | | |- |Firefox | 2 | 2006-10-01 | 1.26% | | | | | | | |- |Firefox | 3 | 2008-05-01 | 10.56% | | | | | | | |- |Firefox | 3.5 | 2009-03-01 | 17.93% | | | | | | | |- |Firefox | 3.6 | 2010-01-01 | ? | | | | | | | |- |IE | 5 | 1999-03-01 | 0.04% | | | | | | | |- |IE | 5.5 | 2000-06-01 | 0.11% | | | | | | | |- |IE | 6 | 2001-09-01 | 11.68% | | | | | | | |- |IE | 7 | 2006-09-01 | 33.67% | | | | | | | |- |IE | 8 | 2009-03-01 | 8.90% | | | | | | | |- |Opera | 9 | 2006-06-01 | 0.21% | | | | | | | |- |Opera | 9.5 | 2008-05-01 | 2.62% | | | | | | | |- |Opera | 10 | 2009-10-01 | 0.02% | | | | | | | |- |Safari | 2 | 2005-04-01 | 0.03% | | | | | | | |- |Safari | 3 | 2007-10-01 | 0.70% | | | | | | | |- |Safari | 4 | 2009-06-01 | 4.17% | | | | | | | |- |} ==Definitions, details== ===Usage=== Percentage of visitors on Wikipedia, derived from Squid logs 1 Nov 2009 to 30 Nov 2009 ===Basic Functionality=== * Multiple file upload * Upload active indicator * Add license to all uploads * Add details :*Description :*Title (based on existing filename, checked for badness, unique) :*Categories (prefilled) :*License (if not already added) :*Location :*Other info *Usage help :*HTML :*On wiki 268bc5y4qy11zswyfngcwkhvu1dgz2f 100 1348 8457 8456 2010-07-13T22:24:03Z NeilK 1629 /* Prototype, layout and flow TODO */ wikitext text/x-wiki ===Deferred=== (until after the March usability tests) * Licensing tutorial * Metadata step :* Licensor ::* I have permission from someone :::* Email author with code in URL :::* Verification of code by visiting link + filling out deed :::* OTRS confirmation ::* Other, less frequent cases (paintins, screenshots, etc.) ::* configurable in preferences ::* memory of the recent licenses selected * Server-side file format conversion ===Must have=== * <s>Multi-step process</s> * <s>Upload step:</s> :* <s>Select file</s> :* <s>Upload progress</s> :* <s>Silently fix filename uniqueness</s> ::* <s>Catch upload errors and display appropriate warning</s> :::* <s>Acceptable file extensions only (shows error)</s> :::* <s>Image fingerprint (hash) checking for uniqueness (shows error)</s> ::::* can override if user has right perms :::* <s>Zero length files</s> :::* <s>Broken format</s> :::* <s>File too small</s> :::* <s>Any other upload errors</s> * Metadata/Macro step :* <s>Licensor</s> ::* <s>Offer choice</s> :::* <s>Own work</s> ::::* <s>Deed</s> ::::* <s>Apply ownwork source and appropriate licenses to all images</s> ::::* <s>Other options</s> ::::* <s>Apply ownwork source and chosen license to all images</s> :::* <s>Found on a website</s> ::::* <s>Enter in all source / license info individually</s> :* <s>Thumbnailing</s> :* <s>Description, change description</s> ::* <s>Multiple languages for descriptions</s> ::* <s>Change filename (with uniqueness check)</s> ::* <s>Extract and prefill with EXIF metadata, or other good guesses such as Wiki username</s> :::* Comment / Description :::* <s>Author (from EXIF copyright, or Wiki signature)</s> :::* License (if available in EXIF) :::* <s>Date (EXIF captured date OR EXIF stored date OR Today's date)</s> ::::* <s>Use calendar + datetime input</s> :::* <s>Source</s> ::* Do not allow progress to next step unless :::* At least one good description :::* All filenames are good :::* All files are licensed in some way * <s>Thanks step</s> ::* <s>Say thanks</s> ::* <s>Provide thumbnails and links and wiki markup for all files uploaded</s> ====Must have for the usability study==== * Step 1 - File selection ** Single file upload ** No validation of file extension, file type, or duplication ** Show progress bar * Step 2 - License selection ** List of images is grayed out or hidden until a license is selected ** My own work *** By default, CC-by-sa 3.0 is selected *** User can override the license selection ** From a web site *** By default, CC-by-sa 3.0 is selected *** User can override the license selection *** No validation on license violation ** If license selection is all unchecked, the message appears to select one. * Step 3 -Successful completion ** "Thank you!" ** Provide a link to the uploaded asset ===Nice to have=== :* Upload Step ::* <s>Multiple files</s> ::* Single click adding files ::* HTML5 and other advanced browsers :::* Fine-grained progress while uploading (XHR) :::* Thumbnails before uploading (FileAPI) :::* Drag & drop adding (HTML5) ::::* Multiple drag & drop adding (HTML5 Upload) :::* Catch errors before uploading ::::* File too large (FileAPI) ::* Firefogg :::* Chunked uploads (via Firefogg) :::* Firefogg thumbnailing :::* Advertise for Firefogg, if user has ffox and not firefogg? :::* Firefogg conversion of file formats, client side :* Metadata/Macro step ::* Map to set Location :::* prefill map with EXIF data ::* Prompt for "bad" filenames e.g. DSC_whatever and suggest change * Thanks step ::* Send a welcome email, if first time ===Won't have=== There is nothing that the Upload Wizard won't have. ===Uncertain=== * <s>Language guessing</s> : (Despite objections here, we have this anyway) : Users have set language codes to be what-the-fucking-ever, so we try to pick a good language that's "close" to theirs : see MediaWiki:LanguageHandler : also, there was some agreement that "pt-br" would be "pt" (visible in UploadForm.js) : also, there is evilness about pseudo-languages combining source and language, like "enownwork", but that should probably die == Prototype, layout and flow TODO == * Prototype :* <s>Fix configuration so article links work</s> :* Import appropriate templates (missing languages/months?) * All steps :* <s>Increase font size in help bubbles and second line of deed</s> :* <s>Remove automatic welcome message on sign-up on Commons prototype</s> :* <s>Add spinner while Step 1 loads</s> :* <s>'''Step1 / Step 2 / Step 3 outlined on top with a series of boxes with arrow points on the left side. Highlights move across bar as user progresses'''</s> :* Nice to have: <s>slide the series of arrow boxes at the top to remove steps</s> (caution: not RTL compatible, needs to flip) :* <s>'''Thumbnails at 120px width'''</s> :* <s>'''Combine deed and files Details step, pre-select checked for deed statement, confirm by clicking OK '''</s> :* <s>For copyright information in individual files, by default it just says "As above", can select to customize<s> :* <s>'''Do not allow customizing copyright information when there's only one file on the page. (There's no point)'''</s> :* <s>light colored horizontal lines to separate files (step 2 and 3 especially)</s> :* <s>more options/fewer options needs to have triangular arrow preceding text, points left for closed, down for open.</s> * Step 1 (adding files) :* <s>'''File input is ugly and not obviously clickable'''</s> :* <s>Remove upload 'X' is hard to click</s> :* <s>Indications of upload activity "uploading..." and "OK" need to be styled correctly</s> :* <s>Upload activity "OK" should have a checkmark</s> :* <s>"Add upload" button should stand off from uploads more, pointer to click</s> :* <s>Nice to have: "Add upload" pops open file dialog (1-click upload)</s> :* <s>Progress bar should be less violent colored, simple blue?</s> :* Message inside progress bar "uploading..." :* <s>progress bar has outline</s> :* Should there be an explicit step to move to the next page? It feels a little abrupt when it moves automatically forward. Consider that the user may have wandered away, switched to another tab. :* Ring a little bell when everything uploaded? * Step 2 (licensing and details) :* <s>'''General layout: thumbnail at left is hanging indent, then block of fields and values aligned from left to right'''</s> :* <s>With exception of description, textareas should appear to be one line initially (e.g. source, author)</s> :* <s>Remove scrollbars from textareas (they grow automatically) </s> :* <s>Thirdparty / found it on a website header text: "They are not my own work."</s> :* <s>Keep "we need information from you" at top</s> :* <s>Links to open deed options should be bolder, larger, cursor: pointer</s> :* <s>'''Checkboxes at left, hanging indent for rest of text'''</s> :* <s>In "own work", Make fine print (last paragraph) smaller </s> :* greyed examples for "Source" :* <s>Nice to have: Field-specific help appears when field has focus, or we need to draw attention to it (pressed submit with missing information). Use box with left-pointing arrow</s> ::* Field help should use specific examples for them to emulate :* When altering title, spinner should appear while it seeks for a unique filename ::* This should block submission :* <s>Validation. Stop them from committing info which is incomplete or problematic. Must help user understand what needs to be fixed (similar to help, perhaps pop open field specific help with red). Must have:</s> ::* <s>Unique filename ::* <s>Source ::* <s>Author ::* <s>License ::* At least one description ::* The required description has to be in some known language (or do we allow it to be blank? Check old form...) ::* <s>Date must be sane (it's as sane as datepicker widget allows, which ought to be enough)</s> :* Nice to have: geocoding :* <s>Nice to have: categories</s> :* Nice to have: fade away files, descriptions when deleted. :* Low priority: Enter author from EXIF (broken?) * Step 3 :* <s>'''Fix layout - thumbnails at left, options at right'''</s> :* <s>Wikitext should be thumbnail with default caption, no alignment</s> :* <s>Don't dead-end -- link back for more uploads, go to home page of wiki</s> * General prettiness :* buttons :* icons for "adding" type buttons :* errors should flash yellow when revealed, or next is clicked to indicate why you can't proceed. == TODO from IRC, email feedback == * You can't use browser back button :*Yes, this will be a bit of a challenge. So far it's a NTH not a must have. * Alert box "Please press this button to start your uploads." after pressing a button :*That's a mistake in the string *<thedj> if i'm on the first page, there are two buttons. "add another file" "upload" and "next". I'm slightly confused about what :*We used to have it so that upload and next were the same button, that is, once it was finished, it went immediately to the next. That felt weird. But perhaps we should hide [next] until all files are uploaded. * It exposes the local filename http://commons.prototype.wikimedia.org/wiki/File:Jimmy_Wales_being_a_good_citizen.png :*I don't understand the criticism. The local filename is likely to be useful; if not we will filter for common patterns of crappy autogenerated filenames. *Upload with "null" as summary http://commons.prototype.wikimedia.org/w/index.php?title=File:Upload_wizard_deadlock.png&action=edi :*Fixing this *Useless? "ZOMG THIS DEED IS NOT READY" message :*This is obviously a placeholder * You can reach to a deadlock situation http://commons.prototype.wikimedia.org/wiki/File:Upload_wizard_deadlock.png * Wizard tabs show a link pointer but you can't browse there. * You are allowed to write new lines in the title (but should not) Also, it doesn't trim leading/trailing whitespace * Font size in text fields is too small * Add support for upload from url * You can change the upload fields *after* they have been uploaded * No option to add another file after the upload (merge upload with next button?) :*Agreed *"To link to it in HTML, copy this HTML code:" fails for long urls (only the first line is shown, breaks at http://commons.prototype.wikimedia.org) :*Yup, agree here *UploadWizardPage.js contains wiki config. It should be a <script> tag int the page. :*I don't understand this comment -- NeilK *Noscript fallback doesn't work (no error either) *Noscript fallback should be a html equivalent Wizard :*Highly unlikely. noscript fallback will be a simple HTML4 file uploader. bellwzpkqcuchd6w8t5cghwklgj57um 10 1351 8637 8635 2010-07-29T13:27:16Z Nemo bis 9 cat wikitext text/x-wiki <div style="float:right; margin-left: 20px; border:1px solid #A7D7F9; padding:1em; clear:right;"> <strong>[[Accessibility Initiative]]</strong> * [[Approach for Wikimedia]] * [[Accessibility issues]] * [[Best practices]] * [[Coordination]] * more to come …<br/>Stay tuned! </div><noinclude> [[Category:Navigational templates]]</noinclude> rzqa55unw0npbprn4r6szzzmxozpvlb 0 1364 8575 8565 2010-07-26T16:55:43Z Guillom 13 #REDIRECT[[Multimedia:Hub]] wikitext text/x-wiki #REDIRECT[[Multimedia:Hub]] 2ok8cpupk1o05z344e8q2sygnwkkvf0 0 1365 8576 8564 2010-07-26T16:56:15Z Guillom 13 #REDIRECT[[Multimedia:Hub]] wikitext text/x-wiki #REDIRECT[[Multimedia:Hub]] 2ok8cpupk1o05z344e8q2sygnwkkvf0 100 1369 9214 9208 2010-10-28T11:52:15Z Drorsnir 1545 Undo revision 9208 by [[Special:Contributions/89.189.74.235|89.189.74.235]] ([[User talk:89.189.74.235|talk]]) wikitext text/x-wiki The '''Multimedia Usability Project''' is realized thanks to a grant from the [http://www.fordfound.org/ Ford Foundation] and aims to improve the interfaces and workflows for multimedia uploading on Wikimedia websites. More information on the project: * ''[http://blog.wikimedia.org/2009/07/02/ford-foundation-awards-300k-grant-for-wikimedia-commons/ Ford Foundation Awards $300K Grant for Wikimedia Commons]'', Erik Möller, July 2009. * ''[[:foundation:Press releases/Wikimedia Ford Foundation Grant July 2009|Wikimedia Foundation receives Ford Foundation grant to grow Wikimedia Commons, a free educational media repository]]'', Press release, July 2009. * [[:foundation:File:WMF Ford Multimedia Participation Project.pdf|Original grant proposal as submitted to the Ford Foundation]] (PDF) == Research == * [[Multimedia:User research|User research]] ** [[Multimedia:Preliminary user research|Preliminary user research]] *** [[Multimedia:Demographics and content dynamics|Demographics and content dynamics]] *** [[Multimedia:Initial survey|Initial survey]] *** [[:commons:Commons:Usability issues and ideas|Open forum]] summarized in [[Multimedia:Issues reported by users|Issues reported by users]] *** [[Multimedia:Ethnographic interviews|Ethnographic interviews]] *** [[Multimedia:Stakeholder analysis|Stakeholder analysis]] ** [[Multimedia:Meeting in Paris|Meeting in Paris]] *** [[Multimedia:Meeting in Paris/Notes|Documentation]] *** [[Multimedia:Meeting in Paris/Summary|Summary]] * [[Multimedia:Domain research/Upload|Domain research/Upload]] * [[Multimedia:UX study, March 2010|UX study, March 2010]] ** [[Multimedia:UX study, March 2010/CfP|Call for Proposals]] == Requirements == [[File:GPaumier multimedia usability draft mock-ups Oct09.pdf|thumb|Draft mock-ups]] * Requirements/needs (including environmental and technical constraints) ** [[Multimedia:Uploading|Uploading]] ** [[Multimedia:Maintenance|Maintenance]] ** [[Multimedia:Editing|Editing]] ** [[Multimedia:Using and reusing content|Using and reusing content]] ** [[Multimedia:Crosswiki integration|Crosswiki integration]] ** [[Multimedia:Multilingual support|Multilingual support]] ** [[Multimedia:Navigation|Navigation]] ** [[Multimedia:Metadata|Metadata]] ** [[Multimedia:Back-end|Back-end]] ** [[Multimedia:Requirements/all|Full list]] == [[Multimedia:Specifications|Specifications]] == <span class=plainlinks>[http://usability.wikimedia.org/w/index.php?title=Multimedia:Specifications&action=edit edit]</span> {{Multimedia:Specifications}} == General == * [[Multimedia:Project schedule|Project schedule]] * [[Multimedia:Brainstorming|Brainstorming]] * [[Multimedia:Resources|Resources]] [[Category:Multimedia usability|*]] 8v297tuvemrxqn0xwhcfas485wppbbw 0 1371 8830 8585 2010-08-28T01:31:14Z 216.130.78.202 wikitext text/x-wiki The following is a DRAFT list of Phase V projects. It was produced by taking the [http://noc.wikimedia.org/conf/all.dblist database list] and removing projects that were part of Phases I-IV. aawiki<br> aawikibooks<br> aawiktionary<br> abwiki<br> abwiktionary<br> acewiki<br> advisorywiki<br> afwikibooks<br> afwikiquote<br> afwiktionary<br> akwiki<br> akwikibooks<br> akwiktionary<br> alswikibooks<br> alswikiquote<br> alswiktionary<br> amwiki<br> amwikiquote<br> amwiktionary<br> angwiki<br> angwikibooks<br> angwikiquote<br> angwikisource<br> angwiktionary<br> anwiki<br> anwiktionary<br> arbcom_dewiki<br> arbcom_enwiki<br> arbcom_fiwiki<br> arbcom_nlwiki<br> arcwiki<br> arwikibooks<br> arwikinews<br> arwikiquote<br> arwikisource<br> arwiktionary<br> arzwiki<br> astwiki<br> astwikibooks<br> astwikiquote<br> astwiktionary<br> aswiki<br> aswikibooks<br> aswiktionary<br> auditcomwiki<br> avwiki<br> avwiktionary<br> aywiki<br> aywikibooks<br> aywiktionary<br> azwiki<br> azwikibooks<br> azwikiquote<br> azwikisource<br> azwiktionary<br> barwiki<br> bat_smgwiki<br> bawiki<br> bawikibooks<br> bclwiki<br> betawikiversity<br> bewiki<br> bewikibooks<br> bewikiquote<br> bewiktionary<br> bgwikibooks<br> bgwikinews<br> bgwikiquote<br> bgwikisource<br> bgwiktionary<br> bhwiki<br> bhwiktionary<br> biwiki<br> biwikibooks<br> biwiktionary<br> bmwiki<br> bmwikibooks<br> bmwikiquote<br> bmwiktionary<br> bnwikibooks<br> bnwikisource<br> bnwiktionary<br> boardgovcomwiki<br> boardwiki<br> bowiki<br> bowikibooks<br> bowiktionary<br> bpywiki<br> brwikiquote<br> brwiktionary<br> bswikibooks<br> bswikinews<br> bswikiquote<br> bswikisource<br> bswiktionary<br> bugwiki<br> bxrwiki<br> cawikibooks<br> cawikinews<br> cawikiquote<br> cawikisource<br> cawiktionary<br> cbk_zamwiki<br> cdowiki<br> cebwiki<br> cewiki<br> chairwiki<br> chapcomwiki<br> chowiki<br> chrwiki<br> chrwiktionary<br> chwiki<br> chwikibooks<br> chwiktionary<br> chywiki<br> ckbwiki<br> collabwiki<br> commonswiki<br> cowiki<br> cowikibooks<br> cowikiquote<br> cowiktionary<br> crhwiki<br> crwiki<br> crwikiquote<br> crwiktionary<br> csbwiki<br> csbwiktionary<br> cswikibooks<br> cswikinews<br> cswikiquote<br> cswikisource<br> cswikiversity<br> cswiktionary<br> cuwiki<br> cvwiki<br> cvwikibooks<br> cywikibooks<br> cywikiquote<br> cywikisource<br> cywiktionary<br> dawikibooks<br> dawikiquote<br> dawikisource<br> dawiktionary<br> dewikibooks<br> dewikinews<br> dewikiquote<br> dewikisource<br> dewikiversity<br> dewiktionary<br> dvwiki<br> dvwiktionary<br> dzwiki<br> dzwiktionary<br> eewiki<br> elwikibooks<br> elwikiquote<br> elwikisource<br> elwikiversity<br> elwiktionary<br> emlwiki<br> enwiki<br> enwikibooks<br> enwikinews<br> enwikiquote<br> enwikisource<br> enwikiversity<br> enwiktionary<br> eowikibooks<br> eowikiquote<br> eowiktionary<br> eswikibooks<br> eswikinews<br> eswikiquote<br> eswikisource<br> eswikiversity<br> eswiktionary<br> etwikibooks<br> etwikiquote<br> etwikisource<br> etwiktionary<br> euwikibooks<br> euwikiquote<br> euwiktionary<br> execwiki<br> extwiki<br> fawikibooks<br> fawikiquote<br> fawikisource<br> fawiktionary<br> ffwiki<br> fiu_vrowiki<br> fiwikibooks<br> fiwikimedia<br> fiwikinews<br> fiwikiquote<br> fiwikisource<br> fiwikiversity<br> fiwiktionary<br> fjwiki<br> fjwiktionary<br> flaggedrevs_labswikimedia<br> foundationwiki<br> fowiki<br> fowikisource<br> fowiktionary<br> frwikibooks<br> frwikinews<br> frwikiquote<br> frwikisource<br> frwikiversity<br> frwiktionary<br> frrwiki<br> furwiki<br> fywiki<br> fywikibooks<br> fywiktionary<br> ganwiki<br> gawiki<br> gawikibooks<br> gawikiquote<br> gawiktionary<br> gdwiki<br> gdwiktionary<br> glkwiki<br> glwikibooks<br> glwikiquote<br> glwikisource<br> glwiktionary<br> gnwiki<br> gnwikibooks<br> gnwiktionary<br> gotwiki<br> gotwikibooks<br> grantswiki<br> guwiki<br> guwikibooks<br> guwikiquote<br> guwiktionary<br> gvwiki<br> gvwiktionary<br> hakwiki<br> hawiki<br> hawiktionary<br> hawwiki<br> hewikibooks<br> hewikinews<br> hewikiquote<br> hewikisource<br> hewiktionary<br> hifwiki<br> hiwiki<br> hiwikibooks<br> hiwikiquote<br> hiwiktionary<br> howiki<br> hrwiki<br> hrwikibooks<br> hrwikiquote<br> hrwikisource<br> hrwiktionary<br> hsbwiktionary<br> htwiki<br> htwikisource<br> huwikibooks<br> huwikinews<br> huwikiquote<br> huwikisource<br> huwiktionary<br> hywiki<br> hywikibooks<br> hywikiquote<br> hywikisource<br> hywiktionary<br> hzwiki<br> iawikibooks<br> iawiktionary<br> idwikibooks<br> idwikiquote<br> idwikisource<br> idwiktionary<br> iewiki<br> iewikibooks<br> iewiktionary<br> igwiki<br> iiwiki<br> ikwiki<br> ikwiktionary<br> ilowiki<br> internalwiki<br> iowiki<br> iowiktionary<br> iswiki<br> iswikibooks<br> iswikiquote<br> iswikisource<br> iswiktionary<br> itwikibooks<br> itwikinews<br> itwikiquote<br> itwikisource<br> itwikiversity<br> itwiktionary<br> iuwiki<br> iuwiktionary<br> jawiki<br> jawikibooks<br> jawikinews<br> jawikiquote<br> jawikisource<br> jawikiversity<br> jawiktionary<br> jbowiki<br> jbowiktionary<br> jvwiki<br> jvwiktionary<br> kaawiki<br> kabwiki<br> kawikibooks<br> kawikiquote<br> kawiktionary<br> kgwiki<br> kiwiki<br> kjwiki<br> kkwiki<br> kkwikibooks<br> kkwikiquote<br> kkwiktionary<br> klwiki<br> klwiktionary<br> kmwiki<br> kmwikibooks<br> kmwiktionary<br> knwiki<br> knwikibooks<br> knwikiquote<br> knwikisource<br> knwiktionary<br> kowikibooks<br> kowikinews<br> kowikiquote<br> kowikisource<br> kowiktionary<br> krcwiki<br> krwiki<br> krwikiquote<br> kswiki<br> kswikibooks<br> kswikiquote<br> kswiktionary<br> kuwiki<br> kuwikibooks<br> kuwikiquote<br> kuwiktionary<br> kvwiki<br> kwwiki<br> kwwikiquote<br> kwwiktionary<br> kywiki<br> kywikibooks<br> kywikiquote<br> kywiktionary<br> ladwiki<br> lawiki<br> lawikibooks<br> lawikiquote<br> lawikisource<br> lawiktionary<br> lbewiki<br> lbwikibooks<br> lbwikiquote<br> lbwiktionary<br> lgwiki<br> lijwiki<br> liquidthreads_labswikimedia<br> liwiki<br> liwikiquote<br> liwikisource<br> liwiktionary<br> lmowiki<br> lnwiki<br> lnwikibooks<br> lnwiktionary<br> lowiki<br> lowiktionary<br> ltwiki<br> ltwikibooks<br> ltwikiquote<br> ltwikisource<br> ltwiktionary<br> lvwiki<br> lvwikibooks<br> lvwiktionary<br> map_bmswiki<br> mdfwiki<br> mgwiki<br> mgwikibooks<br> mgwiktionary<br> mhrwiki<br> mhwiki<br> mhwiktionary<br> miwiki<br> miwikibooks<br> miwiktionary<br> mkwikibooks<br> mkwikisource<br> mkwiktionary<br> mlwikibooks<br> mlwikiquote<br> mlwikisource<br> mlwiktionary<br> mnwiki<br> mnwikibooks<br> mnwiktionary<br> mowiki<br> mowiktionary<br> mrwiki<br> mrwikibooks<br> mrwikiquote<br> mrwiktionary<br> mswikibooks<br> mswiktionary<br> mtwiktionary<br> muswiki<br> mwlwiki<br> myvwiki<br> mywiki<br> mywikibooks<br> mywiktionary<br> mznwiki<br> nahwiki<br> nahwikibooks<br> nahwiktionary<br> napwiki<br> nawiki<br> nawikibooks<br> nawikiquote<br> nawiktionary<br> nds_nlwiki<br> ndswiki<br> ndswikibooks<br> ndswikiquote<br> ndswiktionary<br> newiki<br> newikibooks<br> newiktionary<br> newwiki<br> ngwiki<br> nlwikibooks<br> nlwikinews<br> nlwikiquote<br> nlwikisource<br> nlwiktionary<br> nnwikiquote<br> nnwiktionary<br> noboard_chapterswikimedia<br> nostalgiawiki<br> novwiki<br> nowikibooks<br> nowikinews<br> nowikiquote<br> nowikisource<br> nowiktionary<br> nrmwiki<br> nvwiki<br> nywiki<br> ocwikibooks<br> ocwiktionary<br> officewiki<br> omwiki<br> omwiktionary<br> orwiki<br> orwiktionary<br> oswiki<br> otrs_wikiwiki<br> outreachwiki<br> pa_uswikimedia<br> pagwiki<br> pamwiki<br> papwiki<br> pawiki<br> pawikibooks<br> pawiktionary<br> pcdwiki<br> pdcwiki<br> pihwiki<br> piwiki<br> piwiktionary<br> plwikibooks<br> plwikinews<br> plwikiquote<br> plwikisource<br> plwiktionary<br> pnbwiki<br> pntwiki<br> pswiki<br> pswikibooks<br> pswiktionary<br> ptwikibooks<br> ptwikinews<br> ptwikiquote<br> ptwikisource<br> ptwikiversity<br> ptwiktionary<br> qualitywiki<br> quwiki<br> quwikibooks<br> quwikiquote<br> quwiktionary<br> rmwiki<br> rmwikibooks<br> rmwiktionary<br> rmywiki<br> rnwiki<br> rnwiktionary<br> roa_rupwiki<br> roa_rupwiktionary<br> rowikibooks<br> rowikinews<br> rowikiquote<br> rowikisource<br> rowiktionary<br> ruwikibooks<br> ruwikinews<br> ruwikiquote<br> ruwikisource<br> ruwikiversity<br> ruwiktionary<br> rwwiki<br> rwwiktionary<br> sawiki<br> sawikibooks<br> sawiktionary<br> scnwiki<br> scnwiktionary<br> scowiki<br> scwiki<br> scwiktionary<br> sdwiki<br> sdwikinews<br> sdwiktionary<br> searchcomwiki<br> sewiki<br> sewikibooks<br> sgwiki<br> sgwiktionary<br> shwiki<br> shwiktionary<br> simplewiki<br> simplewikibooks<br> simplewikiquote<br> simplewiktionary<br> siwiki<br> siwikibooks<br> siwiktionary<br> skwikibooks<br> skwikiquote<br> skwikisource<br> skwiktionary<br> slwikibooks<br> slwikiquote<br> slwikisource<br> slwiktionary<br> smwiki<br> smwiktionary<br> snwiki<br> snwiktionary<br> sourceswiki<br> sowiki<br> sowiktionary<br> spcomwiki<br> specieswiki<br> sqwikibooks<br> sqwikiquote<br> sqwiktionary<br> srnwiki<br> srwiki<br> srwikibooks<br> srwikinews<br> srwikiquote<br> srwikisource<br> srwiktionary<br> sswiki<br> sswiktionary<br> stqwiki<br> strategyappswiki<br> strategywiki<br> stwiki<br> stwiktionary<br> suwiki<br> suwikibooks<br> suwikiquote<br> suwiktionary<br> svwikibooks<br> svwikinews<br> svwikiquote<br> svwikisource<br> svwiktionary<br> swwiki<br> swwikibooks<br> swwiktionary<br> szlwiki<br> tawiki<br> tawikibooks<br> tawikinews<br> tawikiquote<br> tawikisource<br> tawiktionary<br> testwiki<br> tetwiki<br> tewikibooks<br> tewikiquote<br> tewikisource<br> tewiktionary<br> tgwiki<br> tgwikibooks<br> tgwiktionary<br> thwikibooks<br> thwikinews<br> thwikiquote<br> thwikisource<br> thwiktionary<br> tiwiki<br> tiwiktionary<br> tkwiki<br> tkwikibooks<br> tkwikiquote<br> tkwiktionary<br> tlwikibooks<br> tlwiktionary<br> tnwiki<br> tnwiktionary<br> towiki<br> towiktionary<br> tpiwiki<br> tpiwiktionary<br> trwikibooks<br> trwikimedia<br> trwikinews<br> trwikiquote<br> trwikisource<br> trwiktionary<br> tswiki<br> tswiktionary<br> ttwiki<br> ttwikibooks<br> ttwikiquote<br> ttwiktionary<br> tumwiki<br> twwiki<br> twwiktionary<br> tywiki<br> udmwiki<br> ugwiki<br> ugwikibooks<br> ugwikiquote<br> ugwiktionary<br> ukwikibooks<br> ukwikimedia<br> ukwikinews<br> ukwikiquote<br> ukwikisource<br> ukwiktionary<br> urwiki<br> urwikibooks<br> urwikiquote<br> urwiktionary<br> usabilitywiki<br> uzwiki<br> uzwikibooks<br> uzwikiquote<br> uzwiktionary<br> vecwiki<br> vewiki<br> viwikibooks<br> viwikiquote<br> viwikisource<br> viwiktionary<br> vlswiki<br> vowiki<br> vowikibooks<br> vowikiquote<br> vowiktionary<br> warwiki<br> wawiki<br> wawikibooks<br> wawiktionary<br> wg_enwiki<br> wikimania2011wiki<br> wikimaniateamwiki<br> wowiki<br> wowikiquote<br> wowiktionary<br> wuuwiki<br> xalwiki<br> xhwiki<br> xhwikibooks<br> xhwiktionary<br> yiwikisource<br> yiwiktionary<br> yowikibooks<br> yowiktionary<br> zawiki<br> zawikibooks<br> zawikiquote<br> zawiktionary<br> zeawiki<br> zh_classicalwiki<br> zh_min_nanwiki<br> zh_min_nanwikibooks<br> zh_min_nanwikiquote<br> zh_min_nanwikisource<br> zh_min_nanwiktionary<br> zhwikibooks<br> zhwikinews<br> zhwikiquote<br> zhwikisource<br> zhwiktionary<br> zuwiki<br> zuwikibooks<br> zuwiktionary<br> fhywmio7jdgqpt3sa2c8meqdc4o8eci 14 1374 8594 2010-07-29T12:28:35Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 14 1375 8595 2010-07-29T12:29:10Z Nemo bis 9 let's at least start the catgeory... wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 14 1376 8611 2010-07-29T12:58:22Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 14 1377 8617 2010-07-29T13:02:58Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 14 1378 8620 2010-07-29T13:12:27Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Wikipedia Usability Initiative]] b71m9ekli9qlfi9hvr755jxxccmm7oe 14 1379 8622 2010-07-29T13:13:17Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 14 1380 8624 2010-07-29T13:14:33Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Wikipedia Usability Initiative]] b71m9ekli9qlfi9hvr755jxxccmm7oe 14 1381 8668 8631 2010-07-29T13:36:32Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Wiki maintenance ]] dkvl5ioyg869pfhfu5xpacj4tllvxdt 14 1382 8632 2010-07-29T13:19:26Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Root]] plgyxa9zdjtjany4tcftrk2sfqdwo6g 14 1383 9363 9210 2011-08-22T11:51:12Z Ruslik0 224 Reverted edits by [[Special:Contributions/89.189.74.235|89.189.74.235]] ([[User talk:89.189.74.235|talk]]) to last revision by [[User:Nemo bis|Nemo bis]] wikitext text/x-wiki [[Category:Maintenance]] it59vo5whwexpgslnlv8id1urubvc0x 14 1384 8634 2010-07-29T13:20:02Z Nemo bis 9 cat wikitext text/x-wiki [[Category:Maintenance]] it59vo5whwexpgslnlv8id1urubvc0x 14 1385 8638 2010-07-29T13:27:28Z Nemo bis 9 Created page with '[[Category:Templates]]' wikitext text/x-wiki [[Category:Templates]] 0t5jiibdq6k1tam9oy4zt1yld5iz80u 14 1386 8642 2010-07-29T13:28:19Z Nemo bis 9 Created page with '[[category:Templates]]' wikitext text/x-wiki [[category:Templates]] 54t1mhyrfy47xko9cthswb14g7xs1s6 100 1394 8713 2010-08-06T20:19:27Z Guillom 13 moved [[Multimedia:UX study, March 2010]] to [[Multimedia:UX study, June 2010]] wikitext text/x-wiki #REDIRECT [[Multimedia:UX study, June 2010]] 0j68mwaanayy8ghhpwzn3lvt2pxp4h6 100 1395 8715 2010-08-06T20:19:50Z Guillom 13 moved [[Multimedia:UX study, March 2010/CfP]] to [[Multimedia:UX study, June 2010/CfP]]: delayed wikitext text/x-wiki #REDIRECT [[Multimedia:UX study, June 2010/CfP]] kh92lhp66mzs6nucx1y2hl36xklxd5v 100 1396 9304 9303 2010-11-30T00:13:16Z Guillom 13 /* How can I get involved or share my feedback with you? */ reword wikitext text/x-wiki Please note that The Upload Wizard is released in beta version. We hope it proves useful for new participants in the simple cases, but we're still improving it and many interface changes are coming, such as a new license chooser and a different way to display help. == General QA == ==== What is the upload wizard? ==== :The upload wizard is a new way of uploading files to Wikimedia Commons, the media library associated with Wikipedia and all other Wikimedia projects. The upload wizard is an [[:mw:Extension:UploadWizard|extension for MediaWiki]], the software that powers Wikimedia's websites. This feature was realized as part of the Multimedia Usability project. ==== What is the Multimedia Usability project? ==== : The Multimedia Usability Project was a special project of the Wikimedia Foundation; it aimed to improve the interfaces and workflows for multimedia uploading on Wikimedia websites. It was realized thanks to a grant from the [http://www.fordfound.org Ford Foundation]. All work documents are hosted on the usability wiki and linked from the [[Multimedia:Hub|Multimedia Usability Project hub]]. : Read more: [http://blog.wikimedia.org/2009/07/02/ford-foundation-awards-300k-grant-for-wikimedia-commons/ Blog announcement], [[:foundation:Press releases/Wikimedia Ford Foundation Grant July 2009|Press release]], [[:foundation:File:WMF Ford Multimedia Participation Project.pdf|Original grant proposal]]. ==== Why are you changing the way to upload media files? ==== : Principally, because the current process is highly complex; it mixes educational components conveying the principles of free culture and free licensing with process components, does not offer a simplified workflow for the most common use cases, confronts all users with very rare edge cases, and does not go far enough in minimizing user effort (e.g. for uploading multiple files or by extracting metadata). This complexity was known before the project began, and systematic user testing has proven that it is a major deterrent for new contributors. : The complexity of the current process can be attributed to the way it has evolved over time: the MediaWiki software that powers our projects only had very limited file upload capabilities to begin with, and the project communities have applied a high degree of bottom-up customization to improve both the messaging around licensing, as well as the management of metadata. This has, however, also led to rapidly increasing complexity and decreasing maintainability. There have been few stepped back efforts to review and improve the process, and they were very resource constrained. : By building a new upload system designed based on user research, our goal is to improve the uploading experience both for new, occasional and experienced users, leading to a more vibrant, active community engaged with rich media on our projects. ==== Will the upload wizard be available on Wikipedia or other Wikimedia projects than Wikimedia Commons? ==== : Wikimedia Commons serves all Wikimedia Foundation projects with freely licensed media files, so it has been our primary target for user interface improvements. It is possible to upload copyrighted media files that aren't permitted under Wikimedia Commons policy to [[m:EDP|some projects]]. For example, the English Wikipedia permits uploading screenshots of movies, album covers, brief samples of copyrighted music, etc., under the "fair use" provisions of copyright law. In order for these narrower secondary use cases to be well-supported by the wizard, we will have to further refine the workflow, and this has not been a priority of the current effort. So, these use cases will fall back to the old upload form for now. : Additionally, one of our wishlist items is to integrate the upload wizard directly into the editing workflow on projects like Wikipedia, as opposed to requiring users to visit a separate website. However, the current separation actually makes sense while the projects maintain separate infrastructure for purposes such as user-to-user messaging and change notification. Until we have improved integration of this infrastructure, it would be too risky to simply transparently send uploads to Wikimedia Commons, as users would not see new message notifications or other change notifications, and the normal interaction with uploaders on Wikimedia Commons could break down. ==== Will the upload wizard be available for other non-Wikimedia MediaWiki websites? ==== : Yes. The upload wizard is available as a [[:mw:Extension:UploadWizard|MediaWiki extension]] and released under the GPL. While it's still in beta phase, it is be possible to install it on any MediaWiki installation (1.16 and above) and it can be customized, depending on the policy requirements of the wiki regarding media files and licenses. ==== How can I get involved or share my feedback with you? ==== : If your question wasn't listed on this page, we warmly welcome your feedback, comments and questions at [[:commons:Commons:usability issues and ideas|Commons:Usability issues and ideas]]. We value the feedback provided by the Wikimedia community and we'll do our best to address your concerns. Please check our '''[https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&component=UploadWizard&resolution=WONTFIX&resolution=LATER&resolution=---&product=MediaWiki%20extensions list of open issues]''' first to save your time. == QA for experienced users == ==== Why do you allow the user to upload without first asking for a license / author / description? ==== : Our goal is twofold. First, we're trying to get closer from the user's mental model, by providing an interface they're expecting, rather than a wall of text and fields to fill in. Also, we want to be able to display a thumbnail of the uploaded files, to make it easier to add information such as a description. Similarly, uploading the image first allows us to extract as much information as possible from the file metadata. For example, the current upload form requires the user to add the date of the work in a very specific format. Our upload wizard extracts that piece of information directly from the metadata and suggests it in the form. This wouldn't be possible in all browsers if we didn't upload the file first. ==== What happens if the user never provides the basic required information? ==== : The file is automatically discarded if the minimum required information is not provided. ==== Why did you remove all the choices such as "uploading someone else's work from Flickr" or "free software screenshot"? ==== : Our goal is to provide a simple interface that guides the user and doesn't overwhelm them with questions. Most alternative choices on the current upload form do not actually provide any field specific to those cases. They mostly differ in the verbose documentation we impose on users, and which has been proven to be ineffective. : Some cases will hopefully be handled better in the future, for example by allowing upload from a URL, recognizing the URL and fetching metadata & copyright terms when possible. Some toolserver-hosted tools like DerivativeFX and Flickr2Commons would definitely benefit the users if integrated into MediaWiki or an extension. ==== Why did you remove the "traps" from the current upload form that catch possible mistakes such as fair use? ==== : We believe it is better to provide an interface that educates the user and encourages them to do what's right, rather than setting traps for them to fall into. "Traps" currently in use on Commons aim to identify unfree content; we would like to empower users to make that choice consciously, based on the tutorial. Our last UX study, which should include the licensing tutorial, will hopefully confirm that this approach works. If not, we'll revise it. : A complementary approach we would like to consider would be some kind of technology-supported mentoring system, as well as better tools to patrol the feed of incoming files. ==== Why did you remove all the instructions from the current upload form? How do you expect the user to do what's right now? ==== : Much of the complexity of the original form was in explaining how to work around various defects of the form itself. For example, we've avoided having to tell the user about proper extensions, by eliminating the extension from the interface entirely. Instead the user only has to give their file a title and the program does the rest. : There are some issues which are necessary to explain to new users, such as licensing. However, we do not believe the "wall of text" approach is helpful. Our research showed that most users were intimidated, or simply didn't read it. : Instead, where issues are complex, we prefer to suggest and explain good default choices, so the user will naturally "get it right". Also, the [http://blog.wikimedia.org/blog/2010/11/05/illustrated-licensing-tutorial-wikimedia-commons/ licensing tutorial] is an essential part of this strategy. ==== Why do you give CC-by-sa such a prominent/default/recommended place? Why don't you use a step-by-step license chooser? ==== : The Creative Commons Attribution/Share-Alike (CC-BY-SA) License is the primary license used for all text in Wikimedia Foundation projects. While more licenses are permitted for media files, the set of licenses permitted is constrained by the [[foundation:Resolution:Licensing Policy|Licensing Policy]]. We believe that the CC-BY-SA license represents a good default choice for works authored by the uploader, consistent with the same values and principles which led to it being chosen as the default license for text contributions. : A default choice also has significant user experience benefits. New users cannot be expected to have any mental model of licensing, and our user testing has shown that some users will click through any license chooser in the understanding that such a choice screen represents "the step where you have to agree to the site terms". This means that we are losing an important opportunity to have an elevated engagement with the user about the core principles of free culture and free licensing, by confronting users with too much detail early in the process of uploading a file. Instead of doing so, our strategy is to a) educate users through a licensing tutorial that is clearly separate from the uploading process; b) have sane default choices for the uploading process consistent with Wikimedia's principles and values, but make it easy for experienced users to change those defaults. ==== Where are the other licenses? ==== : The current beta only offers the most common licensing options. We plan to have an interface to dive into the full list of licenses for people who are looking for exotic licenses. Also, you will be able to specify your preferred license(s) in your user preferences, so you don't have to go through the full list each time. ==== Why do you make it so easy to multilicense works? ==== : Releasing your work under several licenses has been a long-standing tradition on Commons; it wouldn't make sense for us to use the interface to remove the ability users have to multilicense their work. Instead, we're suggesting a recommended license, for new and occasional users, and we're leaving experienced users the possibility to multilicense their work if they wish to do so. ==== I don't want to go through the licensing tutorial each time I upload a file! Can I disable that? ==== : Yes, you will be able to do that soon. Our current thinking is that the last page of the licensing tutorial will include a check box to opt-out, and possibly a link to watch the tutorial again on the first step of the wizard. ==== I already have my preferred license, and it's not the default. Can I change that? ==== : Yes, you will be able to do that soon. You will be able to specify your preferred license in your user preferences, and it will supersede the default recommended license. ==== The general messaging is confusing / inappropriate / could be improved ==== : We still have upcoming changes, notably on the license picker. Commons participants who tested the prototype Upload wizard provided a lot of constructive feedback, and we implemented some changes as to reflect their suggestions. We will continue to refine the upload wizard, and the messaging, as the community continues to suggest improvements. ==== Why don't you use HotCat for categories? ==== : The latest version of HotCat is powerful and, as a consequence, was mostly built with experienced users in mind. We have included a basic version of HotCat to avoid confusing new users, but improving the category adder is definitely on the list of things we would like to do next. Another possibility would be to improve HotCat to have both powerful features ''and'' a user-friendly interface. Also, we're trying to make the upload wizard compatible with the HotCat gadget, so that users who have it enabled can use it transparently when uploading. ==== What are you doing about GLAMs? ==== : Galleries, libraries, archives and museums are important stakeholders for Wikimedia Commons. However, the tools they need to share their works are quite specific, and different from what "regular" users need. We would have loved to address the needs of this target audience as well, but it was not possible during the limited time we had. ==== Can you also add feature X or Y? ==== : The scope and resources of the grant were very limited; we had to prioritize the development of features that would have the most impact. We felt the uploading process was what needed improvement the most. However, we do agree many other improvements are needed to truly improve the user experience on Wikimedia Commons. While we don't necessarily have the resources to implement them ourselves, we wholeheartedly welcome volunteer developers who would like to help us, and we'll do our best to support them, for example by sharing our sketches & designs. == Didn't find your question? == : This Questions & Answers page was written based on the feedback provided over the last few months. If your question wasn't listed above, please leave your comment or question at [[:commons:Commons:usability issues and ideas|Commons:Usability issues and ideas]] and we'll do our best to answer it. [[Category:Multimedia usability]] dnvjw8j66k38ovf9me47sfolakbo8az 100 1397 8728 8725 2010-08-06T23:43:25Z Guillom 13 fix wikitext text/x-wiki We'll continue to post updates about the Upload wizard on the [[:commons:Commons:Village pump|Commons village pump]], the [https://lists.wikimedia.org/mailman/listinfo/commons-l Commons mailing list] and the [http://blog.wikimedia.org Wikimedia blogs]. Still, if you'd like to be notified on your talk page, you can add yourself below. ;Add your username and your project: * For example: guillom on fr.wikipedia.org * ... [[Category:Multimedia usability]] 8dewvdjw3m7hxrw3dsw1vctu7no13cw 6 1405 8804 2010-08-21T01:57:13Z Shijualex 2060 to explain transliteration issue wikitext text/x-wiki to explain transliteration issue 7qhydc6pbgyr11l5kbtva7sp1mq2ng1 6 1406 8805 2010-08-21T01:57:31Z Shijualex 2060 to explain transliteration issue wikitext text/x-wiki to explain transliteration issue 7qhydc6pbgyr11l5kbtva7sp1mq2ng1 6 1407 8833 8832 2010-08-28T13:55:20Z Shijualex 2060 uploaded a new version of &quot;[[File:Vector modified.png]]&quot;: Reverted to version as of 13:54, 28 August 2010 wikitext text/x-wiki to explain transliteration issue 7qhydc6pbgyr11l5kbtva7sp1mq2ng1 8 1409 8829 2010-08-28T01:15:59Z Kylu 101 http://meta.wikimedia.org/wiki/?diff=prev&oldid=2098047#Tr.E1.BA.A7n_Nguy.E1.BB.85n_Minh_Huy.40usabilitywiki wikitext text/x-wiki Cổng đa phương tiện 9ozv7akkwyp6me3ucv20qwxglr4ywm0 100 1424 8967 8902 2010-10-06T17:53:26Z Guillom 13 [[Category:Licensing tutorial]] wikitext text/x-wiki Below are the tentative main points to be covered by the [[Multimedia:Licensing tutorial|licensing tutorial]]. We have to focus on the main points and stay at a very high level. The order isn't final, nor is the content. Suggestions are welcome. # '''Default = can't do.''' By default, everything is copyrighted/protected/unfree and you can't upload it; #* no one can use it or do anything with it #* ex: random picture on the Internet # '''free work = explicit choice''' / release by the creator #* own work = your choice #* not own work = explicit release / permission # '''Derivative works''' #* of unfree works: stay unfree #* of free works: can stay free # '''Public domain''' (for most obvious cases, e.g. creator died more than 100 years ago) # '''Attribution''': The name of the creator stays perpetually attached to their work (if they choose so) # '''Freedoms''' associated with a free license #* freedom to use for any purpose #* freedom to modify and build on #* freedom to redistribute the work & modified work # '''Free licenses = good''' #* facilitate reuse #* encourage dissemination #* example: WP content # '''This is important.''' We take this stuff seriously, not like many other websites where it's often considered "optional" by users. [[Category:Licensing tutorial]] n7mzkoej7wp7hnsd6lm5byalidiyo69 14 1433 8965 2010-10-06T17:52:35Z Guillom 13 [[Category:Multimedia usability]] wikitext text/x-wiki [[Category:Multimedia usability]] ah4y36oij9fcyo95gwbbnkrumkixhzv 100 1434 8973 8972 2010-10-06T23:23:09Z Guillom 13 not a draft any more wikitext text/x-wiki {{internal}} == Goals for the meeting == * Review and agree on project information, time line, responsibilities, etc. (to be prepared by me in advance). * Review where and how the tutorial will be inserted into the interface. * Review the main topics to be covered by the tutorial: is it possible / desirable to include all of them? * Review and acknowledge general requirements (such as the need to address a globally diverse audience) * Answer other questions not listed here (to be prepared in advance by anyone who has questions). == Project information == === Steps === * Everyone: Hold kick-off meeting: agree on general overview, answer each other's questions * Michael: delivers Phase 1 draft designs (Oct. 13th) * Guillaume: shares Phase 1 designs with key stakeholders privately and seeks feedback, including from Jay & David (Oct. 18th) * Guillaume: selects a Phase 1 design (Oct. 18th) * Michael: delivers Phase 2 proposed set of pictures (Oct. 22nd) * Guillaume: shares Phase 2 designs with key stakeholders privately and seeks feedback, including from Jay & David (Oct. 26th) * Michael: delivers Phase 3 (final) set of pictures (Oct. 29th) * Meeting Nov. 1st / 2nd Check-in once a week by phone if required === Roles and Responsibilities === (by order of expected required involvement) {| class="wikitable" |- ! Name !! Role !! Responsible for |- | Guillaume Paumier || Product manager, WMF || Overall execution of the Licensing tutorial project |- | Michael Bartalos || Illustrator || Creation of the artwork |- | David Peters || Design director || Design advice and feedback throughout the project |- | Neil Kandalgaonkar || Software developer, WMF || Integration of the artwork in the interface |- | Alolita Sharma || Engineering programs manager, WMF || Oversight of the Multimedia usability project |- | Jay Walsh || Head of communications, WMF || Overall advice and feedback throughout the project |} == Software and artwork integration == * Including easy way to display a translation depending on the user's interface language (include language code in the filename?) == Topics == * [[Multimedia:Licensing tutorial/Main points]] == General requirements == ''For a longer version of this section, including rationales, see [[Multimedia:Licensing tutorial#Requirements]].'' The tutorial must be: * short * easily translatable ( [[:w:en:Free software Unicode fonts]] ) * from an international, cross-cultural standpoint * fun, enticing, not too boring * lightweight == Other questions == * colors? full color, monochrome etc? *: black and white until the final version http://en.wikipedia.org/wiki/Category:Open_source_typefaces [[Category:Licensing tutorial]] gntx7pagtwgtirkq7rpkmfzg59nbf5t 100 1438 9052 9051 2010-10-19T00:09:51Z Guillom 13 cont. wikitext text/x-wiki <div style="background: #F0F0F0; border: 1px solid #E9E9E9; margin: 0 0 1em 0; padding: 0.3em 1em; "> ;Main questions: * Does the tutorial convey all the important messages we want to fit in this limited space? * Does the character add value? * Are there mistakes? * Are the graphics appropriate? * Should the wording be changed? </div> * [http://usability.wikimedia.org/w/index.php?oldid=9046 Archive] == General comments == * People who commented generally liked the concepts and execution. * On the web, ALL CAPS are usually associated with SCREAMING and don't work as well as in print; they should be used sparingly. * The reading flow is a bit unclear (where to start, how to navigate (zigzag, per column; how will that work on a screen?)). Also, the phase 1 designs were a bit intimidating because they presented both the "good" and the "bad" from the beginning. * The OK/NOT OK or COOL/UNCOOL approach feels very rule-based. It was suggested to adopt a more engaging approach such as "please share" vs. "please don't share" or "we can't accept". == Character == * An overwhelming majority preferred the artwork with the character, because it gave it more personality and was easier to relate to. * However, many people also expressed they didn't really like the current character. It was referred to as "basketball head", "volleyball head" and "Pan-Am logo head". * The character's hat seemed to imply it was male, which some people didn't like. Some others proposed that the character be female. Possible options include a puzzle-piece character, a W character or a camera head character. The character should relate in some way to Wikimedia, Wikimedia Commons and/or its mission. == Content and wording == * Column 2, frame 4: "Photographs of art and statues" are "ok" to upload if they were taken by the uploader, and if the original art/statue etc. was in the public domain. For example, it's ok to upload pictures of the [[:File:Venus de Milo Louvre Ma399 n4.jpg|Venus de Milo]], but not pictures of Pablo Picasso's paintings. One way to improve this would be to say "photographs of recently created art, statues, buildings". * "Freely-licensed works" and "media licensed under "non commercial only" license" is too complicated. We can try to avoid this language by explaining the concept instead. * The header should be more inviting. It's better to avoid explicitly labeling the artwork as a "licensing tutorial". Some people suggested something like "Thank you for contributing to Wikimedia Commons", maybe accompanied with a drawing of people gathering images/musical notes/film. We may not have enough space for that, and it may be too complicated. * The double hyphens should be replaced with an em dash or spaced en dash. * In the list of covers, screenshots: add "promotional photos" * Remove the "legally / illegal" vocabulary * At the end of the page, we should add a footer that says "still unsure? Ask on the Help desk" and link to that page (either directly == Graphics == * The "public domain" metaphor isn't obvious. It was suggested to use an old painting such as a simplified Mona Lisa instead. [[Category:Licensing tutorial]] a2xy0tsdgcgl1e22zdy5k9y7h6z22kc 100 1439 9037 2010-10-15T17:13:30Z Guillom 13 dump wikitext text/x-wiki == Content and community growth == There has been much interest in the academic world about "Who writes Wikipedia?" and whether most of the content is contributed by an elite group of participants or by occasional visitors<ref name="Chi2007">''[http://asc-parc.blogspot.com/2007/05/long-tail-and-power-law-graphs-of-user.html Long tail of user participation in Wikipedia]''. E. H. Chi, N. Kittur, B. Pendleton, and B. Suh. May 2007.</ref> <ref name="Priedhorsky2007">''[http://dx.doi.org/10.1145/1316624.1316663 Creating, destroying, and restoring value in Wikipedia].'' R. Priedhorsky, J. Chen, S. T. K. Lam, K. Panciera, L. Terveen, and J. Riedl. In ''GROUP '07: Proceedings of the 2007 international ACM conference on Supporting group work'', pages 259-268, New York, NY, USA, 2007. ACM.</ref>. In particular, Roth studied the factors influencing wiki viability and noted a "dynamical intertwinement of population and content growth"<ref name="Roth2008">''[http://epubs.surrey.ac.uk/1565/1/fulltext.pdf Measuring wiki viability. An empirical assessment of the social dynamics of a large sample of wikis].'' C. Roth, D. Taraborelli, and N. Gilbert. In ''Proceedings of the 4th International Symposium on Wikis - WikiSym 2008'', New York, NY, USA, 2008. ACM.</ref>; they had earlier suggested that a wiki's success was linked to "a virtuous demographic path with content and contributors co-evolving"<ref name="Roth2007">''[http://dx.doi.org/10.1145/1296951.1296964 Viable wikis: struggle for life in the wikisphere].'' C. Roth. In ''WikiSym '07: Proceedings of the 2007 international symposium on Wikis'', pages 119-124, New York, NY, USA, 2007. ACM.</ref>. In a media repository like Wikimedia Commons, however, the focus of activity is on contributing new media files, rather than improving the existing ones. Once a file has been uploaded, improvements are mostly limited to metadata and peripheral information (description of the media file, copyright information, general topics, location, etc.); the files themselves are rarely edited. As a consequence, it is particularly interesting to study the dynamics of population & content in this special case. For this purpose, we studied the temporal evolution of the Files-to-active Participants ratio (F:P) and compared it to the Articles-to-active Participants (A:P) ratio on the English Wikipedia ({fig:content-vs-participants-chart}). <blockquote> <blockquote>[[Image:content-vs-participants-chart.pdf|frame|none|alt=image]] </blockquote> {\label{fig:content-vs-participants-chart}Temporal evolution of the ratio of media files on Wikimedia Commons per active participant ($\blacksquare$) and evolution of the ratio of articles on the English-language Wikipedia per active participant ($\blacktriangle$). } </blockquote> While the articles-to-participants ratio has remained stable on Wikipedia after the first few years of existence, the files-to-participants ratio has been steadily increasing since the creation of Wikimedia Commons. F:P has exceeded A:P since then and is now ten times higher than A:P. This result is not surprising when one considers the fundamental difference between a media repository, where files are accumulated, and a collaborative encyclopedia, where content is improved over time. However, it does demonstrate that Wikimedia Commons, despite being successful in terms of content, does not follow the usual model of "viable" or "successful" wikis, and requires new metrics and new models in order to assess its health. [[File:Wikimedia Commons - Evolution of content vs participants.svg|thumb|Isotype-style diagram showing the temporal evolution of the number of media files & participants on Wikimedia Commons.]] == Content inflow management == Because of the fundamental difference between a text-based encyclopedia and a media repository, a more interesting approach is to compare the capacity of the community of participants to "absorb" the inflow of new content contributed to the platform. Thus, we studied the temporal evolution of the ratio of persistent new media files uploaded each month, per very active participants on Wikimedia Commons ({fig:content-inflow-commons-enwp}). We compared it to the ratio of persistent new articles per very active participants on the English-language Wikipedia. "Persistent" means that we only count media files and articles that are not deleted during the patrolling process; the actual number of files uploaded and articles created is higher. We chose to consider only very active participants (more than 100 edits per month) since they are the more likely participants to engage into patrolling activities, such as checking newly uploaded files or newly created pages. <blockquote> <blockquote>[[Image:content-inflow-commons-enwp.pdf|frame|none|alt=image]] </blockquote> {\label{fig:content-inflow-commons-enwp}Temporal evolution of the ratio of persistent new media files on Wikimedia Commons per very active participant ($\blacksquare$) and evolution of the ratio of persistent new articles on the English-language Wikipedia per very active participant ($\blacktriangle$).} </blockquote> We found that the ratio of persistent new media files per very active participants has doubled since the creation of Wikimedia Commons and still continues to increase. This ratio is now more than ten times higher than the one for articles on the English-language Wikipedia. Our conclusion is that the content of Wikimedia Commons is growing much faster than the community of very active participants. Because of this imbalance between the growth of the content and the growth of the community, Wikimedia Commons faces a peculiar challenge. The MediaWiki software provides various maintenance and patrolling tools that allow participants to check newly contributed content; one of these tools is the "watchlist", a personal page listing the recent changes made to pages of interest selected by each participant. Watchlists are appropriate for text-based wikis like Wikipedia where participants want to check new edits to existing pages, rather than new pages. However, maintenance activities on Wikimedia Commons mainly consist of checking new files (especially their copyright status) and classifying them appropriately. For this purpose, the usefulness of the watchlist is limited. Some ad-hoc tools have been developed by experienced participants, but the software itself does not (yet) provide dedicated features to help the limited community of participants absorb the inflow of new media files. == Notes and references == <references /> [[Category:Multimedia usability - Research]] 9kwospvjr53i627yv7kkeq38lbiyaei 100 1443 9216 9192 2010-10-28T21:41:16Z Geni 2530 errors wikitext text/x-wiki <div style="background: #F0F0F0; border: 1px solid #E9E9E9; margin: 0 0 1em 0; padding: 0.3em 1em; "> ;Main questions: * Does the tutorial convey all the important messages we want to fit in this limited space? * Which character do you prefer? What would you change about it? * What would you change about the graphics? * What should be the exact wording of each box? * Do you agree with the existing comments below? </div> See also the [[Multimedia:Licensing tutorial/Phase 1 feedback|feedback on phase 1 designs]]. * [http://usability.wikimedia.org/w/index.php?oldid=9168 Archive] == General comments == * Remove the checkboxes (in the phase 1 designs, they made sense because the tutorial read as a checklist, but now it's more educational, so they're not really needed any more.) * Make the connections between the boxes more visible to suggest the reading flow more explicitly. * The Russian boxes give a bit of a busy feeling and constrain us more than necessary. Maybe remove some of them to lighten the document a bit, without altering the meaning (at least around the section headers) == Stop / ok icons == * Remove the icons distributed in all the boxes, and only use some of them in select places: ** The "OK" sign in the header of the "own work" and "exceptions" sections, aligned right ** The "STOP" sign in the header of the "not own work" section, aligned right * Keep them in the conclusion. == Character == * Almost everyone liked the puzzle-piece character, and preferred it over the other options. == Content, wording and graphics == === Own work === * "You may share works that you created entirely yourself.": replace by "You may upload works that you created entirely yourself." * "People that are public figures or are photographed at public events.": replace by "Public figures and people photographed in public places". * "Graphs, maps, diagrams and audio you created entirely yourself.": replace by "Original graphs, maps, diagrams and audio". === What you're committing to === * Have one or two of the "copies" look slightly different (to convey the message that the artwork may be altered). Maybe include, for one copy, a few golden coins, to convey the "it can be sold" message. * Add the little icons there too, on each copy (if we keep the icons elsewhere) * "Remember: By uploading your work to Wikimedia Commons, you grant others permission to copy, modify, re-use, or sell it without notifying you.": replace by "Remember: By sharing your work on Wikimedia Commons, you grant anyone permission to use, copy, modify and sell it without notifying you." === Not my own work === * "You may not share works that others created or that you created based on others' material or artwork": replace by "We can't accept works created or inspired by others" * Add a "By default, you can't upload someone else's work" box as the first one, illustrated by the Stop sign. * The two boxes in the middle are fine: they're good examples of common clear-cut cases of materials we can't accept at Commons. Remove the mention of "fair use" (it's US-specific) and replace it by "This includes:" after the "by default you can't" box. * The graphic for the "logo/CD/promotional photos" needs to be more meaningful. Perhaps replace it by the character holding CDs and DVDs? * If there's enough space, add another box of examples, namely: "Most pictures published on the Internet", with the character in front of a computer with the cross on the screen. * Remove the four corner boxes: ** "Any copyrighted material": Any material under a free license is technically still copyrighted, so this is misleading. ** "Photographs of art, statues, and buildings": Photographs of artwork may be allowed in certain countries ("freedom of panorama"), so it's better not to bring it up (we're addressing what is generally accepted with the ''public domain'' box in exceptions) ** "NC licenses": It's better to avoid mentioning "licenses" altogether, and the "by default you can't" should cover this. ** "unspecified usage rights": Sometimes PD works can fall into this category, so it's misleading. The "by default you can't" should cover the non-legit cases. === Exceptions === * "with two exceptions": replace with "with two main exceptions" (there are others) * "You may share someone else’s work if the author granted others permission to copy, to modify, to re-use, or to sell it.": replace with "You can upload someone else’s work if the author granted permission for anyone to use, copy, modify and sell it.". As for the graphic, reuse a graphic similar to that of the "What you're committing to" section, except in that case, the user should relate to character receiving the artwork, instead of sharing it (i.e. in this case, we would only show the hand of the left character sharing the work, we would still have the copies, but we would have a whole character getting one of the copies) * "You may share photographs of art, statues, and buildings if the works are over 150 years old.": replace with "You can upload your photographs of old art, statues, and buildings (usually over 150 years old).". === Conclusion === * "If your stuff is described by the stop sign, sorry, but we can’t accept it.": replace by "We can't accept works from others without their explicit permission". * "If your stuff is described by the OK ribbon, you’re clear to post!": replace by: "You can upload your original works". * "Thanks for your cooperation - we take these policies seriously!": replace by: "Thank you for cooperation; this is important." === Still unsure === * Keep the "confused character" from page 1. ==errors== "people that are public figures or are photographed at public events" thats not a copyright issue. "everyday objects not considered artwork." false. The legal standard is useful article. It's quite possible for an everyday object (whatever that means) to be protected by copyright. The stuff about buildings is not reflective of the actual situation in the real world. (buildings can be protected by copyright but an aweful lot are not).[[User:Geni|Geni]] 21:41, 28 October 2010 (UTC) [[Category:Licensing tutorial]] sc0kuqz6kxyzsgdymvqcahfx4xmac6l 8 1482 9378 9373 2014-09-10T12:06:49Z Billinghurst 954 locked -> closed, to match naming within http://noc.wikimedia.org/conf/highlight.php?file=closed.dblist wikitext text/x-wiki <div style="border:3px solid #000; padding:1em;">'''This wiki served as a knowledge collective and collaboration space for the [[Wikipedia Usability Initiative]] and the [[Multimedia Usability Project]]. It was discontinued and closed in January 2011, as both these grant-funded projects were over.''' (See also [[Main Page]].) </div> s6zn4bsy3vj8qqe042by5j5539kpt78 10 1767 10246 2015-08-03T23:39:44Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki @[[User:{{{1|Example}}}|{{{2|{{{1|Example}}}}}}]] ht62w5zp7ueoczj6k5jj4tnpk907kdj 14 1770 10251 2015-09-17T03:36:41Z Babel AutoCreate 2758 Automatically creating [[Project:Babel|Babel]] category page. wikitext text/x-wiki Users in this category indicate they have skill level N for language English. 6s3d2b0m3ma7ppvwlsdyjqmh2u52jk4 14 1771 10252 2015-09-17T03:36:42Z Babel AutoCreate 2758 Automatically creating [[Project:Babel|Babel]] category page. wikitext text/x-wiki Users in this category indicate they have skill level N for language French. 91m59mwrmaj0sq717de033rrhxt9s80 10 1772 10253 2015-10-02T20:15:09Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki This post by {{{author}}} was moved on {{{date}}}. You can find it at [[{{{title}}}]]. e5j16chw2130kmdotptl65jvxa6lw5w 10 1773 10254 2015-10-02T20:15:09Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki Previous page history was archived for backup purposes at <span class='flow-link-to-archive'>[[{{{archive}}}]]</span> on {{#time: Y-m-d|{{{date}}}}}. njhr9sbh7lx81p2xfwikn7amdd3n1zn 10 1774 10255 2015-10-02T20:15:09Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki This page is an archived LiquidThreads page. '''Do not edit the contents of this page'''. Please direct any additional comments to the [[{{{from}}}|current talk page]]. nigyidinm7czjt0s9dq851dwhckapia 10 1775 10256 2015-10-02T20:15:09Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki This revision was imported from LiquidThreads with a suppressed user. It has been reassigned to the current user. 1pswkbcu7hauadd98nklgf3pku080ee 10 1776 10257 2015-10-02T20:15:09Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki ''This post was posted by [[User:{{{authorUser}}}|{{{authorUser}}}]], but signed as [[User:{{{signatureUser}}}|{{{signatureUser}}}]].'' gr9xg2oo9p9alcaf8usi587bcmsi65s 10 1777 10258 2015-10-02T20:15:09Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki Previous discussion was archived at <span class='flow-link-to-archive'>[[{{{archive}}}]]</span> on {{#time: Y-m-d|{{{date}}}}}. ccusakfp9y2sl227h5sbt4ok1ptcsxi 10 1778 10259 2015-10-02T20:15:10Z Flow talk page manager 2757 /* Automatically created by Flow */ wikitext text/x-wiki This page is an archive. '''Do not edit the contents of this page'''. Please direct any additional comments to the [[{{{from|{{TALKSPACE}}:{{BASEPAGENAME}}}}}|current talk page]]. hd1xxik7k0u7gcb9oq9ddgh20zmhpy4