VPlayed vs. Drupal vs. TYPO3

As mentioned earlier, leaving the liberty to choose a monetization to the client (us) is a big morale booster for brands who want to generate an extra income stream with their content. Plus, their in-built video player that supports ads is also helping us a lot to multiply our money with the same efforts.

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

TYPO3 is great if you need to connect some systems in company to work together: like ecommerce + CRM + ERP + MRP and build an Extranet for partners/dealers where they can order your products, see particular BOM (bill of material), paid/unpaid invoices and use email marketing on top of it. You can do it but keep in mind that you will need a dedicated hosting, well organized admin(s) and some handwritten code. For simple blog TYPO3 is also a good choose, but WP would be better I think.

Incentivized

• Video streaming
• OTT apps
• scalable video platform
• video security
• mobile and TV apps
• white label

• 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

• open source - do what you want, and even if you dont know how to do it - someone will do it for you
• more secure than others (Joomla, WP, Drupal) - thanks to dedicated Typo3 Security Team
• modularity and diversity - a lot of plugins/extensions
• workflow and user roles - feel free to build a workflow templates ie. for documents routing
• assets management - no matter is it a video, audio or text file, you can REALLY manage it.
• typoscript language - sometimes JS is not enough

Incentivized

• More flexible pricing

• 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

• compared do Wordpress - far less community support
• when you run a simple blog - it is simple as piece of cake. But if it is a large news site, with many user roles, extensions and permissions - it may be hard to find an admin that will organize and keep that stuff working.
• server resources: so you want performance and speed with all that modules enabled? make sure that you have dedicated server in most cases. WP works much better here.

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.

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

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

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

None of the other solution providers offer customizability and ownership. Also VPlayed team's support was excellent!

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

• more complex and elastic revoke system (undoing changes for multi-administrator systems) PHP/JS and TypoScript language
• LTS - long ter msupport (bugfixes and updates)
• usage rights and permissions (much more advanced thatn in WP/Joomla)
• separation of design and content (in WP also but here is complex)
• many plugins to integrate with external systems
• several portals may be operated from a single admin/install

Incentivized

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

• Jump in revenues by at least 3X

• 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

• + 1 platform that handles connections to 11 external systems (CMS, CMR, ERP, MRP, accounting, controlling, email marketing etc.)
• + still lower TCO than commercial systems (Oracle, Microsoft)
• + LTS - long term support - can provide you an updates or bugfixes
• - resource consuming (forget about shared hosting in large projects)

Incentivized