Madison PHP - Getting Started with Magento 2

Editor's Notes

• #2: Greenroom
• #3: WhoamiMagento since 2008 PHP since 2000 Linux since Slackware 2.x days (1994)
• #7: Over 736 websites on Magento 2.1 out of nearly 4000 active m2 sites Magento 1 & Magento 2 have over ¼ Million websites running it.
• #9: HTML5 CSS3 (LESS CSS pre-processor) JQuery (primary JavaScript library) RequireJS (library that helps load JavaScript resources on demand) Third-party libraries (Zend Framework 1, Zend Framework 2, Symfony)
• #10: Better browser caching Etag support to control browser cache Js resource bundles Minification of css,js,html Removal of inline js
• #11: 10 minutes – go through frontend, and admin.
• #14: The resource roots are marked wrong I think: App/code/Magento Lib/internal/Magento
• #16: This is just a select few of the design patterns used throughout Magento 2 and Magento 1 Magento employs the MySQL relational database management system, the PHP programming language, and elements of the Zend Framework. It applies the conventions of object-oriented programming and model-view-controller architecture. Magento also uses the entity–attribute–value model to store data.- Wikipedia
• #17: Single Responsibility – classes should only have 1 function Open Closed – Class open for extension, closed for modification Liskov Substitution – Quakes like a duck, but needs batteries…. Wrong abstraction (not a duck) Interface Segregation – client should not be forced to depend on methods it doesn’t use Dependency Inversion – highlevel modules should not depend on low-level (this is DI)
• #18: Single Responsibility – classes should only have 1 function Open Closed – Class open for extension, closed for modification Liskov Substitution – In mathematics, a Square is a Rectangle. Indeed it is a specialization of a rectangle. Square setWidth/height fails when inheriting from rectangle. Interface Segregation – car should be a client of vehicle Dependency Inversion – highlevel modules should not depend on low-level (this is DI), think power plug or
• #19: We come back to this in a little while during the Configuration part of the quick guide.
• #23: Best practice: Use service contracts to communicate to the domain layer by passing data types through strongly typed objects. This practice can help you avoid the need to replace presentation layer code when replacing business layer logic.With API being used as a “core concept” the web api’s have been moved to the “WebAPI”, which has its own service layer. First we will talk about the request flow and controllers
• #24: Single controller per action Web users interact with components of the presentation layer to select actions that initiate calls to the underlying product layers. Presentation layer components make calls to the Service layer, which in turn sends requests to the Domain (or business logic) layer. Best practice: Typically, the way it accesses the Model is through service contracts.
• #26: Next we will talk about the service layer
• #27: Debugging is more difficult Interfaces are more concrete and may be harder to work with. Service contracts are just interfaces.
• #28: Repositories uses registries to store previous responses as well, which can lead to really solid data caching.
• #29: Repositories provide access to database through a service api Ensures ability to upgrade, and or migrate datasources etc out from under the api.
• #31: Domain layer is next. We will be discussing models and modules.
• #34: OM implements:  Get() returns the same object create() returns a singletonBest practice: request only interfaces, not concrete classes.
• #35: This all fits with the front controller pattern we discussed before.First bootstrap is called, then bootstrap creates the objectmanagerfactoryObjectManagerFactory creates the objectManager The objectmanager than creates a factory which in turn creates the injected objects.Note that a lot of this is compiled in var/generation and can lead to confusion
• #39: Blocks can generate dynamic content and can contain named child view elements that are similar to arguments being passed in. (Theas attribute holds the child view element names for the parent block to reference them) Containers collect an ordered group of children view elements. Presentation code typically calls service contracts, particularly for a store front. The View layer calls code from the Model to get information about the state of the application
• #42: Magento allows class overrides on nearly everything. Magento’s Event/Observer mechanism is pre-built into most business logic. You can add more if you need. Designs/Templates have a fallback system that allows you to utilize any of the core layouts and templates, or replace them in your current design. Even the index.php? Outside of development and very rare implementations you should never need to edit this.
• #44: Shared Libraries: For instance CM_Redis, or a payment gateway that are included with core Magento.
• #50: Module should actually be called “component” as it is referred to by the documentation.
• #57: These are actually called components now, very confusing change. We will be covering a few of these in a slightly different order.
• #58: At this point you have a “working” module. You will be able to see it in the setup_module table in the database and in the app/etc/config.xml/Registrar::register just adds the path of the module to ComponentRegistrar which is used later by the object manager There can also be a composer.json here, and will be if you need dependencies on other extensions etc.
• #59: One class per action.
• #61: Controller calls page factory, creates page, and returns object.Note, this will not work at this stage, we still have to add a block and view.
• #62: All controllers must inherit \Magento\Framework\App\Action\Action which will have the dispatch()  (used to wrap logic)It’s important that every controller extends this class to inherit needed methods and to allow front controller to call dispatch method (which will call execute method). Action also has Forward and Redirect methods (forward is internal) Dispatch calls the controller::execute passing back the result/response
• #63: Before talking about the view, lets look at how the rendering flow looks. By this time most if not all of the work to load the required models, components, etc all done. Layouts are loaded, merged, blocks are generated along with children and elements of those blocks.
• #64: La
• #65: There are three basic parts of a layout/view.
• #67: Service contract interfaces are outside the scope of todays tutorial even though this is the right way to do it.
• #68: Schema installation only on install, the first thing your modules does is perform a schema installation by executing its installation class. Schema upgrade If your module already has an earlier version installed in Magento, then it will perform a schema upgrade instead of an installation. The purpose of a schema upgrade is usually to update the database structure or apply patches.Data installation only during the initial installation of your module. The purpose of data installation is usually to populate the database with initial data for your module. Data upgrade The purpose of this stage is usually to fix data that has been corrupted or populate a new data field from a schema change.
• #73: Altering templates is another way to change the page layoutblock: A block is a unit of page output that renders some distinctive content – a piece of information, a user interface element – anything visually tangible for the end-user.  Container: A container renders child elements during view output generation. b/a attrib: To help you to position elements in a specific order suitable for design, SEO, usability, or other requirements, Magento software provides the before and after layout attributes. Action: Used to set up the execution of a certain method of the block during block generation; the <action> node must be located in the scope of the <block> node. referenceBlock: used to target blocks/containers Argument: passes in arguements
• #79: Overriding Layouts is not recommended.
• #85: Collections implement: IteratorAggregate and Countable Model Collections as arrays that also have methods attached.
• #91: Permissions can be an issue. See devdocs for more info
• #92: Permissions can be an issue. See devdocs for more info
• #93: Customize allows you to set default timezone, currency, languages and modules
• #104: ../../../vendor/phpunit/phpunit/phpunit \ testsuite/p
• #105: ../../../vendor/phpunit/phpunit/phpunit \ testsuite/p
• #110: Css:  ecommerce business goals according to best practices Fed: theming components and the ability to modify the user interface according to best practices No Magento 2 Certification yet except Trained Partner Program.
• #117: N98: customer, admin, db, index, cache, config values, system, cron, module versions, and on and on and on Frontools: Does some pretty amazing frontend development tasks, and can be used in the deployment pipeline. Commercebug: controller, module, crud, collection, blocks,layouts,events,observers, some system tasks
• #120: Join the #realmagento community, we need more developers and it a great bunch of people from all over the world. Once your in, you will never want to leave!
• #121: Most of all thank you for attending.