Ripple Standards: every brand's single source of truth
A brand-asset portal and client-facing guidelines generator, live in production. Studio staff build a brand's section tree once; the platform renders it into a downloads-first toolkit and an editorial guidelines site, shared with clients through scoped, password-protected links. 42 brands across 11 clients and counting.
The problem
Brand assets die in folders. Every studio knows the ritual: the client emails asking for the logo files, someone digs through a drive, exports a zip, and three weeks later the wrong version is on a billboard. Guidelines PDFs go stale the day they are exported. The studio needed one place where the assets, the rules, and the sharing all live together, and where what the team maintains is exactly what the client sees.
The approach
One content tree per brand, two rendered faces. Staff manage sections, subsections and files in an inline editor; the same tree renders as a toolkit page for downloads and an editorial guidelines site with usage rules, both carrying the brand's own accent and both updating the moment the tree changes. Nothing is exported, so nothing goes stale.
- Structure: Group → Client → Brand hierarchy, with company tags as internal metadata. Preset section libraries so a new brand's guidelines start from the studio's standard skeleton instead of a blank page.
- Sharing: scoped share links per brand with passwords, revocation, and per-link usage tracking. Clients get a clean branded site, not a folder dump.
- Control: role-based permissions, audit logs, soft-delete trash, file versioning, and a background worker that virus-scans and converts heavy design files into web-ready previews.
- Analytics: group-wide and per-brand views, downloads and share opens, so the studio finally knows which assets clients actually use.
The outcome
Live in production for the collective's client work, from national media brands to government entities. The logo-request email is gone: clients self-serve from a link that is always current, always on-brand, and revocable in one click. The studio's brand knowledge stopped being a pile of folders and became a system with structure, permissions and a memory.
What I learned
The product is the constraint, not the features. The hard rule that "what you build here is exactly what clients see" forced every internal editing decision to survive contact with a client-facing render, which killed a whole class of half-finished states before they existed. A brand system works when it is impossible to publish something that is not the system.