Skip to content

feat(site): add a landing page and deploy it to GitHub Pages - #33

Merged
killerwolf merged 1 commit into
mainfrom
feat/landing-page
Sep 7, 2026
Merged

feat(site): add a landing page and deploy it to GitHub Pages#33
killerwolf merged 1 commit into
mainfrom
feat/landing-page

Conversation

@killerwolf

Copy link
Copy Markdown
Owner

QuickToss has nowhere to send someone who isn't already on GitHub. The README is a fine README, but "download the app" and "read the repo" are different jobs — a .dmg behind a releases table asks a lot of a person who just wants their Downloads folder cleaned out.

Deploys to https://h4md1.fr/QuickToss/.

The page

  • Screenshot up front. For an app with no registry page doing the explaining, the picture is the pitch.
  • Two Mac builds as the primary action, Apple Silicon and Intel, with the "Apple menu → About This Mac" hint for people who don't know which they have.
  • The "QuickToss.app is damaged" workaround immediately after the buttons, not buried. Every single user hits that dialog on first launch and most read it as malware. It's an amber callout with a copy button on the xattr -cr command.
  • Three-step how-it-works using the app's own red/green toss-and-keep colours, the keyboard table, the preview formats, and the three privacy guarantees.

Download links stay current on their own

Asset names carry the version (QuickToss-1.5.0-arm64.dmg), so there is no stable "latest" URL for them — a hardcoded link would break on every release. The page resolves the newest release's real .dmg URLs from the GitHub API at load:

armHref   → .../releases/download/v1.5.0/QuickToss-1.5.0-arm64.dmg
intelHref → .../releases/download/v1.5.0/QuickToss-1.5.0-x64.dmg
relMeta   → "v1.5.0 — 7 septembre 2026 · All releases · Changelog"

Both buttons start out pointing at the releases page, so they work with JS off, when the API is rate-limited, or offline.

Deployment

Publishes site/ from main via actions/deploy-pages, rather than a gh-pages branch — the page's source lives next to the code it describes, and there's no branch to check out and hand-edit. Triggers only on changes to site/** or the workflow itself.

Pages source must be set to "GitHub Actions" before this can publish; there is no Pages site on this repo yet. I'll set it once this merges.

Verified in a browser

  • All six outbound links return 200, including both .dmg assets.
  • No broken images, no console errors.
  • At 375px: no horizontal overflow, no offending elements, steps and cards stack to one column, the download button fits.
  • Light and dark both handled via prefers-color-scheme.

Caught while checking: a stray Apple-logo glyph (U+F8FF, private-use — renders as tofu off-Apple) had been dropped in encoding, leaving a dangling arrow. Replaced with plain words.

Honesty

Every claim comes from the README — the preview formats, the shortcuts, the privacy guarantees, and the fact that it's macOS-only for now. Nothing invented.

🤖 Generated with Claude Code

QuickToss had nowhere to send someone who isn't already on GitHub. The
README is a fine README, but "download the app" and "read the repo" are
different jobs, and a .dmg behind a releases table asks a lot of a person
who just wants their Downloads folder cleaned out.

Adds site/index.html: the screenshot up front, the two Mac builds as the
primary action, and the "QuickToss.app is damaged" workaround immediately
after them rather than buried — every single user hits that dialog on
first launch, and most read it as malware.

The download buttons resolve the newest release's actual .dmg URLs at
runtime from the GitHub API. Asset names carry the version, so there is no
stable "latest" URL for them; without this the page would go stale on
every release. It degrades to the releases page when the API is
unreachable, so the buttons work with JS off.

Deploys from main via an artifact rather than a gh-pages branch, so the
page's source lives next to the code it describes and there is no branch
to check out and hand-edit. Pages source must be set to "GitHub Actions"
for the workflow to publish.

Every claim is from the README: the previews list, the shortcuts, and the
three privacy guarantees.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@killerwolf
killerwolf merged commit 783b54c into main Sep 7, 2026
2 checks passed
@killerwolf
killerwolf deleted the feat/landing-page branch September 7, 2026 14:41
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