Principles / The longer argument
How we think.
Digital work crosses language, structure, publishing and engineering. These are the principles we use to make those connections work.
Everything changes.
We change it louder.
Same truth as the serious sites — we just deliver it louder.
Search engines, publishing platforms, AI, frameworks, automation and interfaces are successive mechanisms. The fundamental problem remains information — but who says information has to be boring?
Most digital problems aren't problems inside disciplines. They're problems between them. We don't just understand the gaps. We throw parties in them.
Journalism, design, development, search, publishing, automation, AI — these are not separate kingdoms. They are contiguous territories, and we draw the maps in crayon.
Language is a playground.
Words are a playground as much as they are infrastructure.
Content isn't filler between design and technology. Language is something the system operates on — and sometimes the system should operate like it's had too much coffee.
Writing, journalism, editorial direction, content strategy, linguistic frameworks, taxonomy, terminology. These are not afterthoughts. The words are the interface before the interface. The taxonomy is the architecture before the architecture. The pun is the payload.
When you understand language as a playground, you stop asking "what should the page say?" and start asking "what does the system want to say when nobody's watching?"
Structure makes information executable.
Creativity makes it dangerous.
Solid structure is what lets you take creative risks safely.
HTML, CSS, information architecture, semantics, schema, entities, data structures, APIs, Node, front-end systems, scalable web architecture.
This is not a developer portfolio. This is an understanding that how information is structured determines what can be done with it — and what can be done with it should occasionally surprise you.
The structure is the promise you make to every system that will ever touch your information. We keep our promises. We just dress them in neon.
The interface is where the system meets a human.
And gets weird.
An interface can be weird and still work. That’s the sweet spot.
Design, UI/UX, journalism, visual hierarchy, editorial judgment, human interpretation.
Communication is not decoration. It is the translation layer between machine precision and human understanding. A technically perfect system that humans cannot navigate is a failed system. A beautiful interface that cannot scale is a liability. A weird interface that does both is art.
The boundary is where most projects break down.
Search is what happens when information has been structured well enough to be understood.
And interesting enough to be looked for.
Be findable by being impossible to ignore.
Search is part of the cake. It isn't the bill. It's the reason you baked the cake in the first place.
Search is not the hero. It is the consequence of being impossible to ignore. When language is precise, structure is semantic, and publishing is systematic, discovery becomes a property of the publishing system.
You do not optimise for search engines. You build information systems that search engines can interpret more consistently — and humans cannot stop talking about.
Eventually, a website stops being a website.
It becomes a conversation.
At scale, a site becomes a system. Ours has a personality.
Once information starts moving at scale, the page stops being the interesting part. The personality underneath takes over.
What matters is the system underneath: taxonomy, hierarchy, templates, entities, editorial rules, automation, syndication, relationships between information, and the logic that determines what gets published, where it appears and how it can be found.
The technology has changed repeatedly. The problem hasn't. Whether in media, institutional publishing, real estate, education or large digital environments, the same underlying challenge appears: how to make information findable, consistent, sustainable at scale — and actually fun to interact with.
An acquisition system is bigger than a landing page.
It's a really good story with a form at the end.
A pipeline can have character and still convert.
Information moves through a pipeline. But pipelines can have personality.
Acquisition is not a page. It is a flow. From form submission through delivery and syndication, every handoff is an opportunity for signal loss or signal gain. Or signal distortion, which is sometimes better.
The landing page is just the door. The system is the building. What happens after someone expresses interest is where most organisations leak information, lose context and waste the effort that brought the person there in the first place. We plug the leaks. Then we add a disco ball.
The difficult part isn't any individual discipline.
It's what happens when they bleed into each other.
The interesting problems live in the gaps between disciplines. We play there.
Taxonomy, terminology, editorial logic
HTML, schema, entities, APIs
What the system expresses
AI is another collaborator.
AI is a strange coworker. Feed it good structure and it behaves.
The useful question is whether the underlying information system gives the machine something worthwhile to operate on — and whether the machine gives back something worth keeping.
AI is not a revolution that replaces information, language, structure or systems. It is a mechanism that amplifies them — or exposes their absence. It is also, occasionally, a very strange coworker who suggests things you would never have thought of.
An AI system operating on poor structure, vague language and broken publishing pipelines will produce poor results faster. An AI system operating on precise structure, clear language and robust pipelines will produce outcomes that scale. The machine is only as good as the system it touches. We make sure the system is worth touching.