Founded in 1997 with a vision to create the first truly open content management system, Magnolia is presented as a fast way to launch digital experiences. With a mission to help clients move fast and stay flexible and boasting users among brands like Atlassian and The New York Times, Magnolia DXP supports industries ranging from automotive to telecommunications, offering enterprise features and headless agility to help them stay ahead. From humble beginnings in Basel, Magnolia's…
N/A
Titan CMS
Score 8.0 out of 10
Mid-Size Companies (51-1,000 employees)
Titan CMS is a web content management system (CMS) for building public websites, intranets, or extranets from Northwood Software. .Titan CMS is built on Microsoft C#.NET 4.0, SQL 2008 R2, and is designed to operate on the Microsoft Windows Server 2008 R2 64-bit operating system. Titan CMS offers web and data management, e-commerce, SEO, third-party code integration, site analytics, workflow and security.
Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.
Titan CMS is a good full featured CMS if users are fairly tech savvy. It is under active development and has added significant features through the years.
Speed of development - time to delivery from zero to MVP was excellent
Ease of use - the authoring experience is very easy to build and train
PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.
Utilizing a Filter to determine what shows on a page saves countless hours of configuring content that should be displayed on a page - it's been a lifesaver how easy it is to set up too.
Smart Search takes the search box and makes it magical. Common misspellings and alternate names can still send a user to the proper page!
Data nodes and filters can also be configured to Find a Dealer, Doctor, Location etc. It puts the power into a users hands and makes is easy to use.
The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.
I would love to see a "View this Page" button after a page has been updated/published. Every time I publish a new page, I have to open a new browser window, navigate to a different tab, copy the page url "example/example/example" and paste it after "www.mywebsite.com" in order to preview the new page/content.
If Titan and WordPress were in a beauty competition, there is no way that Titan would win. Titan's dashboard, buttons, etc are dated and bland, and is in dire need of a refresh.
A drag and drop to upload feature would be very helpful.
Creating forms is very cumbersome and the pop-up window in which the form is created needs to be revamped. The font-size is much too small and it is not as customizable as it could be.
Titan CMS had a great support system and they helped make my experience go smooth. They offer courses to help people get acquainted, offer support over the phone and are more than willing to make your experience a great one. Once I was familiar with Titan I always found myself wanting to learn more and do more to improve upon the website. Titan makes CMS fun and exciting!
We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.
Everything we've needed to accomplish, Titan CMS has been able to accomplish. From multiple levels of user rights, document rights, tagging pages and documents to make filters do the work of content displayed on a page - it's all easy to set up too. Creating a content rich product detail page template and customizing a ecommerce cart to work for those using a dealer network - needing a request for quote, to go to dealers instead of a self checkout.
I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
I understand that our Web Development Team is very busy, however, sometimes there is a delay in response and a followup email is needed to determine the progress of the issue/question
It was customized to include screen shots of our site and how users can access the content that only pertains to them as well as advanced training sessions for admin duties and everything that goes along with it. Training is in small groups and can be private (your company only) if you like too.
Talk to your project manager for Titan early on in development about minimalizing customizations. It seems obvious, but many times they do what you ask in the respect of "This is how we do it now, make that happen in Titan" vs. think of how Titan can deliver the same results within the confines of the base software. It's not a fault, just human nature.
I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.
Clients have access to the online and PDF documentation, also tips and how-tos for the most current versions of Titan CMS in the market. Check out our full documentation library! unlimited Dev/ QA/ Server install. Load balancing, and cluster support included. Upgrade options included free of cost along with unlimited CPUs per server.
Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
Positive ROI by allowing content contributors embedded within departments with the department domain knowledge to update the site directly. More efficient and less centralized spending.
Requirement for investment in training users of CMS cuts into ROI. Would recommend a two-step workflow where department content contributors enter information into CMS and then approval step is done by webmaster team to ensure content meets standard formatting guidelines. This workflow functionality exists in the Titan CMS.
Positive ROI experienced during projects such as moving to a responsive design because much of the content can migrate untouched. Also positive when updating graphics in template to give site new look.
