JECIS - Three Important Updates

Thanks to all of you for the valuable feedback. I can ensure you that we review all recommendations and many of them have already been added to JECIS!

There are three comments however I would like to share with the community:

• How does JECIS compare to the big E-Commerce Solutions?
• How about Support and Documentation?
• Can I see JECIS in action?

1. How does JECIS compare to the big E-Commerce Solutions?

It is a little like comparing pears and apples. JECIS was not built based on a "tool and feature list". It was never intended to compare features of JECIS with those of ATG or Hybris or Magento or KonaKart and others. The purpose of JECIS is to build sophisticated, but yet exciting commerce experiences using your CMS. JECIS is an API, an E-Commerce framework, which allows marketers (authors) to define commerce-content and transform that content into E-Commerce driven Web experiences. You can build anything, from a simple shop, to reproducing the Amazon site. As long as you are willing to gather and define commerce content and create user journeys, there is no limitation to building any kind of commerce experience.

Therefore, the features between a traditional E-Commerce solution and JECIS are not really relevant. What you want to compare is the process, the effort and the costs to build a commerce driven Web experience. This is were the big advantage of a content-centric E-Commerce framework like JECIS comes into play. Don't hesitate to contact us and let us estimate your commerce-driven project!

JECIS is about a different, modern, content-centric approach to transform marketing strategies into pulse-pounding Web experiences!

To summarize: With JECIS you can use your CMS to build any commerce-driven Web experience. The big difference to traditional E-Commerce solutions is that the responsibility of commerce content is in the hands of marketers (authors), not engineers. Marketers/authors decide and manage content, marketers/authors define and manage store experiences. The developers build the templates, components and functionality to support these experiences.

2. How about Support and Documentation?

The good news is that JECIS does not require a lot of support. If you are comfortable with your CMS (Adobe Experience Manager, Magnolia, Jahia, etc.) you will be comfortable with JECIS.

JECIS follows the subscription based model. When acquiring a license you also subscribe to SLA-0 support (5 business days / 8am to 5pm). In addition we select our technology partners carefully to ensure that JECIS is used following "best practices".

The JECIS documentation is structured into four documents:

• Comprehensive author guide that covers all commerce content management capabilities.
• Author Cheat Sheet - a summary of all out-of-the-box input fields for fast lookup
• A developer guide that explains the API and describes different solutions to work with the commerce content.
• A training guide that walks you through creating a sample Shop, from landing page to checkout.

3. Can I see JECIS in action?

Yes, we have prepared demo sites for Adobe AEM, Magnolia and Jahia.

Don't hesitate to contact me via LinkedIn directly or use the form on jecis.com to request a demo. The presentation usually lasts about 60 minutes and covers:

• Differences between traditional E-Commerce and JECIS.
• JIM - How Authors create and manage E-Commerce Content.
• JECIS - A brief explanation of the JECIS API.
• Demo Site - Walk through a simple Web experience, from landing page to checkout process.

A Note for CMS Vendors

If you have a CMS that uses the JCR Content Repository as storage foundation, let us know! We would love to test and adapt JECIS to run within your CMS solution as well!