Reading/Web/Desktop Improvements/Repository/Wikimania Stockholm research report/ja

ウィキマニアで枠を作ってもらい、経験の長いコミュニティの皆さんと話ができました. 5日間の会期中、私たちが着手するデスクトップ版改善プロジェクトの計画を公表して、複数の設計案にいくつか貴重なご指定先を受けました. 調査の構成は利用者の面談調査、自由形式による提案と指摘集め、さらにプレゼンを行い、加えてテーマごとの意見交換セッションでした. 以下に利用者インタビューを機能ごとにまとめてご紹介します. 被験者はウィキメディアン8名です. この調査報告書をスライド集でご覧ください.

メインのナビゲーション / 折りたたみ式サイドバー


The sidebar contains a lot of useful tools for editors, however is seldom used by casual readers. Making the sidebar collapsible (collapsed by default for logged-out users, and expanded by default for logged-in users) provides a more focused reading experience. Link to prototype

フィードバックの概要:


 * There was general support for this idea. People agreed that this capability is useful and that a collapsed sidebar makes a lot of sense for readers.
 * The links in the sidebar are currently disorganized and many of them are rarely used by readers or editors, though that’s somewhat of a separate issue.
 * Tradeoff between a focused reading experience and the opportunity for people to explore areas they might not otherwise
 * Is the hamburger icon globally recognizable?
 * By showing fewer entry points for contribution, maybe the ones we do show (e.g. Edit, Talk, etc.) will get more engagement

Quick score: support (9 support, 3 neutral, 1 dislike)

Notes/responses to feedback: An additional idea we discussed, and heard support for, but is not part of the prototype is having the sections within the sidebar be collapsible as well:



For more information on this focus area see Research and design: Phase 2#Main sidebar navigation.

言語の切り替え


Currently the language links are located in the sidebar, often below the “fold” of the page. Moving language switching to a more prominent location could facilitate easier switching and a greater awareness of Wikipedia’s multilingual offerings. Link to prototype

フィードバックの概要:


 * There was general support for this idea. People agreed that the language switcher deserves a more prominent location, and liked the placement near the article header.
 * There were some concerns around the idea of collapsing languages (as opposed to displaying the full list).
 * Make sure to use the full language panel with search and settings. This ensures that when you have many languages it’s still a good experience.
 * Could we make it even easier to switch to the desired language? Use geolocation and try to predict?
 * Could we use a more obvious icon?

Quick score: support (9 support, 1 neutral, 2 dislike)

Notes/responses to feedback: The main takeaway from our conversations are that in the cases where people are likely to change languages a dropdown menu may not be sufficiently discoverable. It might therefore make sense to have two different treatments:

検索


Currently the search field is a relatively small element and is only accessible from the top of the page. Increasing the size and prominence of the search field, and making it always available regardless of scroll position would encourage greater exploration and learning. Link to prototype

フィードバックの概要:


 * There was general support for this idea. People liked search being more obvious and liked the fixed header that made it available from anywhere on the page.
 * Could we hide it while scrolling down the page and reveal it upon scrolling up (to preserve as much reading space as possible)?
 * What additional items might be valuable in a fixed header?
 * What will happen as a result of the logo getting smaller?
 * Include images and descriptions in the search results list

Quick score: support (10 support, 1 neutral, 1 dislike)

Notes/responses to feedback:

記事のナビゲーション / 目次


Many popular articles are quite long. How do users navigate within articles to find what they're looking for? Currently the table of contents is only accessible from the top of the page (below the lead section). Making it always available regardless of scroll position might allow people to more easily navigate within articles, helping them to find the information they are looking for more easily. Link to prototype

フィードバックの概要:


 * People mentioned that they don’t use the table of contents often, though they do jump between the top and bottom of the article often.
 * Table of contents is less useful for short articles
 * The placement in the prototype felt unnatural to people
 * People liked having a fixed article header, and wondered what other elements could be included for logged-in users, e.g. article tools (see Article tools section for further exploration of this)

Quick score: support/neutral (5 support, 4 neutral, 0 dislike)

Notes/responses to feedback: For both this prototype and the search prototype people were intrigued by the idea of a fixed/sticky header and what elements would be useful to have there. There could potentially be a fixed/sticky site header (search, user tools, etc.) as well an article header (article title, toc, page tools, etc.). It could also be possible to combine these into one header. Follow up sketches (more specifically just about article navigation / table of contents):

ユーザーツール


By consolidating the user tools in a single menu the interface becomes less cluttered and more welcoming to people who have just created an account for the first time. It also provides a more flexible foundation for introducing additional features in the future. Link to prototype

フィードバックの概要:


 * There was general support for this idea. People appreciated the cleaner interface.
 * Could it be configurable such that you could choose one or two items to expose as icons outside of the dropdown menu?
 * Note that several popular gadgets add links to this area (e.g. UTC Clock gadget)

Quick score: support (5 support, 1 neutral, 0 dislike)

Notes/responses to feedback: Anticipating the need some people will have to expose certain items outside of the menu it would be great if it was easy to specify certain pages and expose them via icons:

記事ツール


Currently some article tools are in the sidebar whereas others are in the article toolbar. By consolidating the tools in the article toolbar we can create a more intuitive page structure. Also by optionally collapsing them into a menu (at least for logged-out users) we can create a cleaner experience. Link to prototype

フィードバックの概要:


 * General agreement that consolidating page tools would be an improvement
 * Some editors use these items very often and expressed concern about the additional click required to access them
 * Note that several popular gadgets add links to this area (e.g. Twinkle)
 * A more descriptive name for the menu (e.g. Page tools) would be helpful
 * People would like to be able to access these tools regardless of scroll position on the page

Quick score: neutral (3 support, 5 neutral, 1 dislike)

Notes/responses to feedback: Out of all the features we discussed this one stands out in terms of the needs of editors/logged-in users being very different from the needs of readers/logged-in editors. We know from looking at the data that a very small percentage of logged-out users interact with page tools, however we heard that easy access is important for editors.

自由形式の提案と指摘


During the three days of the conference we also displayed a poster of a redesigned desktop interface in a main walkway, with the prompt “''Let’s improve desktop. Thoughts?''”. We placed post-its and markers on a shelf underneath the poster. This resulted in 77 comments (we cleared the post-its off periodically when the poster got full). While all of the feedback and ideas were helpful the ones shown below came up more than once (meaning either more than one person wrote it on a post-it, or people added “+1” to existing post-its).

Notes/responses to feedback:

発表と意見交換


プレゼンは会議最終日、「新規閲読者空間」で行いました. コミュニティの皆さんにプロジェクトの概要を公表し（目標と範囲や日程表など）、ラフスケッチやアイデアをお見せする機会でした. 反応は肯定的で注意点の指摘もあり、おおむね応援していただきました.

意見交換セッションでは質問やアイデアがたくさん出揃い、自由形式の提案と指摘の結果にも盛り込んであります. まとめるといくつかのテーマがあがりました.


 * 人によってニーズはさまざま. 閲読者 vs 編集者でも、編集者同士でもニーズは異なる.
 * インターフェースをもっとモジュール化して設定可能にしてほしい. 特に編集者にとって、既存のガジェットやユーザースクリプトの好き嫌いが分かれている点からも明白. インターフェースを自分好みにカスタマイズするには、これをどう形にするか？
 * 閲読者が使うには、あまりインターフェースに詰め込まないほうが良い. だんだんインターフェースがごちゃごちゃになったことは広く賛成意見が集まり、今のようにナビゲーションと chrome 重視ではなく、コンテンツに軸足を置いて改善するべき.