A running record of the packs we build, the studios that put them to work, and the layout problems that pushed each one into the catalogue. Some entries are client jobs, some are internal rebuilds after a font swap broke a master page. All of them start with a real deadline.
Three ongoing builds that shaped how the packs are put together. Each one started as a real request from a small team and ended up changing the grids, layer naming or export presets we ship today.
A concrete project with a clear subject and real-world context.
This page frames a concrete subject instead of using a generic heading. It explains what is being considered, why it matters in the site's context, and what detail a reader can expect next. The copy is intentionally plain and specific, so it reads like a real content item.
Read the project notes
A focused project built around practical decisions and constraints.
This item focuses on practical use, tradeoffs, and decisions that a reader may recognize. It avoids broad promotional claims and keeps the topic tied to a clear situation. The description gives enough substance for a real page rather than a placeholder card.
Read the project notes
A grounded project that adds a different angle without repeating the others.
This page gives the third item its own reason to exist. It covers a separate angle, includes concrete context, and avoids repeating the same promise in different words. The result should feel like a planned article, project, review, or offer.
Read the project notesNotes from studios, media teams and founders who took a pack, swapped the palette and shipped a real document. The useful part is usually what happened on deadline day.
We had a pitch on a Tuesday morning and the deck was still half-built on Monday night. Dropped our swatch library into the master slides, replaced the typeface, and the case study pages held their alignment. Nobody on the client side noticed we had not rebuilt anything.
Two-person studio, Pretoria
The invoice and quote sheets were the reason we bought in. Adding line rows without the totals drifting out of place sounds small until you are sending billing documents every week. The usage note answered the tax row question before I had to ask anyone.
Freelance designer, Johannesburg
Our carousel slides and the A5 flyers now share one grid, which fixed a mess we had been patching for months. Sunday service announcements, midweek events, the lot. The walkthrough video was enough for a volunteer to rebrand the set without me sitting next to them.
Church media team lead
I run a side project around a day job, so I needed something I could finish in one evening. The font substitution list saved me from hunting down missing typefaces, and the print presets meant the label sheet went straight to the printer without a second export pass.
Founder, product label project
Named layers are the whole thing for me. I hand files to a junior and they can find the headline frame without guessing which group it is buried in. We adapted the CV layout for a recruitment client and it took an afternoon, not a week.
Small agency, Cape Town
The free sample sheet told me more than the product pages did. I could open it, check the layer structure and the swatch setup, and decide whether the full pack would fit how we already work. That is why we came back for two more.
In-house design, Durban
Screenshots from recent releases, shot flat on the studio desk. Grids, swatch cards and print proofs included, because a layout only proves itself when it hits paper.
Twenty-four slides with named layers and a CMYK variant for client handouts. Swapped typefaces here without touching the grid.
Quote, invoice and receipt share one grid. Line items sit on separate layers, so adding rows never breaks the totals column.
1:1, 4:5 and A5 flyers built on a single grid. One swatch library keeps a campaign consistent from feed to print run.