4. Introduction
Reason
4
• Customers with ”rich” webshops and websites selling products
• We are an Open Source company, working with TYPO3, Magento and
WordPress
• Content management in Magento: not the best solution
• Selling products in TYPO3: not the best solution
5. Introduction
New project
5
• Long time customer
• Using Magento for webshops
• Using TYPO3 for websites
• Marketeers do miss the possibility to enrich their webshops like in the
websites
• One webshop more “webshop”, others more “website”
11. How we started
Previous version
11
• We did it before with TYPO3 and Magento 1
• TYPO3 renders Magento content
• Checkout pages from Magento
• Problems with SSO, Indexing state of products
12. How we started
Open Source solutions?
12
• Didn’t want to create a “just another TYPO3 Magento integration”
• As MaxServ we embrace open source
• Tried to find an existing open source solution
• Got in contact with Neusta
• Not the same use case and not the same techniques as we normally use
13. How we started
Decision
13
• We will create our own solution
• No “yet another Magento TYPO3 integration”
• Open Source
• Based on the use cases of several webshops
• Scalable solution
15. What are we going to build?
The idea
15
+
• Use the strength of each system
• Let editors do their job
• Make a real integration, not just a wrapper
• Stay as close to core (for Magento and TYPO3) as possible
16. What are we going to build?
Page request flow
16
17. What are we going to build?
Content request flow
17
18. What are we going to build?
Container examples
18
20. What do we have?
Demo Time
20
DEMO
A little demo
21. What do we have?
Open Source Army
21
• Magento - Ben Marks (Evangelist)
• TYPO3 - Mathias Schreiber
• Yoast – Omar Reis (CTO) + Taco Verdonschot
(Community manager)
• MaxServ
24. Are you interested?
Funding
24
• Open source, but we also need to make money
• Would you be interested in help funding the plugins?
• Early access program vs crowdfunding