Skip to content

feat(brand): add ™ to appbar + drawer wordmark#297

Merged
0800tim merged 1 commit into
mainfrom
feat/wordmark-tm
Jun 5, 2026
Merged

feat(brand): add ™ to appbar + drawer wordmark#297
0800tim merged 1 commit into
mainfrom
feat/wordmark-tm

Conversation

@0800tim

@0800tim 0800tim commented Jun 5, 2026

Copy link
Copy Markdown
Owner

Tim 2026-06-05: assert common-law trademark rights on "Tournamental" with the ™ notice (no ® until IPONZ grants registration, since false ® usage is an offence under the NZ Trade Marks Act 2002 s 200). Common-law TM notation requires no registration in NZ/US/UK/AU/EU.

  • AppBar wordmark: Tournamental™ FWC2026
  • Drawer brand: Tournamental™
  • New .vt-appbar-wordmark-tm + .vt-drawer-brand-tm rule sized at 0.35em, gold-tinted, vertically lifted 0.85em so it tracks the Saira cap height. <sup> element for semantic correctness.

Tim 2026-06-05 asked whether the unregistered-trademark notice
needs prior registration. It doesn't (NZ Trade Marks Act 2002
restricts only the (R) symbol pre-registration; ™ is a common-law
notice anyone may use on a mark they're asserting). Wiring it in
ahead of an IPONZ filing so visitors are on notice.

* AppBar wordmark: 'Tournamental(TM) FWC2026'
* Drawer brand name: 'Tournamental(TM)'

Styling:
* New rule shared by .vt-appbar-wordmark-tm + .vt-drawer-brand-tm
* 0.35em size so it reads as a footnote on the mark, not a glyph
  alongside it
* Gold (--vt-gold-400) to subordinate it visually
* Manual vertical-align 0.85em so the TM tracks the Saira cap
  height rather than the default x-height-aligned superscript
* <sup> for semantic correctness; the parent wordmark span is
  already aria-hidden so screen readers continue to hear the link
  label 'Tournamental, homepage' without the TM glyph being
  announced

Once IPONZ grants registration we'll swap (TM) for (R) (one-char
edit in two files). Until then this is the legally-safe form.

Refs: docs/internal/home-polish-spec.md
Signed-off-by: Tim Thomas <0800tim@gmail.com>
@0800tim 0800tim merged commit 42bab7a into main Jun 5, 2026
11 of 12 checks passed
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

DRY-RUN — this verdict is informational; CI is not blocked.

Auto-triage: GREEN — auto-triage clear

Risk score: 0/100

Metric Value
Files changed 3
Lines added 28
Lines removed 2
Apps touched apps/web
New dependencies 0
New 3rd-party hosts 0

No flags raised by the automated scanners. A human reviewer will still take a look.

Labels applied: area:web, auto-triage:green

Posted by @vtorn/pr-triage-bot. How this works: docs/security/01-pr-triage-process.md. Disagree with the verdict? Comment /triage override <reason> and a maintainer will re-review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant