ResourceLoader/Migration guide (users)/Tutorial

Why adapt a Gadget to use ResourceLoader?

 * Please add content about ResourceLoader and it's purpose (which can help users today).

Context:
 * As of Gadgets 2.0 (which is currently still in development) gadgets are required to use ResourceLoader. The raw loading mechanism will no longer be supported.

Rough points:
 * @todo: See ResourceLoader for points on what ResourceLoader is and why it is going to make your gadgets more awesome. That article has recently been updated wich lots of useful information
 * The current version of the Gadgets extension already supports using ResourceLoader (instead of the legacy loader). So this can be done *today* and will make your gadget faster and easier to manage right away.
 * Gadgets 2.0 (coming soon) will bring even more of ResourceLoader's features to Gadgets (see RL2)

Hands-on migration workshop (30 min. demo)
Below, please list any Gadget you'd like to work on migrating during the tutorial. Show us the gadget before the Hackathon will allow better feedback for you.

Gadgets to be used in the demo

 * See also Berlin Hackathon 2012



Gadgets 2.0: What to expect for 2012 and beyond
This will be a 15 min demo of the RL2 prototype cluster featuring Gadgets 2.0. And discussion of the implementation timeline. Collect feedback about how the community is responding/beginning to support the migration... or if/how they would like to the plan changed.

The framework

 * @todo: Why and how Gadgets 2.0

Screenshots and demo
How we plan for this to work.
 * workflow
 * use cases
 * how it will affect people

Feedback and discussion

 * Collect participants' ideas about the documentation overhaul
 * Reminder to document your Gadgets