Topic on Talk:Third-party MediaWiki users discussion

What would you like to see next on MediaWiki?

The purpose of this discussion is to identify the most desired features MediaWiki is missing. Please only suggest features that will be really useful to your work.

This post was posted by 78.90.26.139, but signed as Mitevam.

Easy: Proper WYSIWYG support . That's by far the most common complain. I've used FCKeditor, WYSIWYG extension, but none is supported by the upstream trunk, and have limited support. None support templates, though.

1. WYSIWYG
2. Integrated access control: ability to hide some pages from the groups of users
3. Wiki-markup editor for template gurus - with autocompletion, syntax highlight, template parameters suggestions: more like markup IDE.
4. MediaWiki Core API. Not the HTTP-API but the set of PHP classes in the core that are less likely to change in the next version. Mostly I want core developers to think about MediaWiki as framework with programming interfaces for extension developers. All the changes in those interfaces have to be calm, with slow deprecation. A role model for that is Python compiler.

User:Katkov_Yury, do you know about these discussions? API/REST_proposal/Kickoff_meeting_notes

Requests_for_comment/API_Future

Is this closer to what you are talking about - standardization and stability(and calm transition) between versions.

Also, I've seen this extension for access control.Is that not what you are looking for and how?

Interesting page but it's not what I mean. The API team is doing wonderful but it's all client API for guys from the outside. What I mean is the internal PHP-API for extension developers. It's more administrative than technical issue: you just have to say that this set of classes (e.g. Article, User, WebRequest) are not likely to change a lot in the following three MediaWiki versions, so all can rely on them.

1. A visual editor that functions brilliantly and won't break complex wiki pages.
2. An easy way to share wiki content on social media services.

I would like to see:

• built in support for Google Analytics
• built in support for XML Sitemaps without using command line
• built in support for Google Adsense in popular layout positions
• easy way of gracefully retiring old tags (e.g. Google Maps extension is no longer supported, replaced with Maps which has different tags)
• update to the documentation about creating a simple extension that is XSS safe

This post was posted by QuotesUK, but signed as Quotes.

I see that a WYSIWYG editor is the top wish on the list ( I love the idea too). As you might know, VisualEditor is currently being developed and tested. I would encourage you to actively participate in the process with feedback , ideas, and volunteer help. You can test it here. You have the chance to influence its shape at this stage.

You might also be interested to read this blog post about VisualEditor.

Again related to VisualEditor, there will be a Bug Day focused on testing it with non-latin characters on Jan 28 on IRC. Learn more here.

Quoting an email I received from Nicolas Nallet from http://semantiki.fr/ :

What feature I would like to improve or settle is :

• fine grained read access in the wiki.
• mobile version for website that turns with MediaWiki
• More modern skins included in MediaWiki
• The implementation of Semantic MediaWiki on mediawiki.org website in order to manage easily extensions pages

• +1 for skins. Ok, don't make skins yourself but make it possible to create new skins for us, developers in less time. It's so much easier to create skin for Joomla or Drupal, and the result if often looks elegant (from the program code point of view). Skinning is a problem and skinning is an obstacle for MediaWiki community to grow.
• +1 for SMW on MediaWiki.org. I don't know how you guys can manage so much data without SMW.

MW has built Extension:GoogleNewsSitemap, which I believe satisfies the Google Sitemap xml (NewsSiteMap being an extension of SiteMap) as well. It should not be difficult to modify this extension to be more general.

Hi Quotes,

Chris Steipp from WMF has expressed interest to learn more about your wish: "update to the documentation about creating a simple extension that is XSS safe". He is asking for more details like "is this for an extension with a special page vs parser functions"?

Are you on the mediawiki-l mailing list? Maybe you can reply there. Here is the thread.

Suggestion: formalize the recurrent suggestions at Mentorship programs/Possible projects and let's try to find/create a related enhancement request in bugzilla. Even f some (most?) of these projects may be too complex for an internship we can probably find ways to cut them in chunks. In the worst case, having these ideas on that page will make us remember about them every time a new program starts.

This post was posted by Qgil-WMF, but signed as Qgil.

That is a good idea. I will work on that. Thank you User:Qgil.