Adobe Social, incorporates technology from Context Optional and Efficient Frontier.
Adobe acquired Facebook advertising-management platform Efficient Frontier in November. Six months earlier, Efficient Frontier had acquired Facebook page-management platform Context Optional.
Adobe Social is an enterprise social platform competing with Buddy Media and Involver, enabling things like automated content marketing and social sweepstakes and competitions.
Customers tend to be medium to large…
N/A
Drupal
Score 7.0 out of 10
N/A
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
Plone
Score 10.0 out of 10
N/A
Plone is a free and open source content management system built on top of the Zope application server. Plone can be used for any kind of website, including blogs, internet sites, webshops, and internal websites.
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and …
I used Adobe Social when I use to have my own business on social media. After many months I was having no success in finding the correct clients for my products. Using Adobe Social I was able to market and discover different ways of searching for the correct clients and later on helped my business grow.
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.
The larger your organization, the more appropriate Plone will be. This is not to say that Plone is a worse choice for small websites, only that the minimum investment for a Plone site is certainly higher than for other platforms. If you already use Plone for your site and are looking for a redesign or an overhaul, I would only advise switching to a different platform such as WordPress or Drupal if your organization is downsizing. For any other situation, Plone is the natural choice for your growth.
Adobe Social lacks strengths, as I believe Adobe themselves have acknowledged, given their decision not to continue support or development. But if I need to list three strengths, the first would be it can publish to some social media platforms with a success rate of over 50%. If that's a strength.
It has workflow processes, but they are over-complicated and poorly designed.
It has some basic analytics, but Adobe consultants usually recommend referring to Adobe Analytics instead. Which is great if you actually use Adobe Analytics.
Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
Plone is secure. It is the most secure CMS you can get your hands on.
Plone is flexible, and makes fast development easy.
It would be great if Adobe scheduled video uploads for Twitter.
A time change in a social post automatically puts the post back to Level 1 of approvals. It can be a big hassle to have to start the process over for such a small change.
Adobe uses a different algorithm to measure engagement our company does. It would be great to upload your own algorithm into Adobe.
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.
Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).
I wasn't in charge of making the actual management decision, but I would absolutely renew Adobe Social. As I mentioned, it provides strong and in-depth analytics and listening tools. The reports that it generates are very thorough and easy to read. I loved the platform and would recommend it to anyone
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.
The reason why I give this rating is that the overall platform is simple to use. You don't need to be tech-savvy or have a vast understanding of how to work a marketing tool. It is very simple to use compared to different platforms and you learn a lot of different ways to build your business.
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.
Compared to the amount of Plone sites, users and customizations we have in our organization, the amount of support requests and training needed is really small.
The new user interface in Plone 6 is even better, it is super fast, has lots of different blocks for enhancing the page, has flexible layout system and is easy to extend with more features.
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).
Our Plone sites are very robust. We have critical systems on Plone and we have been running sites on Plone for over 20 years with very little unexpected downtime.
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.
Plone is very intensive in its operations, and if not configured well it can be slow. However it is designed and built with speed in mind and with proper use of coding, templates and caching can perform extremely well under high loads. It is capable of scaling to very high load availability environments with no specific coding requirements.
The reason why I give this a 9 out of 10 in terms of support is because of the mobile app functionality. I have had many issues in terms of logging in and also loading pages. The app overall is easy to use but at what cost? Other than that it is great and I still enjoy Adobe Social.
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.
Training was long and a little confusing. While a number of features carried over, they were still covered in this elongated training. It would have been nice to have training tailored to experience level with the product.
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.
The implementation was done during our POC. We had a very mixed experience here, and have had some issues arise since based on the way the tool was implemented. An Adobe employee went ahead and made a change to our account that was unauthorized (helpful for our implementation) which caused issues in on boarding another team who needed the same change, but could not get it done without costly Adobe certification
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%
Hootsuite Enterprise is superior in many ways, but the biggest factor is probably that it is constantly evolving and adding new features, working directly with social media companies ahead of new releases. Adobe seems to have stopped developing their product.
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.
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and web content where Plone is much better
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.
Although we chose Adobe Social believing it could provide ROI metrics we could not get elsewhere, that turned out not to be the case. Site Catalyst can give us everything we need without Adobe Social
Adobe Social did not create greater efficiencies and speed up our activity within social media. In fact, it has done the oppposite. It is very cumbersome with little clear benefit.
The impact Plone has had at the University of Oshkosh is as follows: this software allows student workers to learn about IT departments and CMS's in a user-friendly way. It gives many students great jobs that look great on their resumes.
Since there are great training manuals for Plone, there is increased employee efficient in the workplace. Training doesn't take long, and if there's ever a question, the Plone manual is a great tool to refer to.
If an employee using Plone quits, its easy to find someone to replace them with quick training and great resources.
