Since Magento 2.0 launched, working with its numerous innovative features has been a dream come true. With a newfound focus on stability and flexibility, Magento 2.0.’s architecture seeks to attract larger businesses on one hand, while taking the PHP community to the next level on the other. Our Magento developers took the time to highlight some of their favourite features, while explaining how they make their day-to-day easier.
Before jumping into the tech side of things, we invite you to explore a fleshed-out demo of a Magento 2.0 interface, put together by our Technical Director, Zachary Allatt. Click here to get a look and feel of the new platform, as you log in as a fictional client in a made up store.
Now, let’s get technical.
Each module is contained in only one repertoire. A feature such as checkout will be in only one module, whereas with Magento 1, we used to place the logic (block, model, controller) inside the module file, and the display (template) in the App/Design folder. Magento 2.0 centralizes everything, which greatly simplifies developers’ lives.
XML files validation
This used to be frustrating for developers in the past…Often, developers would spend hours debugging and without knowing why. Now, XSD file validation is available with a modern editor such as PhP Storm. If the syntax isn’t right, it will be highlighted in red and the problem will be spotted right away.
Faster, thanks to Varnish
Varnish is a reverse proxy system which serves to unload the server to optimize Web performance. High traffic websites can’t do without this kind of solution: the website would surely crash if it only depended on the website. While it was possible to configure Varnish in the Magento 1 era, it wasn’t native (you had to adapt it). With Magento 2.0, it’s a lot more practical for devs.
Two distinct environments
Another big innovation: the addition of a production mode and a development mode. Now the production mode goes into a pub folder, which isolates the Magento code, which shouldn’t be seen by end users. For security reasons, they should not have access to the sites architectural codes, but to the style, images and design files. This is a common practice on more recent platforms, but which wasn’t yet there in Magento 1.
Did you know that Le Site was Magento 2.0-certified?
Don’t hesitate to contact us to discover how this revolutionary platform will simplify your life!