Manual:JS/API/UI Extension Developer Library

About this board

This is the storage place of a book (collection of pages). You can load it from here, generate a PDF, let a book printed, edit it or otherwise update its content. Be reminded that when overwriting this book storage page with an updated version of the book, the previously assigned categories are not automatically copied to the recent version: you need to manually copy the categories from the former version. (Problem has been filed as enhancement request)
JS/API/UI Extension Developer Library
This is a MediaWiki book, a collection of MediaWiki articles that can be easily saved, rendered electronically, and ordered as a printed book. For information and help on MediaWiki books in general, see Help:Books (general tips) and WikiProject Wikipedia-Books (questions and assistance).
[ [// PDF] ]  [ [// epub] ]  [ [// ODT] ]  [ [// ZIM] ][ [// Open in Book Creator] ]  [ [// Order Printed Book] ]
[ About ] [ FAQ ] [ Feedback ] [ Help ] [ WikiProject ] [ Recent Changes ]

The JS/API/UI Extension Developer Library (JEDL) is a collection of pages on the website which can help developers in regards to using JavaScript (JS) within MediaWiki, MediaWiki's Application Programming Interface (API) and MediaWiki's User Interface (UI).

We expect that this will be especially useful for gadget authors those people who extend Wikipedia and other MediaWiki sites primarily through Javascript.

JS/API/UI Extension Developer Resources

Migration guide for users
Default modules
Developing with ResourceLoader
Migration guide for extension developers
JavaScript Deprecations
List of JavaScript Deprecations
Version 1 Design Specification
Version 2 Design Specification
List of ResourceLoader-compatible extensions

Help desk

Previous page history was archived for backup purposes at Manual:JS/API/UI Extension Developer Library/LQT Archive 1 on 2015-07-10.

What else should we add?

MarkAHershberger (talkcontribs)

What else is needed here? What should we add?

Reply to "What else should we add?"

Best practice? Offer possibility of auto-reporting errors

MarkAHershberger (talkcontribs)

I think what User:Rillke has done here -- offering the user a way to automatically report errors -- should be considered a best practice and documented more thoroughly here.

Reply to "Best practice? Offer possibility of auto-reporting errors"
Waldyrious (talkcontribs)

I think this needs a small introductory text, perhaps defining the scope, target audience, etc. Right now it feels like merely a collection of related resources and doesn't make it clear what goal it aims to assist (maybe a few examples would help).

For instance, MAH called it "documentation for gadget authors" in the message he left me on my user page; that's a good start, I believe, but I guess it might be useful for other audiences and purposes as well.

Reply to "Intro?"
There are no older topics