Beau Lebens’ Post

Exciting news—Blaze Commerce is now open source! 🎉 After 2.5 years of development, we’re thrilled to open up Blaze Commerce, our headless WooCommerce platform, to the community. It’s been a journey filled with learning, collaboration, and listening to what the eCommerce world needs. If you're a developer looking to get started, check out our Quick Start Guide https://lnkd.in/gNhGFm_m (you can be up and running in 15 minutes!). Store owners, if you’re curious about what headless WooCommerce can do for your business, we’re here to help with tailored implementations. Learn more about why we made this decision and what’s next for Blaze Commerce in the full announcement here: https://lnkd.in/g6hZvZ-E.

Hopefully, everyone's stomach survived Easter and now you're ready to digest more case studies from our ecosystem 😁 As for the first case study of April I'm bringing you a story of Tediber's migration to Sylius. Key points of the project were: 📌 Completing the migration process quickly within a timeframe of 5 months while also making it headless 📌 Creation of specific migration scripts to adapt the WordPress architecture to Sylius 📌 Handling high traffic peaks, especially after significant media exposure 📌 Leveraging Sylius' flexibility to extend existing functions and meet specific business needs easily The full case study is below👇

Is PWA Studio the answer for Magento? Sanne Bolkenstein from Hyva says not necessarily. She joined Talk Commerce to discuss the pros and cons of PWA Studio vs. Hyva. Hyva's focus on native Magento & performance makes it a strong contender. Plus, we talk about MageOS! Check out the full episode. #Magento #Hyva #PWAstudio #MageOS #Ecommerce

Recently, I have seen many of my fellows Shopify developers get really excited about the new 'inline_asset_content' filter in Liquid and don't get me wrong I am too. It's awesome to output in any web page and with a one-liner the content of a SVG, JS or CSS file located in the assets folder of a Shopify project. The thing is that I don't get why this new filter is presented as a game changer for theme SVGs management. Most of the time, there are a lot of SVGs in any website project and I don't want them to pollute my assets folder, even if they are alphabetically ordered (I'd like to keep my scroll wheel working). Maybe am I missing something here? To me, it would be perfect if we can specify the SVGs subfolder in a parameter like this: {{ 'linkedin.svg' | inline_asset_content: subfolder: 'icons' }} Meanwhile, even if I know it is a bit more work, I'll stick to manually taking care of my SVGs markup within a same file and call each of them this way: {%- render 'icon' with 'linkedin' -%} And you? How do you work with SVGs? Do you know a better way to deal with them? Please feel free to share what your thoughts are about all that and let's discuss it!

Scaling WooCommerce for Shark Tank: A Client's Experience What does it take to handle a Shark Tank-level surge on your WooCommerce site with thousands of visitors at once? Here’s a real-life example from one of our clients: 🚀 9000 concurrent visitors over just 15 minutes. 🚀 27 cores and 600 workers used at peak (1000 allocated). 🚀 40GB RAM utilized. After the initial surge of traffic, it leveled off at 500-800 concurrent visitors to about 130 concurrent visitors by the 8PM PST rebroadcast. How We Scaled for the Next Segment: The second segment maxed out at 1500 concurrent users, a significant drop. We doubled resources not knowing what to expect on the second broadcast. Despite this preparation, our server usage never exceeded 10% – a stark contrast to the first broadcast. Key Issue Resolved: Post-analysis revealed a redirect issue with the favicon, causing 8000 unnecessary requests. Fixing this reduced the load. Watch out for uncached 404 requests! 💡 Key Takeaway: Proper resource allocation and quick issue resolution are critical for handling Shark Tank-level traffic on WooCommerce. Scaling WooCommerce for Shark Tank is challenging but totally manageable with the right strategies. Have you ever had a massive traffic surge on your website? I’d love to hear your own site scaling stories in the comments!

Move the platform forward, one step at a time 🪜 Every step you take reveals new or emphasizes existing pain points. The need for subfolders to better organize assets has been felt by developers long before the new inline_asset_content filter has been introduced, and adding 100 SVG files in the mix only emphasizes the need further. There is no such thing as a quick win when you reach Shopify’s scale. Each time you add an ‘and’ to a feature request, you’re forced to solve for more variables which takes longer to solve and thus delays delivering value to your customer. Take this seemingly simple new filter, inline_asset_content. It does just one thing — take content of the file and inline it in the page response. Simple, right? But that file is hosted on CDNs far away from Shopify’s Liquid Renderer, not in DB like Liquid files are. And that file is now a dependency for the Liquid renderer, which is the main player in page response speed (TTFB). And these files can change and invalidate any cached responses at any time. And what do we even call this filter? And Tobi wants this shipped now, not in 2 months. Yes is would be nice to have options to modify classes in the svg, or specify height, or organize your svgs in the assets folder better — but these are nice to have when considering the main problem you’re trying to solve. What’s important here is progress; each precise step removing SOME complexity. Working with native SVG files is simpler than all previous solutions. End of story. Done. Ship it. Inline_asset_content is one step forward, and hopefully the first of many more steps as Shopify’s online store team picks up momentum again. So what’s next? Subfolders in assets would certainly be nice 😜

Shopify Flow - New Run code action 🙌 Get ready to use a new run code in Shopify Flow 🤓 Within the action, you can now write JavaScript code, which returns data into the workflow. This is naturally based on your code and inputs. More possibilities are available with the new run code: 💥 The ability to count the number of certain types of items on a list  💥With complex meta fields, you can now calculate the value  💥Possibility to transform data like numbers and dates so they can be used in conditions If you’d like to give it a go, you can either create your own Flow from scratch or simply use one of Shopify’s Flow templates to use as a test base 💣 #shopify #shopifyflow #shopifyupdates #shopifyupgrades #shopifystore #onlinestore #onlineshop

While #Shopify theme development or #theme customization, we often face this situation where we need multiple liquid statements. There's an example of a correct code 🔥 approach for this. Using a #liquid tag like {%- liquid ... ... ... -%} will save much time, and effort and is the best way to avoid unnecessary syntax mistakes. It will improve your #coding speed 😎 . Especially, if you're using any development tool like #vscode or any other editor. Where you already have some auto-complete plugins and better error-detection support. You can write code like this much easier than a simple online Shopify theme editor. [Recomendation] Use VSCode as the theme editor, and try using Shopify #CLI 😻 much is now recommended (migrate from the theme kit) for your Shopify development journey. If you add Git & GitHub to manage versions of your theme on top of it, trust me you will fall in love ❤️ with Shopify theme development. #shopifyexperts #shopifyplus #shopifydeveloper #shopifypartners #shopifysuccess