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
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
Decisions needed before doing it
Scope of this issue
Re-check checklist before publishing