Skip to content

Rename Meeting Mind to Context Recall and update project copy#29

Open
JWhite212 wants to merge 1 commit into
mainfrom
2026-05-08/13-58-43/feat/update-project-name-and-references
Open

Rename Meeting Mind to Context Recall and update project copy#29
JWhite212 wants to merge 1 commit into
mainfrom
2026-05-08/13-58-43/feat/update-project-name-and-references

Conversation

@JWhite212
Copy link
Copy Markdown
Owner

Motivation

  • Replace legacy Meeting Mind references with the new project name Context Recall across README and site content to keep the portfolio accurate.
  • Reframe project text to a professional, privacy-first posture using consent-first and local-first language and avoid wording that implies secret or undetectable recording.
  • Update transcription tooling and storage wording to reflect the rename and clarify local data/log paths under user control.

Description

  • Updated the featured project entry in README.md to Context Recall and replaced the repo link with https://github.com/JWhite212/context-recall.
  • Edited lib/content.ts case study: changed slug to context-recall, title to Context Recall, rewrote summary, problem, and approach text to emphasise "consented recordings", "user-controlled capture", "local-first", and "privacy-conscious meeting recall".
  • Replaced occurrences of faster-whisper with MLX Whisper, updated stack, metrics, architecture, media alt text and captions, and added wording that data and logs are stored in app-managed local paths under user control.
  • Ran code style formatting with npx prettier --write and committed the changes; a PR was created for review.

Testing

  • Ran npm run check; initial run reported Prettier style issues which were fixed by running npx prettier --write and re-checking (format check now passes).
  • Ran npm run lint; the lint step fails due to an existing repository configuration issue (Invalid project directory provided, no such directory: /workspace/Portfolio-Website/lint) which is unrelated to this rename and remains outstanding.
  • Changes are formatted and committed; no additional automated test failures were introduced by the textual updates.

Codex Task

@vercel
Copy link
Copy Markdown

vercel Bot commented May 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
portfolio-website Ready Ready Preview, Comment May 8, 2026 1:59pm

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 8, 2026

Warning

Rate limit exceeded

@JWhite212 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 46 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 270227b3-a1bd-4c3c-8c01-b2366c0739ce

📥 Commits

Reviewing files that changed from the base of the PR and between 680f30c and 981b1af.

📒 Files selected for processing (2)
  • README.md
  • lib/content.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 981b1af443

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread lib/content.ts
{
slug: "meeting-mind",
title: "Meeting Mind",
slug: "context-recall",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve legacy project slug with a redirect alias

Changing the case-study slug from meeting-mind to context-recall makes /projects/meeting-mind unreachable, and app/projects/[slug]/page.tsx calls notFound() for unknown slugs, so previously shared links/bookmarks and indexed URLs now return 404. Keep the renamed title, but add a redirect or slug alias so the old route resolves to the new canonical page.

Useful? React with 👍 / 👎.

Comment thread lib/content.ts
{
slug: "meeting-mind",
title: "Meeting Mind",
slug: "context-recall",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve legacy project slug with a redirect alias

Changing the case-study slug to context-recall makes /projects/meeting-mind unreachable because unknown slugs fall through to notFound() in the dynamic route handler, so existing bookmarks/shared links for the old URL now 404. Add a redirect/alias from the legacy slug to the new slug to avoid breaking previously published project URLs.

Useful? React with 👍 / 👎.

Comment thread lib/content.ts
title: "Local-first transcription with MLX Whisper",
detail:
"Runs the entire speech-to-text pipeline on-device using faster-whisper's CTranslate2 backend, avoiding cloud transcription APIs entirely. This keeps all meeting audio on the machine, addresses privacy requirements for sensitive discussions, and eliminates per-minute API costs.",
"Runs the entire speech-to-text pipeline on-device using MLX Whisper's CTranslate2 backend, avoiding cloud transcription APIs entirely. This keeps all meeting audio on the machine, addresses privacy requirements for sensitive discussions, and eliminates per-minute API costs.",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove incorrect CTranslate2 backend claim for MLX Whisper

This text now states the transcription stack is MLX Whisper on a CTranslate2 backend, but those are different inference backends, so the updated case study describes an internally inconsistent architecture. Because this portfolio page is meant to communicate technical decisions, this mislabels the implementation and should be corrected to the actual backend used.

Useful? React with 👍 / 👎.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant