Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nudj.cx/llms.txt

Use this file to discover all available pages before exploring further.

Nudj can be embedded as an iframe widget on your own website, Shopify storefront, or any HTML page. The embed and widget settings let you tune loading behaviour, visibility, and launcher config.

​
Embed emulator

The Embed Emulator (#1937) lets you test how your community looks embedded in different contexts — Shopify admin, a generic ecommerce store, a blog — without leaving the admin panel.
  • Pick an embed context (Shopify / ecommerce / blog / generic).
  • See your community render inside.
  • Test hover, click, and auth flows.
  • Debug iframe permission issues (mic, clipboard).

​
Widget loading state

The widget loading screen is configurable (#2355) — the colour, spinner style, and transition animation. Matches your community theme (or override per community).

​
Community-level widget toggle

Each community has a widget toggle (#2285) — enable or disable the widget per community. Turn off for communities that don’t use embed/widget, on for the ones that do.

​
Embed launcher form

The embed launcher has a form for configuring:
  • Mode — identity (your OAuth) or nudj-login (Nudj-managed auth).
  • Button position — bottom-right, bottom-left, inline.
  • Button label / icon.
  • Auto-open — open automatically on page load for VIP users.
  • FAB (floating action button) config.
The dirty-state fix (#2259) means unsaved form changes don’t silently discard when you switch tabs — you get a confirm-navigation prompt.
The Shopify embed is a specialised form of iframe embed with mic-permission workarounds (voice popup, see Shopify Integration) and dedicated tools.

​
Widget best practices

Don’t auto-open the widget for every visitor. Auto-open is for returning members / VIPs. Cold visitors find it aggressive.
Match your widget loading state to your brand. Default white-spinner-on-white looks unbranded and cheap. Spend 5 minutes on this.
Test on mobile — embeds render very differently on mobile (often full-screen takeover rather than a floating button). Use the embed emulator’s mobile mode before shipping.