Drupal vs. Ibexa DXP vs. PaperWeight

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.

Incentivized

I always recommend Ibexa DXP to my fellows. The only scenario that I would not recommend it is if the site is either too small, too simple, or that they simply cannot afford to stand it up properly.

Very easy to use and customize homepage, dashboard, and multiple landing pages of courses. Easy for setting up intuitive dashboards, rating users, and receiving ratings. Create and edit content or upload documents and make edits. Easy to segregate functions based on user roles. Multi-device support is not so seamless though overall it is responsive and scalable on the web.

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• 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.

Incentivized

• PaperWeight has amazing features for freelance reviewers who can provide insights on how a course can be structured using interactive content.
• PaperWeight is scalable, responsive, secure.
• Freelance reviewers find easy to use PaperWeight.
• We could also rate and provide feedback on the work delivered by freelancers which is visible to a group of users who can allocate future work based on the profile feedback.

Incentivized

• 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.

Incentivized

• Limited partners when you compare to other solutions (WordPress, Drupal, etc). It took us a while to find a solid, trusted developer.

Incentivized

• PaperWeight could improve its usability experience across all devices. Sometimes there are some glitches when viewing on another device.

Incentivized

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.

Very happy with current relationship and websites

Incentivized

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.

Incentivized

It is quite easy to navigate through the backend and also, you can directly work in frontend view. Dynamic content can be created on the fly. Their Landing page features are awesome. You create a page by drag & drop.

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.

Incentivized

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.

Incentivized

They are directly reachable and help you to deal with other services, e.g. if would like to set up a CDN for China or if you would like to integrate a tool like HubSpot. If there is anything you are missing, they help you to find a workaround until they can deliver such items - like local language versions.

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%

Incentivized

The partner selected makes a significant impact on the usability and experience

Incentivized

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.

Incentivized

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.

Incentivized

We like the light-weightedness of PaperWeight, scalability, and its ability to meet our needs at a reasonable cost. Pre-existing relationships and business process outcomes helped in making the decision to go with PaperWeight. The product roadmap being aligned with our own roadmap also was a huge factor in the decision-making in favor of PaperWeight.

Incentivized

We’ve priced other enterprise products and found Ibexa DXP to be a bit more expensive. However, not enough to dissuade us from staying with the product.

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.

Incentivized

The partner ecosystem is small. However, we've worked with two Ibexa partners over the last 10 years. They were very skilled. They were great companies. We've interviewed other Ibexa partners in North America. We found them all to be professional with solid resumes.

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• 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.

Incentivized

• It has [made it easy to] find freelancers for our course reviews.
• We can trust the reviewers who are onboarded on our portal and we feel safe to share business content with them on PaperWeight.
• We are able to prevent [unauthorised] downloads of our content.

Incentivized