Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
N/A
Sitecore Experience Manager
Score 7.9 out of 10
N/A
Sitecore Experience Manager is an enterprise-grade CMS competing with Oracle WebCenter, IBM Web Content Manager and Adobe. It presents a fairly wide and comprehensive swath of inbuilt features. In Sitecore WCM editing takes place from within the page with its inline editor, allowing editors and authors to create display rules and content within the context of the page in an integrated process. It allows the creation of blogs, wikis, polls, integrates with social media, and is mobile…
Paligo is particularly well suited for developing similar document sets for multiple products or product lines. It is not a page layout application, so don't expect the same capabilities as popular applications for graphics-heavy documentation. With some up-front time developing good layouts, however, Paligo does manage to create very usable PDF output for customer-facing documents.
Great for companies that are looking to create customized, tailored content solutions and be willing to put in the hard work and effort to maximize the value out of the tool. If your company is just looking for very basic content management without all the bells and whistles, I'd recommend looking elsewhere for less [money].
The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.
Personalisation of advertising banners based upon knowledge of the customer, like location or previous searches enables us to target customers with products and offers that they are more likely to engage with, which has been done to good effect.
The use of Sitecore for content management enables the business and design team to perform changes to things, like images, content and page structure, which would otherwise have required a code release, which is costly in terms of man power.
The A/B testing in Sitecore is good because it allows us to statistically verify minor changes to the site - like advert changes or component ordering on the page - as to whether or not they positively impact conversion.
The amount of CSS/JS required to customize a site's appearance can be cumbersome
Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members
Sitecore is Customer Engagement Platform. It comes with lots of features (e.g. Authoring, Analytics, personalization, A/B Test, Webforms for marketers etc), But, most of them are not being used by many clients. If you are really looking for just CMS (only authoring and publishing), then I don't think Sitecore is a way to go.
You need to have a strong Sitecore certified developer base to manage the Sitecore platform (if you are using all features). It's the same case with others. But, finding a Sitecore certified (costs $$) developer is tough in the market. Now the market is growing (thanks to Sitecore promotional events) and Sitecore is gaining popularity, It may be easy to find such developers in the future. If you want to leverage most out of the Sitecore community you need to be a Sitecore certified developer.
Sitecore comes with lots of built-in features and marketplace components. I feel this puts in a little tricky situation. It gives an opportunity for a normal developer to use some of the free marketplace module, which may or may not be supported in a future version of Sitecore. which may put the entire platform in risk to upgrade to latest Sitecore version. You need to have a proper process to control and validate the marketplace components before using them.
Sitecore has proven that it can deliver on its promise of a robust, reliable enterprise CMS solution with plenty of features. Also, they keep updating it with more and better features. Now that we are highly trained on it we have started on getting the most out of it and we plan to keep doing more of that in the future.
Generally, I'm very happy with Paligo and the productivity gains that I get from using it. There are a few arbitrary limitations on structure, and when applying conditional formatting, that I don't really understand. Unlinking / editing reused text uses this broadly inscrutible colour-coding that I just hate. It would be nice to double-click a component, make edits, then respond to a popup asking if I want to confirm the edit for all linked content, or unlink this instance. Likewise converting from an informal topic insertion to duplicates of its raw contents.
With any platform that offers so much capability, usability will naturally be more challenging. Sitecore does an admirable job and made massive strides in version 8, but at some times offers too many ways to achieve the same task allows users to sometimes take a path less efficient than the preferred path.
All the support requests I've submitted have been resolved in one way or another. Sometimes it takes some back and forth, which is to be expected. This is where being on a different continent becomes a drawback. Since we became Enterprise users, we've also had an additional level of help and support from a dedicated account manager in the US, and the resolutions seem to come more quickly
Sitecore Support is very knowledgeable and helpful. We have raised a number of issues with them and they rarely fail to come up with an acceptable solution.
Sitecore captures and remembers every single interaction your customers and prospects have in any part of the system, allowing you to build comprehensive, ever-learning profiles of each individual. From email marketing, to social media, to online shopping, Sitecore remembers where each interaction left off so you can automatically continue the conversation. Sitecore helps you manage your content for each and every experience your customers enjoy. Customize what content you want and the system will take care of how it's displayed.
Make sure you work with a partner that can help you take advantage of the entire platform. Specifically we see a lot of customers not taking advantage of Sitecore DMS and thus missing a huge opportunity. Sitecore is a platform that is meant to be constantly optimized and improved upon.
We moved from Flare to Paligo. One of the main reasons was the fact that Paligo is a cloud product. Collaboration with anyone outside of our team was more difficult with Flare. Also, maintaining a server for Flare content was going to become an issue, and overall I felt the Flare desktop product was prone to errors and issues. The flexibility of assigning Paligo licenses was a huge factor, as was the stability of the cloud platform.
The decision to select Sitecore was not ultimately mine, but the fact that we were able to leverage in-house Microsoft .Net (C#) experience on a platform that had a library of extensions, but also allowed us to customize and keep private our confidential IP has been a big help. When you see a SharePoint site or a Drupal site you can usually tell "oh this is a MS SharePoint site", but with Sitecore the ability to customize and have different views even different components based on device type makes Sitecore a clear winner.
I am not involved in the financial decisions for my company regarding Paligo; the decision to migrate our content to this environment predates my hiring. However, I know that the migration effort from WordPress to Paligo was an initially heavy lift, but any content migration effort would be. I believe that ultimately, getting our content out of WordPress was a positive move, and I look forward to seeing what Paligo will help us accomplish in the future. Sorry, no hard numbers from me. :)
ROI depends so much on implementation. Its would be difficult to comment in a positive or negative regarding CMS product to direct ROI. A non-technical user would be surprised at what a basic installation of Sitecore looks like. "Hello World" comes to mind. With that in mind we can look at two things, Sitecore Support and Sitecore Partners.
Certified Internal Developers and Sitecore Support: This depends on the qualifications of your existing departments regarding implementing a enterprise CMS. No experience to some experience, this is a no brainer, rigorously vet top and middle partners and hire one to lead this effort. If your experienced still hire a partner and vet them but hire a middle to small partner and have them help, not lead.
"Sitecore Window": You could equate Sitecore in some implementation as throwing expensive parts at a car problem. If your business requirements and data consumption needs are not within this cost window then in the end on paper it will be difficult to see ROI or that there just wasn't a return. Then it will be time to look at other lower cost alternatives The initial cost is just the start. Over engineering and expensive horizontal integration partners can cost someone a promotion or job.
If your content workflows are complex, sites rendering data requirements are large and performance and scalability are paramount. Sitecore should be in your top 3.
