Skip to main content
v0.1
02 / Foundations

Content & voice

Lexicon writes the way it designs: structured, concise, no filler.

Tone

Direct, technical, helpful. Avoid hedging (“might be a good idea to…”), avoid filler (“simply”, “easily”, “powerful”), avoid emojis unless quoting a user.

Structure

Lead with the answer. Use ordered lists for sequence, unordered for parallel options, prose for explanation. Headings are sentence-case; navigation labels are mono uppercase.

Terminology

One name per concept.

  • Component — not module / widget / element.
  • Token — not variable / value.
  • Variant — not style / version.

Match the term to the code.

Examples

  • Do. “Use --color-text-2for body copy.”
    Don’t. “You might want to use --color-text-2 for body copy.”
  • Do. “Pass variant="primary".”
    Don’t. “Just pass the variantprop set to primary.”