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
Salesforce Experience Cloud
Score 8.0 out of 10
N/A
Salesforce Marketing Cloud Engagement (formerly Salesforce Experience Cloud or Salesforce Community Cloud) is an online forum powered by Salesforce that enables businesses to connect with their employees, customers, partner organizations, and prospects. Designed to help facilitate communication and information sharing, customers can ask questions and request help, administrators can integrate data from third-party apps, and employees can collaborate across projects and…
Salesforce Experience Cloud (formerly Salesforce Community Cloud) is better when you are using Salesforce for applications. Drupal is a solid open-source web content management system for internal and external websites, but if you are using Salesforce for services or case …
Salesforce Community cloud stacks fairly well, as it's a unique product. To get a lot of the functionality, we looked at building a custom application that would serve something similar to this. The amount of time to build that application vs using Community Cloud was quite …
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 well-suited, this product is great for your external clientele groups that you would not necessarily want to have a high user fee rate for. So basically general public or a group that will be authorized to come in and just do a few things here and there, but you don't necessarily want them access to all of your systems and your data points for groups that it would not be a great use for. I'd say probably your high level internal staff, they're going to be using a lot of the backend functionality automations, evaluating data, managing data, and doing custom inputs. That's just not what's intended for.
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
Complete integration with the Salesforce ecosystem. Data displayed in your Community portal reflects records from a Sales Cloud organization
Highly customizable. A Community Cloud portal can be totally customized both visually and with different funcionalities with little to no coding skills required
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 documentation for implementing Experience Cloud can be a bit confusing as their rebranding hasn't made it's way into all articles, resulting in different terminology being used to refer to the same thing
Some things are not as intuitive regarding their customizability, so there's a bit of a learning curve (i.e. Lightning apps can't be used to customize layouts in Experience Cloud)
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.
Usability is pretty streamlined, especially if you're familiar with other Salesforce products, but even if not, take it from me, as I just entered the technological space about two years ago, that this product is pretty simple to learn. You don't have to jump in with your head underwater. Small wins and learnings along the way are what foster long-term understandings and enable your evolution alongside the product. I definitely recommend Salesforce Trailhead along with it
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.
It's delivered on our original requirements and we've found ways to grow its usage. We continue to build on our original success and we can report our data out to leadership to show a true return on investment which is great for growing support and expanding uses for the system.
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.
We have weekly calls with our Salesforce reps. They bring new ideas to the table and help with taxonomy builds. They have also answered many questions and connected us to the right people for us to grow our knowledge and utilization of the platform. They are a good partner overall in comparison.
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.
Salesforce Experience Cloud was selected due to its tight integration with our existing Salesforce CRM platform. Customization of the portal was much, much simpler compared to Sharepoint - especially with role-based security parameters that are ultimately inherited based on attributes within the Salesforce CRM platform. Salesforce Experience Cloud was a natural fit for this customer-facing purpose.
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.
