Contact person: Business Client

Phone:Show

Email:Show

Location: Ceres, South Africa

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need a lightweight Chrome extension that runs entirely on the user’s machine. The extension should inject a small content script into any [login to view URL] page and let me click on visible text—scores, team names, kick-off times, or any other DOM text node—and replace it instantly. Nothing may be sent to, or requested from, external servers; no remote-code injection or analytics.

Core behaviour
• Works only on [login to view URL] pages, using a manifest-v3 content script and a simple CSS overlay.
• When the edit mode is active, hovering a text node highlights it; clicking opens a small popup editor positioned near the cursor.
• Edits apply immediately in the DOM, persisting only in-memory (unless you opt to cache them in [login to view URL] so a single-page refresh can recall them; full reload returns the page to its original state).

Quality-of-life additions
• Keyboard shortcuts for the main actions (toggle edit mode, save change, cancel, undo, redo).
• Full undo/redo stack for the current page session.
• Visual highlight (subtle background colour) for every text node that has been altered.

Controls
• Primary on/off toggle appears in the right-click context menu; once enabled, a slim floating toolbar indicates status.
• No toolbar icon or omnipresent UI required beyond the context-menu entry and the in-page popup editor.

Tech notes
• Please stick to standard Chrome APIs: content scripts, [login to view URL], contextMenus, and minimal CSS for the overlay.
• No frameworks are needed; vanilla JavaScript or a micro-library like [login to view URL] or lit-html is fine if it keeps the payload small.
• Code should be clean, modular, and well-commented so I can extend it later.

Deliverables
1. Unpacked extension folder ready for Developer-Mode loading (manifest v3).
2. Brief README with installation steps and a table of default shortcuts.
3. Source files with descriptive comments.

I’ll test by loading the extension, opening a current [login to view URL] match page, replacing a few scores, undoing/redoing them, and confirming no network calls are made in DevTools. If the above workflow runs smoothly, the job is done." (client-provided description)