Task Board Brand Kit

The visual reference for anything produced for the Redbelly DAO Community Task Board: the board itself, task graphics, social assets, and contributor deliverables.

Redbelly DAO logo

Scope, and what this is not

Every value here is read from the live application at app/globals.css, not from a mood board. If a token changes in the app, it changes here. That is the point: contributors and the board should not drift apart.

This is the Task Board brand, not Redbelly Network's corporate brand. It is built to sit consistently alongside Redbelly Network's own identity, but it is not a substitute for it and it does not govern Redbelly Network material. If a deliverable is going out under the Redbelly Network name rather than the DAO Task Board, check with the core team first.

The design language is called Kinetic Consensus. It reads as corporate modern with a technical edge: deep slate surfaces, one high-impact red, generous negative space, monospace reserved for anything machine-generated. Industrial and robust, but approachable enough for a community board.

Colour

One accent, used everywhere, never joined by a second. The red is the only saturated colour in the system and it is reserved for high-impact actions, brand moments, and critical status. Everything else is a slate neutral.

#EF5350 Brand red. The single accent. Primary buttons, brand moments, the mark.
#0f181d Base surface. Never pure black.
#e4ebf0 Primary text on dark.

Dark surfaces, lowest to highest

container lowest#0a1216Wells, inset areas
surface / background#0f181dPage base
background deep#121b20Lifted base so cards separate
surface slate#1e2a31Cards, panels, modals
container#1b252aNested fills
container high#27323aHairlines, soft dividers
outline variant#3a4650Borders
outline#93a4aeSecondary text, muted labels

Accent and state

brand#EF5350Primary action fill
primary (dark)#ffb3aeAccent text and links on dark
ok#86EFACApproved, complete, paid
warn#FCD34DPending, revision requested

The accent flips value between themes. On dark, accent text is #ffb3ae, because #EF5350 does not carry enough contrast for small text on a slate ground. On light, it darkens to #B3272A for the same reason. The solid fill #EF5350 stays constant in both. Get this wrong and the accent either disappears or shouts.

Light counterpart

The board ships a light theme. It is the same brand, not a second one.

surface#F6F7F8Page base
surface slate#FFFFFFCards
on surface#16202APrimary text
primary (light)#B3272AAccent text and links

Typography

Be Vietnam Pro carries every heading and all body copy. JetBrains Mono is functional only: wallet addresses, transaction hashes, task IDs, timestamps, scores, and any other machine-generated value. Never use the mono for prose because it looks technical.

Both are open-licence and free. Be Vietnam Pro and JetBrains Mono are both on Google Fonts. If a contributor's tool cannot embed them, the fallback order is the system UI sans and the system monospace, in that order. Never substitute a serif, and never substitute Inter as a stand-in.

headline-xl / 48 / 700 / -0.02emCycle 2 is open
headline-lg / 32 / 600 / -0.01emSubmission under review
body-lg / 18 / 400 / 1.55Read the full task before you claim a slot. Claims expire after five days.
body-md / 16 / 400 / 1.5Every deliverable listed on a task is required. A submission missing one is incomplete, not partial.
label-mono / 14 / 500 / 0.05emTASK-19   0xb45ffb51984d626ee758b336c61cf20990c6bf13   31/35
label-caps / 12 / 700 / 0.1emDocumentation

Rules

RuleValueWhy
Body line height1.5Governance and technical documents get read end to end. Tight leading fatigues.
Line length65 to 75 charactersAnything wider loses the reader between lines.
Minimum body size on mobile16pxMost board traffic arrives from a Discord link on a phone.
Heading emphasisWeight and colourControl hierarchy with weight, not raw scale. No oversized headings for their own sake.

Logo

There are two variants of the same lockup. Dark ink for light backgrounds, light ink for dark ones. Pick by background and never place either on a plate: the plate was a workaround from when only the dark variant existed, and it is retired.

Light-ink lockup on the dark surface

On dark. dao-logo-on-dark.png, bare, no plate.

Dark-ink lockup on the light surface

On light. dao-logo-on-light.png.

Light-ink lockup on the brand red

On the brand red, use the light-ink variant.

ConstraintValue
ShapeLandscape, close to 7:5. The mark sits above the wordmark. Scale by height and let the width follow; never set both.
Clear spaceMinimum the height of the mark's tallest letterform on all four sides. Nothing enters that box. The files already carry part of it, so do not crop them tight.
Minimum size28px tall on screen. Below that the wordmark stops reading, so use the favicon instead.
Which variantLight ink on any surface darker than #DADDE1, including the brand red. Dark ink on anything lighter. Never a plate.
Master filespublic/dao-logo-on-light.png and public/dao-logo-on-dark.png, copied alongside this page.

