32 years old web developer and/or alleged person? I have convinced myself that I know what I am doing when it comes to development. ASD focused on Shopify stuff
Pennsylvania, USA
Joined August 2011
- Tweets1.2K
- Following833
- Followers192
- Likes5.3K
Moving brand-side when things like Editions are released for Shopify I get to look and see what specific items fill gaps "we" have now. In agency, I had to think about every shop, current tickets / past tickets where we had to be hack-y or say something was just more trouble than it is worth. However, I'm still in the mindset of "share what I learn to those who it could help". I sent out a little "sorry to bother you so soon" text to some former co-workers and let them know some of the items I think they should really take a look into. The new "product update" trigger for Flow is a game changer for one of their clients.
The Fall 2026 Editions site is up (shopify.com/editions/fall202…) and now I get to scour the site not for the easter eggs, but to find items that I wasn't able to find out about already.
Very nice and exciting items. Custom fields in checkout and account with possible post sign in forms. Variant editor gets a refresh. Native additional fees that cannot be altered by the customer via hacky methods.
Oh boy there are a lot of things. Very nice, very exciting. There are some items I haven't seen surfaced in the docs yet I think. For example the tailwind bit is mentioned but AFAIK only operates in Canvas, and I cannot find anything yet in the docs about it regarding config/styles.css.
Already seeing some items I haven't seen before. @AlexHooper78640 had found some docs on custom fields coming at some point to checkout: help.shopify.com/en/manual/c…
Agency life ended on October 23rd 2026. Since February 5th 2018 I have been living the Shopify partner agency life and I have been involved in the development of roughly 27 Shopify Plus stores, and a few non-Plus. I have decided to pivot over to direct brand employment where I can put all of my effort towards a single business. I already have quite a list of things to review and take care of, which is very enjoyable for me!
Under 6 hours left of my employment at Revyrie Commerce before I move on to my next role on Monday. I am working on some final handoffs and I feel like I'm still missing a lot sometimes when I consider my weird knowledge, but I wanted to check some git stats. For one major client repo, 4445 out of 6878 commits are from me attributed spread between 3 different work e-mails. I have worked with some of these shops for a bit over 4 years spread between 3 different companies. Wild.
25 hours of Agency time left, realistically 19 hours workable time. Still a pile of things I want to do and some I have to do. Have to get pushing things up to the Notion of the ocean.
My last day of agency work is on Friday and I still have many things I wish to somehow complete or provide enough detailed ideas on. It just means I do my usual “no sleep” routine for the next 44 hours. Easy.
I promise I'm getting on those posts. I have to set up custom apps and then write the content. I may have to branch off and forward to my Plus development store for some of these.
I'll update this as I can, here is the current code from the Canvas theme I am working on for crggr.com
github.com/MatthewRCrigger/g…
Does Canvas generate invalid schema, or just something we don't have access to yet that blocks the Shopify CLI?
You can download a Canvas theme via CLI, but when I try to push it up I get errors for invalid `visible_if` conditions. The generated `visible_if` is attempting to check a compiled value that is set in the main `{% liquid %}` chunk, and not an accessible setting.
When you re-upload a Canvas theme, it loses the "Canvas" badge if anyone was curious. The code can be expanded on and all, you can re-implement whatever you need but expect 0 theme editor support unless you go back to Sections. We knew this wasn't going to work but I like to poke around
How to transfer canvas builds between stores!
Optional?: Upload any used assets over to the other store. Update any direct product / collection / metafield links to ease the transition.
1. Use CLI to download your Canvas theme
2. In the other store, start a basic "blank slate" Canvas
3. Use CLI to push your Canvas theme from Store 1 into the "blank slate" Canvas theme in Store 2.
You have now transferred your Canvas build across shops.
Checking every day until my actual personal production Shopify site gets access to Canvas so I can move my build over. Still nothing.
Tonight I asked Sidekick in Canvas "Let's try to recreate MacOS but in my GRID Design System" with some notes. It tells me "Yeah this sounds pretty kick-ass man, lets see what we can do".
I'll circle back.
Canvas as we know has no support for App Embeds. So the really dumb thing I have done is find app embeds in a live theme, I just copy the SSR injected code, and I have been pasting that into a new `Third Party Integration` metaobject that I have looped in the Canvas code. I haven't asked Sidekick to do it, you can just use CLI to download your Canvas theme, make code edits and push it back up. So the `Third Party Integration` is risky since it's just "throw in some code, set some settings for delays and all" which opens it up to pasting in bad stuff. But it's what I gotta do.
I haven't figured out anything for custom liquid yet.
We were never meant to see Canvas code. Sidekick how did you do this. Why did you do this. I get it wants to try to align the columns, and maybe it looks better in a Sidekick's computer vision it must have. But I feel like this is a personal attack.
Duplicate a Canvas theme, pull it with CLI, edit it with CLI and push back up to that Canvas theme and you still retain Canvas. Pull a Canvas theme, push it as a NEW theme, and you no longer have Canvas and you're back in the "good luck buddy" theme editor that has no idea what the hell you're talking about in your block-loaded liquid templates.
We knew this.