Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
$4,800
per year
Titan CMS
Score 8.0 out of 10
Mid-Size Companies (51-1,000 employees)
Titan CMS is a web content management system (CMS) used to build public websites, intranets, extranets and portals. Powered by Northwoods, it leverages industry standard MVC for .NET Framework and provides a content management workstation interface to produce performance-driven websites.
$9,500
one-time fee
Pricing
Paligo
Titan CMS
Editions & Modules
Professional
from $4800
per year
Business
Contact Sales
per year
Enterprise
Contact Sales
per year
Base License
$9,500
one-time fee
Professional License
Contact Sales for Details
one-time fee
Corporate License
Contact Sales for Details
one-time fee
Enterprise License
Contact Sales for Details
one-time fee
Offerings
Pricing Offerings
Paligo
Titan CMS
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
$5,000 null
Additional Details
—
—
More Pricing Information
Community Pulse
Paligo
Titan CMS
Features
Paligo
Titan CMS
Security
Comparison of Security features of Product A and Product B
Paligo
-
Ratings
Titan CMS
3.0
Ratings
91% below category average
Role-based user permissions
00 Ratings
3.00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Paligo
-
Ratings
Titan CMS
4.0
Ratings
62% below category average
API
00 Ratings
4.00 Ratings
Internationalization / multi-language
00 Ratings
4.00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Paligo
-
Ratings
Titan CMS
4.6
Ratings
51% below category average
WYSIWYG editor
00 Ratings
8.00 Ratings
Code quality / cleanliness
00 Ratings
3.00 Ratings
Admin section
00 Ratings
6.00 Ratings
Page templates
00 Ratings
2.00 Ratings
Library of website themes
00 Ratings
8.00 Ratings
Mobile optimization / responsive design
00 Ratings
2.00 Ratings
Publishing workflow
00 Ratings
3.00 Ratings
Form generator
00 Ratings
5.00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
Titan CMS is a good full featured CMS if users are fairly tech savvy. It is under active development and has added significant features through the years.
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.
It gets easier, after taking a couple starter courses and really digging into detail with what Titan could do, it became super user-friendly and I actually enjoyed learning new things about the product.
The support group for Titan was extremely helpful. Whenever I had a question or needed some assistance they were always ready and willing to go the extra mile to make sure everything was accounted for.
Titan made it super easy to be able to preview and save recent work before making it live on the website. This really helped in getting an idea of how to improve simple texts and pictures.
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
Titan requires some training and users should have fairly good technology skills. Our organization has moved toward more central editing of web content because distributed staff using Titan struggled too much and so it was easier to have more centralized editing than distributed editing. The problem is that administrative staff didn't have enough technology skills. Titan could improve by having two level of editors... full editors using Titian as it is now and then basic editors that would interact with a page similar to interacting with a Facebook page.
Can be slow at times when you want to quickly move between screens in Titan. This may be the result of our specific hardware that Titan is implemented on.
Sometimes need to edit HTML directly to fix font/formatting problems.
Wish CMS integrated Google Web Analytics to allow viewing of page analytics while editing.
Wish CMS provided help during a responsive design migration by inspecting HTML and highlighting elements (such as tables) that require modification.
Titan CMS had a great support system and they helped make my experience go smooth. They offer courses to help people get acquainted, offer support over the phone and are more than willing to make your experience a great one. Once I was familiar with Titan I always found myself wanting to learn more and do more to improve upon the website. Titan makes CMS fun and exciting!
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.
Everything we've needed to accomplish, Titan CMS has been able to accomplish. From multiple levels of user rights, document rights, tagging pages and documents to make filters do the work of content displayed on a page - it's all easy to set up too. Creating a content rich product detail page template and customizing a ecommerce cart to work for those using a dealer network - needing a request for quote, to go to dealers instead of a self checkout.
So far, support has been excellent. They reply very quickly and give in-depth replies. Solutions advisors and account managers have also been very responsive and clearly focused on creating the best experience for implementation. And that's only when the answers can't be found in excellent product documentation. The online training class and tutorials are also very good.
I understand that our Web Development Team is very busy, however, sometimes there is a delay in response and a followup email is needed to determine the progress of the issue/question
It was customized to include screen shots of our site and how users can access the content that only pertains to them as well as advanced training sessions for admin duties and everything that goes along with it. Training is in small groups and can be private (your company only) if you like too.
Talk to your project manager for Titan early on in development about minimalizing customizations. It seems obvious, but many times they do what you ask in the respect of "This is how we do it now, make that happen in Titan" vs. think of how Titan can deliver the same results within the confines of the base software. It's not a fault, just human nature.
Paligo gives you the benefits of a fully integrated XML content database, making the whole package much easier to setup and use than a system using Oxygen. It's much easier to set up and far less expensive than Adobe's XML offerings. The cost is comparable to MadCap, but all our content was already in Docbook, so the transition to Paligo was nearly seamless.
I am a super fan of WordPress and would have suggested having our website built within that platform in a heartbeat, however, I began my employment here after the website had already been built within Titan. Essentially, Titan was chosen as our CMS because we needed something that could work in relationship with our CRM, and the Web Development Team needed to be local (within a reasonable distance). Titan and WordPress are very similar in many different ways, and I think that at some point, Titan could be as "smooth" as WordPress, but there are still a few other weaknesses that it needs to overcome
Positive - has allowed us to create templates for integration documentation. this has greatly sped up our process for creating articles for each of our integrations, which we haven't had up to this point.
Positive - has created greater alignment between the self-service content team and the marketing team.
Positive - has introduced a review and feedback workflow for our content creation that was not available in ZenDesk. The feedback directly in the app allows me to pinpoint comments about text and other elements so my writers can address them directly and become better writers in the long term.
Negative - long ramp up time due to a completely different approach to creating content. My team was training in early August and we have not yet published our new help center (though, to be fair, it is a lot of content that had to be completely rewritten)
Positive - any UI updates only require updating a single image, which has saved us dozens of hours of updating already.
Positive ROI by allowing content contributors embedded within departments with the department domain knowledge to update the site directly. More efficient and less centralized spending.
Requirement for investment in training users of CMS cuts into ROI. Would recommend a two-step workflow where department content contributors enter information into CMS and then approval step is done by webmaster team to ensure content meets standard formatting guidelines. This workflow functionality exists in the Titan CMS.
Positive ROI experienced during projects such as moving to a responsive design because much of the content can migrate untouched. Also positive when updating graphics in template to give site new look.