Filippos Dematis’ Post

If you or someone else is making changes to your Shopify theme's code, always do this: Add a specific comment, to let you easily find them in the future. If you don't do that, you'll have no idea what custom code to copy when you want to upgrade your theme version. Same for when you get a different theme. For every place in theme files where you add code, write a comment above: {% # Custom code %} When you edit a line of code, comment it out and do the same. {# Custom code #} {{ my_new_code }} {% comment %}{{ my_old_code }}{% endcomment %} You can also add information about what feature the code implements, or what other locations are relevant. For example, the section schema JSON, which doesn't allow comments. When you do want to migrate, download the theme to your device and search for the comment you added. #shopify #shopifyplus #ecommerce

yes exactly, if there is a minor upgrade you can pick the code according to your need from the upgraded version. otherwise it will be just waste of time and money.

Reminder: when there's a new Shopify theme version, 99% of the time it's completely okay to skip upgrading. Most stores have a lot of custom code on their theme already. So the upgrade can't be applied automatically. Instead of the huge development effort to merge the custom code into the new version, do this: Go to the theme's page, and look at the "Release notes". If you do see a change that's necessary, then have your developer merge that change only. It's a lot more practical. A lot of people think that when adding custom code to the theme, everything will automatically sort itself out in the future. It's not like that, and it's a cost that comes with running a business based on software. #shopify #shopifyplus #ecommerce

There's a catch-22 with paid Shopify theme trials. To buy it, you should review its code. To review its code, you need to buy it. Why should the code be reviewed? An e-commerce business won't scale without a proper codebase. This has to do with both income and costs. I've seen horribly developed themes that are sold for $400. And I've seen the exact opposite - excellent pieces of software that make extending them a breeze. The problem? When you trial a theme, you're not allowed to see its code. So you can't make a proper decision on whether it's a good theme or not. You only rely on: - Reddit (where you might get bad advice). - Public repos where devs accidentally uploaded the store's theme (and it's probably altered). - Inspecting the site (but you can't see the Liquid code). - Previous experience (but you'll need to pay for "bad" themes). - Getting it from someone who sells pirated themes. Obviously the theme devs don't want the code publicized. But there should at least be a way to get a refund if you find that the code is problematic. This can be proven in a lot of cases. #shopify #shopifyplus #ecommerce

👨🏽💻 To whoever is working with Shopify functions, I just released a VS Code extension that calculate the query cost of the opened function input, I thought someone else could need it. https://bit.ly/4dcUmEE #Shopify #ShopifyFunctions #vscode

Enhance Your Shopify Store Experience with Custom Quick View and Upsell Features! 🚀✨ Excited to share our latest development on a Shopify store! We've implemented a Quick View option, allowing customers to view product details instantly without leaving the current page, enhancing the user experience and reducing browsing time. 🛍️ Plus, we’ve added a powerful Upsell Feature that showcases related or complementary products, encouraging customers to explore more and increasing the average order value. 💡💸 All of this was made possible with custom coding, tailored to meet our client’s unique needs. If you're looking to upgrade your Shopify store with advanced features, let us help you make it happen! 🚀 #ShopifyDevelopment #EcommerceSolutions #QuickViewFeature #UpsellStrategy #CustomCoding #ShopifyExperts #dvlp.studio

New to Shopify Flow: `console.log` for more efficient debugging of your code! Debugging can often be challenging, especially if you want to dig deeper into your Shopify store's code. But We have great news for you: Shopify Flow has expanded its functionality and now allows you to use `console.log` in the Run code action. This means that you can now use `console.log(“foo”, order)`, for example, to monitor values directly in the workflow log during execution - a real game changer for anyone taking their shop to the next level want! 👉 Why is this such a win? It's simple: You receive direct feedback in the log about what is happening in your code. This makes debugging much easier and helps you identify and fix sources of errors more quickly. By the way. What is your favorite flow that you use regularly? #shopify #shopifyflow #ecommercetips #onlineshop #onlinestore #shopifyupdate

Shopify going the extensibility route is a great thing. It allows you to stay up-to-date without getting stuck in outdated versions. I tried to explain why this is important in a short video, using the example of the checkout. PS: The video here is just a snippet, you can find the full explanation here: https://lnkd.in/emHNA4kG Feel free to reach out if you have any questions! #shopify #extensibility #checkout

Shopify launched a number of new dynamic sources for themes. Here's why this makes managing the store much easier: Let's say you want to change where the product description is shown. For example, you need it on an image-with-text section. The only way was to write Liquid code. You couldn't use any section or block setting and show it as a dynamic source (the small icon that links dynamic instead of hardwritten text). Now, you can use any rich text field anywhere on the page. Same for some other fields and settings, like product featured image, collection description, blog content, etc. This makes infinite layouts possible, without writing any code. To test which fields you can use, open any section or block setting and click on the Dynamic sources icon. #shopify #shopifyplus #ecommerce