Jump to content

การอ่าน/เว็บ/การปรับปรุงเดสก์ทอป

From mediawiki.org
This page is a translated version of the page Reading/Web/Desktop Improvements and the translation is 13% complete.
Outdated translations are marked like this.

เป็นเวลา 12 ปีแล้วที่สกิน Wikimedia เริ่มต้นในปัจจุบัน (Vector) ถูกปรับใช้ ในช่วงทศวรรษที่ผ่านมา อินเทอร์เฟซได้รับการปรับปรุงด้วย extensions, gadgets และ user scripts สิ่งเหล่านี้ส่วนใหญ่ไม่ได้มีการประสานกันทางแสดงผลภาพหรือข้ามวิกิ ในขณะเดียวกัน การออกแบบเว็บรวมถึงความคาดหวังของผู้อ่านและบรรณาธิการก็พัฒนาขึ้นเช่นกัน เราคิดว่าถึงเวลาแล้วที่จะนำแนวคิดเหล่านี้บางส่วนมาปรับใช้กับประสบการณ์ใช้งานเริ่มต้นของผู้ใช้ทั้งหมด บนวิกิทั้งหมด ด้วยวิธีที่เป็นระเบียบและสอดคล้องกัน

Between 2019 and 2023, we were building a new skin. เป้าหมายของเราคือการสร้างวิกิในโครงการวิกิมีเดียเป็นมิตรและเพิ่มเครื่องมือแก่ผู้ใช้ใหม่ รวมถึงเก็บเครื่องมือสำหรับผู้ใช้ที่มีอยู่แล้ว

In 2022, the new skin became ready to be the default. Since then, we are introducing it on more and more wikis. Ultimately, we need to have one skin as the default everywhere. This is because keeping two as the default indefinitely is impossible.

อัปเดต

มีวัตถุประสงค์อะไร?

ลองจินตนาการตู้เก็บเสื้อผ้า

ปัจจุบัน, อินเตอร์เฟสนี้

ยังไม่เป็นมาตรฐานที่คาดหวังไว้ยังมีความยุ่งเหยิงและยังไม่เป็นธรรมชาติยังไม่เน้นทางด้านสังคมและยังไม่สอดคล้องกับรุ่นอุปกรณ์เคลื่อนที่

  1. The desktop interface did not match the expectations created by the modern web platforms. It felt disorienting and disconnected. Navigation and interface links were organized haphazardly.
    • Readers were unable to understand the purpose, terminology, and concepts of available tools such as the main menu, user menu, and page tools.
    • Editors found the hierarchy of the navigation to be confusing for newcomers.
    • Editors and other contributors wanted easier access to tools they used frequently.
    • Editors expressed interest in having fewer, but more prominent, ways to begin contributing.
  2. There was clutter that distracted users from focusing on what they came for. It was challenging for readers to focus on the content. New editors were unable to use their intuition to perform simple tasks not related to reading.
    • Too much information density and navigational elements on the page made it difficult to focus on a particular reading or editing task.
    • Readers found it difficult to navigate the page and spent a lot of time scrolling.
    • Readers found it difficult to search for information that is relevant to them.
    • Multilingual readers were not aware of language switching functionality.
    • Readers wanted to have an easy way to view the table of contents throughout the page.
    • Character count per line was more than three times the recommended value.
  3. A very small percentage of readers understood how Wikimedia wikis functioned. Many readers were not aware that the content they were reading was written by volunteers and updated frequently, or that they could potentially contribute as well.
  4. The large difference in experiences among our desktop interface, apps, and the mobile web, made it difficult for readers to connect our products. There was a lack of unity in the concept of Wikimedia sites.

How we were making the changes

หลักการ

We were not touching the content.We did not change skins other than Vector.We did not remove any functionality.We did not make major changes in single steps.

  1. We work on the interface only. No work was done in terms of styling templates, the structure of page contents, map support, or cross-wiki templates.
  2. Skins other than Vector were out of the scope of our project. We have frozen Vector to Legacy Vector, and begun deploying our features as parts of the new default Vector.
  3. We were moving around the elements of the interface, but all navigational items and other functionality available previously by default remained.
  4. We took an evolutionary approach. We wanted the pilot wikis to continue feeling familiar to readers and editors. Each feature was discussed, developed, and deployed separately.

