Manual: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). | ||||||||
| [ Download PDF ] [ Download epub ] [ Download ODT ] [ Download ZIM ] | |||||||||
| [ About ] [ FAQ ] [ Feedback ] [ Help ] [ WikiProject ] [ Recent Changes ] | |||||||||
The JS/API/UI Extension Developer Library (JEDL) is a collection of pages on the MediaWiki.org 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 [edit]
- API
- ResourceLoader
- Origins
- Requirements
- Migration guide for users
- Default modules
- Developing with ResourceLoader
- Migration guide for extension developers
- JavaScript Deprecations
- List of JavaScript Deprecations
- Vocabulary
- Version 1 Design Specification
- Version 2 Design Specification
- List of ResourceLoader-compatible extensions
- GlobalFunctions.php
- CSS
Help desk [edit]
- [History↑]
Contents
| Thread title | Replies | Last modified |
|---|---|---|
| Best practice? Offer possibility of auto-reporting errors | 3 | 03:07, 20 March 2012 |
| Intro? | 3 | 14:22, 19 March 2012 |
| What else should we add? | 2 | 17:51, 9 March 2012 |
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.
User:Rillke also pointed me to w:de:Wikipedia:Technik/Skin/JS which has lots of helpful pointers.
And here is a request to have some sort of error reporting added to RL core.
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.
Thanks for pointing this out!
I appreciate it. I've added a little bit more about the intended audience.