Files

1.8 KiB
Raw Permalink Blame History

Game UI Rename Example: "Feeding Frenzy" → "Shark Attack Fantasy League"

When the game was renamed from "Feeding Frenzy" to "Shark Attack Fantasy League", the following procedure was used across 6 files with 13 occurrences.

Files affected

File Occurrences What changed
draft-room.html 1 <title> tag
settings.html 1 <title> tag
league.html 1 <title> tag
help.html 5 title, hero subtitle, PWA description, notification step, troubleshooting ×2
how-to-play.html 3 title, overview paragraph, footer game-link-hint
sw.js 1 push notification default title
index.html 0 No references — landing page already used "Shark Attack"
manifest.json 0 No references

Second rename pass (Jul 9, 2026)

After the initial 13-occurrence rename, a follow-up pass found 8 more occurrences that were missed:

File Occurrences What changed
index.html 5 H1 heading, button text (HTML + 3 JS template literals)
league.html 1 H1 heading in top-bar
help.html 1 H1 heading in top-bar
how-to-play.html 1 H1 heading in top-bar

Renamed from "Feeding Frenzy" → "Shark Attack Fantasy League" and "Join the Frenzy" → "Join the League".

Verification state

  • Final search_files(pattern='Feeding|Frenzy', path='/var/www/shark-game/')total_count: 1 — one false positive in draft-room.html ("prime feeding times" — shark safety tip, genuine content).

What was NOT renamed (deliberately)

  • CSS class names, HTML IDs, JS variable references — unchanged
  • Database region names, league names from users — unchanged (they're user data)
  • API endpoint paths — unchanged
  • File/directory names — unchanged