![]() – that are only possible with JavaScript. It defines a large set of user interface widgets – comboboxes, tabs, etc. – a sister library to jQuery, though it has had quite a different “career trajectory”. jQuery has been included in MediaWiki since 2010. It offers a logical way to access and modify the different elements of the HTML (or DOM, if you prefer calling it that). This is a slight decline from its peak of 97% around 2020, but jQuery still dominates. – by far the most popular JS library in the world, currently used by 95% of all websites with a known JS library, according to the site. Let's take a look at some of the JavaScript libraries that MediaWiki makes use of, to understand both the current state and where things are headed: 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |