Acoustic Content (formerly IBM Watson Content Hub) vs DNN Platform

• It has a wide variety of built-in API calls.
• Building unique pages is simple and straightforward and requires only basic fundamental knowledge to get started.
• More advanced API calls can be developed simply.

Read full review

• Very easy to use CMS - Ease of use is paramount with CMS products to minimise on support calls. Also the template structure of pages ensures that content editors cannot inadvertently corrupt the layout of the page.
• Powerful application framework - The existence of APIs for all functionality within the CMS provides limitless scope in terms of developing bespoke applications which sit within the CMS.
• Commercially supported option available - For larger clients, the comfort factor of having a direct line to the developers of the application is a big selling point.

Read full review

• It doesn't work well with our IBM systems and as you might expect, that seems to be a common problem with IBM products.
• Application settings are bad and some items are easily accessible and can be buried in menus

Read full review

• Out of the box, it has some modules, but not enough unless you do a paid version.
• The support is a bit slow.
• The menuing can be confusing and terms used a bit strange. which makes training difficult.

Read full review

• Approved developer is a simple tool for integrating other end-user applications.
• It has allowed us to have one-stop-shop and easy-to-use debugging, saving time.

Read full review

• DNN helps us win bids on projects through the improvements the community has done over the past few years; we were ready to scrap it all together but it has made great strides
• DNN's community has come back and is actively working to improve and expand the capabilities of the cms
• on a negative note, the confusion between evoq and dnn has caused us headaches

Read full review