Profile avatar
headlessheretic.com
Headless heretic 🔱 Writer. Freelance developer (ecommerce). Sci-fi and whiskey. I talk about headless development, e-commerce and freelancing
78 posts 31 followers 46 following
Regular Contributor
Active Commenter

0 days since I last took down production

Maybe I'm weird, but I've always preferred learning by doing over learning by watching a tutorial video. I don't think I've ever followed a tutorial from start to finish.

Apparently a hot take: If you're already paying an agency a lot of money to do custom development on your theme, you're better off with Hydrogen.

Invoicing day! 💰

Debugging Hydration mismatch errors and having fun Or not

I've been having too much fun with Hydrogen and Sanity to post in a while

Figured out a solution to this. In the GROQ query, you can concatenate the string with an empty string, seems to throw stega off so it doesn't get appended. E.g. 'alignment': '' + alignment

I split my weeks between headless and theme development, and let me tell you, they're polar opposites. One has a great DX and allows for modern dev practices, while the other is extremely error-prone and leads to many headaches. I would quit ecom if I had to work in themes exclusively 1/2

What is going on here? JavaScript, you're drunk!

Trying to see how fast I can rebuild a site with Hydrogen using my recipe collection. The site is already headless, so I can reuse a fair bit. But it uses Chakra and Gatsby on the frontend, and I'm all in on Tailwind. Plus the Sanity schema is a mess and the Studio is V2, so an upgrade is in order

Trying to enable drag and drop for visual editing in Hydrogen with @sanity.io , but not having much luck. I followed the steps here: www.sanity.io/docs/enablin... but I can't seem to enable the drag and drop editing.

Rebuilding a site with Hydrogen this week, with @sanity.io for content. I've missed this setup so much.

Headless provides a better experience for everyone. Why is it even an argument? Sure, there's some a lack of housekeeping, but this screenshot highlights the disparity between modern systems and whatever this is

A few months ago I found a Shopify plugin for Vite and thought it would be awesome. But it just made me realise that the problem with themes is not the tech, it's the DX The plugin doesn't fix any of the underlying issues which makes theme dev such a bad experience

I've set up CI for themes. But I don't trust it. The way Shopify handles content for themes is so clunky

Deploying a theme next week. Fun times. Scared to death I'll mess up the content somehow. This DX sucks

Why would you use a private npm package if you're building for a client? You're only creating problems for everyone, including yourself, down the road.

What are the benefits and potential drawbacks of embedding the @sanity.io studio on the site? I'm still debating which is the better way to go

I'm done being silent maxkarlsson.dev/blog/rise-of...

Another underappreciated bonus of Hydrogen+Oxygen is that you get hosting included. There is no need to sell merchants an additional monthly hosting cost.

I'm a big advocate for using the frameworks and starters developed by the platforms (Hydrogen for Shopify, Catalyst for BigCommerce, etc) because they provide a standard, at least as a starting point, that can be handed over to other devs. Tear down the walls, make headless more accessible

Why did Lorna Jane use Next.js instead of Hydrogen? Genuinely curious. I hope it's not because the agency they contacted used their in-house framework with years of tech debt to deliver a brand-new site

When you build for a client, you're also building for other devs. You don't want to be saddled with an unhappy client that can't go anywhere else because you built a wall around their garden. It will eventually hurt your reputation