LGL-OS — Tone & Identity Guide

Who we are

Let's Go Live! builds infrastructure for live production. LGL-OS is the product suite — the operational layer that sits between signal entry and content delivery. We serve people who work live, under pressure, where the stakes are real.

We're not a streaming app. We're not an editing tool. We're the system underneath — the thing that makes sure everything else works when it counts.

Brand traits

Direct Precise Operational Calm under pressure Trustworthy

We are not

Hype-driven Vague Consumer-cute Self-congratulatory

Our audience

Broadcast engineers

They've built signal chains in the dark at 5am. They know what works and what's marketing. Earn their trust with specifics, not promises.

Technical directors

They need to see the whole system at a glance and trust it won't break mid-show. They care about reliability and operational clarity.

Production teams

They're running events under time pressure. They don't read manuals in advance — they need things to be obvious when they sit down.

Voice principles

The voice stays consistent everywhere. It's who we are, regardless of the channel. Think: experienced colleague, not brand mascot.

Say what it does, then stop

No filler, no build-up. Lead with the function. "Vault records continuously" is better than three sentences explaining why recording matters.

Confident, not loud

We don't need superlatives. "Reliable" beats "ultra-reliable." "Fast" beats "blazingly fast." The product is the proof.

Technical when it matters

Our audience knows what SRT, RTMP, and LTC mean. Don't over-explain. Don't put protocols in quotes. Trust the reader.

Human, not robotic

Precision doesn't mean cold. Write like a person — just one who happens to be really good at this and doesn't waste your time.

The gut check

Before publishing anything, ask yourself four things:

Would a TD at Pinkpop read this and nod, or roll their eyes?

Could I say this out loud to a colleague without it feeling weird?

Did I say what it does, or just what it is?

Is there a shorter way to say this?

Tone by context

Same voice, different temperature. The formality and detail shift depending on where the words appear.

Casual

Direct

Technical

Academic

Product UI

Shortest possible. Verb-first. Clarity is the personality.

Write this

Recording started

Source disconnected. Retrying...

2 streams ingesting

Not this

Your recording has been successfully initiated!

Oops! Something went wrong.

You are currently ingesting 2 streams.

Product pages & marketing

Conversational but grounded. Like explaining it to a smart colleague, not pitching a VC.

Write this

Vault records continuously. If the stream is live, the file is growing.

What you see in the timeline is what you get in the export. Frame for frame.

Not this

Our state-of-the-art recording engine leverages cutting-edge technology...

Say goodbye to timeline drift forever!

Documentation

Task-oriented. Lead with what to do, not background. Write for someone at 2am before a show.

Write this

To add an SRT source, navigate to Relay → Sources → Add.

Not this

In this section, we'll walk you through the process of configuring a new source...

Error states

Specific about what happened. Specific about what to do. Never cute, never vague, never blame the operator.

Write this

Ingest source 'CAM-02' dropped. Last frame: 4s ago. Check connection.

Export failed: disk full. Free 2.1 GB to continue.

Not this

Something went wrong. Please try again.

Uh oh! We hit a snag 😅

Naming & hierarchy

Clear naming creates clarity for everyone — operators, customers, and ourselves.

Name	What it is	When to use
Let's Go Live!	The company and parent brand	Corporate contexts, contracts, about pages, legal
LGL-OS	Written form — hyphenated, single color	Body copy, documentation, product pages, anywhere it's typed
LGLOS	Logo form — no hyphen, "OS" in violet	Logo lockups, nav bars, headers, brand marks
LGL [Module]	Individual modules (no "OS" in module names)	Feature pages, in-app navigation, docs

LGL-OS vs LGLOS

Two forms, two contexts. Never mix them.

Written — LGL-OS

Hyphenated. Single color. Used in body text, docs, and anywhere you're typing the name inline.

"LGL-OS handles ingest, recording, and replay."

Logo — LGLOS

No hyphen. "LGL" in white, "OS" in violet. Used in logo lockups, navigation, and brand marks.

LGLOS

The modules

LGL Relay

LGL Switch

LGL Vault

LGL Timeline

LGL Replay

LGL Archive

LGL Monitor

How to introduce a module

First mention on a page: full name + what it does. After that, just the short name.

Correct

LGL Vault handles continuous recording across all active streams. Once Vault is running, every frame is captured.

Avoid

"LGL-OS Vault" (double branding)

