Skip to content

feat(site): Make omesser.github.io/fidget the Fidget landing page #1210

Closed

Description

@omesser

Goal

Make https://omesser.github.io/fidget/ the place a first-time visitor lands: what Fidget is, what it looks like moving, and one click to install it. It is for people arriving from a link, a post or a search, who have never opened the repository. Contributors keep the README and the design pages.

Current state

Design

Demo: #1211 (merged). It is a Dated mockup at docs/design/landing.html, published at /landing.html, and it uses the gallery's own published frames. It is laid out as a hero with the README headline, three platform buttons and the cask line, then Buddy Bot perched on a mock window and talking. Below that sit the four "What it does" cards, the Harness list, the eight packaged Fidgets walking, and three cards on adding your own. It ends with a footer linking the gallery and the design pages.

Landing mockup at 1280 px

The shipped page is Generated, not hand-written. scripts/make-landing-page.py reads the headline, the feature bullets and the Harness names from README.md, the cast from characters/*/character.manifest, and the release tag from the cask. The README and the landing page then share one source and cannot drift, which answers ADR-0011's objection. The generator reuses the frames the gallery already copies into _site/characters/.

URL plan:

URL After this issue
/ and /index.html The landing page
/design.html The design-page directory. Every existing design page stays published and reachable from it, linked from the landing footer only, off the visitor path
/characters.html, /cues.html, /bubble.html, /chat.html, /chat-mockups.html, /expression.html, /window-titles-hint.html Unchanged
/landing.html Gone once the generated page owns the root. Nothing links a specific landing file, only / (decision 5)
omesser.github.io/ai-buddy/* Stays 404. Losing the old slug is accepted (decision 4)

Decisions

Answered by @omesser on 2026-10-01.

  1. Amend ADR-0011: yes. Task 2 goes ahead.
  2. Hero media: yes. Originally a shared GIF (not docs(readme): Lead with a hero GIF of a throw, a perch, and a reply #1188's). docs(readme): Lead with a hero GIF of a throw, a perch, and a reply #1188 put an MP4 on the README; feat(site): Play the README's demo video in the landing hero of the website #1254 made the landing hero play that same attachment URL instead of a GIF. Task 7 is done under that design.
  3. Delete the tmp: #588 release: no. A new, more relevant release is coming. Task 6 originally pinned via the cask; feat(site): Link each download button to its asset in the Latest release #1257 instead links Latest-release assets by suffix (and falls back to /releases/latest when an asset is missing).
  4. Redirects for omesser.github.io/ai-buddy/*: no. The old slug can go.
  5. About website field: yes, set to https://omesser.github.io/fidget/. Done — repo homepage is that URL. The root serves the landing page, so nothing should link landing.html or any other specific file.

Tasks

Each item is one PR against main, in order. Every PR runs node --test tests/, and its Pages build job uploads the site artifact, which is the preview.

  • 1. docs(design): Propose the landing page as a Dated mockup. Done in docs(design): Propose the landing page as a Dated mockup #1211 @ 1b47786. Touches docs/design/landing.html, docs/design/index.html (entry), .github/workflows/pages.yml (one cp) and tests/design-pages.test.js. Published at /landing.html. Depends on nothing.
  • 2. docs(adr): Let a Generated landing page own the site root. This adds a new ADR that amends ADR-0011 and leaves it live, because pages.yml and both generators cite it. It touches docs/adr/00NN-*.md and one pointer line in ADR-0011. Verified by node --test tests/ (adr-citations.test.js). Depends on decision 1.
  • 3. ci(pages): Also publish the design index at /design.html. This one is additive, and the root stays as it is. It touches .github/workflows/pages.yml, and switches the demo's "Design pages" links to design.html. Verified when the PR's Pages artifact holds both index.html and design.html with identical bytes, and after deploy curl -I /design.html returns 200. Depends on 2.
  • 4. feat(site): Generate the landing page from README.md and characters/. This adds scripts/make-landing-page.py (stdlib, --out and --self-check, like the gallery). It turns docs/design/landing.html into the page shell with a data block and publishes it at /landing.html. It also adds tests/landing-page.test.js, which runs the generator into a temp dir and asserts that the README headline and all eight character names appear, and that a README with no H1 fails the build. The cast and its count come from characters/, so a ninth character needs no page edit. Review on docs(design): Propose the landing page as a Dated mockup #1211 also asks for the walk loops to pause while the tab is hidden, with reduced-motion stills kept, and for the hero bubble to be tied to the sprite for assistive tech. Verified by that test, --self-check in the workflow, and a screenshot of the PR artifact. Depends on 3.
  • 5. feat(site): Serve the landing page at the site root. The generator writes _site/index.html, the design index moves to /design.html only, and /landing.html is no longer published. It also adds <meta name="description">, Open Graph tags with a PNG image and a canonical link. The brand link points at the root, and "Design pages" appears in the footer only. It touches .github/workflows/pages.yml, the generator and tests/landing-page.test.js. Verified by the artifact check (root is the landing page, and every URL in the table resolves) and, after deploy, by curl on each URL in the table. Depends on 4.
  • 6. feat(site): Link each download button to its asset in the pinned release. Done in feat(site): Link each download button to its asset in the Latest release #1257 @ 8d1aa10 with a changed design: pages.yml reads Latest via gh release view --json tagName,assets and the generator matches each button by asset suffix (_aarch64.dmg, -setup.exe, .AppImage); no cask / build: Publish the Homebrew cask with each Release #1204 dependency. Missing asset falls back to /releases/latest. A successful Release run refreshes the page via workflow_run. Verified by landing-page tests and live / linking the three v0.1.0 Fidget_* assets (302). Depends on 5 (decision 3 path evolved).
  • 7. feat(site): Show the hero GIF on the landing page. Done in feat(site): Play the README's demo video in the landing hero of the website #1254 @ 76a62d9 with a changed design: the hero plays the README's user-attachments demo video (hotlinked <video>), not a GIF; no .mp4 in the repo and the _site guard is unchanged. Desk vignette remains the fallback. Verified by landing-page tests + Chrome CDP checks in the PR. Depends on 5 and the README media (decision 2 / docs(readme): Lead with a hero GIF of a throw, a perch, and a reply #1188 path evolved).
  • 8. docs(readme): Point the README at the landing page. This adds one link under the banner and leaves Get It as is. It touches README.md. Verified by node --test tests/ (readme-gifs only — rename-to-fidget was removed on main; see hygiene after chore: Delete the one-time rename-to-fidget lever and its test #1233). Depends on 5.

Decision 5 (About website) is set. All numbered tasks 1–8 are done.

— Claude Code agent, on @omesser's behalf.

Activity

  1. added this to the V1 milestone on Sep 30, 2026
  2. added
    enhancementNew feature or request
    p2Eventually: real, but nothing waits on it
    on Sep 30, 2026
  3. omesser commented on Oct 1, 2026

    @omesser
    OwnerAuthor

    Hygiene after #1233: task 8’s verify line still names rename-to-fidget, but that test (and the lever) were deleted on main. When that task runs, verify with readme-gifs (and the rest of node --test tests/) only — drop the rename-to-fidget mention.

    — Cursor agent (Coder), on @omesser's behalf.

  4. omesser commented on Oct 1, 2026

    @omesser
    OwnerAuthor

    Hygiene after #1211 merged onto main @ 1b47786:

    Done — task 1. The Dated mockup is on main: docs/design/landing.html, design-index entry, Pages cp to /landing.html, and the design-pages tests. Live preview path: /landing.html (root still the design directory until later tasks).

    Still open — tasks 2–8 (ADR amend, /design.html, Generated landing, root cutover, pinned download links, hero GIF, README link). No close.

    — Cursor agent (Coder), on @omesser's behalf.

  5. omesser commented on Oct 1, 2026

    @omesser
    OwnerAuthor

    Tasks 2, 3, 4, 5 and 8 are in #1244, one commit per task:

    Still open:

    — Claude Code agent, on @omesser's behalf.

  6. omesser commented on Oct 1, 2026

    @omesser
    OwnerAuthor

    Hygiene after #1244 merged onto main @ ad368d5:

    Done — tasks 2, 3, 4, 5, and 8 (checkboxes updated in the issue body).

    On main now:

    • ADR-0038 amends ADR-0011; ADR-0011 Status points at it
    • /design.html is the design directory (docs/design/design.html); Pages no longer publishes /landing.html
    • scripts/make-landing-page.py + tests/landing-page.test.js generate the root page from README + manifests
    • Root / / index.html is the Generated landing page (meta description, Open Graph, canonical)
    • README links the site under the banner

    Still open — leave this issue open:

    • Task 6 — pinned release download assets (buttons still point at v0.0.1-dev; Homebrew line waits on the cask on main / build: Publish the Homebrew cask with each Release #1204)
    • Task 7 — hero GIF (and .gif in the Pages guard)
    • Decision 5 — set the repo About website to https://omesser.github.io/fidget/ once Pages has deployed this merge (repo setting, outside PRs)

    No close.

    — Cursor agent (Coder), on @omesser's behalf.

  7. omesser commented on Oct 2, 2026

    @omesser
    OwnerAuthor

    Hygiene after #1188 merged onto main @ 1ad038c:

    README hero shipped — the README now embeds a throw/perch/reply take as a user-attachments MP4 (not a repo GIF). docs/readme/hero.gif is gone; scripts/scenarios/hero-gif.sh is on main.

    Does not clear task 7 — decision 2 still stands: landing-page hero waits on a separate GIF recording that the README and generator can share as a file. This merge also does not extend the Pages _site guard with .gif.

    Still open — leave this issue open: task 6 (pinned release assets), task 7 (hero GIF + guard), decision 5 (About website once Pages is current).

    No close.

    — Cursor agent (Coder), on @omesser's behalf.

  8. omesser commented on Oct 2, 2026

    @omesser
    OwnerAuthor

    Task 7 is in #1254, with a changed design. The hero plays the MP4 the README already embeds, hotlinked from its user-attachments URL. There is no GIF and no .mp4 in the repo, and the _site extension check is unchanged. Without the video the hero is the sprite desk scene.

    — Claude Code agent, on @omesser's behalf.

  9. omesser commented on Oct 2, 2026

    @omesser
    OwnerAuthor

    Hygiene after #1254 merged onto main @ 76a62d9:

    Done — task 7 (checkbox + decision 2 note updated in the issue body), with the PR’s changed design rather than a GIF:

    • Landing hero plays the README’s first standalone user-attachments URL as a muted looping <video> (hotlinked; no .mp4 in the repo)
    • _site extension guard unchanged (no .gif / .mp4 publish)
    • Sprite desk vignette stays as fallback when there is no attachment line or the video fails to load
    • Reduced motion: paused with native controls
    • Covered by three new tests/landing-page.test.js cases plus the PR’s Chrome CDP checks

    Still open — leave this issue open:

    • Task 6 — pinned release download assets
    • Decision 5 — set the repo About website to https://omesser.github.io/fidget/ (repo setting; task 5 already deployed)

    PR open question left as product follow-up, not tracked here: whether every visitor should get controls for WCAG 2.2.2 (autoplay loop without a pause control).

    No close.

    — Cursor agent (Coder), on @omesser's behalf.

  10. omesser commented on Oct 2, 2026

    @omesser
    OwnerAuthor

    Task 6 is in #1257, with a changed design. The Pages build reads the Latest release with gh release view and matches each button to its asset by suffix. It no longer reads the cask tag, so it does not depend on #1204. A button with no matching asset links /releases/latest. The page refreshes when a Release run succeeds, so publishing a release needs no commit.

    — Claude Code agent, on @omesser's behalf.

  11. omesser commented on Oct 2, 2026

    @omesser
    OwnerAuthor

    Hygiene after #1257 merged onto main @ 8d1aa10:

    Done — task 6 (checkbox + decision 3 note updated in the issue body), with the PR’s changed design rather than a cask-pinned tag:

    • pages.yml reads Latest with gh release view --json tagName,assets and passes it to make-landing-page.py --release
    • Each download button matches its asset by suffix; missing asset → /releases/latest
    • Successful Release runs refresh the page via workflow_run (no commit needed)
    • No dependency on build: Publish the Homebrew cask with each Release #1204 / the Homebrew cask
    • Live https://omesser.github.io/fidget/ already links the three v0.1.0 Fidget_* assets; each returns 302 to the download CDN

    Also done — decision 5: repo About website is already https://omesser.github.io/fidget/.

    All tasks 1–8 and decisions tracked here are complete → closing as completed. #1204 stays open on its own (Homebrew cask publish).

    — Cursor agent (Coder), on @omesser's behalf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestp2Eventually: real, but nothing waits on it

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions