Did you know that you can review your changes visually?
When you are finished editing the page, type your edit summary and then choose "Review your changes".
In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
Click the toggle button to switch between visual and wikitext diffs.
The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history.
You can read and help translate the user guide, which has more information about how to use the visual editor.
A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [1]
You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [3]
The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [4]
The Categories item has been moved to the top of the Page options menu (from clicking on the icon) for quicker access. [5] There is also now a "Templates used on this page" feature there. [6]
You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [7]
Tables can be set as collapsed or un-collapsed. [8]
The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [9]
A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [10]
There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K on a PC or Command+K on a Mac. [11]
Future changes
The VisualEditor team is working with the Community Tech team on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [12]
The kind of button used to Show preview, Show changes, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [13]
Hi. We're into the last five days of the Women in Red World Contest. There's a new bonus prize of $200 worth of books of your choice to win for creating the most new women biographies between 0:00 on the 26th and 23:59 on 30th November. If you've been contributing to the contest, thank you for your support, we've produced over 2000 articles. If you haven't contributed yet, we would appreciate you taking the time to add entries to our articles achievements list by the end of the month. Thank you, and if participating, good luck with the finale!
ArbCom 2017 election voter message
Hello, Hmich176. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Did you know that you can now use the visual diff tool on any page?
Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.
If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.
Click the toggle button to switch between visual and wikitext diffs.
In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence. An arrow indicates that the paragraph changed location.
You can read and help translate the user guide, which has more information about how to use the visual editor.
The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [15]
The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. This tool has been used at the English Wikipedia for a long time. It is very popular and useful to editors, although it can be tricky for admins to set up. Other wikis can have this service, too. Please read the instructions. You can ask the team to help you enable citoid at your wiki.
Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. This has already been enabled at the English Wikipedia. If you want columns for a long list of footnotes on this wiki, you can use either <references /> or the plain (no parameters) {{reflist}} template. If you edit a different wiki, you can request multi-column support for your wiki. [17]
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
I'm working on a study of political motivations and how they affect editing. I'd like to ask you to take a survey. The survey should take no more than 1-2 minutes. Your survey responses will be kept private. Our project is documented at https://meta.wikimedia.org/wiki/Research:Wikipedia_%2B_Politics.
I am asking you to participate in this study because you are a frequent editor of pages on Wikipedia that are of political interest. We would like to learn about your experiences in dealing with editors of different political orientations.
The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
Hello, Hmich176. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Progress of the project has been generally delayed since September due to development issues (more bitrot than expected, some of the code just being genuinely confusing, etc) and personal injury (I suffered a concussion in October and was out of commission for almost two months as a result).
I currently expect to be putting out a proper call for CollaborationKit pilots in January/February, with estimated deployment in February/March if things don't go horribly wrong (they will, though, don't worry). As a part of that, I will properly update the page and send out announcement and reach out to all projects already signed up as pilots for WikiProject X in general, at which point those (still) interested can volunteer specifically to test the CollaborationKit extension.
Wikipedia:WikiProject X/Pilots was originally created for the first WikiProject X prototype, and given this is where the project has since gone, it's only logical to continue to use it. While I haven't yet updated the page to properly reflect this:
If you want to add your project to this page now, feel free. Just bear in mind that more information what to actually expect will be added later/included in the announcement, because by then I will have a much better idea myself.
Until then, you can find me in my corner working on making the CollaborationKit code do what we want and not just what we told it, per the workboard.
In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply edit the submission and remove the {{db-afc}}, {{db-draft}}, or {{db-g13}} code.
If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.
Updates: I've been focusing largely on the development side of things, so we are a lot closer now to being ready to actually start discussing deploying it and testing it out here.
There's just a few things left that need to be resolved:
A bunch of language support issues in particular, plus some other release blockers, such as the fact that currently there's no good way to find any hubs people do create.
We also probably need some proper documentation and examples up to even reference if we want a meaningful discussion. We have the extension documentation and some test projects, but we probably need a bit more. Also I need to be able to even find the test projects! How can I possibly write reports about this stuff if I can't find any of it?!
Some other stuff that's happened in the meantime:
Midpoint report is out for this round of the project, if you want to read in too much detail about all the problems I've been running into.
WikiProject Molecular Biology have successfully set up using the old module system that CollaborationKit is intended to replace (eventually), and it even seems to work, so go them. Based on the issues they ran into, it looks like the members signup thing on that system has some of the same problems as we've been unable to resolve in CK, though, which is... interesting. (Need to change the content model to the right thing for the formwizard config to take. Ugh, content models.)
The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team has recently launched two new features to improve the mobile visual editor:
The purpose is to help contributors focus on their edits.
The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
The purpose is to smooth the transition between reading and editing.
Section editing and the new loading overlay are now available to everyone using the mobile visual editor.
New and active projects
This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.
Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how:📲Try Edit Cards.
Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.
Looking ahead
Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to them about how editing can be improved.
Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.
Learning more
The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.
The Hurricane Herald is the arbitrarily periodical newsletter of WikiProject Tropical Cyclones. The newsletter aims to provide in summary the recent activities and developments of the WikiProject, in addition to global tropical cyclone activity. The Hurricane Herald has been running since its first edition ran on June 4, 2006; it has been almost thirteen years since that time. If you wish to receive or discontinue subscription to this newsletter, please visit the mailing list. This issue of The Hurricane Herald covers all project related events from June 1–July 31, 2019. This edition's editor and author is ♫ Hurricanehink (talk) .
Please visit this page and bookmark any suggestions of interest to you. This will help improve the newsletter and other cyclone-related articles. Past editions can be viewed here.
Hurricane Barry was the wettest tropical storm on record in Arkansas, and one of only four hurricanes to strike Louisiana in July. Originating from a trough over the southeastern United States, Barry formed on July 11 off the southeast Louisiana coast. Despite wind shear and an asymmetrical structure, the storm intensified into a minimal hurricane before making landfall near Intracoastal City, Louisiana. Barry dropped heavy rainfall from the Gulf of Mexico to the Ohio Valley, peaking at 23.43 in (595 mm) near Ragley, Louisiana. The storm caused flooding rains, power outages, and one death due to rip currents. Damage totaled over US$500 million.
The Atlantic hurricane season, and the Central Pacific hurricane season, began on June 1. The 2019-20 tropical cyclone year in the Southern Hemisphere began on July 1 in the South-West Indian Ocean, Australian region, and South Pacific.
Since the last newsletter, 18 other systems have formed worldwide, in addition to Barry.
Western Pacific
In the Western Pacific, Tropical Storm Sepat in June passed near Japan and was classified as a subtropical storm by the JTWC. In early July, Tropical Storm Mun killed two people when it struck Vietnam. Tropical Storm Danas formed near the Philippines and moved northward, later crossing the Korean peninsula. Toward the end of July, Tropical Storm Nari moved across Japan as a tropical depression, and Tropical Storm Wipha struck southern China. There were also three tropical depressions, one of which the JTWC classified as a tropical storm.
Short-lived Tropical Depression Three formed near the Bahamas and dissipated east of Florida in late July
North Indian Ocean
Cyclone Vayu was a powerful cyclone that threatened western India, but stalled and weakened significantly before moving ashore. The storm killed eight people, and lashed western India with heavy rainfall and high tides.
South-West Indian Ocean
In late July, Zone of Disturbed Weather 01 lasted for a few days east of Madagascar in the southern hemisphere winter.
New WikiProject Members since the last newsletter in June/July 2019
More information can be found here. This list lists members who have joined/rejoined the WikiProject since the release of the last issue in May 2019. Sorted chronologically. Struckout users denote users who have left or have been banned.
To our new members: welcome to the project, and happy editing! Feel free to check the to-do list at the bottom right of the newsletter for things that you might want to work on. To our veteran members: thank you for your edits and your tireless contributions!
Current assessment table
Assessments valid as of this printing. Depending on when you may be viewing this newsletter, the table may be outdated. See here for the latest, most up to date statistics. As of this issue, there are 152 featured articles and 70 featured lists. There are 142 A-class articles, but that number is subject to change, depending if we mandate that all A-class articles have an A-class review first. There are 961 good articles, meaning it is possible we get to our 1000th GA by the end of the year. There are only 62 B-class articles, perhaps because because most articles of that quality already passed a GA review. There are 363 C-class articles, 717 start-class articles, and 141 stub-class articles, with 26 lists and 9 current articles. The number of lists may decrease further as the "Tropical cyclone X" articles continue to be reclassified as set index articles. These figures mean that more than half of the project is rated a GA or better - including the lists/current/future articles, there are 1283 articles that are below GA status, versus 1325 that are GA or better.
Reports, bulletins, and other products issued by Regional Specialized Meteorological Centers are the authoritative source on meteorological information pertaining to tropical cyclones in their respective basins. This includes both quantitative and qualitative information about a storm's characteristics, including intensities, durations, and locations. The most recent post-storm assessments take precedence over operational data. Thus, post-season revisions to a storm's "best track" file, new information presented in a tropical cyclone report, or official database adjustments made by the Atlantic hurricane reanalysis project, or other official reanalyses supersede operational information where they disagree. Data in operational RSMC products can still be used if later data does not dispute them. Information from other public agencies can also be used, but generally require in-text attribution. While the original best track data from meteorological agencies is a reliable source and can be referenced, readers often find difficulty interpreting them. Consider using IBTrACS, a more easily understandable track database, which is endorsed by the World Meteorological Organization (WMO), for this information. Because the Automated Tropical Cyclone Forecasting System (ATCF) used by the Joint Typhoon Warning Center and National Hurricane Center is liable to change frequently in realtime, they should not be used for currently active storms. Forecasts from these agencies and RSMCs should only be used to cite the forecasts themselves; in other words, they can only be used to describe what was expected to occur, and never to describe what did occur.
Maps and other graphics published by meteorological agencies may be used to describe events (see the associated essay). However, they should only be referenced if they are explicit in conveying the supported information and do not require any rigorous meteorological interpretation (such as satellite analysis or drawing conclusions over what the arrangement of meteorological features represents). In general, self-published sources should not be used as sources for present or historical storm intensities. However, information contained in articles from reliable sources or commentary from established tropical cyclone experts can be used as sources for information not covered by WMO-endorsed agencies. If such sources dispute WMO-endorsed meteorological data, commentary on the disputed information may be used, making sure to attribute claims and giving due weight.
Storm effects are typically referenced with a wide array of published sources. These may include news organizations, risk assessment organizations, non-governmental organizations (NGO), government agencies, and impact databases. So long as they are reliable sources, they can be used as references for tropical cyclone impacts. Note that figures from early impact reports, often disseminated by the first NGO situation reports and news reports, may quickly be outdated in light of newer information. When sourcing damage totals or casualty figures, use the most recent value from a reliable source, as these values tend to be more stable and use more up-to-date information. If such figures are disputed by other reliable sources, this should be noted in the article, making sure to attribute claims and giving due weight. Routine calculations of damage and casualty figures (for instance, adding casualties from different countries) are acceptable as long as they arise from reliable sources.
Latest WikiProject Alerts
The following are the latest article developments as updated by AAlertBot, as of the publishing of this issue. Due to the bot workings, some of these updates may seem out of place; nonetheless, they are included here.
The article for hurricane (tropical cyclone) was created on December 2, 2001. On October 3, 2002, User:Ed Poor created an article for Hurricane Lili while the storm was active and near peak intensity; since then, 163 other people have edited the article to help make it a . In March 2004, User:BigT27 created an article for the hyperactive 1995 Atlantic hurricane season, then the 3rd most-active Atlantic hurricane season on record. On August 14 of that year, an article was created for Hurricane Iniki, the first non-Atlantic storm, and on August 31, the 1900 Galveston hurricane became the first TC-related . On October 4, 2004, Cyclone Tracy became featured, which was the 2nd FA in the project. A week later, User:Golbez created the article for 2004 Pacific hurricane season, which was the first season article for the EPAC.
On August 26, 2005, User:CrazyC83 created an article for Hurricane Katrina after the legendary storm crossed over southern Florida. By two days later, there were 500 edits to the article, and the hurricane was threatening to hit New Orleans as a Category 4 or 5. We now know it was “only” a Category 3 at landfall. In the 14 years since Katrina, there have been 6,327 editors to the Hurricane Katrina article, along with 23 sub-articles. During the 2005 season, there were debates among editors whether lesser notable storms, like Hurricane Cindy (2005), should have articles. At one point in 2006, there were articles for every named storm during the 2005 AHS, but in the 13 years since then, articles for tropical storms Franklin, Harvey, and Lee, and Philippe were created and merged. As a way to coordinate edits among the tropical cyclone pages, User:Jdorje created Template:Hurricane on September 12, 2005. This is the same template that appears on the talk pages for every article in the WPTC. On October 5, Jdorje officially created WP:WPTC, the tropical cycloneWikiProject. That October, in quick succession, the Atlantic hurricane seasons reached back to the beginning of recordkeeping (before 1600s) due to a collaboration of several editors; User:RattleMan created the first season article for the North Indian Ocean; User:Miss Madeline successfully nominated List of California hurricanes for featured list; and Jdorje created a a standardized storm path template.
In 2006, a series of users improved articles worldwide to featured article status. Professional met David Roth joined the project, and in the same year, the NOAA and NHC copied some material from Wikipedia, including track maps, and the Tropical Cyclone Report for Tropical Storm Chris (2006). In June 2006, User:Nilfanion created the project assessment page, which documents the status of every article, organized by basin, the year, and storm shaded by the quality. On August 1, the chat room on IRC for the project was created, which allowed real-time communication among editors. There’s something special about conversing with fellow weather geeks during an epic storm, which seems to have become all the more common. On January 1, 2007, the number of good articles in the project reached 100. On January 29th, a collaboration of users made the List of retired Pacific hurricane names the first featured topic in the project. It was joined by the 2003 Atlantic hurricane season in March 2007.
In 2008, further collaborations helped make the article for tropical cyclone a featured article, one of 100 FA’s in the project. Notably among project members, Tropical Storm Erick (2007) became featured on December 14, 2008. The storm lasted for a short amount of time over open waters, and as such, it was the shortest featured article anywhere on Wikipedia. Users questioned whether the storm was notable enough to have such a detailed article, but the article described the storm in articulate detail. After an AFD and two featured article review (and a series of low-notability storms being merged), Erick was delisted as a featured article on March 2, 2013.
In the period from 2008 to 2013, users created task forces for various basins, articles for all of the seasons in the Atlantic and EPAC, and enough high-quality articles that more than half of all storm/season articles were good or featured articles. In January 2008, there were 1000 articles in the entire project. On January 1, 2014, User:Yellow Evan created Typhoon Nancy (1982), which was the 2000th article in the project. In October 2008, there were 100 FA’s in the project, which reached 200 on November 28, 2015, with Hurricane Fay (2014). By March 2016, every basin had at least 100 storm articles, multiple featured articles, and season articles of various quality.
Featured Content
This section lists content that have become featured, articles and lists, since the past newsletter in mid-April 2019. From June 1–July 31, 2019, one featured article and one featured list was promoted:
An awards program for the project began on May 31. It involves 25 levels that may be gained by earning points for completing various actions such as getting good or featured articles. Additional awards will be added in the future.
In June 2019, the most popular article in the project was Cyclone Fani, viewed 139,696 times during the month. The generic cyclone was 2nd most popular, with 91,890 views. In 3rd place was the 2019 Atlantic hurricane season with 90,741 views, followed by Hurricane Katrina with 78,591 views. Included in the top 20 were the 2019 season articles for EPAC, WPAC, and NIO, TFA Cyclone Raja, 2018 and 19 Atlantic hurricane seasons, hurricanes Michael, Harvey, Maria, and Sandy. In July 2019, Hurricane Barry (2019) was viewed 85,793 times, with a peak on the day after the storm moved ashore.
WPTC 15th Anniversary push: some goals for the 15th year of WPTC include the creation or improvement of many other articles listed in the first section on the WPTC talk page.
Project Goals & Progress
The following is the current progress on the three milestone goals set by the WikiProject as of this publishing. They can be found, updated, at the main WikiProject page.
The third grant-funded round of WikiProject X has been completed. Unfortunately, while this round has not resulted in a deployed product, I am not planning to resume working on the project for the foreseeable future. Please see the final report for more information.
What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!
Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team would value your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.
Talk Pages
The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.
The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.
Mobile visual editor
The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.
In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
New navigation: The buttons for moving forward and backward in the edit flow have changed.
Seamless switching: an improved workflow for switching between the visual and wikitext modes.
Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.
Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
Measuring the impact of Edit Cards: The Editing team hopes to share results in November. This study asks whether the project helped editors add links and citations. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.
The article will be discussed at Wikipedia:Articles for deletion/List of Dune Houses until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. Sandstein 20:58, 6 January 2020 (UTC)[reply]
The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
an easy way to mention another editor ("pinging"),
a rich-text visual editing option, and
other features identified through user testing or recommended by editors.
You may prevent the proposed deletion by removing the {{proposed deletion/dated files}} notice, but please explain why in your edit summary or on the file's talk page.
Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing @. You can test the new features on the Beta Cluster. Some other wikis will have a chance to try the Beta Feature in the coming months.
New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.
Seven years ago this week, the Editing team made the visual editor available by default to all logged-in editors using the desktop site at the English Wikipedia. Here's what happened since its introduction:
The 50 millionth edit using the visual editor on desktop was made this year. More than 10 million edits have been made here at the English Wikipedia.
More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
The proportion of all edits made using the visual editor has been increasing every year.
Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.
In 2019, 35% of the edits by newcomers, and half of their first edits, were made using the visual editor. This percentage has been increasing every year since the tool became available.
More than 300 editors used the Reply tool at these four Wikipedias. They posted more than 7,400 replies during the study period.
Of the people who posted a comment with the Reply tool, about 70% of them used the tool multiple times. About 60% of them used it on multiple days.
Comments from Wikipedia editors are positive. One said, أعتقد أن الأداة تقدم فائدة ملحوظة؛ فهي تختصر الوقت لتقديم رد بدلًا من التنقل بالفأرة إلى وصلة تعديل القسم أو الصفحة، التي تكون بعيدة عن التعليق الأخير في الغالب، ويصل المساهم لصندوق التعديل بسرعة باستخدام الأداة. ("I think the tool has a significant impact; it saves time to reply while the classic way is to move with a mouse to the Edit link to edit the section or the page which is generally far away from the comment. And the user reaches to the edit box so quickly to use the Reply tool.")[19]
The Editing team released the Reply tool as a Beta Feature at eight other Wikipedias in early August. Those Wikipedias are in the Chinese, Czech, Georgian, Serbian, Sorani Kurdish, Swedish, Catalan, and Korean languages. If you would like to use the Reply tool at your wiki, please tell User talk:Whatamidoing (WMF).
The Reply tool is still in active development. Per request from the Dutch Wikipedia and other editors, you will be able to customize the edit summary. (The default edit summary is "Reply".) A "ping" feature is available in the Reply tool's visual editing mode. This feature searches for usernames. Per request from the Arabic Wikipedia, each wiki will be able to set its own preferred symbol for pinging editors. Per request from editors at the Japanese and Hungarian Wikipedias, each wiki can define a preferred signature prefix in the page MediaWiki:Discussiontools-signature-prefix. For example, some languages omit spaces before signatures. Other communities want to add a dash or a non-breaking space.
New requirements for user signatures
The new requirements for custom user signatures began on 6 July 2020. If you try to create a custom signature that does not meet the requirements, you will get an error message.
Existing custom signatures that do not meet the new requirements will be unaffected temporarily. Eventually, all custom signatures will need to meet the new requirements. You can check your signature and see lists of active editors whose custom signatures need to be corrected. Volunteers have been contacting editors who need to change their custom signatures. If you need to change your custom signature, then please read the help page.
Next: New discussion tool
Next, the team will be working on a tool for quickly and easily starting a new discussion section to a talk page. To follow the development of this new tool, please put the New Discussion Tool project page on your watchlist.
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The Reply tool is available at most other Wikipedias.
The Reply tool has been deployed as an opt-out preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
It is also available as a Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following these simple instructions.
Research notes:
As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool. Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.[20]
The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.[21] Some of the remaining changes are automatic corrections for Special:LintErrors.
A large A/B test will start soon.[22] This is part of the process to offer the Reply tool to everyone. During this test, half of all editors at 24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in Special:Preferences.
During Talk pages consultation 2019, editors said that it should be easier to know about new activity in conversations they are interested in. The Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at mw:Talk:Talk pages project/Notifications.
Good Article Nomination Backlog Drive The March 2021 GAN Backlog Drive begins on March 1, and will continue until the end of the month. Please sign up to review articles and help reduce the backlog of nominations!
Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.
The key results were:
Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.
These results give the Editing team confidence that the tool is helpful.
Looking ahead
The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The new [subscribe] button notifies people when someone replies to their comments. It helps newcomers get answers to their questions. People reply sooner. You can read the report. The Editing team is turning this tool on for everyone. You will be able to turn it off in your preferences.
The discussion will take place at Wikipedia:Articles for deletion/Toboggan (Hersheypark) until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The Editing team is beginning a project to help new editors of Wikipedia. It will help people identify some problems before they click "Publish changes". The first tool will encourage people to add references when they add new content. Please watch that page for more information. You can join a conference call on 3 March 2023 to learn more.
Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
There is an ongoing discussion taking place at the following articles, regarding whether the current redirects should be removed, which may be of interest to this user:
Hello! Voting in the 2024 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 2 December 2024. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.