AI Engineer World's Fair 2026
Content Is Code
Loading slides…
Read the talk
Content Is Code
AI makes code a practical medium for technical communication, but accurate changelogs, polished videos, and reusable content pipelines still depend on a carefully structured source of truth.
From a talk by Matt Palmer
Before you start: Basic familiarity with React components and pull requests is helpful for the code example and release workflow discussion.
Choosing a medium
Should this explanation be a blog post, a video, or a conference talk? The choice often follows the creator’s existing skills: writers write, video creators record, and speakers present. Code introduces another possibility—a medium for producing the assets through which an explanation travels. Matt Palmer frames its growing accessibility in 2026 as a departure from a world where creating content through code usually required a professional software engineer, whose time was mostly devoted to engineering.
Technical communication explains what problem a product solves. It includes documentation, changelogs, product marketing emails, video, and the broader work associated with developer relations, but anyone can do it. The standard is usefulness to the reader or viewer: documentation for a data access framework, for example, should accurately cover the whole framework, not merely introduce its most visible features.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A changelog starts with knowing what changed
A timely changelog with useful supporting assets depends on something less visible: an accurate product diff. Before explaining a release, someone—or some system—must establish what actually changed. Without that foundation, the work falls to a person combing through pull requests to reconstruct what shipped. Writing the announcement is only the last part of the job.
Once the changes are understood, they can be summarized over a longer period in product updates and emails. The same communication problem also extends beyond text: a homepage can show a product tour instead of a static screenshot. These formats all explain what a product does or how it has changed, using written material, code, and distinct visual assets.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Recreating a product surface in React
Video overlays are a relatively small application of this approach: code supplies an engaging element inside a larger production. The next step is to build the entire demonstration in code. Palmer shows a tour of Conductor made with React and Remotion. He recreated the product surface inside a Remotion scene and used it to walk through a sample user flow. The result is an authored interface demonstration, not a screen recording of the live product.
Remotion’s frame-driven React model makes the mechanism concrete: a component can select the interface state to display from the current video frame. A minimal illustrative scene might move a sample workspace from a preparation screen to a review screen:
tsx
import { AbsoluteFill, useCurrentFrame } from 'remotion';
export const WorkspaceTour = () => {
const frame = useCurrentFrame();
const reviewing = frame >= 90;
return (
<AbsoluteFill
style={{
backgroundColor: '#111827',
color: '#f9fafb',
padding: 64,
fontFamily: 'sans-serif',
}}
>
<h1>Sample workspace</h1>
<nav>Prepare → Review</nav>
<section>
<h2>{reviewing ? 'Review changes' : 'Prepare changes'}</h2>
<p>
{reviewing
? 'Inspect the proposed update before merging.'
: 'Describe the update you want to make.'}
</p>
</section>
</AbsoluteFill>
);
};
Here, the frame changes the rendered scene; it does not execute a product operation. This is the basic distinction that lets a recreated interface become a controllable video asset.
Palmer describes his tour as a prototype: it is a little buggy, and the flows are not fully worked out. His expectation is that this kind of production will become normal. Coming from data engineering, then leading DevRel at Replit and, at the time of the talk, developer experience at Conductor, he describes the broader change as content shifting left toward code as the source of truth.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
From handcrafted assets to scarce engineering time
Palmer divides content production into three eras: handcrafted assets, expensive code, and inexpensive AI-assisted code. In the handcrafted era, the available levers are time, money, and skill. You make the asset yourself or hire someone with the expertise you lack—an agency or a professional motion graphics creator, for example. Personal effort eventually runs into the limits of the working day.
In the second era, code and cloud infrastructure are mature, but engineering becomes the bottleneck. Palmer associates this with the zero-interest-rate, or ZIRP, period: organizations pay heavily for engineers, and producing sophisticated assets requires access to their time. The supplier changes from an agency to an engineer, while the dependency on scarce expertise remains.
Robust documentation and polished websites compete with other engineering priorities. Palmer dismisses the earlier low-code website services as inadequate for the quality he wanted; in his account, a good website still needed a front-end engineer. That opportunity cost also explains his view of Remotion’s earlier limited adoption: the framework existed, but few people had both the time and the role of a content engineer. This is his explanation of the adoption pattern, rather than a measured usage history.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
TypeScript becomes a creative medium
In the third era, more of that production spending goes to providers such as Anthropic or OpenAI. Claude can help create videos, documentation, websites, and motion graphics. But access to generation does not guarantee a good result. Palmer emphasizes an engineering mindset and an understanding of the systems involved as the means to produce high-quality assets.
For Palmer, code or code generation is now the fastest way to prototype videos, websites, slides, images, and other creative assets—a practical judgment without a timing comparison in the talk. Preparing this presentation led him to a surprising conclusion: his favorite medium was TypeScript. Apart from recording himself and writing, he made the ancillary assets with React or TypeScript.
That preference did not come from deep prior expertise in the stack. His background is Python and data engineering, and he readily admits that his TypeScript is not especially strong. Nevertheless, React, TypeScript, CSS, and HTML have become the tools he needs to learn because they give him a route to high-fidelity visual assets. The medium follows what he can now produce with assistance, rather than only what he already knows how to make by hand.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Structure is the expensive input
If code becomes inexpensive, what remains expensive? Palmer declines the familiar answer of taste and points to structure. Producing a polished asset depends on maintaining the inputs that constrain it: a well-organized codebase, consistent brand guidelines, and design tokens kept distinct from front-end and back-end implementation. Those inputs give repeated generations a shared foundation instead of requiring each asset to reconstruct the design system.
The same discipline applies to the record of product changes. Clean pull requests need tags and useful descriptions. A feature should be distinguishable from a bug fix, and a reverted pull request should not disappear from the organization’s understanding of what happened. Palmer says none of the organizations he has worked at maintained the full discipline he describes. Internal documentation matters for the same reason: even capable agents need documentation or skills that explain how to accomplish the work.
These practices support different parts of the output:
| Structured input | What it helps preserve |
|---|---|
| Brand guidelines and design tokens | Consistent visual decisions |
| Separated code responsibilities | Clear sources for different concerns |
| PR tags, descriptions, and revert history | An intelligible account of changes |
| Internal documentation and skills | Knowledge needed to perform the task |
Together, they explain the difference Palmer draws between generic AI purple gradients and professional polish: the generated artifact inherits the quality of the material and instructions available to it. He connects that care to conscientiousness.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Care moves from making to checking
Conscientiousness means being meticulous, careful, and guided by a sense of moral or professional duty. In this workflow, its practical expression is checking that the outcome matches the intended result. As model capabilities improve, Palmer expects exceptional technical skill to become less decisive than the care given to those expectations and their fulfillment.
That is why he connects AI’s rewards to organizational excellence and structure, including the structure of AI skills themselves. A generated skill is not automatically useful: its contents and organization need attention. Palmer criticizes skills produced without that care, then returns to the assets shown at the beginning. He attributes them to design tokens, structured code, and structured assets, describing production without those inputs as “exponentially harder”—an expression of difficulty, not a quantified scaling result.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Toward declarative content pipelines
Content can move toward the codebase only if the codebase is a structured source of truth. Moving production upstream does not remove the need for accurate product knowledge, consistent design, or operational instructions. It puts those responsibilities inside the process of creating software. The code can then serve both the product and the communication derived from it.
Palmer predicts that the best-communicating teams in 2026 and beyond will be the ones that instill discipline and rigor in software creation and bring content closer to that work. He calls 2026 the year of the creative technologist in DevRel and forecasts 2027 as the year of the content engineer. The distinction points toward a more systematic production role: building declarative, robust pipelines that produce walkthroughs, documentation, screenshots, and product updates. Previously manual assets become outputs created through code and React with AI assistance, grounded in the same structured material that defines the product.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
From the talk
Learn how React components, frame numbers, and composition metadata define a programmatic video.
Introduction to Conductor's coding-agent workspaces and review workflow.
Further reading
Official guidance for installing and using Remotion skills with coding agents to create, preview, and render videos.
Generate release summaries from merged pull requests and organize them with labels, categories, and exclusions.
Palmer's public post presenting a changelog concept created with Remotion and Replit.
Full transcript
Loading transcript…