Reading/Web/Desktop Improvements/Features/Page tools/ja

デスクトップ改善プロジェクトの主な目標のひとつは、利用者がインターフェース内にあるすべてのリンクとツールを直感的に使いやすくすることです.

現在のところ、私たちのインターフェースはウェブサイトに関連するリンクとツール、そしてページ自体に関連するリンクとツールの間の区別をしていません. メインページ、おまかせ表示、最近の更新、は前者のグループです. リンク元、関連ページの更新状況、このページを引用、は後者のグループに属します. この混同が新規読者の混乱を招いています. 新規編集者もそれぞれのリンクが何をするものなのかよく知りません. これらのグループが混在することによって、ツールを自然に探索することが著しく難しくなっています.



背景と目標
以下のためにページツールを表示する方法を再検討したいと考えています：
 * 個別のページのためのツールとウェブサイト全体のためのツールを区別しやすくする
 * それぞれのリンクの目的が何なのか、リンクに触れることなく直感的に理解しやすくする
 * これらのツールへのアクセスを持続的に提供し続ける

目次の第3回試作品テストによって、私たちのツールの重要性と持続的なメニューの有意性が浮き彫りになりました. この機能を設計したとき、必要とする人が簡単にアクセスできることを確実にすることに焦点を当てました. 読む体験において読むことを妨げたり押しつけたりしないことも重要でした.



使用事例

 * 読者または編集者として、ページの構造をより良く理解できるようにページツールとグローバルツールを素早く区別したいです
 * 読者または編集者として、自分が必要とするツールを見つけるのに多くの時間を費やさないようにページツールとグローバルツールに素早くアクセスしたいです
 * 読者または編集者として、自分の体験が自分のニーズを満たすように、いつも見たいツールを選択できるようになりたいです

機能の説明と要件

 * 1) ページツールのみを含む新しいメニューが作成されます
 * 2) その新しいメニューはページツールとしてより直感的な場所に配置し、リンクの場所とリンクの目的を視覚的にリンクさせます
 * 3) グローバルツールまたはページツールを固定して、読むあるいは編集するニーズに適合させるオプションがあります
 * 4) グローバルツールおよびページツールのメニューは、ログイン利用者に対して既定で持続的に（固定して）利用可能です
 * 5) グローバルツールおよびページツールは、匿名利用者に対して既定で持続的に（固定して）利用可能ではありません

調査と設計


目次との関係
最も楽しみにしている変更のひとつは、目次をページの横に移動し、下にスクロールしても利用可能なように固定したことです. 調査とテストを通じて、この変更は人々にとって、ページに着いてすぐに概要がわかるようという利点があり、読む体験の間中より簡単にページを見て回る役に立つであろうということがわかりました.

大多数のフィードバックは肯定的でした. ほとんどのコミュニティのメンバーは新しい目次の場所と機能性を気に入り、全体的に変更を支持しています. ほとんどのインターフェースへの変更と同様に、目次の移動にはいくつかの課題がついてきます. The main challenge community members raised was: where should we put the sidebar menu, which was originally located in the space that we were moving the table of contents to? Below we explain our proposal for addressing this challenge, which was also be the subject of our following round of prototype testing.



私たちの短期的な解決策
We decided that as a short term solution, the entire sidebar would remain available in its current location. It would remain collapsible, and the state (i.e. open vs. collapsed) of the sidebar would continue to persist between pages. (So if you open it, it would stay open as you navigate around the site.) What was to be changed: when it was to be open, it would push the table of contents down the page. Here is a screen recording of how it would work:

We didn’t think this was the optimal solution. It was more like a quick fix that would allow us to release the table of contents and keep moving forward. And we understand how this might have felt like a step backwards to some, because after the change, the table of contents was further down the page than it had been previously.



私たちの長期的な解決策
A few things we learned from community feedback, and from data collection, are informing our proposal: Additionally, something that we’ve been trying to accomplish throughout this project is moving things into logical places. We think it makes sense for all of the page tools to be in one area, rather than the current situation where some of them are in the sidebar and others are in the toolbar above the content of the page.
 * 1) Most editors like the new location of the table of contents
 * 2) For some editors it is important to have page tools (e.g. What links here, Related changes, Wikidata item, etc.) available as soon as they land on a page
 * 3) Most of the global navigation items in the main menu (e.g. Current events, Contents, etc.) are used infrequently
 * 4) Some editors have large screens and would like the interface to make better use of the space on the far side of the page

There are two main parts of our proposal: Here is a visualization of those two parts:
 * 1) Splitting the sidebar into two menus: a main menu with global links, and an page tools menu with page-specific links
 * 2) Moving the page tools to the far side of the page, so that they are near the other page tools (History, Edit, Move, etc.)

