"Project" relabelled to "Matter" in UI copy; codebase internals left as-is

vincentbirot renamed every user-facing "Project" label to "Matter" across the Lex Nova frontend, aligning the product to standard legal-industry vocabulary. File names, component names, routes, and API identifiers were deliberately kept unchanged.

brandingchat-ui

Two commits, 17 files. The first pass (bf59784) touches 15 components - tab labels, button text, aria attributes, breadcrumb spans, modal headings, empty-state copy, and the column header in the tabular reviews table. The second (a461d97) fills in strings missed in AddNewTRModal.tsx and DisplayWorkflowModal.tsx.

The stated scope was strictly user-visible copy: JSX string literals, placeholders, and toast messages. Component names stay NewProjectModal and SelectAssistantProjectModal. The /projects route is unchanged. TypeScript types, prop names, and API method names (listProjects) all retain "project". Anyone reading the URL bar, browser history, or server logs sees the original term while the UI speaks "matter". vincentbirot documented this as intentional - a minimal first step, with deeper renaming deferred if it ever becomes necessary.

The PR opened and merged in roughly twenty minutes. It was also described as a smoke test for an autonomous Claude Code build loop running Haiku 4.5 on a local Mac, which explains the tight two-commit shape.

So what Worth pulling if you serve law firms and want the UI vocabulary to match how lawyers talk about their work. The adoption cost is low now but accumulates on every upstream merge - the same string positions will conflict each time. If you adopt it, consolidating labels into a single constants file would stop the conflicts from compounding.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from vincentbirot/lexnova-mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`bf597840`	feat(ui): rename Project label to Matter	Vincent Birot	2026-05-03	↗ GitHub
commit body Update all user-facing UI labels from "Project"/"Projects" to "Matter"/"Matters" to align with legal industry terminology. Component names, prop names, types, routes, and API endpoints remain unchanged. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
`a461d97c`	feat(ui): rename Project label to Matter	Vincent Birot	2026-05-03	↗ GitHub
commit body Rename user-visible "Project" text to "Matter" throughout the frontend to align with legal terminology. Changes include: - Navigation sidebar: "Projects" → "Matters" - Form labels and placeholders: "project/projects" → "matter/matters" - Buttons and breadcrumbs: "Projects" → "Matters" - Empty states and messaging: Updated all user-facing copy Does NOT change: - File names, component names, prop names, types - URL paths and API endpoints - Variable and function names Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

SHA

Subject

Author

Date

bf597840

feat(ui): rename Project label to Matter

Vincent Birot

2026-05-03

↗ GitHub

commit body

Update all user-facing UI labels from "Project"/"Projects" to "Matter"/"Matters"
to align with legal industry terminology. Component names, prop names, types,
routes, and API endpoints remain unchanged.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

a461d97c

feat(ui): rename Project label to Matter

Vincent Birot

2026-05-03

↗ GitHub

commit body

Rename user-visible "Project" text to "Matter" throughout the frontend to align with legal terminology. Changes include:
- Navigation sidebar: "Projects" → "Matters"
- Form labels and placeholders: "project/projects" → "matter/matters"
- Buttons and breadcrumbs: "Projects" → "Matters"
- Empty states and messaging: Updated all user-facing copy

Does NOT change:
- File names, component names, prop names, types
- URL paths and API endpoints
- Variable and function names

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-325.md from inside the repo you want the changes in.