Skip to content
C.W.K.
Stream
Lesson 05 of 05 · published

Look Is Chrome, Not Content

~10 min · chrome, identity, ember, palette, tui

Level 0Spark
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

Recognize the Window Without Reading the Title

A family terminal has to be findable from across the room. That is not a branding exercise. It is how you do not click into the wrong glass when four windows are open and one of them is still iTerm. Smolder puts identity in the chrome: a SMOLDER wordmark, an ash title bar, an ember rail under the title bar and tab strip, an ember cursor. The ash is #191412. The ember is #FF7A3C. Those two values are the face. They do not need a theme store to exist, and they must not leak into the grid that programs draw in.

Content colors stay standard. htop, lazygit, vim, a TUI that assumed a normal sixteen-color palette — they get to keep that assumption. A terminal that repaints the world orange will fight every one of those programs, and the fight will be scored as a reach for iTerm. Identity and content live on different layers on purpose. Chrome says which app. The grid says what the job is printing.

The Ember Is a Pointer, Not a Theme

The ember rail is chrome under the title bar, not a per-pane marker. Inactive panes dim so you do not have to hunt. The ember cursor marks where input will go, which matters more once a phone can watch without typing. Neither is a license to recolor ANSI. A focused pane that inverts the whole TUI is a focused pane that just broke the operator's map of the program they were in. Focus is a chrome fact: dimming the inactive panes, maybe a thicker divider or a word in the title. Not a second rail on the leaf. It is not a new LS_COLORS.

The wordmark is the same kind of fact. It sits in chrome so a glance is enough. Hiding it to gain two rows of grid is how every terminal ends up looking like every other terminal, and then you are back to reading titles. Two rows are not the bar. Absence of a reach is the bar. If the window cannot be recognized, the bar is already collecting a dated row: opened the other app because this one disappeared into the wallpaper.

No Theme Store, On Purpose

Track 1 already refused a plugin market and a theme store. This lesson is that refusal at the pixel layer. A theme store is how someone else's multiplexer comes back wearing a prettier palette. It is also how content colors drift until a TUI is unreadable and the operator blames the TUI. Smolder's look is a small, named set of chrome choices. Operators can still configure the emulator — font, scrollback, Option as Meta, the standard palette the core already offers — without Smolder pretending to be a skinning engine.

The phone will wear the same ember. Same wordmark energy, same rail idea, adapted to a compact chrome. That is Track 5's universal app, not a second brand. If iOS grew a different orange, you would have two faces for one fire, and across-the-room recognition would fail in a pocket. Chrome is identity. Content is the job. Keep them from dyeing each other.

Identity is chrome. Content colors stay standard. Ash title bar, ember rail, ember cursor, SMOLDER wordmark. A terminal that paints the TUI orange has not found a look. It has started a fight with every program that assumed a normal palette.

Code

Two layers, two palettes, one face·text
CHROME (identity, owned by Smolder)
  wordmark:     SMOLDER
  title bar:    ash     #191412
  ember rail:   ember   #FF7A3C   # under title bar, not per-pane
  cursor:       ember   #FF7A3C
  these may appear on Mac and on phone
  they do not enter the character grid

CONTENT (the job, owned by the program in the PTY)
  standard ANSI / xterm palette
  TUI themes (htop, lazygit, vim) keep their own colors
  Smolder does not recolor them to ember

# Illegal leaks
  orange ls, orange vim, orange htop because "brand"
  a theme store that lets a skin rewrite the grid
  hiding the wordmark to gain two rows of cells

External links

Exercise

List six visible pieces of a Smolder window (wordmark, title bar, rail, cursor, htop bars, vim syntax). Put each in chrome or content. For every content item, write one sentence about what breaks if it inherits ember. For every chrome item, write one sentence about what is lost if you hide it to gain grid rows.
Hint
If htop turns orange, you broke a TUI. If the wordmark vanishes, you broke across-the-room recognition. Both are reaches waiting to be dated.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.