ステップ1：ふたつのメニューに分ける



ステップ2：ページツールを移動する



更新されたインターフェースはこのようになるでしょう：



Here is a screen recordings showing some of the possible configurations of the updated interface:



注記
There are two additional changes included in the above proposal: 
 * 1) Moving the page title bar above the toolbar.
 * 2) * In general we see the title bar being useful to all users, whereas the toolbar is more relevant to experienced users and contributors. Therefore we think it makes sense to have the titlebar come first, and the toolbar below
 * 3) ** Specific example: the titlebar now has the language switcher in it, and we think language switching is more valuable to most people visiting the site than the items in the toolbar
 * 4) ** Possible future example: in the future we're hoping to add additional reader tools to the interface (such as Share, Font settings, etc.) and plan on putting them in the titlebar, next to the language switcher
 * 5) * From an information architecture standpoint the links and tools in the toolbar are related to the page you are on, so it makes sense to have the title above and the related links and tools below
 * 6) * From a readability standpoint it's nice to have the page title be the first thing you see
 * 7) * Our mobile skin, Minerva, shows the titlebar above the toolbar, and it's generally a best practice to be consistent when possible. Possible supporting evidence:
 * 8) ** Timeless and Winter both place the titlebar above the toolbar
 * 9) ** Google Docs places the page title above the toolbar
 * 10) Restyling the tabs and other elements on the page
 * 11) * This is an ongoing process. The styles included in the mockup above are not final, rather they are just stripped down versions to serve as placeholders while we continue to work on visual design stuff.

定性的テスト


編集者対象の試作品テスト
In December 2021, we ran prototype testing of our table of contents across 30 wikis. The results of this prototype testing were crucial to the development of the page tools menu. Please see the results of our ToC prototype testing and our ideas for next steps for details.

In April 2022 we tested a prototype where the page tools were separated from the main menu, and moved to the opposite side of the page. The prototype also placed the page title above the page toolbar.

フィードバックの要約：
 * We received feedback from 244 editors in over 15 different languages.
 * ✅ The majority of people support separating the page tools from the main menu, and moving them to the opposite side of the page
 * ✅ The majority of people support moving the page title above the page toolbar
 * ⚖️ The feedback was split pretty evenly between the two menus being open vs. closed by default
 * 😀 Many people mentioned how much they like having the table of contents on the side of the page, and available as they scroll down the page
 * The most detailed feedback was regarding the behavior for hiding and showing the main menu, table of contents, and tools menu. 主なポイントは：
 * When you hide a menu it should hide completely (without having to click a second time)
 * When you hide a menu it should be more obvious where it has gone
 * The hamburger menu icon should disappear when the main menu is moved to the sidebar
 * The labels for hiding/moving the menus should be better (or use icons instead)
 * The tools menu, if it has been moved to the sidebar, should remain visible as you scroll down the page
 * The tools menu, table of contents, and main menu should hide automatically when the screen gets narrow
 * You should be able to collapse the table of contents manually, at any screen size

We've attempted to address all of the points above in this updated prototype. Keep in mind that the prototype is not perfect. Hopefully it is sufficient to communicate the main ideas: Deutsch · English · Nederlands · Tiếng Việt · Español · Français · Italiano · Polski · Svenska · Pусский · Yкраїнська · فارسی · 中文 · 日本語

See also the updated prototype. 

ガジェットの互換性
ガジェットの互換性についての情報は、このPhabricatorチケットで入手可能です. 以下のガジェットはテストされており、問題なくページツールメニューで動作するはずです：


 * Twinkle (the TW menu should insert itself after the page tools menu)
 * MoreMenu (The "Page" menu is inserted before the Page Tools menu. The "User" menu, only visible on user pages, is also inserted before the Page Tools menu.)
 * ProseSize
 * RTRC
 * Add a toolbox link to reload the current page with the system message names exposed

We were able to maintain compatibility for a few reasons:


 * 1) The Page Tools menu is rendered server-side, which maintains the expected JS execution order (i.e. the expected HTML menu exists when the gadget JS executes).
 * 2) We maintain the same IDs that were previously used to target this menu by gadgets.
 * 3) When we move the menu, we maintain the JS behaviour and events that have already been bound to the HTML elements by gadgets.

We also tested the Page Tools persistence feature with gadgets and did not notice any loss of functionality. The only noticeable difference is that, when the menu is pinned by default, you can sometimes see the addition of new links after the page loads. This could potentially cause a layout-shift, but that would only be an issue if the Page Tools was pinned by default for anonymous users and a gadget that adds a link was also enabled for anonymous users (unlikely).