Stand-alone Player with Content Text

What “stand-alone” means in GSpeech

Most players narrate whatever sits under Content Selector on the live page. Stand-alone flips that: the spoken script is authored in the widget’s Content Text field. The page only needs the connection script and a mount for the player chrome — no article body required for audio to work.

• Content Selector empty — the widget UI says to leave it empty when you use Content Text. That instruction is intentional.
• Content Text filled — this string becomes the audio content (same field Welcome Message uses for its greeting line).
• Mount still required — Full / Button / Circle still inject into Render Element; Content Text does not remove the need for a place on the page.
• Demo feel — a nearly blank HTML page with one mount can still play a full script stored in the console.

Stand-alone Full/Button/Circle vs Welcome Message

• Stand-alone Full / Button / Circle — visitor clicks (or uses) a normal listen player; script comes from Content Text; you control mount placement and player chrome.
• Welcome Message — short greeting widget; also uses Content Text, but it is a different widget type (greeting / autoplay-oriented), not a Full listen bar. See Welcome Message how-to.
• Normal page player — Content Selector points at DOM; Content Text stays unused (or only as fallback if the selector finds nothing).

Rule of thumb: if you want a demo player with no surrounding copy, use Full / Button / Circle + empty Content Selector + Content Text — not Multi-Page reading self_class.

How to build a stand-alone Content Text player

1. Ensure the site connection script is live (Html Website embed, or your CMS integration). See HTML guide or call a custom widget.
2. Create or open a Full / Button / Circle widget in the Cloud Console.
3. Add an empty mount on the page, e.g. <div class="gsp_full_player"></div> or your own class — same as any custom call.
4. Set Render Element to that mount selector (e.g. .gsp_full_player).
5. Clear Content Selector — leave the field empty. Do not leave parent_class / self_class if you want Content Text only.
6. Open Content Text and paste the full script visitors should hear. Save.
7. Optional: Allowed / Blocked Urls so this stand-alone widget only runs on the demo / landing URL.
8. Set Published, Save, hard-reload the page. Play the player — you should hear Content Text even if the page body is empty.

Minimal HTML — player only

This is the demo-style shape: connection + mount, almost no copy. Spoken text lives entirely in the widget Content Text field.

• HTML — empty <div class="gsp_full_player"></div> + connection script before </body>.
• Widget — Render Element .gsp_full_player; Content Selector empty; Content Text = your script; Published.
• Optional title — Title Text still labels the player UI; it is separate from Content Text.

Skeleton:

<div class="gsp_full_player"></div>
<!-- GSpeech connection script from Integrations -->

Same pattern works with .gsp_button_player / .gsp_circle_player or any custom mount class — as long as Render Element matches.

Keep stand-alone audio clean

• Do not mix modes by accident — if Content Selector still points at a DOM node (even several pieces with commas), that page text wins when found; clear the selector for pure Content Text.
• Edit script in the console — change Content Text and Save; hard-reload the demo page to hear the new line.
• Voice still Global or custom — Content Text does not force a voice; inherit website Settings or override on the widget. See Global vs custom.
• Characters — long Content Text still counts toward usage when audio is generated; keep demos focused.
• URL scope — pin the widget to one demo path with Allowed Urls so it does not replace article players site-wide.