Skip to content

fix: landing CTA showed 'pip install spiritwriter-core'#16

Merged
aaronmarkham merged 1 commit into
mainfrom
fix/landing-install-label
Jun 1, 2026
Merged

fix: landing CTA showed 'pip install spiritwriter-core'#16
aaronmarkham merged 1 commit into
mainfrom
fix/landing-install-label

Conversation

@aaronmarkham

Copy link
Copy Markdown
Owner

The bug

The home page's second copy-install button displayed pip install spiritwriter-core — the stale "core" CTA visible live on news.spiritwriter.ai (footer commit 3636876). This was the one spot the package rename missed:

  • Button 1 (landing.html:1079): pip install spiritwriter ✅ (already correct)
  • Button 2 (landing.html:1348): pip install spiritwriter-core ❌ → fixed
  • Clipboard JS (landing.html:1415): copies pip install spiritwriter ✅ (already correct)

So the button copied the right command but showed the wrong one.

Why it looked like a stale deploy

It wasn't — the deployment was current with main. The latest code itself still carried this visible label. The distribution name is spiritwriter (the GitHub repo stays spiritwriter-core), so only the install-command text needed to change.

Change

One line: the visible label on the closing-CTA copy button → pip install spiritwriter. No other spiritwriter-core strings remain in landing.html outside the legitimate GitHub repo URLs.

Merging this to main triggers the deploy workflow, which re-renders the site.

🤖 Generated with Claude Code

The second copy-install button's visible label still read the old
package name while the clipboard action and the first button already
used `spiritwriter`. Distribution is `spiritwriter`; the repo stays
`spiritwriter-core`. This is the "core" CTA visible live on the home page.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@aaronmarkham aaronmarkham merged commit 863d1d5 into main Jun 1, 2026
1 check 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