Learn what it means to treat content as data (not just words on a screen).
To treat content as infrastructure is to stop viewing words as a static piece of text and start seeing them as a foundational layer of the product.
By systemizing content as data, you move toward a model where copy is an integrated component of the product’s architecture. You scale your work. You grow your influence with other teams. And you create more reliable, impactful copy.
This shift is happening now because AI has democratized creation. In a world where anyone can—and does—generate text at scale, the value of content design has moved upstream. Our responsibility lies in defining the guardrails, taxonomy, and logic that give a product its meaning.
To explore this shift, we co-hosted a panel discussion with UX Content Collective on what’s next for content design. We heard from some industry experts:
The panel discussed how treating content as data fundamentally changes the role of the writer from a manual task manager to a strategic architect.
It brought together perspectives from design systems (Dave), internal systems and AI tooling (Chris), and content-first product tooling (Jess), to provide a blueprint for how to start building content infrastructure. The speakers shared practical steps for content designers to exert more influence, from learning technical foundations to aligning work directly with business objectives.
Design has design systems and engineering has components, but text is the last part of product development to be systemized. Treating content as data means systemizing it so we can use it in the same way we do design or code.
This lets us reuse, govern, iterate on, measure, and improve our content.
In turn, this makes product copy, and content design as a discipline, more strategically valuable, too.
"To treat content as data is to understand the fact that it is representative of something, and not just words on a screen," said Dave. He argued that when you write for a system, your strings represent the objects, the metadata, the entire system underneath.
The secret sauce for building content infrastructure? Context.
Chris pointed out an important caveat: "You can only really call it data if you treat it as such... giving it the proper sort of infrastructure and observability... so we can see where this content lives, what the surrounding context is."
Why should we care about content as data—and why now?
By making this shift, content designers can be drivers of the product experience, and make other teams better in the process.
Jess pointed out that with the right system, content and product designers gain a high-leverage position. They can own the product copy, assess adherence, and make tweaks on a larger scale, rather than manually searching and making changes to text. “Everyone is empowered to move closer to business decisions and direct impact,” said Jess.
It opens the door to new ways of working. Chris shared an example where, instead of working in Figma, he’s switched to collaborating with his product design partner in GitHub, where he’s using a Claude Code UX writing skill. Ultimately, it’s allowed him to speed up copy work and meet his product and engineering teammates where they are.
When you treat content as data, AI can run in the background to enforce your brand standards and style guides. Chris suggested that it also opens the door to assessing content in a quantifiable way. An example he referenced: you can use AI to run a series of binary tests and score your content.
Growing your influence as a content designer requires architecting the systems that power your words.
While AI lets you generate content at speed and volume like never before, content design needs to prioritize the underlying system by treating content as infrastructure.
From there, you can use tooling to free yourself from manual work, so you have more time for taste and craft—your ultimate differentiators.
.png)
