Global IT
Community
Network
City by city. Country by country. One network.
This book
The rules for everyone who makes something in the network's name: chapter leads, volunteers, designers, editors and the tools that build on this system.
The live, always-current version is the design system this book is exported from. When the two differ, the live system wins.
City by city.
Country by country.
One network.
Global IT Community Network is the international network that grew out of IT Community of Uzbekistan: independent, volunteer-run tech communities under one name, one mark and one domain. Wherever you build, you are never building alone.
A chapter speaks for its own city. The network gives it a stronger voice without replacing it.
The network is not a program of any company, park or ministry. Nothing in the identity should suggest otherwise.
The mark itself is assembled from separate segments. Show many pieces becoming one, in layouts, films and events.
Plain,
specific,
generous.
Write like a senior engineer who also runs meetups. Say what happens, where and when.
- "We" for the network, "you" for the reader. Never "users".
- Headlines are uppercase, one to three words, with a full stop.
- Triads climb in scale: CITY. COUNTRY. WORLD.
- No emoji in brand material. No filler stats, ever.
- Full name on first mention, then "the network". "GITCN" is internal only.
| Write | Not | |
|---|---|---|
Headlines | CITY BY CITY. | Welcome to our amazing new global community! |
Body | Hiring day, Tashkent, 14 November, 18:00. | Join us for an exciting evening of networking! |
Person | We run meetups. You bring the questions. | Users can register for events. |
Name | IT Community Tashkent | GITCN Tashkent Hub |
English is the network language. Chapters publish in local languages (Uzbek, Russian and others) using the same type system and the same rules.
The mark
Built on a 1254-unit square from one construction. Never redraw it by eye; always use the master files.
Versions
Mono black mirrors mono white for light grounds. On single-ink versions the letters are knocked out, and the highlights and crescent merge into the block. Chapter lockups are covered in Network architecture.
Space & size
Clear space on every side equals 14% of the mark's width. Nothing enters it: no text, no logos, no image edges.
Below 64px COMMUNITY stops being readable, so switch to the app icon. Never re-typeset the lockup words: use the master files.
Palette
Sampled from the master artwork; identical in every theme. Near-white for headline type on black is Snow #E8F6FA. *CMYK values are a naive starting point. Proof on the actual stock before any print run.
One bright spot
Cyan is always the brightest thing on the page. Purple, pale and teal appear as segments (bars, frame pieces, badges), never as big washes. No gradients, ever.
| Aa | Snow / ink | 15.9+:1 | Body, headlines |
| Aa | Muted | 7.2+:1 | Secondary copy |
| Aa | Cyan | 9.9:1 | Links, eyebrows |
| Aa | Violet text | 6.8:1 | Purple words on dark |
| Aa | Black on cyan | 9.9:1 | Primary buttons |
| Aa | White on purple | 7.9:1 | NEW badge |
| Aa | White on teal | 4.5:1 | LIVE badge, 14px+ |
| Aa | Purple on black | 2.65:1 | Never as text |
One geometric family, like the mark. Shout in Bold caps, talk in sentence case, and use two weights per layout. Mono is only for technical meta. For Cyrillic, pair with Montserrat (proposed; proof first).
display-xlBold 120 / 0.95ONE COMMUNITY.headlineBold 56 / 1.05IT Community NetworktitleBold 32 / 1.2Launching in TashkentsubtitleMedium 22 / 1.35Independent tech communities, connected worldwide.bodyRegular 16 / 1.6Meetups, mentoring and hiring days, organised by volunteers.labelMedium 14 · +18% · capsGLOBALeyebrowMono 13 · +12% · caps// 01 · SIGNALFour devices
Drawn around square content: a speaker photo, a QR code. One per layout.
CITY.
Signs off a headline or lockup, as wide as the words above it.
A 60px dot pitch in pale at 12–24%. Texture, never louder than type.
One tile per chapter, for moments of scale. Active chapters light up cyan.
Layout
Leave a lot of black. Use one hero object, one headline and one segment rule per layout.
120 BPM
Everything moves on the beat. One beat is 500 ms and one bar is 2 s. Scenes last whole bars, and every visual hit has an audio hit.
ease-out-expo
ease-in-expo
ease-in-out
Segment slam. 11 frame pieces land, staggered by 30 ms.
Block assembly. The I drops, the T bar slides in and the stem rises.
Masked rise. Words rise into a clip line over 250 ms.
Colour chase. The frame colours run one lap.
Light sweep. One diagonal pass across the block.
Converge. Nodes fly into the mark's outline.
Depth split. Layers separate in Z, then close.
One mark,
every city
The mark is identical in every chapter; only the name line changes. Local character belongs in photography and language, never in the mark.
Chapter names go in English caps on the lockup. A local-language line may follow in the same label style.
The founding chapter, IT Community Uzbekistan, may add "Founding chapter" as an eyebrow. Local domains such as itcom.uz redirect to the chapter page.
Domain and handle patterns (@itcommunitynet, @itcommunity.<city>) are proposed; confirm them before launch. Chapter avatars are always the app icon.
In the world
For new chapters the NEW badge sits beside GLOBAL or the chapter name for 90 days, then retires. Use one primary cyan action per piece. Badges carry the name in title style and the role in label style.