Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


The Magento Way

This presentation gives you an idea about how magento works, and what it's good for.

Zsolt Molnár

on 7 March 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of The Magento Way

The Magento way Name: Zsolt Molnár

Before Inviqa:
- TTL of myVIP.com

Magento projects:
- Warner artist webshops
- Dreams.co.uk
- Smythson.com
- Ideal Shopping

Contact info:
twitter: zsotyooo
linkedin: linkedin.com/in/zsotyooo eCommerce
Enterprise Community edition MVC Magento MVC Open Source
eCommerce platform
based on Zend Framework (PHP)
Originally made by Varien
Owned by eBay
Integrated API (Rest, SOAP)
Community and Enterprise editions
Magento go Cloud hosting Commercial license
Magento Support
Private sales
Store staging / merging
Gift card
Store credit (reward)
Store level ACL
Admin log
SOLR integration
Full page cache
14 420 USD Enterprise OSL v3.0
Magento forums
Basic modules
0 USD Commercial VS MVC
EAV data structure
Loads of Events
Factory, Singleton, Registry
Iterator, Object pool, Lazy load
Prototype, Service locator, Adapter
Configuration based architecture
SOLID principle Design SRP: Single responsibility principle
OCP: Open for extension / closed for modification principle
LSP: Liskov substitution principle. Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program
ISP: Interface segregation principle. Client specific interfaces are better than general.
DIP: Dependency inversion principle. Depend on abstraction rather than concretions EAV Directory Structure codepools 3rd party extension code pool core extension code pool our extension code pool design templates, translations and layout config local config, and global module config files global translations core js libraries static files design specific css, js files logs, reports, file cache, ... company controllers module = extension block handlers helpers backend models module backend config files install, upgrade and downgrade scripts Config app/etc/modules/MageTalk_HighlightMenu.xml app/code/local/MageTalk/etc/config.xml example code snippet I. Theme directory structure Layout XML app/design/frontend/base/default/layout/page.xml app/design/frontend/default/default/layout/hellokitty.xml app/code/local/MageTalk/etc/config.xml Why Magento? Very powerful, flexible and reliable
Great Community
Wide range of extensions
Professional templating system, wide range of community themes
Language support
Multiple websites, and stores under one Magento instance
Wide range of reports: Sales, low stock, inventory, search
Best SEO support
Different product types (Simple, Configurable, Grouped, Bundle)
Product relations
Promotions (Catalog, Cart and Discount codes)
Built in Wishlist, and Compare product
Built in CMS (pages, and blocks)
Built in Google checkout, Paypal
API for almost everything
Various Caching solutions
Easy to install and customize a simple Magento store for your uncle. Why Not? More serious modifications require a certain level of understanding ? Using in template: Using in Controller: Using in CMS page/static block: {{block type="core/template" template="cms/insertthis.phtml"}}
Full transcript