- Draft for the article / content collection in the phpMagazin -
Hey guys, we make a little content collection for the article in the phpMagazine. It has to be finished on the 9th of August(!) so we're a little pressed here.
The size of the article should be about 25.000 characters. That will be about 5 pages in the magazine!
Further infos:
Note: It's a magazine for professionals so we can get really geeky!
Main topics in the article should be:
- Piwik (oh wonder!) ;)
- Webanalytics in general
- Installation
- Plugin-Development
- Accessing / using the API
- high-traffic setup using lighttpd on port 81
- after 1.0: professional Usability-Analysis
- expressive screenshots
Details on the main topics:
Piwik:
- fundamental idea / behind piwik / Team / foundation of project, Matthieu
- (Matt: not necessary to talk about this) connection to phpMyVisites (?)
- open source
- call to contribute / note: we're talking to a well targeted audience here!
- translations of the software and website
- build up a usecase (?)
- connection with Zend_Framework
- tuning Piwik for high traffic (mySql-setting, Apache-setting for best performance / lighttpd Setup for tracking)
- future of piwik (more enterprise level analytics features (segmentation, custom reports), scalability)
- .
- - Links
Development:
- measuring performance increase / decrease (e.g. jmeter) in the future [tagged: interesting metrics]
Webanalytics in general:
- importance / chances / risks of webtracking / A/B testing / Campaings / E-Commerce-Tracking / etc.
- data policies (IP-Addresses, designated plugins)
- Main differences to Google-Analytics concerning the tracking data
Installation:
- see docs
- tipps / tricks / links for support on errors
- requirements (PDO, etc.)
- .
- .
- - Links
. .
Plugin-Development
- see exisiting docs
- tips / tricks / usecase
- short outline of build in plugins (plugins can: track data, create new APIs, add menu entries, add widgets
- .
- .
- - Links
- .
- .
Accessing / using the API
- see docs
- tips / tricks / usecase
- short outline of build in widgets
- "remote"-tracking http://piwik.org/docs/tracking-api/
- .
- .
- - Links
- http://dev.piwik.org/trac/wiki/API/Reference
- http://piwik.org/docs/analytics-api/
- .
- .
The chief editor Björn Schotte kindly asked, if we could reference the mobile client of piwik that is right now developed by the open source company "mayflower" since he is closely connected with them and open source software. I think this would be a good idea and shows performance and innovation in piwik. --> very soon released you can mention for sure.
Ideas?
Comment by SteveG:
What should this reference look like and how long should it be?
We could write a view lines about:
- small overview with screenshots & market links (qr-code for android)
- something about Titanium (what it is, how it works and why we used it)
- our coding structure - a small javascript mvc
- ...
By the way: Is the article in english or german?
