This page is a translated version of the page Beta Features and the translation is 18% complete.
For the extension, see: Extension:BetaFeatures.

Ciri Beta adalah satu cara untuk anda menguji ciri baru di Wikipedia atau tapak-tapak Wikimedia yang lain sebelum ia dilancarkan untuk semua orang. Pergi ke halaman keutamaan anda untuk mendayakan Ciri Beta; sila ingat bahawa ciri itu berfungsi berdasarkan pada setiap tapak.

Sila beritahu kami apa yang anda fikirkan mengenai program ini di halaman perbincangan ini.

Tujuan

Tujuan utama Ciri Beta adalah untuk membenarkan pereka dan jurutera Wikimedia (daripada Yayasan Wikimedia dan komuniti yang serupa) untuk melancarkan pembaikan teknikal di dalam persekitaran di mana sejumlah besar pengguna boleh menguji, memberi maklum balas dan menggunakan ciri tersebut di dunia nyata. Tujuan kedua Ciri Beta adalah untuk menyediakan laluan supaya alat-alat yang direka dengan baik dan kod komuniti yang lain dapat disepadukan ke dalam teras selepas diperiksa, diuji dan ditinjau oleh pihak Rekaan dan Kejuruteraan Wikimedia.

Kod untuk menyediakan ciri seperti ini merupakan suatu sambungan, Sambungan:BetaFeatures . Keutamaan Ciri Beta tersedia di tab Keutamaan, boleh dicapai melalui bar peribadi di atas laman untuk semua pengguna yang telah melog masuk.

Kefungsian

Buat masa ini, para pengguna boleh:

  • manually opt-in to individual features
  • automatically enroll in all additional features as they are subsequently released[issue 1]

To use either function, users should select the appropriate checkbox, then click “Simpan”, which will save their Beta Features preferences (like with other preferences). Every now and then new features are made available to users, as outlined at Beta Features/Roadmap .

Current Beta Features

Here are the current beta features which we are testing with this system:

These features are only available on some wikis:

These features are beta features on some wikis while enabled for everyone on all others:

We invite Wikimedia product teams and community volunteers who want to test out new features, or significant changes to existing features, to do so through this project.


Current features gallery

Deployed features

Other features

This list may document extensions or features that are obsolete or dormant, or are still in planning. Do not rely on the information here being up-to-date.


Creating your own

Do you want to create your own Beta Feature? Great! James is happy to help guide you.

First, you should check that your code meets the following basic requirements:

  • Not significantly degrade site performance;
  • Not noticeably degrade perceived performance of the site, or the user's system;
  • Not crash the user's browser;
  • Not cause data loss, or corruption;
  • Pass basic interoperability with other Beta Features features; and[issue 2]
  • Contribute positively to the user's experience of the site, and be additive in nature. E.g. Beta Features cannot be used to remove site features or functionality without adding features meant to replace what was removed.
  • You should expect to test your new feature on the WMF pre-deploy beta server for at least one week before deploying to production. This testing period is intended to catch any serious bugs before jeopardizing users on production.

If you're happy your code meets these requirements, you should write-up your proposal on the New Features proposal page. As part of creating the Beta Feature, you will be asked for some text copy and an image to represent your feature in the user interface; the Design and Product teams can help you with this.

Appearance

The appearance of the “Ciri beta” tab in Preferences is purposefully different, to both inspire interest and propose a departure from the standard layout and complexity of the existing user preferences.

Here is a screenshot of the “Ciri beta” preferences tab:

 
Screenshot of the “Ciri beta” preferences screen in Legasi Vektor (2010).

Known issues

  1. Note that this currently doesn't enroll users until they visit the Preferences page. (phab:T64815)
  2. This is not to say that interoperability is a blocker. Interoperability issues need to be surfaced, and blocker-ness will be determined on a case-by-case basis.

External links