Write code. Not marketing hotfixes.

Hello {engineer_who_needs_rescuing} 👋

You're probably reading this in between notifications about "urgent” but simple website front-end fixes that stop you from ever getting to the part of your site where you can make a REAL difference.

I know those moments well, so I’ll keep this quick.

None of us got into engineering for this. 

We signed up to solve complex technical challenges. To build things that matter.

Instead, we’re frustrated and so are our mates in marketing. They’re tired of developers telling them stuff can’t be done as quickly as they need.

And we’re sick of not being able to get the work done as the backlog grows, our time sucked up by adding more processes to manage project work while listening to complaints from all the teams that are blocked.

It’s a motivational drain that puts strain on working relationships, and often results in talented people leaving.

I've spent enough time as an engineer to know that adding another platform to your tech stack usually means adding another set of problems. 

But avoiding that challenge is exactly what’s driven the direction of our engineering at Squiz.

We’re here for the developer and the marketer, so we set out to build a system where marketers create and manage websites independently, within technically-governed boundaries.

Where component architecture enforces clean separation of concerns at the framework level – yes, actual separation of concerns, not just aspirational comments in the codebase.

Where your deployment pipeline won't get clogged with emergency website CSS fixes because design systems handle that automatically.

Where integration patterns keep your codebase clean and maintainable.

This isn't about adding another system to maintain.

It's about getting back to solving interesting technical problems (instead of playing whack-a-mole with broken marketing plugins).

If you want to dig into our documentation  jump in here. You might also find this security doc useful, because we both know that's the first thing you'll want to check.

If you're curious about how we actually pulled this off – and want to verify I'm not just another suit making bad promises about technical debt – grab a coffee with me (in-person or virtual, whatever works).

We can dig into the architecture, look at our design decisions, or you can just grill me about our security.

Cheers,
Greg // CTO

P.S. If you're wondering why our own marketing team actually let me write this, it's because they're too busy shipping campaigns without engineering tickets. Imagine that.