Skip to content

feat(site): install is a Community link, not an org lookup - #31

Merged
tiagomoraes merged 2 commits into
mainfrom
feature/community-install
Jul 28, 2026
Merged

feat(site): install is a Community link, not an org lookup#31
tiagomoraes merged 2 commits into
mainfrom
feature/community-install

Conversation

@tiagomoraes

Copy link
Copy Markdown
Collaborator

tofig is public on Figma Community, and the site still told people to find it under their organization's plugins — a route that does not exist for anyone outside acaso.

Targeting main because develop no longer exists on the remote (deleted after #30) and main is what the Pages deploy watches.

Site

  • Every install route points at the listing: hero CTA on both pages, a persistent Get the plugin button in the nav, footer link, docs header, installUrl/sameAs in the structured data.
  • The install section is reordered for the people who actually install it: three plain steps — Open in… → pick a Design or Slides file → reopen from the canvas — with npm run build and the renderer CLI moved below them into the cards.
  • Docs Install rewritten around the Community page plus the in-file route (right-click → Plugins, or Actions). Quick start step 2 says where the plugin actually lives.
  • Nav button hides under 560px, where the row is already spent on brand + switch + star. Hero note leads with "one click, no account" and drops MIT to stay on one line; the licence still shows in the install meta and footer.

Docs

  • LISTING.md carries the canonical URL and a description written for the store page, with the Claude export prompt in the body.
  • PUBLISHING.md marked published-and-public.
  • README.md leads with the Community install; importing a manifest is labelled as the developer path.

Verified

Chrome at 390 / 520 / 600 / 840 / 900 / 1024 / 1100 / 1280 / 1440: no console errors, no horizontal overflow, nav CTA inside the wrap padding at every width. X-ray names the new step nodes (Frame · install-step). The workflow's internal-link check passes locally.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NJ5rqmRHgZn76zd5ytr2Zh

tiagomoraes and others added 2 commits July 28, 2026 14:45
tofig is public on Figma Community, and the site still told people to
find it under their organization's plugins — a route that does not exist
for anyone outside acaso.

Every surface now points at the listing, and the install section is
ordered for the audience that actually installs it: three plain steps
(Open in… → pick a Design or Slides file → reopen from the canvas), with
`npm run build` and the renderer CLI moved below them into the cards. A
build command above a one-click path makes the one-click path look like
a build step.

The nav gets the one filled control on the page, hidden under 560px
where the row is already spent on brand, switch and star. The hero note
leads with "one click, no account" and drops MIT to stay on one line;
the licence still shows in the install meta and the footer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NJ5rqmRHgZn76zd5ytr2Zh
LISTING carries the canonical plugin URL and a description written for
the people who read it on the store page rather than in the repo: the
Claude route and its export prompt are in the body now, since that is
what decides whether a first conversion succeeds.

PUBLISHING is marked published-and-public rather than describing the
public step as something still ahead. README leads with the Community
install; importing a manifest is what it is, a developer path.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NJ5rqmRHgZn76zd5ytr2Zh
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@tiagomoraes
tiagomoraes merged commit 96bfa4c into main Jul 28, 2026
4 checks passed
@tiagomoraes
tiagomoraes deleted the feature/community-install branch July 28, 2026 17:48
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