Downloaded 28 times
Uploaded byBen Marks
Magento 2 Development Best Practices
The document outlines best practices for Magento 2 development presented at ZendCon 2016, emphasizing the importance of understanding the framework's MVC structure, proper installation methods, and the coding standards to follow. It encourages developers to leverage existing components, utilize dependency injection, and maintain a solid testing regimen while being aware of different modes of operation. Resources and tools like Docker, PHPStorm, and community support are also suggested for improving the development process.
More Related Content
![Magento 2: New and Innovative? - php[world] 2015](https://cdn.slidesharecdn.com/ss_thumbnails/talk1-magento2newinnovative-151119210353-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
![Fundamentals of Extending Magento 2 - php[world] 2015](https://cdn.slidesharecdn.com/ss_thumbnails/talk2-fundamentalsofextendingmagento2-151120140930-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
![Magento 2 Dependency Injection, Interceptors, and You - php[world] 2015](https://cdn.slidesharecdn.com/ss_thumbnails/phpworld2015-magento2talk-151118174734-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Magento 2 Development Best Practices
![php[world] Magento101](https://cdn.slidesharecdn.com/ss_thumbnails/phpworld-magento101-151118144537-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
Magento 2 Development Best Practices
- 1. @benmarks ZendCon 2016 Magento2 Development Best Practices
- 2.
- 3. @benmarks ZendCon 2016 What’syour first M?
- 4. @benmarks ZendCon 2016 HaveProper Expectations • M1 != M2 • M1 expertise is helpful, but not imperative • Framework + Digital Commerce Application • Open Source
- 5. @benmarks ZendCon 2016 Knowthe Basics • Own MVC framework, own ORM • PHP + XML + PHTML • Composer • PSR 1-4 (2*) • Tests (unit, integration, functional) • Native FPC. Many caches & indexes.
- 6. @benmarks ZendCon 2016 Havethe right setup • Local environment, or… • …Virtualization: Docker* & Vagrant • Use an IDE. PhpStorm is great. • Step debugger • Documentation: devdocs.magento.com • PHP 7!
- 7. @benmarks ZendCon 2016 Installthe Right Way • Archive or Composer (installs under ./vendor) composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition • Contributing (installs under ./app/code) git clone github.com/magento/magento2 (PRs: -b developer - not stable!) • Sample data bin/magento sampledata:deploy bin/magento setup:upgrade
- 8. @benmarks ZendCon 2016 Prepareto develop • Enable Developer Mode bin/magento deploy:mode:show bin/magento d:m:set developer • Disable onl bin/magento cache:disable config bin/magento cache:flush config
- 9. @benmarks ZendCon 2016 UnderstandModes • Developer mode • Static file materialization is not enabled. • Uncaught exceptions displayed in the browser • Exceptions thrown in error handler, not logged • System logging in var/report, highly detailed. • Production mode • Deployment phase on the production system; highest performance • Exceptions are not displayed to the user -- written to logs only. • This mode disables static file materialization. • The Magento docroot can have read-only permissions. Default Mode: just no.
- 10. @benmarks ZendCon 2016 Knowyour Job Scope • Customizations may involve: • New functionality • Changed functionality • Thematic changes
- 11. @benmarks ZendCon 2016 RegisterWisely • Framework convention for registering components: register.php & composer.json • Modules • Themes • Libraries • Langage Packs
- 12. @benmarks ZendCon 2016 UseOthers’ Work! • We went to the trouble to make M2 work with Composer • PSR 1, 2, 3, 4 • Leverage the effort of others! • marketplace.magento.com • https://packagist.org/search/?q=magento%202
- 13.
- 14. @benmarks ZendCon 2016 Followcoding standards • Code demarcation standard • PHP coding standard • JavaScript coding standard • jQuery widget coding standard • DocBlock standard • JavaScript DocBlock standard • LESS coding standard • HTML style guide devdocs.magento.com/guides/v2.1/coding-standards/bk-coding-standards.html
- 15.
- 16. @benmarks ZendCon 2016 Decouple! •Upgradeability and testability are essential • Use composition (constructor DI) • SPI - extension points (events, interfaces) • Core can be a good reference • @api - Use, don’t extend
- 17.
- 18. @benmarks ZendCon 2016 UseInterception before, after, around Plugins
- 19.
- 20.
- 21. @benmarks ZendCon 2016 BeAware of Generation • Depending on technique, and MAGE_MODE, class definitions are generated from DI settings + definition • Developer: normal step debugging • Production: check ./var/generation for generated classes
- 22. @benmarks ZendCon 2016 UseUI Components • DRY system for data templating • “Easy to use” • Define data source, and go! • Example
- 23. @benmarks ZendCon 2016 Use/extendCLI tool • bin/magento - extendable, one-stop shop for developer functions
- 24.
- 25.
- 26.
- 27.
- 28. @benmarks ZendCon 2016 UseYour Friends • Alan. Storm! - @alanstorm - alanstorm.com • Alan Kent - @akent99 - alankent.me • Magento SE - magento.stackexchange.com • DevDocs - devdocs.magento.com • Marketplace - marketplace.magento.com
- 29.
- 30. @benmarks ZendCon 2016 Resources •PhpStorm + XDebug + Virtualization • Docker: MageInferno hub.docker.com/u/mageinferno/ • Vagrant: github.com/paliarush/magento2-vagrant-for-developers • Laravel Valet • n98-magerun • Dev toolbars: • Inviqa: github.com/inviqa/MX_HelperBar • Alan Storm’s Commerce Bug: store.pulsestorm.net/products/commerce-bug-3
- 31.
- 32.