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
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…
We evaluated many CMS systems and Drupal came out on top because of its flexibility and that its open source. We didn't always know everything we would be asked to build and Drupal allowed us to be nimble enough to do what needed to get done. We also liked that it handled …
Drupal is the king of enterprise opensource content management systems. It is the most robust and comes from the most forward thinking community. Drupal 8 is designed for the next evolution in web design and development. WordPress and Joomla! are stuck in the web 2.0 revolution …
Drupal is not as powerful, extensible, or easy to use as Sitecore, but it is free, whereas Sitecore can be quite expensive. It offers a similar service as Umbraco, but from a PHP codebase. For clients that need a free CMS system, it is the clear choice for those with a PHP …
Drupal is simply the most robust open source content management solution available. It also does a great job stacking up against other licensed solutions like sitecore or CQ5.
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. …
Of all the competitors listed above, Sitecore owned, by far, the best combination of power, easy-of-use, and extensibility. It easily outperformed the other paid-for CMS systems. Its power is especially noticeable in its ability to handle very complex workflows, security …
Sitecore provides an incredible amount of capabilities, endless customization and seamless integration. Each customer situation is unique, but in general, these are the driving forces behind the selection.
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
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].
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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%
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.
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.
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.
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.
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.
