WP Manifestindependent plugin directory
manifest / ai / digital-royalty-beacon

WP Beacon

Connect WordPress via Beacon to gain: automation, content intelligence, and publishing

by Digital Royalty · github.com/digital-royalty-ltd/digital-royalty-beacon · website

0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/digital-royalty-ltd/digital-royalty-beacon/archive/refs/heads/main.zip

# Beacon by Digital Royalty

Beacon connects WordPress to the Digital Royalty dashboard.

It enables AI-driven tooling directly inside WordPress, powered by a secure API connection to the Beacon SaaS platform.

Features

  • AI meta title and description generation
  • Content gap analysis
  • Draft content generation
  • Report-based onboarding scans
  • Webhook-based automation
  • REST API endpoints for dashboard integration

Installation

  1. Download the latest release zip.
  2. Upload via Plugins → Add New → Upload Plugin.
  3. Activate the plugin.
  4. Go to Beacon AI → General and enter your API key.

Architecture

Beacon follows a layered structure:

src/ Admin/ # WordPress admin UI (Screens, Views, Actions) Database/ # Plugin-managed tables Repositories/# Data access layer Rest/ # WordPress REST API endpoints Services/ # Service container & shared services Support/ # Infrastructure utilities (autoloading, enums, helpers) Systems/ # Core domain logic (API + Reports)

Design Principles

  • Clear separation of concerns
  • No business logic inside Views
  • No rendering inside Actions
  • Systems contain domain logic
  • Repositories handle database access
  • Enums prevent magic strings
  • REST routes are versioned (beacon/v1)

Requirements

  • PHP 8.0+
  • WordPress 6.0+
  • PSR-4 namespaced structure

Development

  • Tables are installed on activation and during admin boot.
  • Schema changes use dbDelta() with version tracking.
  • REST endpoints are registered under beacon/v1.
  • Services are resolved via a lightweight static container.