LightCMS, from NetSuite, was a cloud-based content management system for building websites and eCommerce storefronts. It is designed to be used by individuals, non-profits, and small to medium-sized businesses. The product has been discontinued.
N/A
Paligo
Score 9.9 out of 10
N/A
Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
LightCMS is perfect for 90% of websites out there. It has all the basic modules like calendars, photo galleries, news/blog, or forms building built in. Small businesses to mid-sized businesses are perfect for LightCMS. We use other solutions when the requierments for the website include a lot of third party integrations or custom modules. As a hosted CMS it has the same limitations as others with server-side development.
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.
LightCMS provides all the major functionality 90% of sites need. It keeps out of its own way by making these solutions intuitive and simple and not trying to solve every problem for everyone which would over-complicate the tool-set.
This is the easiest to use CMS we have ever seen. I tell my client's that if they can make a Facebook post, they can manage their website, and it's true. Their UI is so easy and keeps getting easier to use. Untrained users get it in minutes and are able to manage their sites without our help.
LightCMS's code is simple and light-weight. Sites are fast and the CMS doesnt get in the way of performance.
You can do almost anything you want (except server-side programming) with LightCMS. So, we can create any design we want and it works great with Light CMS's tokens and editable regions concept (which is also simple to implement.)
Constantly upgraded and fixed, the product is 1000x better after 10 years of working with it, but is still simple and not bloated.
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.
While keeping it simple is LightCMS's thing, some of the elements/modules could use deeper options or control for advanced users.
Some content, such as calendars, cannot have data exported/imported easily.
Support was amazing 10 years ago. We openly talked about how awesome they were... it isn't as good as it once was, but is still way above almost every support of other CMS systems we have used.
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
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.
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
We have looked at hundrends of CMS's and LightCMS is a perfect entry-level system for most of our small to mid sized clients. LightCMS's feature set is less complex than almost every other system and the actual interface is miles ahead of most other CMS systems. It's simply thought out better. It lacks sensibility and an API as well as other advanced features many more expensive or more DIY systems have, but the simplicity makes up for it.
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.
While I always think the price could be cheaper, LightCMS is incredibly inexpensive if you consider the costs of hosting, support, and upgrading is all included.
As part of their partner program, we are able to control client accounts from our master account, making moving between clients easier and supporting them faster which ultimately makes our labor costs better.
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. :)
