Bhavin Patel

Hi. I'm a coach tech developer, and I have more than 10 years of experience implementing solutions with Magento and commerce cloud projects. I've worked with various areas, like implementing custom extensions and integrating with 3rd party integrations. I'd like to highlight my expertise in the fulfillment of the order process flow. Apart from that, I have experience with cloud deployment-related things and have implemented projects from scratch using the Magento 2 platform. I've also worked with Magento versions and related to Magento migration. In terms of migration, I've worked on migrating from Magento 1 to Magento 2, as well as migrating data from WordPress to Magento 2. Additionally, I've worked on speed optimization of ecommerce websites in Magento, and I've handled technical aspects related to security, collaborating with developer teams, designer teams, new teams, and client teams. This is a summary of my work experience and expertise in the ecommerce journey. This is my introduction.

So in Magento 2, when we need to sell products in different countries, we need to follow certain approaches. Like, first of all, we need to create a store view for each country and then enable the currency per store view. Once it's enabled, we need to set up the languages for the store view. Based on that, it will be available at the frontend side. During the creation and configuration of the product, we need to do customization at the product level and shape the pricing for country-wise. Apart from that, we also need to take care of the configuration of text rules for each country and set up shipping methods for countries, optimize issue-related stuff as well. Like, whenever we set up a country-wise catalog in our digital store, and also in terms of the frontend pages, such as CMS pages and other static content logs and related stuff. So we need to localize based on that. We need to make sure to sell when we start the actual sale with our different stores. The product will be available based on the localized and country-specific information. By using this approach, we can profile this setup for stores and catalog-related data. And then it will be available in terms of pricing as well as the content of products at the frontend side. Then customers will be able to buy items based on the country they select or when they land on the website. By default, based on geolocation, we can identify and set up the default country. And if they want, they can change countries and then complete the product journey. Yeah. By using that approach, we can set products by country-wise.

In Magento, to provide different advantages and features for CLI level, they offer the different operations. This helps us to directly execute different tasks by using the CLI. The CLI allows us to first install and configure the Magento setup whenever we request. It quickly sets up the environment. Using the CLI, we can enable, disable, install, or uninstall any composer packages and modules. By using the CLI, we also follow daily tasks such as cleaning the cache and disabling the cache. Apart from that, when working with the local environment, we can switch the modes of Magento, like using the develop mode. There are other modes, like when we need to take the site down, so we can set the maintenance mode and when our site is live, we set the production mode. We need to set up the production mode. Using the CLI, we can switch to different Magento modes. Apart from that, we can manage cron jobs using this. When we need to compile our static content, we can run the command and compile and execute the static content. Apart from that, the CLI provides a way to connect to the server and go through any errors or debugging things we need to check and find. This helps us here. By using the CLI, we can do many things in terms of merging the CLI.

Okay. So when we want to create a new custom theme into our Magento front end, we let it change this. So first of all, we need to create the directory as a design frontend. Then within that, we need to define our folder as a vendor, and we need to create the file, which we can say is the theme XML file. And then after that, we need to register our theme. So in that registration BSP file, we need to register our theme, whatever the name we have chosen. And also, we need to mention our parent theme. By defining the parent theme, we can use the built-in features and then customize the changes in our custom theme. And apart from that, in the theme, there is a view XML file. This is mostly helpful in allowing us to define different component-related image sizes, like what size image would be available on the EDP page, BLP page, and then whenever we are showing the products like cross-sell, upsell, related products, and into the frontend side, so that we can set from over there. And also, we can set different things, like we need to bypass any case in terms of minification and related steps so that we can share over there. And specifically for the gallery of the product detail page, so related changes and configurations, we are going to do from that view XML file. And apart from that, the static contents like images, CSS, JavaScript, fonts - related folders, we need to create within our vendor, then theme, and then frontend folder, and all their based on the content, we need to create the folders like assets, and then we need to do it in a modular way. We can able to create and override the existing files for CSS and JS specifically. So these are the basic steps we need to follow when we are creating a custom theme or customizing the layout-related things in Magento 2 frontend.