Ticket #280 (new Bug)

Description (Last modified by matt)

It's hard to write a good developer documentation. Examples are easier to understand and to maintain. We will write a number of plugins, that each uses one feature of Piwik:

• ExampleDBAccess
• ExampleFeedburner
• ExampleWidget
• ExampleEditMenu

Then we would:

• build a wiki page listing all the Example plugins
• print their quick description
• link to their source code

Examples of other open source project plugin documentation

• writing a plugin http://codex.wordpress.org/Writing_a_Plugin
• plugin api http://codex.wordpress.org/Plugin_API
• mediawiki plugin hooks http://www.mediawiki.org/wiki/Manual:Hooks

Ideas of simple useful plugins

• "You have X websites and Y users registered in Piwik. You are using Piwik A.B version."
• "Featured user" that randomly picks a use case from our use case base.
• "Piwik has been downloaded N times."

Technical notes:

• content loaded from piwik.org via highly cached proxy pages
• if piwik.org is down, should not affect loading time of dashboard
• have one widget for general purpose content (Piwik has been downloaded X times)