Beta Features/pt-br



Recursos Beta são novos recursos para você experimentar na Wikipédia e em outros sites da Wikimedia antes de serem lançados para todos. Visite suas preferências para ativar os recursos Beta; lembre-se que a ativação dos recursos só se aplica ao respectivo site.

Por favor, compartilhe suas ideias conosco na página de discussão (em inglês).

Propósito
O propósito principal dos recursos Beta é permitir que designers e engenheiros da Wikimedia (tanto da Fundação quanto da comunidade) possam implementar melhorias técnicas num ambiente onde um número maior de usuários possam testar, comentar e usar os recursos num cenário real. Outro propósito importante dos recursos Beta é o fornecimento de um caminho para que gadgets e outros códigos úteis e bem elaborados possam ser integrados ao núcleo após exames, testes e revisões efetuados pelas equipes de Design e Engenharia da Wikimedia.

The code to provide features like this is in an extension, Extension:BetaFeatures. Beta Features' preferences are available in a Preferences tab, accessible via the personal bar at the top of the page for all logged-in users.

Funcionalidade
Right now, users can:


 * manually opt-in to individual features
 * automatically enroll in all additional features as they are subsequently released

To use either function, users should select the appropriate checkbox, then click 'Save', 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:


 * Compact language links (lead: Pau Giner) — show a shorter version of the language list, with just the languages that are more relevant to you.
 * Hovercards (lead: Jon Katz) — give readers a short summary of an article whenever they hover over a link to it.
 * Flow on user talk (lead: Roan Kattouw) — Enables a new structured discussion system on your user talk page.
 * Read more (lead: Jon Katz) — Suggests related topics at the bottom of a page.
 * Content translation (lead: Amir Aharoni) — A tool to quickly translate pages into your language with side-by-side editor.
 * ORES (lead: Amir Sarabadani) — ORES is an AI-based tool that highlights probably damaging edits in recent changes and watchlist.
 * RevisionSlider (lead: Lea Voget) — The RevisionSlider extension adds a slider interface to the diff view, so that you can easily move between revisions.
 * Special:MyLanguage/2017 wikitext editor (lead: James Forrester) —
 * Special:Mylanguage/Extension:TwoColConflict (lead: Lea Voget) —

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.

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
 * 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 Beta Features 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 Beta Features preferences tab: