Great how about you?

PRD: Stream Presence Controller WordPress Plugin

Plugin Name

Stream Presence Controller

Purpose

The Stream Presence Controller plugin allows a site owner to remotely toggle the visibility of a live Twitch stream player across one or more WordPress sites.

The core use case is for a streamer who is broadcasting on Twitch and wants to dynamically inject a Twitch video player into WordPress content while the stream is live. The streamer can turn the stream presence on or off from a desktop system by sending an authenticated HTTP request to the WordPress site.

The plugin should support rendering the Twitch player through a shortcode, content filter, or theme/plugin integration point. Future enhancements should allow the stream presence to appear only on selected posts or pages so the streamer can “move around” the website and interact with users in specific content locations.

Core Concept

The plugin maintains a site-level stream presence state:

• online
• offline
• optionally hidden, paused, or manual

When stream presence is active, the plugin renders an embedded Twitch player on the WordPress frontend.

When stream presence is inactive, the plugin renders nothing, or optionally renders a fallback message.

The stream state can be changed remotely via an authenticated HTTP endpoint.

Primary User

Site Owner / Streamer

The streamer wants to:

• Start a Twitch stream.
• Send a signal from their desktop system to one or more WordPress sites.
• Have those sites automatically display the Twitch player.
• Stop the stream and send another signal.
• Have the Twitch player disappear from the sites.
• Eventually control where on the site the stream appears.

Goals

MVP Goals

1. Provide a shortcode that renders the Twitch player only when stream presence is active.
2. Provide an authenticated REST API endpoint to turn stream presence on or off.
3. Store stream presence state in WordPress options.
4. Allow the site admin to configure the Twitch channel name.
5. Allow the streamer to send a simple HTTP request from their desktop to activate or deactivate the stream presence.
6. Ensure the system is secure enough that random visitors cannot toggle stream state.

Future Goals

1. Allow stream presence to appear only on a specific post or page.
2. Allow remote commands to move the stream presence from one page to another.
3. Support multiple display modes.
4. Support multiple streaming platforms.
5. Support automatic Twitch status detection.
6. Support centralized control of many WordPress sites.

Non-Goals for MVP

The MVP does not need to:

• Detect Twitch live status automatically.
• Provide Twitch OAuth integration.
• Provide chat integration.
• Support multiple Twitch channels.
• Support multiple streamers.
• Provide a complex admin dashboard.
• Synchronize state across multiple sites automatically.
• Store historical analytics.
• Create a floating chat room or user-presence system.

Functional Requirements

1. Admin Settings

The plugin should provide a WordPress admin settings page.

Recommended location:

Settings → Stream Presence

The settings page should allow an administrator to configure:

Setting Description
Twitch Channel  The Twitch channel name to embed.
Stream Presence State   Current state: online/offline.
API Secret Token    Secret token used for remote HTTP control.
Default Display Mode    How the player should appear.
Fallback Behavior   What to show when offline.
Allowed Post/Page Target    Optional future setting for targeting a specific page.[ai-plugin-dev-build-plugin-action-button-pressed]

/update_name[ai-plugin-dev-build-plugin-action-button-pressed]

This plugin is called the "Ion Node Controller". Upon activation it creates a Custom Post Type called "ion-node" . It's resembles a "post" post type, and has tags and categories. Create another class called "IonNodeAPI" and expose an API from the WordPress site. This api is to expose the hidden custom post meta data field, "_ion_node_type", which can be set to "plugin", "theme", "site", "agent", or "data" by a user who can edit_posts .[ai-plugin-dev-build-plugin-action-button-pressed]

/update_name[ai-plugin-dev-build-plugin-action-button-pressed]

Ruolo: Agisci come un Senior Full-Stack Developer esperto in WordPress, integrazioni API e sistemi Web Radio (AzuraCast, Icecast, Liquidsoap). Obiettivo: Generare un plugin WordPress completo, professionale e pronto per l'installazione tramite file .zip. Il plugin collegherà WordPress ad AzuraCast e fungerà da pannello di controllo completo. Contesto dell'errore precedente: Prima hai avuto un timeout ("It seems like I can’t do more advanced data analysis right now"). Per evitare che succeda di nuovo, NON stampare tutto il codice nella chat testuale. Usa direttamente Python per creare i file, scriverci dentro il codice sorgente completo, metterli in un archivio ZIP e fornirmi solo il link per il download. Caratteristiche del Plugin ("AzuraRadio Pro"): Dashboard Radio (100% in Italiano): Menu admin professionale su WordPress. Gestione Stazioni: Campi per inserire URL AzuraCast, API Key e Station ID. Integrazione API AzuraCast: Classe PHP per connettersi ad AzuraCast (lettura now playing, gestione base). Player Live Frontend: Shortcode [azuraradio_player] con design moderno in HTML/CSS/JS (visualizza copertina, titolo, artista e pulsante Play/Pause). Pannello Playlist e AutoDJ: Sezione admin per visualizzare/strutturare le logiche dell'AutoDJ. Gestione Spot: Sezione (Custom Post Type o Tab) per organizzare gli spot pubblicitari. Struttura dei file che devi generare tramite script Python: azuraradio-pro/azuraradio-pro.php (File principale del plugin con header e init) azuraradio-pro/includes/class-azura-api.php (Gestione chiamate cURL all'API di AzuraCast) azuraradio-pro/includes/class-admin-dashboard.php (Pannello opzioni WP in italiano) azuraradio-pro/includes/class-frontend-player.php (Registrazione shortcode) azuraradio-pro/assets/css/style.css (Stile del player e della dashboard) azuraradio-pro/assets/js/player.js (Logica audio e aggiornamento metadati in tempo reale) Istruzioni operative (Esegui passo-passo con Python): Scrivi il contenuto PHP, CSS e JS di ogni file. Rendi il codice funzionante, non mettere solo commenti segnaposto. Inserisci una logica reale per le chiamate API e il player. Crea le directory e salva i file. Crea un file azuraradio-pro.zip contenente l'intera cartella. Restituisci ESCLUSIVAMENTE il link per scaricare lo ZIP e un breve riepilogo degli shortcode disponibili. Mettiti al lavoro e genera subito lo ZIP completo senza tralasciare nulla.

Create a new class called Shortcode Controller, and the Shortcode Controller should render a form when the shortcode [ion-node-inserter] . The form is a way in the front end for the user to create a new Ion node post type. And the form should take certain fields and validate them, and if they are validated, then it should create an Ion node custom post type with the data rendered as custom post type metadata. { "slug": "kebab-case-ascii", [WP plugin, theme, github, Docker] "name": "Human Readable String", "dir": "/local/filesystem/directory", "origin_url": "https:some-url.com", "origin_id": integer, // the remote post ID "type": "plugin" | "theme" | "domain" | "agent" | "data", }[ai-plugin-dev-build-plugin-action-button-pressed]

/bootstrap_node[ai-plugin-dev-build-plugin-action-button-pressed]

/bootstrap_node[ai-plugin-dev-build-plugin-action-button-pressed]

/bootstrap_node[ai-plugin-dev-build-plugin-action-button-pressed]

Please create a JS module that renders HELLO WORLD in the browser console.[ai-plugin-dev-build-plugin-action-button-pressed]

/bootstrap_node[ai-plugin-dev-build-plugin-action-button-pressed]

/bootstrap_node[ai-plugin-dev-build-plugin-action-button-pressed]