Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Evoq Content
Score 8.7 out of 10
N/A
Evoq Content is a content management system within the Evoq business suite. Evoq Content is extensible with many modules that add caching, advanced content approval workflow, granular permissions, document management, mobile accessibility of content, web farm support, and an ecommerce engine.
N/A
Paligo
Score 9.1 out of 10
N/A
Paligo is a component content management system (CCMS) that helps teams manage complex technical documentation through structured authoring, content reuse, and controlled publishing.
Drupal has the best community and support system of any other CMS that I have used. Drupal is more flexible from A-Z including installation, building and customizing the CMS. The only other (free) CMS that is close, in my opinion, is Dot Net Nuke.
Drupal is a highly expensive tool and is not offering anything extraordinary at a high price. If I keep its pricing in account then there should be some extraordinary features but unfortunately, there isn’t anything special about it; rather it was slow in its working. All these …
A few products stack up against DNN like Wordpress, Drupal, SharePoint. Drupal, Wordpress, Joomla all are php based systems, while DNN, SharePoint were all .NET systems which is what I preferred. Comparing SharePoint to DNN, first would be the cost of SharePoint server along …
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
If you just need to implement a website that is dynamic but not real big in Data Processing almost anyone can do so with very limited knowledge as long as you know how to use a Word Processor and your Browser. If you don't have experience with setting up a Server to run a website there are Companies like PowerDNN, Rackspace and WinHost that can help and I recommend them in that order if you are using DNN. If you need a more sophisticated e-commerce website and don't have much experience with Servers, SQL Server etc. then you should find a consultant to help you install and setup not just the DNN Platform but also select the proper Modules to accomplish what you want to do. If you need a highly customized website that is very data intensive and you are not experienced then be sure to save yourself the time and money by finding a qualified Consultant to help you. The beauty of DNN is that it can handle as simple or as complicated of an Application as you need depending on what your needs are and how far you want to take it.
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.
DNN is a feature-rich, open-source project with a flexible license. This let us use it without licensing costs for custom solutions or as-is with no custom code just plug-in modules.
DNN is written in Microsoft .NET C#. This allows our developers and our customers to use their existing skill set to install and maintain the solution.
DNN is made for Windows platform, allowing us and our customers to deploy solutions to existing Windows servers or in some cases hosted platforms.
DNN integrates with Windows authentication allowing us to deploy intranet solutions and use single sign-on for improved user experience and security.
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.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
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
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
Even though DNN is a good CMS, I have worked with other CMSs which are far more robust at this point, and would not be overly inclined to select DNN unless cost of the product is the most important factor along with staying on .NET. DNN is a whole package so unless the client has a requirement of including authentication, authorization for users, eCommerce, sticking to something simple is a better option.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Evoq proved to be a solid backbone for our property-management portal, handling ≈300 active rental listings without performance hiccups. The page-builder made it straightforward to craft listing templates that surface photo galleries, floor-plan PDFs, and embedded map pins, while role-based workflows let leasing agents edit unit details (price, availability, pet policy) without touching global site settings—a big win for operational control.
For the management side, the platform’s extensibility let us plug in a third-party rent-payment widget and an automated maintenance-ticket form with minimal custom code. Evoq’s built-in analytics have already highlighted which neighborhoods and bedroom counts drive the most traffic, guiding our marketing spend.
Two caveats:
Search & filter logic – Out-of-the-box search was too shallow for renters who expect Zillow-style filtering. We had to commission a custom module for filter chips (price range, amenities, walk score), which added time and cost. Mobile image optimization – High-resolution gallery images affected load times on 4G; a CDN or Evoq’s Digital Asset Optimizer add-on is advisable.
Overall, Evoq delivers reliable content governance and enough flexibility to support both consumer-facing listings and back-office property-management workflows, provided you budget for advanced search customization and image delivery tuning.
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.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
I don't see how it could get any better unless they moved their staff into our offices. You have available to you any type of Support you need or want, both paid and free from thousands of developers and consultants all over the world. You might even find some on Mars if you look hard enough.Also, with all of the available resources available from your Browser you can literally find the answer to any question you have in a matter of minutes.
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
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Evoq proved to be a solid backbone for our property-management portal, handling ≈300 active rental listings without performance hiccups. The page-builder made it straightforward to craft listing templates that surface photo galleries, floor-plan PDFs, and embedded map pins, while role-based workflows let leasing agents edit unit details (price, availability, pet policy) without touching global site settings—a big win for operational control.
For the management side, the platform’s extensibility let us plug in a third-party rent-payment widget and an automated maintenance-ticket form with minimal custom code. Evoq’s built-in analytics have already highlighted which neighborhoods and bedroom counts drive the most traffic, guiding our marketing spend.
Two caveats:
Search & filter logic – Out-of-the-box search was too shallow for renters who expect Zillow-style filtering. We had to commission a custom module for filter chips (price range, amenities, walk score), which added time and cost. Mobile image optimization – High-resolution gallery images affected load times on 4G; a CDN or Evoq’s Digital Asset Optimizer add-on is advisable.
Overall, Evoq delivers reliable content governance and enough flexibility to support both consumer-facing listings and back-office property-management workflows, provided you budget for advanced search customization and image delivery tuning.
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Drupal is a highly expensive tool and is not offering anything extraordinary at a high price. If I keep its pricing in account then there should be some extraordinary features but unfortunately, there isn’t anything special about it; rather it was slow in its working. All these things actually forced us to move to Evoq that is just perfect in its working. Its working speed, interface, and UX are so simple that none of our team members find it tough to utilize. It has so many features like content scheduling and rich text edit. It allows easy editing of the text as well, and one can directly add text according to need.
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.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
DNN have given us the ability to have basic sites for clients up and running in a very short time. This makes the client happy.
DNN has taken the trivial, simple tasks of changing text on a page or an image on a page and put it into the hands of the client. They do not have to pay us to do it and that also frees up more time for us to spend on development.
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. :)
