ancestry had an existing CMS in place for a few years and the biggest pain point for us that we wanted to solve was the usability of the tool the previous tool that we had was very feature-rich but it was very inaccessible to sort of the general non-technical customer so we wanted something that was significantly more accessible made finding content easier creating content easier and Magnolias really solved those issues when we decided to redesign our architecture we had a few things in mind we wanted the system to be highly performant a minimum of two fold increases what we see so the new system is like you know twice as faster as the older one technology is changing and the product that we have did not support that shift so we needed something that would plug into our existing ecosystem and didn't require some enterprise solution at some enormous price and with all the integration with our testing tools it helps us get there faster installing the endpoints the rest endpoints that are abstraction layer needs on Magnolia was super easy you know we took advantage of the of the servlet capabilities and you know all of our components that we developed we're you know easy to add one we brought Magnolia on board one of the awesome features was an effective search so I could very easily find assets that I was looking for simply by searching has actually been one of the most helpful features that I've lacked for the last five years so looking at the performance I think that was like a big win for us that removed all the suspicion we had on the tool like would it scale the tool actually scaled well right I feel good about saying this is the right tool because it'll offer you X Y & Z and I know that when they come in to use it they're gonna have a good experience it's made my life easier because the support staff are super responsive to any questions that we have it's been a really nice experience you