Adobe Experience Manager vs. Movable Type

I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.

Incentivized

For the purpose of simple, day-to-day blogging, Movable Type will get the job done. As I mentioned before, it has an intuitive UI so that most beginners can pick it up and build a simple blog post. But if you're looking for a CMS that will host multimedia content, interactive content, or any "fancy" production that goes beyond paragraphs and bullet points, then I would recommend something different - maybe even a custom CMS for the maximum control over your website's back-end coding. Keep in mind that the CMS does have some quirks and can be finicky, but the support staff is extremely helpful and available.

Incentivized

• It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.

Incentivized

• Once you understood how the MT language and framework worked, customization wasn't too difficult.
• Allowed for levels of user access.
• Ease of creating RSS feeds.

• There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
• Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
• Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.

Incentivized

• While it's beneficial to be able to assign administrative rights to a user so they can only post to certain places of a website, I can recall that Movable Type did not inform general users of the types of privileges they had. So, for example, when I knew I needed to make a posting to a certain area, and was unable to do so, I was not informed that I did not have access to make that posting. It would have been helpful for Movable Type to post a message on the screen, saying that I needed more permissions. This was very frustrating, especially when I was on deadline for a newspaper story.
• Unfortunately, (or fortunately), I do not recall other negative experiences. I thought it was a pretty clean, friendly interface.

We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.

I think there are still improvements to be made. I haven't tapped in to the full functionality of the CMS yet but the rating I give it now is only based on what I've been able to use it for

Considering I'm completely self-taught on Adobe Experience Manager, I have to rate usability quite high since plenty of aspects were easy to figure out on my own. With its cloud-based platform, access from anywhere it super great for overall usability. Edits can also be made pretty quick and easy, which is another great feature.

Incentivized

Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.

Incentivized

With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.

Incentivized

Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.

Incentivized

Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint

SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance

Incentivized

Movable Type is better than Wordpress because it generates static sites that cannot be broken by losing your database connection. The custom fields in MT are superior to Wordpress because of the way the fields are presented in the new content form. You need to get paid plugins in order to get that kind of functionality in Wordpress. Most of the templates in MT can be customized with greater control because you're provided with more templates.

• Makes it easy to reuse components across multiple pages and site, which reduces the overhead needed to create all the individual components.
• Improves business process agility by allowing users to easily create entirely new pages or content by using existing templates
• Increases conversion rates across our sites by enabling a more consistent experience for users

Incentivized

• Movable Type definitely increased employee efficiency. Having everyone on the same platform to edit multiple websites from system is crucial.
• Expanding our website presence was a super simple process with Movable Type. All we needed to do was add another site, destination folder, and we're ready to go.
• Having all of our web designers on the same platform helped immensely with communicating information and structuring education for new employees.