// brand system
qubicfold brand.
The working reference for building qubic* surfaces. Palette, type, wordmark, voice. Everything on qubicfold.com and its sibling tools should read like it came from the same operator — this is the sheet that keeps that true.
// 01 — palette
OKLCH, cool axis, one accent.
The palette runs on a single cool hue (blue-slate at 240°) for surfaces and text, with one mint-cyan accent at 175° for anything that has to draw the eye. Everything is authored in OKLCH so the values stay perceptually consistent across surfaces.
// surface
// text
// accent
// 02 — type
Two families. That's it.
Inter for everything visible. JetBrains Mono for anything technical — code, tags, eyebrows, metadata, filename-style labels. No serifs. No display faces. Weight and case do the differentiation, not additional families.
// 03 — mark & wordmark
A folded cube, a chevron prompt.
The mark is a 2×2 grid of squares — a cube unfolded, a fold reduced to its faces. The wordmark is set in JetBrains Mono, prefixed with a shell chevron (>) in footers to signal the operator context.
// 04 — voice
Operator's voice. No marketing register.
The whole surface is written for the smart senior technical operator who has to live with what gets shipped. Direct. Specific. Never trying to persuade.
// do
- Name the concrete thing. "Aprimo Marketing Operations at scale." Not "enterprise martech."
- Lead with the problem. Then the design. Then the stack.
- Own the trade-off out loud. "No Docker unless a client insists" is a stance, not a pitch.
- Use // markers for eyebrows and technical asides. Use > for the operator-shell context.
- Short sentences beside long ones. Rhythm matters for scan-reading.
// don't
- Adjectives before nouns. "Robust", "cutting-edge", "innovative" — cut them.
- Persuasive superlatives. If it's the best, describe it and let the reader conclude.
- Corporate abstraction. "Solutions", "outcomes", "transformation" — name what changed instead.
- Emoji or exclamation points anywhere in product copy.
- Any language that reads like a sales page. This is documentation-adjacent, not conversion-optimized.