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
OpenText WEM
Score 9.0 out of 10
N/A
OpenText's Web Experience Management is part of the Customer Experience suite and is based on the Vignette product that OpenText acquired in 2009.
N/A
Streamlit
Score 8.0 out of 10
N/A
Streamlit is an open-source Python library designed to make it easy to build custom web-apps for machine learning and data science, from the company of the same name in San Francisco. Streamlit also hosts its community's Streamlit Component offered via API to help users get started.
N/A
Pricing
Drupal
OpenText WEM
Streamlit
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
OpenText WEM
Streamlit
Free Trial
No
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Drupal
OpenText WEM
Streamlit
Features
Drupal
OpenText WEM
Streamlit
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
OpenText WEM
8.5
2 Ratings
4% above category average
Streamlit
-
Ratings
Role-based user permissions
8.174 Ratings
8.52 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
OpenText WEM
8.2
2 Ratings
6% above category average
Streamlit
-
Ratings
API
7.264 Ratings
8.52 Ratings
00 Ratings
Internationalization / multi-language
8.160 Ratings
8.01 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
OpenText WEM
7.9
2 Ratings
1% above category average
Streamlit
-
Ratings
WYSIWYG editor
6.171 Ratings
7.42 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
8.02 Ratings
00 Ratings
Admin section
6.878 Ratings
8.02 Ratings
00 Ratings
Page templates
5.577 Ratings
7.52 Ratings
00 Ratings
Library of website themes
5.568 Ratings
8.52 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
7.52 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
8.02 Ratings
00 Ratings
Form generator
6.372 Ratings
8.52 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
Areas where OpenText WEM is well suited 1. Improved digital/web presence of the organization's leaders globally. 2. Established the leaders as go-to experts for thought leadership and domain knowledge among C-level executives of related industries. 3. Amplified the client’s marketing and branding efforts. 4. Customer engagement reflected by interaction count on social media—likes,comments and conversations.
- Don't want to pay Tableau $1,000 / seat? Use Streamlit - Want fully custom views and navigation? Use Streamlit - Want access to Machine Learning and not just your dev team? Use Streamlit - Want to keep things internal and secure? Use Streamlit - Want your Data Science team to be able to crank out projects quickly? Use Streamlit - Sick of Jupyter Notebooks and Business Leaders not understanding them? Use Streamlit Our D.S. strategy has moved completely to delivering pages in Streamlit. I can hand an executive a Jupyter notebook and it'll get lost in translation. I can give them sign-in access to a page and they can answer all of their own "What-If?" questions! We've used Streamlit to productize our Data Science and Machine Learning capabilities.
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.
Recent Security issues (they quickly released an update to combat this though...)
Requires a bit of HTML knowledge to really customize. If you're going quick, you don't need HTML though. Streamlit commands will pump your page out fast.
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.
We have choosen OpenText WEM against other vendors because : 1. Helped client reinforce brand image through unique design language and templatization of collaterals, consistent messaging, and regular competitor benchmarking. 2. Enables lead generation through high-quality gated collateral, product videos, etc. 3. Senior management and sales lead meet client regularly for project review meetings and feedback on engagement
I started using Streamlit when it first came out and thought it was really useful and powerful. A few years later and they've really hit their stride! The features / widgets / materials they provide have been well researched, well designed, and well implemented. I will take Streamlit to any future companies I go to as well as be a strong promoter wherever I'm currently at. It's free. It's easy to use. It is really powerful. Sure? You could go pay for a larger system but your Data Science team should be able to handle Streamlit easily. I'd argue a non-technical person spending a few weeks in python could pick up Streamlit really quickly.
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.