Posts

Showing posts from February, 2016

Sitecore Hackathon 2016

Image
After participating in the Sitecore Hackathon of 2015, we had really been looking forward to this year’s edition. And it turns out that this edition was again very valuable, an opportunity to work together closely, explore unexplored aspects of Sitecore and deliver another valuable building block to Sitecore. But let’s kick this post of by explaining what a Hackathon is all about. A Hackathon is a community driven event that aims at creating new functionalities around an existing concept or product.  As the event is participated voluntarily, no real product enhancements are developed to be incorporated into the base product. Often these Hackathon events are organized as small competitions to increase the gamification factor and add some healthy competition. A Hackathon mainly aims at developers although some front-end and analysis is often required to conceive and complete the project. A Hackathon usually has a timeframe of 24 hours, this allows for the team to prove their

Sitecore Hidden Gems - Updated: Admin Pages (based on Sitecore 8.1)

Image
About a year ago I wrote a blog post on the admin pages and some of the hidden functionalities with Sitecore. This post is meant to elaborate on that by showing the differences that have come up since then with the release of the Sitecore 8.1 version. You can read up on the previous post here: http://kverheire.blogspot.be/2014/12/sitecore-hidden-gems-admin-pages-based.html And I will not be repeating myself endlessly, so my goal is to list the differences in this post. I think a good excercise could be to start of in pretty much of the same structure and post : The List versus              When comparing these two we can see the following differences: ContentTestingUpgrade.aspx InstallLanguage.aspx kill.aspx * PathAnalyzer.aspx RebuildKeyBehaviorCache.aspx RedeployMarketingData.aspx UpdateSocialProfiles.aspx  The updated admin pages - what are the actual differences and funcionalities As my previous blog post already goes into enough detail on the other