Skip to content

Remove footer Privacy control and trim README - #22

Merged
msmfa merged 1 commit into
masterfrom
codex/typo-cleanup
Sep 10, 2026
Merged

Remove footer Privacy control and trim README#22
msmfa merged 1 commit into
masterfrom
codex/typo-cleanup

Conversation

@msmfa

@msmfa msmfa commented Sep 10, 2026

Copy link
Copy Markdown
Owner

What changed

Removed the footer Privacy controlscripts/build.mjs:180

Dropped the <button id="analytics-preferences" hidden>Privacy</button> from the footer nav in the generated page shell. It appeared on every generated page.

Trimmed the README — removed the Analytics and referrals, Deploy, and Search discovery sections, leaving Run locally, AI panel, and Content and checks.

Added a walkthrough GIFdocs/site-walkthrough.gif (263 KB), embedded under the website link. Shows the landing page followed by the Variables, Functions, Arrow Functions, and Closures pages.

Ignored /.claude — local editor and tooling config, alongside the existing /.vscode entry.

Why

Requested cleanup: the Privacy control and those README sections were no longer wanted, and the README needed a visual of the site.

Reviewer notes

Two consequences of removing the button that are not addressed in this PR, and may want a follow-up:

  1. That button was the only UI path for a visitor to reopen or withdraw the analytics consent choice. GA4 and PostHog still load on the production host; there is now no in-page way to change a saved decision.
  2. The consent banner copy at scripts/build.mjs:187 still reads "Change your choice anytime under Privacy," which no longer refers to anything.

Separately, the removed README prose was the only documentation of the GA4/PostHog configuration and the npm run indexnow step. Both still exist in the code (src/analytics-config.js, src/search-config.js, scripts/submit-indexnow.mjs); only the docs are gone.

Testing

node --test test/*.test.mjs — 70/70 pass.

src/analytics.js:146 already guarded the lookup with if (preferences), so the module works with the element absent. The analytics tests build a synthetic DOM harness rather than parsing the generated HTML, so they were unaffected by the markup change.

Verified against a running dev server: the served footer at /javascript-variables/ is now LinkedIn, Contribute on GitHub, Contact, Share. Note the button was hidden on localhost regardless, since analytics only starts on the production hostname allowlist, so the check that matters is the element being gone from the served HTML.

The GIF was assembled from headless Chrome screenshots of the local build, not a screen recording, so it has no cursor or click indicators.

🤖 Generated with Claude Code

Remove the hidden `#analytics-preferences` "Privacy" button from the
footer nav in the generated page shell. `startAnalytics` already guards
its lookup with `if (preferences)`, so the analytics module keeps working
with the element absent; the consent banner itself is unchanged.

Trim the README to what a contributor needs to run and change the site:
drop the "Analytics and referrals", "Deploy", and "Search discovery"
sections. Add a walkthrough GIF under the website link showing the
landing page and four concept pages.

Ignore /.claude, which holds local editor and tooling config.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@msmfa
msmfa merged commit 60a92b0 into master Sep 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant