Widget install guide · public board first

Add the widget where ideas happen, then make the demand public.

The IdeasDiamond widget is not a private suggestion box. It is a lightweight website input for a public board where ideas can collect votes, move through roadmap status, and become changelog receipts.

Open widget page See website use case Request widget controls

Install snippet

<script async src="https://www.ideasdiamond.com/widget.js" data-organization="your-organization-slug" data-board="your-board-id" data-label="Share an idea"></script>

Replace the organization slug and board id with the public board you want the widget to feed. Start with one board before adding more widgets.

View board View roadmap View embed

Install checklist

A useful widget needs a useful public board behind it.

1

Choose one narrow board

Do not ask for every possible idea at once. Pick one promise: product feedback, restock requests, menu ideas, docs improvements, civic suggestions, or feature requests.

Check: You can describe the board in one sentence.

2

Seed 3–7 starter ideas

Add the recurring requests you already see in emails, support tickets, reviews, chats, GitHub issues, or customer conversations so the board does not feel empty.

Check: Each starter idea is concrete enough to vote on.

3

Place the script where intent is highest

Start on one useful page: pricing, product docs, a sold-out collection, a menu page, an open-source project page, or a local service page.

Check: The widget appears near the moment someone has an idea.

4

Send people back to the public board

The widget captures ideas in place, but the board is where votes, duplicates, roadmap status, and changelog receipts become visible to everyone.

Check: The widget page links to the board, roadmap, or embed.

5

Publish one visible response

Move a real idea through a roadmap status or ship one tiny changelog receipt. Proof beats a bigger private backlog.

Check: A visitor can see that submitted ideas are not ignored.

Placement examples

Where to put the first widget.

Install the widget on one high-intent surface first. If the board earns attention, paid controls can improve reach, trust, moderation, analytics, styling, or private access.

SaaS or app website

What should we improve next?

Place on: Pricing, docs, dashboard help, feature pages

Paid signal: Widget attribution, private beta boards, roadmap analytics

Ecommerce shop

What should we restock, bundle, or make next?

Place on: Sold-out products, collection pages, post-purchase pages

Paid signal: Demand analytics, promoted boards, branded widget controls

Restaurant or local venue

What would make this place better?

Place on: Menu, events, reservation, contact pages

Paid signal: Moderation, official claim badge, local discovery

Open-source/community project

Which idea deserves community attention?

Place on: Docs, roadmap, download, community pages

Paid signal: Duplicate merging, sponsor-ready evidence exports, maintainer controls

Next move

Use the widget to prove a public idea loop, not to collect another hidden inbox.

If the first board gets real ideas or votes, request early-access controls for the exact bottleneck you found: more reach, owner verification, moderation, analytics, custom styling, embeds, or private boards.

Request widget controls Compare paid controls