Never recolour, stretch, rotate, add a shadow to, or place the mark over a busy photograph. If it will not read, use the wordmark in Be Vietnam Pro 700 instead.

Shape, spacing, depth

One radius scale, applied consistently. Soft enough to feel modern, square enough to stay architectural. Pill shapes are not used for primary buttons.

TokenValueApplies to
radius base4pxButtons, inputs, chips, small cards
radius lg8pxPanels, modals, large containers
radius full9999pxStatus dots and avatars only
spacing base4pxAll component padding steps off this
gutter24pxGrid columns
margin, mobile16pxStrict. Never less.
margin, desktop64pxSection separation uses 48, 64, 80
max width1280pxContent column

Depth is tonal, not shadowed. A card sits above the page because it is a lighter slate, with a 1px border a shade lighter than its own fill. Heavy drop shadows are not part of this system. Modals and navigation may use a backdrop blur of 12px to 20px over a semi transparent dark fill.

Components

Buttons

Primary is a solid brand fill with white text. Secondary is a ghost with a neutral border that picks up the accent on hover. Destructive uses #DC2626, which is the one place a red other than the brand red is allowed, so that "delete" never reads as "confirm". Labels are one to three words and never wrap.

Inputs

Label above the input, always. Never use a placeholder as the label. Focus takes the accent border plus a 2px aura. Error text sits below the field, not beside it.

Status

Approved Under review Rejected Withdrawn

Status is a small dot plus a monospace label. It is not a filled pill. This keeps dense lists calm, which matters on the submissions and admin views where dozens stack vertically.

Cards

Staking and Voting Power Explainer

Locked versus unlocked positions, delegation timelines, and which wallet counts for Snapshot.

Card header separated from body by a 1px rule. Use a card only when elevation communicates real hierarchy. Otherwise group with a top border or plain negative space.

Social and graphic assets

Sizes for anything produced for the DAO's channels. Deliver exports plus editable source files, always.

AssetDimensionsNotes
X single image post1600 x 90016:9. Keep text inside a 5% safe margin.
X square post1080 x 1080Better for dense reference graphics such as a venue list.
X header1500 x 500The centre 1500 x 360 is the only reliably visible band.
Discord embed image1200 x 630Also the correct Open Graph size for any linked page.
Avatar512 x 512The lockup centred on a square, sized to leave full clear space left and right rather than filling the width. Pick the variant that suits the avatar background.
Export formatPNGSVG where the asset is pure vector. No JPEG for anything containing text.

Graphics that carry facts which expire, such as a list of exchanges or a set of chain IDs, must carry a dated "last verified" line in the artwork itself. A screenshot outlives the post it was attached to.

Voice and copy

The board's writing is first person, direct, and plain. It owns mistakes rather than smoothing them over. These are hard rules for anything published under the DAO Task Board name.

Do

  • Use plain hyphens. Write two sentences where you were reaching for a longer pause.
  • Say the number. "Five days", not "a few days".
  • Name the thing that went wrong and what happens next.
  • Cite the rule number when you invoke a rule, and pull it from the board, not from an older draft.
  • Lead with the answer, then the reasoning.

Do not

  • No em dashes or en dashes. Anywhere. Not in copy, not in graphics, not in commit messages.
  • No emoji. The board's own checkmark and cross glyphs are the only sanctioned symbols.
  • No filler verbs. Not "elevate", "seamless", "unleash", "revolutionize".
  • No corporate hedging. If a decision is not final, say what would make it final.
  • No second accent colour introduced to make something feel important.

Contrast

Every pairing below meets WCAG AA. Anything not listed here has not been checked, so check it before shipping.

ForegroundBackgroundRatioUse
#e4ebf0#0f181d14.92:1Body text on dark. Passes AAA.
#b8c4cc#0f181d10.10:1Secondary text on dark.
#93a4ae#0f181d6.98:1Muted labels. Do not go below this grey.
#93a4ae#1e2a315.70:1The same muted grey on a card. Still AA, with less headroom.
#ffb3ae#0f181d10.53:1Accent text and links on dark.
#ffffff#EF53503.49:1Primary button label. Large text only, 18px and up or 14px bold.
#16202A#F6F7F815.37:1Body text on light.
#B3272A#F6F7F86.04:1Accent text on light.

The white on brand red pairing is the one tight spot in the system at 3.5:1. It is fine for a button label at 14px bold or larger, which is how the board uses it. It is not fine for body copy, captions, or small print on a red field. If you need small text on red, invert: dark text on #ffdad7.