The importance of good Sitecore implementation
Is your Sitecore Implementation failing you? There are a number of clues that’ll reveal a problem with your Sitecore Implementation. Here are five of the most common signs:
The first and most common indicator is the editor experience. Sitecore is a fast platform. An editor should be able to create pages and add content to them in seconds. An editor that has been through Sitecore training should easily find and reuse content. They should also be able to create different language versions of content items using Sitecore’s built-in languages. If something isn’t right with your site’s implementation it’s likely to be slowing down their progress. As editors use the Sitecore editor for much of their working week this could be could be costing valuable time.
A content editor using a solid Sitecore implementation should be able to create and manage their daily content from the page editor. From Sitecore 6.5 onwards, the page editor has been the corner stone of the Sitecore platform. It is a myth that the page editor doesn’t work out of the box. This should provide users with a quick and intuitive tool to manage content.
Sitecore Analytics provides valuable information on how a site used. Even if you only look at the high level reports, there’s a lot of knowledge to be gained. If users can’t view Sitecore analytical data it may be that the analytics database hasn’t been set up correctly.
Sitecore Experience Marketing (in Sitecore 8), more commonly known as DMS, is the engine that powers personalisation. Personalising content should be easy for an editor. You’re able to set what rule you want to apply and select a new data source. Once the conditions of the rule are met, a visitor will see the personalised content. If none of your widgets are data sourced then you won’t be able to use the rules engine to personalise content. This is a common trait of websites with poor Sitecore implementation.
One of the most common issues we find (and can easily fix) is non-page items within the content tree. Sitecore creates a unique URL for every item. Your content tree should only hold items that can be found via a URL. If there is a URL path, it should have presentation information. If it doesn’t, it shouldn’t be treated like a web page. You should expect to see clear definition between your site pages, your data source content and website configuration. If the difference is not clear. And non-page items are within your site’s page tree there may be something wrong with your implementation.
Sitecore is a powerful platform. There are a number of different ways to set up and build similar functionality within the platform. It all depends on customer requirements, timescale, budget and a partner’s experience.
At Kagool, we’re Sitecore experts. We make sure all of our clients get the best out of Sitecore. If you’ve noticed issues with your Sitecore Implementation get in touch with us. We offer a comprehensive Sitecore audit to help get you back on track.