"the Vault module" (unnecessary)

"LGL-OS's Relay" (awkward possessive)

Color palette

The Midnight Pulse palette. Dark foundation, violet identity, intentional status colors.

Core identity

#8B5CF6

Vivid Violet

Primary accent, identity color

#050508

Deep Space

Background, page base

#0E0E14

Core Panel

Cards, panels, surfaces

#161620

Raised

Borders, dividers, hover states

Status & signal

#10B981

Neon Live

Live states, healthy ingest, success

#F59E0B

Queue Warning

Pending, congestion, warnings

#EF4444

Error Alert

Failures, dropped sources, critical

Usage rules

Violet is identity, not decoration

Use for primary actions, active states, brand elements. Don't scatter it everywhere — it should always feel intentional.

Status colors are reserved

Green = confirmed live / healthy. Amber = pending / warning. Red = failure / critical. Never use these for branding or decoration.

Status in practice

2 streams ingesting

Export queued

Source dropped

Organic polygon background

The signature marketing background. A gradient-filled organic shape clipped with clip-path, then dot-masked to create a halftone texture. The shape sits behind content, partially bleeding off the edges. Subtle enough to layer text over, distinct enough to feel intentional.

How it's built

Layer	Technique
Base	Dark background (`#050508`)
Shape	Gradient fill (`linear-gradient 145deg`, violet 8%→65% opacity) clipped via `clip-path: polygon()`
Texture	Dot mask — `radial-gradient(circle, #000 1.2px, transparent 1.35px)` at `8px 8px`
Position	`width: 65%; height: 110%; right: -8%; top: -15%` — bleeds off the right edge

LGLOS

Gradient blob clipped to an organic shape, then dot-masked

clip-path + mask · gradient-filled shape · Marketing pages only

View CSS

.section {
  position: relative;
  overflow: hidden;
}

.section::before {
  content: "";
  position: absolute;
  width: 65%;
  height: 110%;
  right: -8%;
  top: -15%;
  background-image: linear-gradient(
    145deg,
    rgba(139, 92, 246, 0.08) 0%,
    rgba(139, 92, 246, 0.65) 100%
  );
  clip-path: polygon(
    18% 8%, 72% 0%, 100% 24%,
    89% 74%, 50% 100%, 0% 82%, 8% 42%
  );
  mask-image: radial-gradient(
    circle, #000 1.2px, transparent 1.35px
  );
  mask-size: 8px 8px;
}

Typography

Two fonts. One for impact, one for work.

Syne — Marketing

Marketing pages, landing pages, promotional material. Bold, technical, slightly aggressive. Feels like broadcast equipment, not a lifestyle brand. Not used in applications.

One timeline. Every source.

Syne 800 · Uppercase · Tight tracking

Inter — Applications

The workhorse. All application UI, data-dense interfaces, body copy, documentation, labels. Legible at every size, professional at every weight. The default font for everything inside the product.

Vault records continuously across all active streams. If the stream is live, the file is growing. Every frame is captured, buffered, and written with integrity safeguards.

Inter 400 · Sentence case · Default tracking · 1.65 line-height

Monospace — System & Code

Timecodes, status readouts, code samples, technical values. Small, dense, functional.

01:14:32:18 · SRT://ingest-01.lgl.live:9000 · 1920×1080 · 29.97fps

Courier New / Consolas · System readouts, timecodes, labels

UI voice

How the interface talks to operators. Every label, tooltip, and notification is copy — treat it that way.

Buttons

Verb-first. Describe the action, not the destination. Short enough to scan instantly.

Write this

Start recording · Add source · Export clip · Open timeline

Not this

Click here to start · Submit · Go · Recording options

Empty states

Tell the operator what to do, not what's missing.

Write this

No sources connected. Add one via Relay → Sources.

Not this

Nothing here yet! Get started by adding your first source 🎉

Confirmations

State what happened. Past tense. Done.

Write this

Clip exported · 00:02:14 · 1080p

Not this

Your clip has been successfully exported! Great job!

Words we use

Use	Instead of
stream, source, feed	input, asset (in live context)
record	capture (unless at ingest level)
extract	pull, grab
timeline	session, project
operator	user (in production context)
reliable	robust, rock-solid, bulletproof

Banned words

Revolutionary Seamless Leverage Solution Simply Game-changing Ecosystem Utilize