Likelihood to Recommend I was strictly the implementor of Livefyre (for my company only). That task alone was at least 3 weeks worth of work. From a user standpoint, Livefyre is a good product which is why this review is strictly about how difficult it was to implement. Therefore, if a colleague was to ask me if I recommend Livefyre, it's not a straight answer. Questions like, 'how fast do you need it?', 'how centralized is your user database?', 'do you want social login?', all come into question and were details that made my job not easy (hence, my review of 5/10 for suggesting it to others). Once implemented, Livefyre is a great product (notice my overall review is higher), but based on my experience with implementation, it certainly requires a senior developer's dedicated time and patience to set up exactly as desired. For smaller companies with small/simple user bases and websites, the process may be more straightforward, but from my experience, it wasn't out-of-the-box at all.
Read full review Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using
WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Read full review Pros It provides and allows comments and comment management that is fast, seamless and shareable. Having used disquss, WordPress comments and many others I like Livefyre better for its seamless integration and transparency It is really nice that they have a range of services from free to enterprise with increasing functionality and benefits. Read full review Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website. Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp. Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require. Read full review Cons Implementation was not easy. Although flexible, I personally wrote at least 1,400 lines of code to get this implemented over a few week's time. The social login aspect is cool, but again, hard to implement. They did not write any of those modules, although they could have. This required senior-level developmental skills and a knowledge of how social media is interfaced with programmatically. Lots of questions arose from this and it was difficult to implement with virtually no help from Livefyre, other than to provide the hooks into their system for when users were validated. I had to write at least 2 separate login/redirection scripts to accomplish this flow. CSS tweaking was tricky. We could override lots of common CSS classes, but to get things just the way we wanted it, I ended up writing LOTS of jQuery listeners and functions to transform the output into exactly what we wanted. This was a surprise since the software was sold to us as being 'fully customizable'. Documentation was sufficient, but not great. Getting the flow of the callbacks that are fired wasn't clear at first, and sometimes did not work as expected. It should be noted that, after this review was published, Livefyre contacted me stating they now have better documentation and process for implementation (for version V3, specifically) and urged me to revise this review. However, I can only write of my experience with V2, and it WAS difficult to implement over 3 weeks of dedicated time. Another developer on my team implemented version V3 and his evaluation is very similar to mine, claiming much difficulty with the CSS customization. Read full review 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. Steep learning curve, but worth it Read full review Likelihood to Renew We feel we have a real partnership with Livefyre and we both make each other better. Their customer service has been phenomenal even during a time of rapid growth.
Read full review 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.
Read full review Usability It's really easy to implement that app but should improve some analytics.
Read full review It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
Read full review Reliability and Availability 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).
Read full review Performance 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.
Read full review Support Rating From purchasing to implementation, the customer service/support was really perfect!
Read full review 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.
Read full review In-Person Training 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.
Read full review Online Training 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.
Read full review Implementation Rating 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%
Read full review Alternatives Considered We felt Livefyre was more innovative and better at SEO. It felt like we were working with a partner for the long haul who was interested in our business and how to improve it.
Read full review Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
Read full review Scalability 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.
Read full review Return on Investment The heavy work is already done given that we take the time to implement. Very useful insights and AI powered delivery. Read full review Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact. Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact. Drupal has allowed us to build great solutions for our clients which give them an excellent ROI. Read full review ScreenShots Adobe Experience Manager Livefyre Screenshots