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
eXo Platform
Score 10.0 out of 10
N/A
eXo Platform is an open-source, social-collaboration software designed for enterprises. Some key features include: Enterprise Social Network, Enterprise Content Management and Social Collaboration.
$5
engaged user/month
Pricing
Drupal
eXo Platform
Editions & Modules
No answers on this topic
Enterprise
5$
engaged user/month
Professional Edition
5$
engaged user/month
Enterprise Unlimited
9$
engaged user/month
Offerings
Pricing Offerings
Drupal
eXo Platform
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
$5 per engaged user
Additional Details
—
Professional:
Starting at 100 users//
Enterprise:
Starting at 300 users//
Enterprise Unlimited:
Starting at 500 users
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
It is especially suitable for working together remotely or from disconnected locations, allowing them to access collaborative work and tools to facilitate communication. Internal and cloud options also seem to offer a flexible adoption roadmap. It addresses the problems of efficient collaboration and effective communication between employees, particularly with regard to working and completing projects
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.
I personally love the user-friendly interface. Often you find software which is difficult to learn, and not utilized as often as it should be because of this. With eXo Platform, the interface is easy to understand, and is not particularly challenging to new users and non-tech savvy individuals.
It allows you to get work done, without feeling like using the platform is part of the actual work. It feels more like a natural system you would use in your leisure time to connect with friends and family, rather than a social intranet designed to facilitate employee communication and help you meet project deadlines.
The cloud platform allows users to easily share information and files, and collaborate on project work. Another benefit to this is it makes mobile collaboration possible.
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.
As the platform appears to be packed with features and functionality it may be a bit daunting at first to get used to it.
The initial adoption in a corporate setting would involve a number of questions, such as integration with other applications, data migration and security and the optimum adoption road map in order to maximise the benefit from the platform.
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.
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.
This platform has a pleasant user interface, is very easy to use, and offers a lot of useful accessories and add-ons. At first it can be a little intimidating, but it doesn't take long to get used to it. It is considerably reliable and safe. Facilitates connection and collaboration with coworkers. It provides tools that allow you to capture, organize and act according to the internal knowledge of your team.
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.
The eXo platform offers a high quality support, which satisfies the requirements of our company, especially when the platform begins to be used, due to the amount of tools that can be overwhelming. Support responses are made in a short period of time.
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%
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.
We selected this product firstly because it's easy to use for end-users, even if it's not so simple to configure from an administrative point of view. Managing and tracking overall activities is quite easy and it's also possible to have an immediate vision of everything that is done on the platform. Users feel confident and are encouraged to share resources.
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.
