=== BLR Backline ===
Contributors: badlittlerobot
Tags: music, bands, crm, outreach, events
Requires at least: 6.9
Tested up to: 6.9
Requires PHP: 8.0
Stable tag: 1.0.1
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Front-end dashboard for bands and music projects.

== Description ==

BLR Backline is a private front-end back office for bands, musicians, and music projects running on WordPress.

It gives authorized users one centralized workspace for managing releases, tracks, contacts, outreach, events, tasks, fan signups, and basic project operations without needing to work inside the standard WordPress admin area.

BLR Backline is designed for musicians who need practical project infrastructure without duct-taping together spreadsheets, CRMs, calendar tools, and half-broken mailing workflows.

Features include:

* Front-end dashboard for authorized users
* Discography management for releases and tracks
* Contact management for industry, fan, venue, press, and project contacts
* Outreach campaign management
* Background outreach queue processing with campaign locking
* Newsletter signup handling with email confirmation support
* Newsletter subscription statuses for pending, subscribed, and unsubscribed contacts
* Event and calendar views
* Task and workflow tracking
* Front-end profile management
* Privacy exporter and eraser support for supported plugin data
* Optional uninstall cleanup controls

BLR Backline is self-contained. Its dashboard assets are bundled locally with the plugin and are scoped to the BLR Backline interface rather than being loaded from third-party CDNs.

The plugin does not include telemetry, usage tracking, external analytics, or “call home” behavior.

Email sending for outreach and signup confirmation uses WordPress mail handling through `wp_mail()`. If you need authenticated delivery through a third-party provider, configure a dedicated SMTP or transactional mail plugin at the WordPress site level.

== Installation ==

1. Upload the plugin folder to `/wp-content/plugins/`.
2. Activate the plugin through the Plugins screen in WordPress.
3. Go to the BLR Backline settings page.
4. Configure the dashboard slug, allowed users, and default sender identity.
5. Install and configure a dedicated WordPress mail or SMTP plugin if you need authenticated email delivery.


== Screenshots ==

1. BLR Backline dashboard showing high-level project stats, finance summaries, and quick actions across the workspace.
2. BLR Backline settings screen for configuring dashboard access, mail behavior, branding, and plugin options.


== Privacy ==

BLR Backline stores site-managed operational data inside WordPress for the features it provides.

Depending on which modules and workflows you use, the plugin may store:

* Release and track records
* Contact records, including names, email addresses, phone numbers, company names, roles, websites, locations, newsletter signup flags, subscription status, and internal notes
* Fan signup submissions, including email address, optional first name, signup timestamp, source label, tag details, confirmation status, and confirmation timestamps where applicable
* Outreach campaigns and outreach logs, including recipient email address, delivery status, sent timestamp, notes, and recorded error messages
* Event, task, finance, and notification records created by authorized users
* Plugin settings related to dashboard access and behavior

The plugin does not send analytics or telemetry to the plugin author.

The plugin sends outreach email and signup confirmation email only through WordPress mail handling. If the site owner configures an SMTP or transactional mail plugin, email may then be relayed through that separately configured provider.

BLR Backline includes integration with WordPress personal data export and erasure tools for supported contact and outreach log data, including supported newsletter confirmation details.

Site owners are responsible for using the plugin in a way that complies with applicable privacy, consent, marketing, and email laws and platform policies.

If uninstall cleanup is enabled in the plugin settings, plugin-owned data can be removed during uninstall. If uninstall cleanup is not enabled, plugin data is left in place.

== Third-Party Resources ==

BLR Backline bundles the following third-party assets locally for use inside the BLR Backline dashboard:

= AdminKit =

* Path: `assets/adminkit/`
* Files: `assets/adminkit/css/app.css`
* Version marker in bundled CSS: 3.4.0
* License: MIT
* Source: https://adminkit.io/

= Bootstrap =

* Path: `assets/vendor/bootstrap/`
* Files: `assets/vendor/bootstrap/css/bootstrap.css`, `assets/vendor/bootstrap/js/bootstrap.js`
* Version marker in bundled CSS: 5.3.8
* License: MIT
* Source: https://getbootstrap.com/

= Select2 =

* Path: `assets/vendor/select2/`
* Files: `assets/vendor/select2/css/select2.css`, `assets/vendor/select2/js/select2.js`
* Version marker in bundled JS: 4.0.13
* License: MIT
* Source: https://select2.org/


= Flatpickr =

* Path: `assets/vendor/flatpickr/`
* Files: `assets/vendor/flatpickr/css/flatpickr.css`, `assets/vendor/flatpickr/js/flatpickr.js`
* Version marker in bundled JS: 4.6.13
* License: MIT
* Source: https://flatpickr.js.org/

= Feather Icons =

* Path: `assets/vendor/feather/`
* Files: `assets/vendor/feather/js/feather.js`
* License: MIT
* Source: https://feathericons.com/

All bundled third-party assets are served locally by the plugin. No third-party CDN is required for runtime operation.

Additional bundled asset notes are documented in:

`assets/THIRD_PARTY_ASSETS.md`

== Frequently Asked Questions ==

= Who can access the dashboard? =

Administrators always have access. Other users must be explicitly added to the allowed users list in the plugin settings.

= Does BLR Backline replace the normal WordPress admin area? =

No. BLR Backline provides a front-end workspace for supported music project workflows. WordPress administrators can still manage the site normally through the WordPress admin area.

= Does the plugin send email directly through an external SMTP service? =

No. The plugin uses WordPress mail handling through `wp_mail()`. For reliable delivery and authenticated sending, use a dedicated SMTP or transactional mail delivery plugin.

= Does the plugin support newsletter signup confirmation? =

Yes. BLR Backline supports newsletter signup confirmation workflows and subscription statuses for pending, subscribed, and unsubscribed contacts.

= Does the plugin collect analytics or send telemetry to the developer? =

No. BLR Backline does not include telemetry, usage tracking, external analytics reporting, or call-home behavior.

= What personal data can the plugin store? =

That depends on which features you use. The plugin can store contact details, fan signup details, newsletter confirmation details, outreach logs, and other administrative records created by authorized users. See the Privacy section above for a summary.

= Will uninstalling the plugin remove its data? =

Only if uninstall cleanup is enabled in the plugin settings. Otherwise, plugin data is left in place.

== Changelog ==

= 1.0.1 =

* Renamed plugin display name to BLR Backline.
* Changed the default front-end dashboard slug to `blr-backline`.
* Removed Gravatar fallback avatar loading.
* Moved flagged inline scripts and styles to WordPress enqueue/inline asset APIs.
* Tightened upload and request sanitization.

= 1.0.0 =

* Initial public release.
* Added front-end dashboard for bands, musicians, and music projects.
* Added release and track management.
* Added contact management.
* Added outreach campaign management.
* Added background outreach queue processing with campaign locking.
* Added newsletter signup handling with email confirmation support.
* Added newsletter subscription statuses for pending, subscribed, and unsubscribed contacts.
* Added event and calendar views.
* Added task and workflow tracking.
* Added front-end profile management.
* Added privacy exporter and eraser support for supported plugin data.
* Added newsletter confirmation details to supported privacy export data.
* Added optional uninstall cleanup controls.
* Bundled dashboard assets locally so the BLR Backline interface does not require third-party CDN assets at runtime.