6. ABOUT ECOMMERCE
NOT DEVELOPER FRIENDLY
NOT USER FRIENDLY
NO EASE OF USE
ABOUT INTEGRATION
ALWAYS DIFFERENT
PARTNERS ARE LOOKING FOR THE BEST APPROACH
29. WE BUILD, LICENSE, SERVICE
& MARKET MAGNOLIA CMS
DEMO
WHAT YOU
WILL SEE IN
THE DEMO
DYNAMIC TEMPLATES
LANDING PAGE
CAMPAIGN PAGE
SHOPPING CART COMPONENT
30. WE BUILD, LICENSE, SERVICE
& MARKET MAGNOLIA CMS
DEMO
WHAT YOU
WILL SEE IN
THE DEMO
CAROUSEL
CURRENCIES
LANGUAGES
CATALOG PREVIEW
CAMPAIGNS APP
31. WE BUILD, LICENSE, SERVICE
& MARKET MAGNOLIA CMS
DEMO
WHAT YOU
WON’T SEE IN
THE DEMO
A FULL INTEGRATION
USER MANAGEMENT
… MANY OTHER MISSING
PIECES
34. Magnolia Public
Magnolia Public
Magnolia Public
Magnolia Author
E-Commerce
Publish
“NO” INTEGRATION
Easy
Two tools for editors
Redundancy (CSS, HTML, Navigation, …)
Sharing assets might be a pain
Not likely to provide good UX
But… if it works for you, it works for me.
AKA IF IT WORKS, IT WORKS …
41. Magnolia Public
Magnolia Public
Magnolia Author Magnolia Public
E-Commerce
REST API
REST Client REST Client
Publish
“REMOTE” INTEGRATION
More work ?
Decoupling, SOA
Uptime, scaling and updates
Clearer SoC in tools
One tool for editors
47. CONCLUSION
NO MATHEMATICAL FORMULA TO DEFINE THE BEST APPROACH
ALWAYS ANALYZE THE BUSINESS REQUIREMENTS
EACH INTEGRATION IS UNIQUE
RE-USE PATTERNS TO SPEED UP YOUR INTEGRATION