Process for developing the features

  1. 2019: Problem identification research with both readers and editors – We studied the way people used the site. We identified the largest usability issues as well as obstacles in becoming more engaged with reading or editing. We did this by interviewing readers and editors across multiple countries and locations. We also surveyed gadgets and user scripts. Some of them deserved to be surfaced and be a part of default experience. (See the links: Research and design: Phase 1, Research and design: Phase 2.)
  2. 2019–2022: Prototype development and testing – We built out the ideas for features and began showing prototypes. Each feature was tested with readers and editors through interviews and on-wiki prototype testing. We used Central Notice banners across multiple languages and Wikimedia projects. Each prototype was tested by approximately 200 editors on average. (Example)
  3. 2020–2023: Refining and building – We refined or changed the features based on the outcomes of the prototype testing. In some cases, we asked for additional opinions to ensure we were making the right decisions.
  4. 2020–2023: A/B testing and other quantitative testing on wikis – This was the "beta" phase:
    • We performed tests for whether the features worked as expected based on the previously defined criteria of success. We made "before and after" comparisons or performed A/B tests. As the latter, we gave a new feature to 50% of users and compared them to the other 50%. After two weeks we compared the results.
    • If we received negative results, we identified the reasons across different audiences and made changes to the feature. Then, we would test the feature again. In the case of significantly negative results, we rolled back our changes. (Example)
    • We tested these changes in collaboration with a diverse set of volunteering early adopter (pilot) wikis , both Wikipedias and sister projects.
    • We also monitor usage across all wikis, where many account holders have been already using the new skin.
  5. 2022 – onwards: Deployments on more and more wikis – The results of testing and subsequent analysis concluded that our changes result in improved usage of the skin, and save time previously spent in scrolling, searching, and navigating. We interpret this as an easier and more comfortable reading experience. There are no negative effects to pageviews, account creation, or edit rates. Knowing this, we continue to roll out the skin on more and more wikis.

คุณสมบัติอะไรบ้างที่จะเพิ่ม

แผนการพัฒนาและไทม์ไลน์

The skin is now ready to become the default on any wiki.

Year Month Deployments
พ.ศ. 2562 พฤษภาคม First team discussions
พ.ศ. 2563 กรกฎาคม/สิงหาคม The new logo , collapsible sidebar , and limited content width introduced on the first early adopter (pilot) wikis , including French Wikipedia
กันยายน The new search widget is introduced
พ.ศ. 2564 มิถุนายน The new language switching is introduced
กุมภาพันธ์ Deployments on more pilot wikis, including Bengali, Korean, and Portuguese Wikipedias
พ.ศ. 2565 สิงหาคม The new user menu is introduced
มกราคม The new sticky header is introduced
Deployments on more pilot wikis, including Indonesian, Thai, and Vietnamese Wikipedias
กุมภาพันธ์ The changes are separated out from the Vector legacy code to a new skin "Vector 2022"
พฤษภาคม The new table of contents is introduced
มิถุนายน The skin is introduced on the last pilot wikis, including Catalan and Japanese Wikipedias
The first visual refinements are introduced
ตุลาคม Deployments on the smallest Wikipedias
พฤศจิกายน The new full/limited-width toggle button is introduced
ธันวาคม Deployments on Arabic and Greek Wikipedias
พ.ศ. 2566 มกราคม Deployment on English Wikipedia
กุมภาพันธ์ The full/limited width preference becomes persistent for logged-out users
มีนาคม The new page tools menu is introduced
เมษายน Deployment on Polish Wikipedia
พฤษภาคม Deployment on Spanish Wikipedia
สิงหาคม Deployment on Chinese (zh) and several smaller Wikipedias
ตุลาคม Deployments on Swedish, Hungarian, Dutch, Hindi, Norwegian bokmål Wikipedias
Also on Meta-Wiki and most Wikibooks, Wikinews, Wikiquotes and Wikiversity wikis
พฤศจิกายน Deployments on most Wikivoyages and Wiktionaries
The last visual refinements (known as Zebra 9) are introduced
พ.ศ. 2567 มีนาคม Deployments on most Wikisources and Foundation internal wikis

เข้ามีส่วนร่วมและติดต่อ

  • สมัครจดหมายข่าว
  • Opt-in individually: in Preferences, check the option เวกเตอร์ (2565). You can also enable our changes using the Global preferences.
  • Promote: Inform your community. Share our updates and blog posts.
  • Report bugs: to report a bug, create a task in Phabricator and add #Desktop Improvements Vector 2022 project.
  • การแปล: ช่วยเหลือเราด้วยการแปลหน้าต่าง ๆ ที่เกี่ยวข้อง:
Priority translations 

TOP3

  1. การอ่าน/เว็บ/การปรับปรุงเดสก์ทอป
  2. Reading/Web/Desktop Improvements/Frequently asked questions
  3. การอ่าน/เว็บ/การปรับปรุงเดสก์ท็อป/คุณสมบัติ

Other priority translations

  1. Template:Reading/Web/Desktop Improvements/Talk page intro
  2. Template:Reading/Web/Desktop Improvements/Features/Navigation
  3. Template:Reading/Web/Desktop Improvements/Header
  4. Reading/Web/Desktop Improvements/Updates
  5. Reading/Web/Desktop Improvements/Repository#posts
  6. Template:Reading/Web/Desktop Improvements/Office hours announcement

Direct link to all translations