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
eZ Platform
Score 5.0 out of 10
N/A
ezPlatform, formerly ezPublish is a content management solution from eZ Systems. The vendor says their solution provides organizations with the technology and framework to build a suite of digital experiences including news and media sites, brand sites, multichannel apps and the Internet of Things, intranets and web portals. This solution is multichannel, multilingual and multisite ready.
ezPlatform features user defined content and classes, version control, templates, workflow…
eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:
Developers, system administrators, and project manager can all speak the same language during the development and …
Overall, I would give my rating of Drupal a 7/10 because there is an easy user experience for those without a website background but there is some technology work required to build more website capabilities that aren't as user-friendly. Drupal is specifically well suited to update content (like changing Relationship Manager cards when there is employee turnover), post announcements (putting up a holiday banner to let our customers know the dates we will be closed over Thanksgiving, Christmas, etc., and creating a sophisticated website hierarchy of pages (for our firm, several dropdowns depending on if you're looking for personal banking, business banking, investment banking, about us, etc.).
For a new site: 1. Are there any hosting requirements? eZ Publish works best on a traditional LAMP stack. 2. What is the expertise of the development and systems administrations individuals? There should be some PHP development experience and a solid level of Apache and MySQL hosting. 3. Who will be managing the content of the site? What is their bandwidth for training? For ongoing content changes?
It has excellent security features and consistent updates.
It allows for extensive customization with the integrated themes and core code, especially when you first install it. This allows our dev team to get creative with marketing initiatives.
There is a large online community of Drupal users that consistently help answer any questions and issues
Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.
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 template language: Outputting content or doing something special with it requires use of the templating language. Myself along with other developers I have trained, found this to be one of the biggest hurdles.
Layout of physical files: The system decides what settings files and templates to use based on a hierarchy of modules. The same file can exist in multiple modules and you can find yourself deep within very similar looking folder structures, causing confusion during debugging.
Community: eZ has a solid set of community contributors but the gap between it and Drupal or Wordpress is pretty large.
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.
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.
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 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 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.
eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:
Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
End-user training is very straight-forward.
Vendor support is available.
Client IT departments can access if need (developers/designers/sysadmins).
The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.
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.
Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
Training: Due to its content taxonomy, end-user training often went well.
Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.
