crafter vs other Java CMS

[mrrosenthal85]

Hi,

What are the main differences between Crafter and other Java CMS options like hippo magnolia opencms etc.  I looked on wikipedai and its not listed as a java cms.  its also not usually compared to these 'enterprise' options.

We are using alfresco for ECM.  Some websites recommend liferay as well and then crafter, but I dont know the reasons why.  Thanks!

[Russ Danner]

Great question.  A comprehensive answer here could take quite a while but let me give you a few major distinctions:

Crafter CMS is a much more modern approach to web and digital content management than what is offered by Hippo, OpenCMS, Dot CMS and Magnolia.  

Modern Technology, Better Architecture:
The architecture is decoupled, much cleaner and extremely more scalable.  These other CMS solutions use relational databases and JCR repositories.  These technologies are slow and force you in to a developer centric, schema specific build.  They are difficult and slow to develop for and maintain and when you finally deploy them, they are difficult to scale.  Crafter CMS eliminates all of those concerns with a shared-nothing, highly scalable deployment architecture that uses a combination of in-memory and Apache Solr based content retrieval.   

Scripting and Rapid Development/Deploy:

Crafter fully embraces scripting with technologies like Groovy and Freemarker.  You can create new functionality and do integrations with your site and never once need to do a war file deployment. 

True Freedom of Content Delivery:

Crafter allows you to deliver your content any way you need it.  Crafter can deliver HTML, Content as a Service (JSON/XML) or even other kinds of responses like VRML.  With HTML We support any front-end framework and any markup.  You can do responsive (client side) or adaptive (server side) design or both at the same time.  With Content as a Service you can leverage our out of the box Restful APIs or quickly define your own.

Great for Content Authors and Developers Alike:
Content authors work with a easy to use web UI.  Developers can work in the web tool or through local tools.  We even support developer based workflows with technologies like Git.

Repositories / Integration with Alfresco:

- Crafter has a repository abstraction layer that allows us to change out repository implementations.  We integrate with Alfresco because of its awesome enterprise feature set.  No other CMS solution as strong an integration with Alfresco as Crafter CMS.  

/R

----

Russ Danner, Vice President, Products

Voice: +1.617.834.2781 GTalk: russ....@craftersoftware.com

--
You received this message because you are subscribed to the Google Groups "CrafterCMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to craftercms+...@googlegroups.com.
Visit this group at https://groups.google.com/group/craftercms.
For more options, visit https://groups.google.com/d/optout.

[mrrosenthal85]

Thanks for the explaination

Can you comment on how solutions such as liferay, alfresco and crafter would be used together?
I havent been able to figure out which tools solve which problems

[Piergiorgio Lucidi]

We have a customer story where all these platforms are used together. 

You can also take a look at my talk at the Alfresco Summit 2014 in London kept with Russ :) . You will find slides, video and other useful informations from my website at the following page:

http://www.open4dev.com/journal/2014/9/23/my-talk-at-the-alfresco-summit-2014-in-london.html

Liferay can be used in for building intranet portals when you have an extensive use of profiled pages and you want to use some existent portlets for your needs.

Crafter is used for managing all the web contents for public and private websites and editors work only on Crafter Studio where they collaborate using the Crafter workflow for publishing contents.

We have integrated Crafter with Liferay for allowing a portlet to let editors choosing web contents created by Crafter Studio and publish them on Liferay pages.

Practically Crafter is the owner of web contents, also for Liferay portals, I think that in big companies where they need a complex WCM platform this makes a lot of sense ;)

Hope this helps.