|Wikimedia Commons has media related to Wikimedia Beta Features.|
Beta Features are a way for you to test new features on Wikipedia and other Wikimedia sites before they are released for everyone. Go to your preferences to enable Beta Features for yourself; remember enabling features works on a per site basis.
Please let us know what you think of this program on this discussion page.
The primary purpose of Beta Features is to allow for Wikimedia designers and engineers (from the Wikimedia Foundation and community alike) to roll out technical improvements in an environment where large numbers of users can test, give feedback, and use these features in real-world settings. The secondary purpose of Beta Features is to provide a path so that helpful, well-designed gadgets and other community code can be integrated into core after vetting, testing, and reviewing by Wikimedia Design and Engineering.
The code to provide features like this is in an 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.
Lige nu, kan brugere:
- 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 “Gem”, 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.
Here are the current beta features which we are testing with this system:
- Indholdsoversættelse (lead: Amir Aharoni) – A tool to quickly translate pages into your language with side-by-side editor.
- New wikitext mode (lead: James Forrester) – Enable the new wikitext mode inside the visual editor. It has many of the tools present in the visual editor, uses a similar design, and allows better switching between the two.
- Tokolonners redigeringskonflikt (lead: Lea Voget) – Show the edit conflict view using a more advanced paragraph-based view.
- Visuelle forskelle (lead: Ed Sanders) – Enable the new visual mode on revision difference pages.
- New video player (lead: James Forrester) – Watch video files in a modern player with a cleaner look and mobile compatibility.
- Reference Previews (lead: Johanna Strodt) – Show a preview of a reference by hovering over its footnote marker.
These features are only available on some wikis:
- Visuel redigering (lead: Roan Kattouw) – Aktiver visuel redigering. Den vil ikke være tilgængelig for diskussionssider og for nogle andre navnerum.
- Flow on user talk (lead: Roan Kattouw) – Enables a new structured discussion system on your user talk page.
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.
|Wikimedia Commons has media related to Ikoner for betafunktioner.|
Nuværende galleri over funktioner
Show a preview of a reference by hovering over its footnote marker.
Allows for easy exporting of files to Wikimedia Commons.
New video player
Watch video files in a modern player with a cleaner look and mobile compatibility.
VisualEditor language tool
Tool for marking the language in which text is written.
Uses a new algorithm for search as you type, that is tolerant to small typos.
Other projects sidebar
Adds section to the sidebar for sister project links, based on Wikidata site links.
View and organize notifications more easily. Includes cross-wiki notifications, which lets you see messages from other wikis.
ORES is an AI-based tool that highlights probably damaging edits in recent changes and watchlist.
Enhances Special:Search through an advanced parameters form
Edit Review Improvements
Review edits on Recent Changes using new filters, user-defined highlighting and other improvements.
Give more attention to the mobile skin and use it as a vehicle for accelerating change in mobile and desktop.
Sider i nærheden
Se hvilke andre sider er i nærheden.
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.
The appearance of the “Betafunktioner” 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 “Betafunktioner” preferences tab:
- Note that this currently doesn't enroll users until they visit the Preferences page. (phab:T64815)
- 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.