What do you like best?
1) The ease with which I can make a custom type. I was previously making modules using Christoc, which was fine, but now I specify a content type and make it instantly in the cloud.
2) This is a truly headless CMS, though using it as such takes a bit of setup. By making API calls, I will be able to skip making visualizers and keep my content completely separate from having to make pages.
3) For when I do need to make pages, the visualizers are a nifty way of showing this content - they are using the Shopify Liquid Content templating system which is a fully featured (if at times slightly odd) templating engine.
4) The DNN support is amazing, so different from other CMS' I have used in the past. I have bothered these poor people with so many questions and they have always been great.
What do you dislike?
These dislikes are temporary, solved by the product maturing to the stage where they allow unwashed peasants like myself into their content by direct API call.
1) Cost of being bleeding edge, I do not have an API key so I cannot use the EVOQ content without a visualizer right now. That ability drops with the 9.1.1 release, due out this week.
2) No inherent way to import content out of the gate. They have an import export tool coming but because of timing I will have to whip up something myself. When I get the key they have an example made with excel that I can use.
3) Minor gripe. I want objects to be able to reference themselves. As an example, if I was building a menu, I do not want a content type for level 1 another for level 2 etc - I want a content type menu-item which can have children of itself. Then I can easily build a menu. As I say, minor gripe but it has made me use the old DDRMenu module instead because I don't want a splattering of Content types for different menu levels.
Recommendations to others considering the product
While I am still in the implementation phase, I am super excited for what this offers. One of AEM's newest boasts is that you can use it headlessly - and I think their methodology is kludgy. Sitecore you would have to make all the services yourself, last time I did so I had to do it using SOAP, blurgh.
EVOQ is built to be used this way, it is clean, quick and stores everything in the cloud. Very
What business problems are you solving with the product? What benefits have you realized?
We are making a new Angular4 site so I will be using a microservice to pull pure data by url. I can then package it up as json objects, which it needs.
To see some of the things this makes possible, go look at what dnn people are doing internally with it http://www.builtwithdnn.com/ ... tantalizing!