Frontend Architecture

Physical invitations with an advanced customizer.

"Build your own understanding and offer help where you can" .

Contributing to the future of Magento front-end, Magento PWA Studio, as an active member of the Magento Research PWA Studio Github team. Contributing code and documentation, and helping developers who get started by responding to Github issues.

Full scale Migration from M1 to M2

We created this module on our first M2 frontend project.

The module can be used to load different themes base on the client device (desktop, tablet, mobile). It uses the template exception system to load a different theme based on the user device. It can also be used to redirect users based on the device they are coming from, for example, if the user comes from a mobile device they can be redirected to another domain.

The project can be found here: https://github.com/EaDesgin/magento2-mobiledetect https://www.eadesign.ro/magento2/magento2-mobile-detect-system.html https://marketplace.magento.com/eadesignro-module-mobiledetect.html

The site design was made by our designers and branding managers. The old version is used only for mobile. We just start working there. The site features special products, special grouped products loaded by ajax. The concept is 100% EaDesign. Lots of extensions and customization's. ERP integration also. In beta for one week or so.

Reusability of individual parts and the maintainability of the code for future phases is one of the ambitious goals in our projects. This talk shows good and bad examples regarding this issue. In frontend the pre-processors like Less / Sass are the most important tools to provide structure and organization.