Skip to content

Publish widget to Figma Community – unblock view-only access for non-installers #36

Description

@jnwrnr

Background

During the internal beta, a tester (Patrick) opened a board with GitJam cards on it in the browser, saw the static card data, but hit 'Could not find widget code to run' when trying to click anything. This is expected behaviour for dev-imported widgets: the widget code only runs on the machine of the person who imported the manifest. Other viewers see a static snapshot of syncedState but can't interact.

See: https://gitlab.com/jnwrnr/gitjam/-/work_items/2

What changes with a Community publish

  • Widget code is hosted on Figma's side and runs for every viewer of a file, without any local install.
  • Non-installers can click the card, interact with edits, toggle status etc.
  • The install instructions currently in the README become unnecessary for viewers — only people who want to place new cards still need access to the widget (by searching in the widgets panel).

Decisions needed before doing it

  • Visibility: widgets on Community don't have an 'unlisted' mode. We'd be fully public. Accept that.
  • Pricing tier at launch: free initially (per monetization-strategy.md), paid feature-gate later. This impacts which features we want active on day 1.
  • Review timing: Figma review for Community widgets takes roughly 1–2 weeks.
  • Cover image + screenshots + description – we already have the cover asset and README; need to produce 3–5 listing screenshots.

Scope of this issue

  • Check that nothing in our dev manifest blocks a public publish (editorType both already set).
  • Prepare Community listing assets (description copy, screenshots, tags).
  • Apply for Community creator status if not already done.
  • Publish, monitor review, ship.

Re-check checklist before publishing

  • Verify the 'viewer can interact' behaviour referenced in this issue is actually fixed post-publish (test on a second machine with no local install).
  • Ensure the private Cloudflare Worker URL and proxy are production-ready (no stray logs, reasonable rate limits).
  • Close Patrick's GitLab issue with a link to the public listing.
  • Update README and getting-started to say 'install from Figma Community' instead of 'download the zip'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Nice to havearea:widgetFigJam widgettype:infraTooling, CI, build, tests

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions