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.
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 …
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
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.
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
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.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
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.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
I have not found anything that was as user friendly and easy to use with tons of Community Support as well as Corporate Support like Training Videos, Forums, Blogs, Documentation, Wiki, Free CodePlex downloads, Free Modules and then the DNN Store that has thousands of Skins and Application Modules to accomplish everything you need.
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.
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%
I would never look back and question our decision to implement DNN not only as the Platform for our own use but also to use it to develop a complete turnkey system for our Clients worldwide. Everything you need is available and there is more expertise around the globe than you could ever imagine
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
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.
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.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
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.