How to Build a Website for Browsers and AI Agents From a Shared Content Model
The Walden Robotics website uses 19 reusable content components and publishes 6 discovery surfaces for automated clients. Both start with the same architectural decision: content is modeled once, then delivered in the form each client needs. We built the platform with Prismic and the Next.js App Router. Editors assemble pages from structured components, visitors receive generated HTML, and…
Walden Robotics has developed a website architecture that supports both human and AI clients by modeling content once and delivering it in formats tailored to each user. The platform, built with Prismic and the Next.js App Router, employs 19 reusable content components to create pages, which editors assemble as needed.
Structured content components, including hero sections, calls to action, and lead forms, are defined in Prismic's Slice Machine. These components can be combined to create new pages without altering component code. Content is separated into page-specific and shared records, with shared items like navigation, SEO defaults, and global announcements having a single source of truth. Global content changes are made once in Prismic and automatically reflected across the site.
The site uses Next.js App Router's static generation, caching, and automatic revalidation to serve generated pages to visitors. Editors can publish updates without manual rebuilds. Draft Mode allows editors to preview unpublished content without affecting live traffic.
When CMS-configured forms are used, they are treated as untrusted input. The platform signs form field definitions with HMAC before they reach the browser and validates submitted data on the server. This HMAC verification ensures integrity and authenticity without encrypting the data. The platform also restricts requests to approved endpoints and uses honeypot fields and timeout mechanisms to prevent abuse.
Editorial flexibility is maintained through server-side enforcement of behavioral configuration limits. Operational data, such as career listings, is sourced from Rippling's applicant tracking system, while the editorial experience around those listings remains in Prismic. Next.js combines both sources in the rendered page, preserving the workflow of each team responsible for their respective information.
The platform also supports HTTP content negotiation, allowing clients to request Markdown representations of content, ensuring both human visitors and automated systems receive appropriate content.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
