← Knowledge base

Community owners · Account & settings

Widgets, components and public links

Embed the storefront or registration wizard on another website and keep the generated configuration with the page that uses it.

JollyBee supplies public links for sharing and script-based components for placing selected experiences inside another website.

Settings exposes links for the community page, join flow and sign-in. Use the community page for discovery, the join link for a membership campaign and sign-in for people who already have an account. These are ordinary links and work without installing a widget.

Storefront component

The storefront widget can include active memberships and access offerings, products and events. Its generator can control the visible sections, layout, cart behaviour, columns, maximum items, call-to-action text, images, descriptions and filters.

Preview every chosen section. The generator warns when a selected section has no eligible public content, but a technically valid embed cannot invent an active offering or event.

Registration-wizard component

Use the registration component when another website should open the community's active default signup wizard, or the wizard assigned to an optional pre-selected tier slug. The generator does not choose a wizard ID directly. Test the resolved wizard, its required fields, agreements, validation and payment before embedding it.

Install and maintain the snippet

Copy the generated script into a custom HTML or embed block on WordPress, Wix or another site that allows scripts. Plain HTML pages can include it directly. The surrounding site must allow the script and network requests; a strict content-security policy or sanitising editor can block it. There is no in-app widget preview, so paste it into a staging page and complete a real test there before publishing.

The generator's choices are encoded in the copied snippet. They are not saved as a named widget configuration in JollyBee. When the layout or sections change, regenerate the snippet and replace the old copy on every website that uses it.

Changing community content normally flows into the component because it reads current public records. Changing the snippet options does not update an already pasted copy. Keep a note beside the website page or content-management record so the next editor knows which community and options it embeds.