See https://www.mediawiki.org/wiki/Help:VisualEditor/VE_as_the_main_editor .
At the end of the day, when the visual editor is fully developed,
it is still not useful as it should be until the "community side" of the work, detailed at the page above, has started on each wiki.
Can we build a "hub" of tech-savvy and keen community members who could help their wikimedian fellows all over the world to get the same rewarding visual editor experience they have?
What we know:
*smaller communities have capacity problems;
*volunteers never spare themselves when they figure out what a problem is and what the steps are to fix it. "If you build it, they will come": if we give them good starting points, they'll build awesomeness on those.
At some point, I will no longer be involved in VisualEditor work. Before then, I must make sure communities have the "tools" they need. I feel that this task is strongly tied to https://meta.wikimedia.org/wiki/Technical_Collaboration/Strategy#How_we_succeed .
Phase 0: improving the current checklist page, and making room for "expert" names.
First phase is "just" about getting people to list themselves. It involves finding them with on-wiki and mailing lists communications. I'd like everyone to add themselves to every category that applies. It will start by the end of June.
Page created at https://www.mediawiki.org/wiki/Help:VisualEditor/Community_Taskforce .
The second phase is about checking with these people what worked for them. Did they use existing documentation, or are there gaps in it we need to take care of? Did they create additional documentation to help themselves and others? (If so, we'll want to list those resources.) Did they perhaps seek help from someone else as well? The existing checklist will be scrutinized at this point.
The third phase may be about actually covering gaps (especially documentation ones. I don't think we have learning patterns docs about VE, for example, and that's something we may consider creating).
The fourth phase should be about presenting new and/or revisited resources to communities which should benefit the most from all of this work (the ones without much capacity, which are those I hope to serve with this task).
The fifth phase will be about checking whether people find those resources easier to use now. It may still be that they don't manage to get much work done, but at least we need to make sure that there's an established path for them, that may be reused/adapted for other products as well.