Frontend

In software, the frontend is the client side of a website or app: the HTML, CSS and JavaScript that run in a browser or on a device to present pages, navigation, forms, buttons and media. It handles layout, interaction and much of what makes a service usable and accessible, while the backend decides which information to send in the first place.

For content, the frontend is wherever content reaches people. That might be a web page or an app screen, but also an email, a push notification, a printed leaflet, a voice assistant’s reply or a chatbot’s answer. It includes the words on buttons and in error messages as much as articles, along with the order, emphasis and timing in which they appear. Ann Rockley’s frontend content strategy describes this end of the work: who the audience is, what they need, which content types serve them and how to write for them.

Why it matters for content

Meaning changes with presentation. A sentence in a CMS field may become a heading on one screen, a notification on another and a spoken answer on a third, each with different constraints of length, context and attention. A warning that reads clearly in the editing interface can be easy to miss once it’s placed below the action button. Headings, labels, link text and reading order carry meaning in the way punctuation does for a sentence, which is why content people need to see and test the frontend rather than approve isolated strings. The same structure, expressed in well-formed headings and semantic HTML, is what assistive technology, search engines and AI systems rely on to make sense of a page.

The frontend is also where the backend gets judged. Readers never see the content model, the taxonomy or the approval route. They see whether the fee is right, whether the page answers their question and whether search turns up what they came for. In a content operating model, the answers to what is published and for whom are tested here, so what people do at the frontend should feed back into the models, workflows and guidance behind it. Components work best when content, design and development shape them together, around real language, errors, translations and edge cases rather than placeholder text.

How AI changes the picture

More of the frontend is now composed at the moment someone asks. A chatbot or search assistant writes an answer that no editor saw in that exact form, drawing on whatever sources it can reach. Editorial work moves from approving finished screens towards setting the patterns, sources, boundaries and fallbacks for what may be composed: how to express uncertainty, when to hand over to a person and what to say when the answer isn’t known. Language becomes the main control surface, so wording and recovery are design decisions in their own right.

People also meet content on frontends the organisation doesn’t control. AI summaries in search results, assistants inside other products and agents that browse on someone’s behalf all present an organisation’s content in their own words and layouts. You can’t design those screens, but titles, summaries, clear structure and accurate metadata influence how well content holds up when it’s presented elsewhere. It helps to check what these tools say about your services, as you would test your own pages.

Building frontends has changed too. AI can generate interface code and working prototypes quickly, which lets content designers try real wording in a real layout much earlier than a design handover would allow. A generated interface still knows nothing about the service behind a button, so content priorities, accessibility tests and real source content remain the measure of whether it works.