One of the awesome selling points of Sitecore Experience Manager is the vast amount of data that can fairly easily be collected on site visitors. The information can be used to trigger engagement plans, site personalization, etc.…to help the visitor feel a connection to your organization. When giving a demo, I always get the most ooohs and ahhhs when showing of the Experience Analytics Dashboard and the Experience Profiles, but behind all that flash is some serious data complexity and planning that is required.
My first post in a series exploring Experience Analytics is ready for your exploration, http://www.paragon-inc.com/resources/blogs-posts/engagement-analytics-quickstart.
One click, two click, three click, where is that field? Once a day, I get so lost expanding and collapsing field sections when working in Sitecore’s Content Editor interface, that my poor mouse almost takes a unplanned trip across the office. As the industrious Sitecore developer I am, I decided enough was enough. My decision lead to the creation of Custom Content Editor Buttons.
There is nothing worse than getting half-way to three quarters of the way through a Sitecore upgrade, just to be hit in the face with a strange error related to Solr. In the recent months, my team and I have seen an increase interest in Sitecore upgrades involving Solr implementations. In my latest post Sitecore Upgrades Mixed with Solr, I review some of the hurdles we’ve faced to help you on your path.