Frontend copy: "Project" replaced with "Matter" across 17 files, internals unchanged

vincentbirot's first merged PR is a pure label swap - every user-visible "Project"/"Projects" in the Mike frontend becomes "Matter"/"Matters" to match legal-industry vocabulary. No schema, route, or API identifier changes.

brandingchat-ui

The bulk of the work is commit bf59784: ~40 changed lines across 15 components covering tabs, button labels, aria attributes, breadcrumbs, modal headers, empty states, and column headers. A follow-up commit a461d97 catches the strings missed in AddNewTRModal.tsx and DisplayWorkflowModal.tsx.

The boundary was drawn deliberately. Component names (NewProjectModal, SelectAssistantProjectModal), TypeScript types, prop names, the /projects URL path, and all API identifiers (listProjects, projectId) are untouched. So the URL bar still reads /projects, developer logs still say "project", and the database schema is identical to upstream. The commit messages name this tradeoff explicitly.

The practical consequence: every future upstream merge from willchen96/mike that touches these string positions will produce conflicts. Not a lot of conflicts, but predictable, recurring ones.

So what Worth pulling if your product targets law firms where "matter" is the expected term for a client engagement. Skip if you're not in legal - the rename creates ongoing merge friction with no benefit to a non-legal audience. If you do adopt it, a labels constants file would be cheaper to maintain than scattered string replacements.

View this fork on GitHub →

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

Commits in this thread

3 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>
9d5c2abb Merge pull request #1 from vincentbirot/feat/rename-project-to-matter vincentbirot 2026-05-03 ↗ GitHub
feat(ui): rename Project label to Matter

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-97.md from inside the repo you want the changes in.

⬇ Download capture-thread-97.md