1. Home
  2. Brand Guidelines
Design System

TASMU Brand Guidelines

The single source of truth for designing and building on the TASMU Platform. Every screen, component and asset — English or Arabic — must follow the rules on this page.

Version 1.0 · Maintained by the TASMU Design Authority, MCIT

1. Brand Foundation

Purpose
TASMU is Qatar's national smart-nation platform, an initiative of the Ministry of Communications and Information Technology. The brand must read as sovereign, precise and technically credible — never playful, never generic.
Brand personality
SovereignPreciseConfidentHuman-centredForward-looking
Voice & tone
Clear, short, factual sentences. Lead with the outcome for the citizen or entity. Avoid marketing superlatives, avoid vendor jargon, never abbreviate government entity names on first use.

3. Colour System

TASMU is dark-first. All colour is consumed through semantic tokens defined once in the stylesheet — never hard-coded hex values in components.

Core surfaces
--background
Page background
oklch(0.16 0.01 260)
--surface
Cards, panels
oklch(0.19 0.012 260)
--surface-2
Inputs, nested blocks
oklch(0.23 0.014 260)
--surface-3
Hover, dividers
oklch(0.28 0.016 260)
--sidebar
Sidebar, footer
oklch(0.14 0.008 260)
Brand & accent
--tasmu-yellow
Primary action, active state
oklch(0.88 0.18 95)
--foreground
Primary text
oklch(0.98 0.005 255)
--muted-foreground
Secondary text
oklch(0.72 0.02 260)
--tasmu-purple
AI / agent accent (sparing)
oklch(0.65 0.22 305)
--border
Hairline borders
oklch(1 0 0 / 8%)
Status
--chart-4
Success / Live
oklch(0.75 0.18 145)
--chart-1
Warning / Pending
oklch(0.88 0.18 95)
--destructive
Error / Failed
oklch(0.67 0.22 25)
--chart-2
Info / Provisioning
oklch(0.7 0.18 200)
Usage ratio

Roughly 70% background and surfaces, 20% foreground text, 10% TASMU Yellow. Yellow is reserved for the single primary action, active states and key data highlights on a screen.

4. Typography (EN / AR)

Latin
Space Grotesk · Inter

English uses Space Grotesk for display and headings, Inter for UI and body copy. Headline tracking is tightened to -2.5%; body copy sits at -0.5%.

Arabic
نوتو كوفي · آي بي إم بلكس

Arabic uses Noto Kufi Arabic for display and headings, with IBM Plex Sans Arabic for body. Arabic is never letter-spaced, never italicised, and never set in all-caps.

Type scale
ElementSize / weight / line-heightSample
Display / H160 px · 500 · 1.05
Smart Nation
H2 Section36 px · 500 · 1.1
AI Marketplace
H3 Card title20 px · 600 · 1.3
Digital Twin
Body14 px · 400 · 1.6
Deploy blueprints in minutes.
Caption / meta12 px · 400 · 1.5
Updated 2 hours ago
Eyebrow11 px · 500 · uppercase · +0.15em
Design System
Cross-script pairing

When both scripts appear together, set Arabic one step larger (+2 px) than the Latin equivalent so optical weight matches, and increase line-height by 0.15 to accommodate diacritics.

AI Marketplaceسوق الذكاء الاصطناعي

5. Spacing, Grid & Radius

A 4 px base unit drives all spacing. Approved steps: 4, 8, 12, 16, 24, 32, 48, 64, 96. Page gutters are 24 px on mobile and 24 px within a 1280 px max content width on desktop.

4
8
12
16
24
32
48
64
Grid
12-column fluid grid, 24 px gutters. Card grids: 1 column mobile, 2 tablet, 3–4 desktop. Section rhythm is 96 px between major bands.
Elevation
Depth comes from surface lightness plus a soft ambient shadow and a 1 px inner top highlight — never from heavy drop shadows or outer glows.
Corner radius
sm — 8 px
Chips, tags
md — 12 px
Inputs, small cards
lg — 16 px
Cards, panels
full — pill
Buttons, avatars

6. Iconography & Imagery

Icons

