There are many other JS libraries available, but jQuery at the moment dominates the field: according to an ongoing survey at, jQuery is currently in use on an astounding 74% of all websites, and on 97% of websites that use any JavaScript library. Since its release in 2006, it has become, to some extent, a standard on the web. JQuery is a third-party JavaScript library that simplifies a lot of typical JavaScript tasks considerably. MediaWiki also includes PHP functions that serve as a wrapper for displaying many of OOUI's utilities. Unlike other similar user-interface-oriented JS libraries, OOUI has excellent support for internationalization (translation into many languages, right-to-left display display, etc.) and accessibility (support for the visually impaired, etc.). It defines a variety of specific interface utilities, like autocompletion, datepickers, etc. OOUI (which to some extent stands for "OOjs User Interface") is the other big JS library developed at the Wikimedia Foundation. OOjs provides a framework for the rest of MediaWiki's JavaScript. In theory, it can be used outside of MediaWiki, though this doesn't seem to have happened yet. OOjs (which stands for the rather generic name "Object-Oriented JavaScript") is a JavaScript library developed at the Wikimedia Foundation for specific use in MediaWiki. MediaWiki at the moment contains four main JavaScript libraries: OOjs, OOUI, jQuery and jQuery UI. If you go with this approach, you would still most likely want to block non-logged-in users from being able to edit the wiki, but that's easy to accomplish (see here). The custom actions are usually still there, if users manually type in URLs that end with "action=history" and the like but the absence of links on the screen will mean that the vast majority of users will never know that there's a wiki behind the scenes, let alone see the history of page, the set of recent changes, etc.
MEDIAWIKI MOBILE SKIN
The idea is that users who can edit the wiki (of whom there will be relatively few), and who are logged in, will see the wiki with a normal skin while the majority of users/readers, who aren't logged in, will see the wiki with a custom skin that doesn't show the history and edit tabs, the standard sidebar, etc.: it's a lightweight method of making a regular-looking website with the editing convenience of a wiki. One interesting, unconventional usage of skins is as a way to turn a wiki into a more standard content-publishing system.
0 kommentar(er)
