Magnolia vs. WebWave

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.

Well suited: Small businesses and entrepreneurs: WebWave is an excellent option for small businesses and entrepreneurs who need a professional-looking website without spending a lot of time and money. It's easy to use, customizable, and offers fast load times and responsive design. Less appropriate: Large e-commerce websites: If you're looking to create a large e-commerce website with a vast number of products and advanced features, WebWave may not be the best option. Its e-commerce functionality is limited compared to other website builders, and it may not be able to accommodate the needs of a large-scale online store. Also, if you need much coding, you would rather have it with something that is wordpress-based.

Incentivized

• 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.

• WebWave's site builder is the platform's truly innovative feature. I've never come across another service that deploys a layer-based approach in web design, as most of them usually deploy a grid-based system. This is an incredible alteration that ensures WebWave behaves much like a traditional graphic design tool, thereby resulting in an experience that is a lot more intuitive and instinctive. I believe this has the potential to radically change the way people approach no-code web design.
• WebWave provides automatic, daily backups and a free SSL certificate for every website. This results in excellent security.
• WebWave's support team is first-class! I had some teething-issues in the beginning, but the support team quickly got me back on track.
• WebWave's community/forum is an excellent place to vote and request new features. This proves the development team is committed to making WebWave better by listening to their users.

• 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.

Incentivized

• Some scope for improvement in UX (colors are not very appealing). It is simple to use but design is a little dated. Especially in the builder section, I'd like to see modern design for buttons and maybe gradients also: as this is where visual motivation is also important
• Some edits take effect only after pressing OK. That should be eliminated as it's an unnecessary addition. It's also kind of annoying to do that again and again, which can add up to a lot as we do so many small tweaks while building the website.
• Few things (maybe glitches) in design. The rectangle below the footer was uneditable for me. I spent quite some time trying to figure it out so I'm convinced it's a glitch.
• Website speed should be increased.

We have invested a lot of time and energy into tailoring a solution that works for the company.

We think the new features in v6.2 will help us get to the next level

We also don't have the resources to rebuild a website platform from scratch even if we wanted to

Incentivized

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.

Incentivized

Very easy to use, intuitive, has many options and plug-ins, and is cheap.

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

1. The support person does not seem to understand the issues, and seems like they go off to talk to somebody and revert back every 5 to 10 minutes. It takes up a lot of time. 2. There is a lack of reading material to address simple issues like changing the website name in the dashboard, pasting a code, etc.

Incentivized

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.

Incentivized

WordPress is a more flexible and adaptive content management system than Webwave. In addition to the functionalities that are already built-in, I am unable to add any customizable plugins or add-ons. However, in the majority of cases, the inherent features of Webwave are sufficient for developing a website that serves its intended purpose. Webwave also makes it possible for you to add animations and the appearance of each of your design elements, whereas WordPress builders require additional plugins in order for users to access most of such capabilities. Webwave has several essential design features available internally, thus saving money and time.

• 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.
• The templates makes the whole process easy

Incentivized

• saved 30 hours per year per site (previously I had to manually run updates and check if everything is fine)
• earns money for me without a touch (thanks to automatic billing of my customers for hosting and support) - additional (ca.) 120 USD per year per site
• no negatives so far