User talk:Matt Heard/Archive 10

Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:

After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements

VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead (T90734).

Looking ahead

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.

Let's work together

Share your ideas and ask questions at mw:VisualEditor/Feedback.
Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
The design research team wants to see how real editors work. Please sign up for their research program.
File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

-Whatamidoing (WMF) (talk), 17:50, 3 April 2015 (UTC)[reply]

The Signpost: 08 April 2015

Op-ed: We are drowning in promotional artspam

News and notes: Advancement department to be created at the Foundation, milestone fixes

In the media: Wikipedia on 60 Minutes, Kickstarter, and in the classroom

Traffic report: Resurrection week

Featured content: Partisan arrangements, dodgy dollars, a mysterious union of strings, and a hole that became a monument

WikiProject report: WikiProject Christianity

Arbitration report: New Functionary appointments

Technology report: Bugs, Repairs, and Internal Operational News

The Signpost: 15 April 2015

News and notes: Erik Möller leaving Foundation; annual plan grants under community review

In the media: Saving Wikipedia; Internet regulation; Thoreau quote hoax

Blog: Single-User Login provides access to all wikis

Traffic report: Furious domination

Featured content: Au-delà de les Alpes, le chien lit de Sainte Bernard. Sous les pavés, les trimes d'argent! Mes enfants, suivez-moi!

WikiProject X Newsletter • Issue 3

Greetings! For this month's issue...

We have demos!

After a lengthy research and design process, we decided for WikiProject X to focus on two things:

A WikiProject workflow that focuses on action items: discussions you can participate in and tasks you can perform to improve the encyclopedia; and
An automatically updating WikiProject directory that gives you lists of users participating in the WikiProject and editing in that subject area.

We have a live demonstration of the new WikiProject workflow at WikiProject Women in Technology, a brand new WikiProject that was set up as an adjunct to a related edit-a-thon in Washington, DC. The goal is to surface action items for editors, and we intend on doing that through automatically updated working lists. We are looking into using SuggestBot to generate lists of outstanding tasks, and we are looking into additional options for automatic worklist generation. This takes the burden off of WikiProject editors to generate these worklists, though there is also a "requests" section for Wikipedians to make individual requests. (As of writing, these automated lists are not yet live, so you will see a blank space under "edit articles" on the demo WikiProject. Sorry about that!) I invite you to check out the WikiProject and leave feedback on WikiProject X's talk page.

Once the demo is sufficiently developed, we will be working on a limited deployment on our pilot WikiProjects. We have selected five for the first round of testing based on the highest potential for impact and will scale up from there.

While a re-designed WikiProject experience is much needed, that alone isn't enough. A WikiProject isn't any good if people have no way of discovering it. This is why we are also developing an automatically updated WikiProject directory. This directory will surface project-related metrics, including a count of active WikiProject participants and of active editors in that project's subject area. The purpose of these metrics is to highlight how active the WikiProject is at the given point of time, but also to highlight that project's potential for success. The directory is not yet live but there is a demonstration featuring a sampling of WikiProjects.

Each directory entry will link to a WikiProject description page which automatically list the active WikiProject participants and subject-area article editors. This allows Wikipedians to find each other based on the areas they are interested in, and this information can be used to revive a WikiProject, start a new one, or even for some other purpose. These description pages are not online yet, but they will use this template, if you want to get a feel of what they will look like.

We need volunteers!

WikiProject X is a huge undertaking, and we need volunteers to support our efforts, including testers and coders. Check out our volunteer portal and see what you can do to help us!

As an aside...

Wouldn't it be cool if lists of requested articles could not only be integrated directly with WikiProjects, but also shared between WikiProjects? Well, we got the crazy idea of having experimental software feature Flow deployed (on a totally experimental basis) on the new Article Request Workshop, which seeks to be a place where editors can "workshop" article ideas before they get created. It uses Flow because Flow allows, essentially, section-level categorization, and in the future will allow "sections" (known as "topics" within Flow) to be included across different pages. What this means is that you have a recommendation for a new article tagged by multiple WikiProjects, allowing for the recommendation to appear on lists for each WikiProject. This will facilitate inter-WikiProject collaboration and will help to reduce duplicated work. The Article Request Workshop is not entirely ready yet due to some bugs with Flow, but we hope to integrate it into our pilot WikiProjects at some point.

Harej (talk) 00:57, 19 April 2015 (UTC)[reply]