Benjamin's diverse experience in web development has been a primary factor in Roundedcube's growth and success since he joined the team in 2005. Benjamin has ten years of experience in the Web industry and had created his own IT start-up prior to joining Roundedcube.

As Vice President of Technology, Benjamin manages our team of project management development and also helps guide Roundedcube's endeavors into new technology research and development. He has been on the forefront of emerging technologies such as AJAX, XAML and has expert knowledge of web application architecture and established technologies such as ASP.NET, web services, Microsoft SharePoint, various WCM systems and integrations.

Ben is a Sitecore Certified .NET Developer and a Sitecore Certified Marketer in Sitecore DMS 2.0.

Sitecore Engagement Analytics Reports is divided into three areas: Sales, Site Health, and Recent Activity. This post we will focus on the Site Health area of Engagement Analytics. The goal of this post is to understand how to use these reports practically and how marketers can depend on these reports to identify specific pitfalls within their audience’s experience. If you are currently in the developing process of your Sitecore solution, the development team should keep these reports in mind to ensure that marketers can start leveraging these reports to their maximum to identify potential problem areas directly after the launch of the site.

As more web developers come into the Sitecore community, I have seen a conceptualization gap from a .NET developer who is not use to building websites within a CMS such as Sitecore. The realization that the web solution of a CMS is not the same as building an application from the ground up takes a couple of failed implementation to convince.

As the number of Sitecore 6.5 implementations ramp up and we transition more users into the use of Page Editor, we've recently uncovered a problem with the default handling of how a data source is saved that can cause alot of problems for content authors if not addressed.

Let me preface this post by saying that Roundedcube has a lot of Sitecore CMS implementations under our belt (we've actually lost count I think), but in the last year and a half we've been involved with a couple Sitecore Foundry implementations. We quickly realized that while the two products share a common foundation, developing a solution with Sitecore Foundry is a different beast than with Sitecore CMS. My hope is to share some of the most significant differences we've encountered to help you overcome the same issues in your solution development.

Benjamin Vidal

Chief Technology Officer

Benjamin's diverse experience in web development has been a primary factor in Roundedcube's growth and success since he joined the team in 2005. Benjamin has ten years of experience in the Web industry and had created his own IT start-up prior to joining Roundedcube.

As Vice President of Technology, Benjamin manages our team of project management development and also helps guide Roundedcube's endeavors into new technology research and development. He has been on the forefront of emerging technologies such as AJAX, XAML and has expert knowledge of web application architecture and established technologies such as ASP.NET, web services, Microsoft SharePoint, various WCM systems and integrations.

Ben is a Sitecore Certified .NET Developer and a Sitecore Certified Marketer in Sitecore DMS 2.0.