docs: Update README title to 'Blip' and add a project tagline.

[themasterchiefdev]

Summary by CodeRabbit

• Documentation

  • Updated project title to "Blip" and added a short descriptive line to the README.

• Chores

  • Added automated build-and-deploy workflow to publish the site on pushes to main and a feature branch.
  • Configured the app to serve correctly from a subpath so hosted site asset paths resolve properly.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updates replace the README main header and add a short subtitle, add a GitHub Actions workflow to build and deploy the site to GitHub Pages on pushes to main and a feature branch, and set Vite's build base path to "/Blip/".

Changes

Cohort / File(s)	Summary
Documentation header update README.md	Main header changed to "Blip" and a subtitle added: "This app has been vibe coded using Google Anti Gravity." The previous main heading moved into an existing subsection.
CI / deployment workflow .github/workflows/deploy.yml	New GitHub Actions workflow triggered on pushes to main and feature/update-readme: checks out repo, sets up Node 20, caches npm, runs npm ci, builds with npm run build, and deploys dist to gh-pages using JamesIves/github-pages-deploy-action@v4.
Vite configuration vite.config.ts	Adds base set to "/Blip/" for build/public base path.

sequenceDiagram
    autonumber
    participant Dev as Developer (push)
    participant GH as GitHub
    participant Runner as Actions runner (ubuntu-latest)
    participant Node as Node.js (setup)
    participant NPM as npm / build
    participant Deploy as gh-pages-deploy-action
    Note over GH,Runner: Push to main or feature/update-readme
    Dev->>GH: push branch
    GH->>Runner: start build-and-deploy job
    Runner->>Runner: actions/checkout
    Runner->>Node: setup-node@v4 (Node 20)
    Runner->>NPM: npm ci -> npm run build (outputs `dist`)
    Runner->>Deploy: JamesIves/github-pages-deploy-action@v4 (deploy `dist` -> `gh-pages`)
    Deploy-->>GH: update `gh-pages` branch
    Note right of GH: Site published at repo GitHub Pages (expect base `/Blip/`)

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–30 minutes

• Review .github/workflows/deploy.yml for correct branch triggers, permissions, and the action version.
• Confirm vite.config.ts base matches the GitHub Pages repository path and routes.
• Ensure npm run build produces dist and that the deploy action's target branch and folder are intended.

Poem

🐰 I hopped through README, renamed with glee,
Pushed a workflow that ships the site carefree,
Vite got a path — "/Blip/" for the show,
Builds flow at night and pages softly glow,
I nibble the keyboard and dance in the snow. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title accurately describes the main documentation change (updating README title to 'Blip' and adding a tagline), but the changeset includes additional substantial changes like a new GitHub Actions deployment workflow and Vite configuration updates for GitHub Pages deployment.	Update the PR title to reflect all significant changes, such as 'docs: Update README, add deployment workflow, and configure Vite for GitHub Pages' or split into multiple focused PRs.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 094be2e and 59fcd57.

📒 Files selected for processing (1)

• .github/workflows/deploy.yml (1 hunks)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1dcd97c and 014335d.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[grammar] ~3-~3: Use a hyphen to join words.
Context: ...pp has been vibe coded using Google Anti Gravity. ## React + TypeScript + Vite ...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (1)

README.md (1)

1-5: Solid rebranding structure.

The rebranding looks good—moving "Blip" to the main title while demoting the tech stack to a subsection preserves the original context while establishing the project identity. The tagline is informal and engaging, fitting for a project-specific README.