Lucide, 1.5 px stroke, 16 px in dense UI, 20 px in navigation, 24 px in feature blocks. Icons inherit text colour; TASMU Yellow is used only for the icon of an active or primary item.

Imagery
Photography and renders are dark, cool-toned and architectural: Qatari infrastructure, control rooms, ports, transit and data visualisation. Overlay images with a 40–60% background-coloured scrim so foreground text keeps contrast. No stock-photo handshakes, no purple AI clichés.

7. Components

Every component below is production code from the portal. Reuse them; do not create alternative variants without Design Authority approval.

Buttons

Pill-shaped, 40 px tall (32 px compact). One primary action per view.

Chips & filters
AllTransportationHealthcareEnvironmentSports
Form controls

48 px tall, pill radius, 1 px border, yellow focus border. Labels always visible above the field.

Cards

Surface background, 1 px border, 16–20 px radius, 24 px padding, ambient shadow on hover.

Digital Twin
Deployable blueprint
Digital Twin
Deployable blueprint
Digital Twin
Deployable blueprint
Status badges
LiveProvisioningPendingFailed
Data tables

Uppercase 11 px muted headers, 1 px row dividers, 12–14 px rows, numerals right-aligned and tabular.

ServiceStatusUsage
TASMU CIAMLive12,480
GIS APIsLive3,209
Dialogs
Centred, max 720 px, surface background, 20 px radius, blurred backdrop. Primary action bottom-right in LTR, bottom-left in RTL.
Navigation
Sticky translucent header with blur, 64 px tall. Dashboard sidebar is 260 px, sidebar surface, active item marked with a yellow left rule (right rule in RTL).

8. Motion

Motion is functional: it explains where things come from. Never decorative, never longer than 400 ms.

Durations
  • 120 msHover, colour change
  • 220 msEnter / exit, fade-rise
  • 400 msPage & wizard transitions
Easing
  • cubic-bezier(0.22, 1, 0.36, 1)Standard ease-out
  • spring(260, 24)Success & celebration
  • linearProgress & loaders
Patterns

Content rises 12 px while fading in. Cards lift 2 px on hover. Wizard steps slide along the reading direction — left-to-right in English, right-to-left in Arabic. All motion is disabled under prefers-reduced-motion.

9. Bilingual & RTL

  • Arabic is a first-class language, not a translation layer. Every screen must be reviewed in both scripts.
  • Set dir="rtl" on the document root for Arabic — never mirror with CSS transforms.
  • Mirror layout, navigation order, icon direction (arrows, chevrons) and progress indicators. Do not mirror logos, media controls or clock icons.
  • Numbers, dates and currency use Arabic-Indic or Western digits consistently per tenant setting; currency is always QAR.
  • Keep English product names (TASMU CIAM, GIS APIs) in Latin script inside Arabic copy.
  • Allow 25–35% text expansion when translating English into Arabic; never truncate a label to fit.

10. Accessibility

  • Body text meets WCAG 2.1 AA — 4.5:1 minimum; large display text 3:1.
  • TASMU Yellow is only used for text on the dark background, or as a background under near-black text. Never yellow text on a light surface.
  • Visible focus ring on every interactive element: 2 px yellow outline with 2 px offset.
  • Minimum touch target 44 × 44 px.
  • Colour is never the sole carrier of meaning — pair status colour with a label or icon.
  • All imagery carries meaningful alternative text in both languages.

11. Do & Don't

Do
  • · Use semantic tokens for every colour, radius and shadow.
  • · Keep one primary yellow action per screen.
  • · Set Arabic in Noto Kufi Arabic with generous line-height.
  • · Compose new screens from existing components.
  • · Test every layout in both LTR and RTL.
Don't
  • · Do not introduce new accent colours or gradients.
  • · Do not place the logo on light or busy backgrounds.
  • · Do not stretch, recolour or outline the logo.
  • · Do not letter-space, italicise or capitalise Arabic text.
  • · Do not use drop shadows, glows or decorative animation.

12. Assets & Governance

Logo files, the Figma library and the token export are distributed through the TASMU Design Authority. Request access or raise a deviation before shipping anything that departs from this document.

brand@tasmu.gov.qaReviewed quarterly. Deviations require written approval from MCIT Digital Design Governance.