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.
Oh boy this is really cool. crggr-plus.myshopify.com, password "MCP EOL."
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.
If you want to experience hell, duplicate an OS2.0 theme in Canvas that has 612 and counting templates. IYKYK. Canvas seems to take a minute or two loading up the template. Excessive file count is the bane of theme duplicate, pushes, and pulls. The current theme takes like a minute or so to duplicate it's a chore. Maybe 30 seconds with CLI.
Don't @ me, I'm working on a fresh build that consolidates a lot of that with CMS friendly metaobjects and metafields, currently down to 244 due to custom page and article templates I have yet to find a "feel good" solution for.
If we're going back to .liquid templates for the best Canvas experience, we're going back to third party integrations in the theme code again I guess.
On the subject of Canvas and all of that, it looks like we're still not able to just use `config/styles.css` all on our own, if that was ever an intention. Canvas will have that file defined and then you see an assets/styles.min.css that is used in the theme. So far I can't get CLI to just build the min for me. Oh well. It isn't documented anyway.
Working with Canvas on a development store, crggr-plus.myshopify.com, storefront password is "MCP EOL.", this only has the default products Shopify can supply you with, no metaobjects or metafields yet. Just messing around with Sidekick.
I pull down the code every now and then to give it a look and see if anything is worth applying to my non-canvas theme for my personal.









