A layout system that lets Qwoach's AI build each blog page around its content.

Qwoach is software for therapists and counselors to record and organize notes on their clients, with practice tools such as genogram creation built in. Buzzinga Co. designed the original Qwoach application, and has been building components for the product since then, so this project started with a team that already knew the software from the inside.

Qwoach had a growing library of blog articles, with more content continuing to be added.

Designing every article individually wasn't practical, and one fixed blog template would flatten the differences between them.

The goal was not to design each finished blog page by hand. Buzzinga Co. set out to build a flexible layout system that could give Qwoach's planned AI workflow enough approved options to build each page around its actual content.

Every article could contain a different mix of information. Some needed detailed comparisons, while others relied on step-by-step guidance, examples, statistics, definitions, imagery, FAQs, resources, or key takeaways.

A single template could make publishing easier, but it would also make every page follow the same visual rhythm. Designing every article independently would solve the variety problem, but wouldn't scale.

We started with a content audit rather than a blank page: instead of beginning with complete blog templates, we read through the existing articles and looked for the recurring types of information that appeared across them.

Patterns began to emerge: heroes, image-and-content sections, comparisons, steps, statistics, examples, FAQs, callouts, resources, CTAs, and other repeatable content structures.

But identifying the sections was only part of the problem. The same type of content could require a different presentation depending on its context. A comparison might work best as two opposing columns in one article, while another might need a detailed table. A content section might need a strong supporting image in one place and a compact editorial layout somewhere else.

For each recurring section type, we designed as many structurally different layouts as its content actually needed, rather than one reusable component. Most ended up with two or more; a few kept a single layout, because that content only ever takes one shape.

A hero, for example, could be text-led, image-led, centered, split into two columns, or built around a stronger visual moment, and the same thinking ran through the rest of the library.

These aren't cosmetic alternatives. Each layout changes the hierarchy, composition, image placement, content density, or visual emphasis to suit a different content situation.

At handover, Qwoach's AI workflow was planned rather than live, and the library was designed around it. Instead of generating a blog page from an empty canvas, the workflow chooses from layouts that have already been designed and approved.

Each part of an article maps to a section type, and a variant is picked to suit it. One article can open with a visual introduction, move into an image-led explanation, compare two options side by side, break a process into steps, and close with a CTA. Another can lead with an editorial opening, then statistics, FAQs, and related resources.

Variety only works if the options still feel connected. Typography, spacing, styling, and behavior stay consistent across the library, so layouts that differ structurally can sit on the same page without the experience feeling assembled from unrelated pieces.

What we handed over is not a set of finished blog pages. It is a reusable layout library: 49 layouts across 19 recurring section types in Qwoach's articles, with more than one layout wherever the content can take more than one shape, all in one visual language.

The library is what their AI workflow draws from when it assembles a page.

Instead of designing each new blog page one by one, we designed the system that can create them.