Rocket.Chat brand guidelines
Rocket.Chat houses its brand guidelines within its technical documentation portal, detailing logos, colors, and iconography.
Documentation portal overview introducing the Rocket.Chat brand and visual guidelines.
Logo usage guidelines showing variations, clearance protection rules, and icon positioning.
Alternate documentation view detailing logo variants, clear space units, and inverted symbols.
Color documentation page displaying primary, secondary, supporting, and highlight gradient swatches.
Color guidelines highlighting palette swatches, hex codes, and text highlight samples.
Iconography guidelines page showing principles and sample icons organized by color.
Want a brand center like Rocket.Chat’s?
Create your brand center with Freedam ↗Freedam's take
I like finding brand systems tucked neatly inside technical documentation. Rocket.Chat places its visual identity right inside its developer docs tree, adopting a clean layout with article navigation and feedback modules. The logo guidelines use a charming visual device: measuring clearance space with the three dots from its own speech bubble symbol. Color palettes are equally clear, featuring swatches with hex codes and gradient highlight shades for text accents. It is a no-frills, practical approach tailored to technical teams.
At a glance
- Sections
- Logo · Colors · Patterns · Iconography · Photos · Brand usage examples · Media kit
- Tone
- Technical and pragmatic guidance embedded directly inside product documentation.
What I noticed
- The brand guidelines are nested directly inside the documentation portal under Resources in the left-hand navigation tree.12
- The logo clear space rule defines a minimum exclusion zone equal to three dots from the symbol.34
- The color guide arranges swatches into Primary, Secondary, Supporting colors, and Highlight shades alongside hex codes and gradient samples.5678
- The iconography documentation shows icon examples grouped by color themes including blue, green, and red or pink.9
Numbers refer to the screenshots above.
What I could not see
- No downloadable file packages or direct download formats were visible on the captured documentation screens.
- Typography rules and font specifications were not visible on the captured pages.
Ideas to borrow
Quick answers
Reviewed on 25 September 2026. Request a correction · I built this
