Last week we had our first Hackathon at Colours, and it was a blast! There were a lot of great ideas, ranging from better time-tracking apps and a mobile poker app for Scrum poker sessions, to multiple content management add-ons and even an iBeacon utility that you can easily administer online. My submission came in at a third place (just behind the poker app and a standardized Drupal website with generation wizard) and, of course, was related to Sitecore. I worked out my concept of bringing component statistics (analytics data) directly to the content editor, showing the relevant data per component in the Page Editor.<\/p>\n
My idea basically came down to the following two questions: How often does a content editor really take action to change his content based on website statistics (most of the time only visible to the web analyst)? And wouldn’t it be great to get this information per component?<\/p>\n
After a fun night of coding, Laphroaig Cask Strength<\/a> whisky (oh that’s sooo good), lots of table soccer games of questionable quality, loud and good dubstep (but also some traditional Belarusian music from our Minsk-colleagues), pizza, fries and Red Bull, my concept started coming together. I started with a clean Sitecore installation of version 7.5, built a small website to demonstrate my concept (some renderings do work with live content, but not all of them) and then I’ve built the data collection events. Lastly, HighCharts<\/a> was used to display the results.<\/p>\n You can get a more in-depth view of my concept and implementation by watching the following screencast:<\/p>\n