Thanks for reading over and improving the project page. I'm curious though, you've segmented out a bit of the content under the heading "English Wikipedia". I was under the impression that while the Ambox template (and Lua module) originated at English Wikipedia, that they are in use across many projects. I don't want to give folks the wrong impression that this information only pertains to English Wikipedia. How can we make this better? Do you think maybe we shouldn't link to the English Wikipedia pages, but maybe something more movement-wide (like the Wikidata entry)? Thanks for your time and I'd love to hear your thoughts.
Thanks for taking a look at the Mobile page issues project
Hi Chris, I fixed various issues related to ambox support in hewiki, and while going over the documentation I found it is very oriented to English Wikipedia.
The main issues I find there - "Ambox" terminology isn't clear to someone who doesn't write in enwiki (AM is abbr), and the whole hierarchy of templates (messagebox=>ambox=>article for deletion) doesn't have to be the same in other wikis (the introduction and the screenshot is clear enough).
I think it would be ideal to document it from technical perspective - e.g not template Ambox but an element with CSS class ambox. Also I was about to open a phab ticket about it - if software assume there is a Lua module "Ambox", we should pack it nicely as part of Scribunto (or some other extension) to avoid each wiki copy&pasting module from enwiki. However after a 2nd thought I'm not sure about it (microformats of CSS class are also valid choice - but need to documented with the correct terminology).
A few questions for you
Hi there! Because you are a proud member of the community taskforce for the visual editor, I'm sending you this short questionnaire so that we can learn how to improve existing resources and about different ways to build and share community knowledge. Thanks for participating! I'll come back here to collect your answers on September 9th. I'll collate answers on the taskforce talk page. Talk to you soon!
PS: If for any reason you'd like to provide your answers privately, just send me an email instead.
- Was the existing documentation about how to adapt the visual editor to your context useful to you?
- Do you have ideas about how to improve or expand it? (Note it has been changed recently, here's what it looked like before.)
- What is your preferred format to learn about something or about how to get things done? Feel free to list tools or other resources, even if they aren't being used currently on our sites.
- What is the one thing related to adapting the visual editor which is not explained well anywhere and you're still struggling to learn more about?
- Did you create additional documentation/resources to help yourself and others? Like user guides, how-to/instruction pages, etc.? If so, please provide links.
- Did somebody else from WMF or your community assist you with the visual editor community work you did so far? Please list names and the ways they provided support (like, Alice sent me an email to explain how to do X). Please, add community members' names to the taskforce list if they are not there yet.
- I didn't know of this documentation, so it wasn't useful for me, but it seems to be nice idea.
- I think it is too long and as such not very accessible. I believe the audience for this page are mostly non English speakers so it would be nice to make it sentence-less page with pointers to more details
- MediaWiki documentation pages for extensions
- "adopt" = adopt wiki / customizations to make VE work in wiki or adopt=adopt user to VE? I will answer both:
- Users - There is a gap in the way newbie can adopt VE. For example as talk pages doesn't work with VE. Hence, newbies most learn both (simple) wikitext as well as VE for actual editing.
- Wikis - WMF cannot, and probably don't want to, take responsibility for developing any type of customization that specific wiki need. (and if it does, it usually end up badly as Extension:PageTriage which is by design works only for enwiki). Special, non built-in customization for VE, required for specific site can only be written as JS gadgets - I did try to improve this area (see 3), but I feel it is still partially missing. I hope this obstacle can be mitigated at least partially in T106996 and by additional examples of gadgets.
- VisualEditor/Gadgets - which I think is one of the more important stuff that is still partially missing (because there are not so many existing examples).
- VE team (and Mooeypoo) are very responsive and kindly assists me whenever I need any help
Thanks, and regards,