Overview

Status: Available, schema-owning · Kind: package · Tier: premium · Bundle: newsletter · Contexts: admin, frontend · Product group: Capell Marketing

Newsletter manages audience capture, subscriber records, consent evidence, provider connections, provider sync attempts, segments, imports, and public subscription lifecycle routes.

Install

composer require capell-app/newsletter

The package requires capell-app/admin, capell-app/core, capell-app/form-builder, capell-app/frontend, and capell-app/tags.

Admin Surfaces

SubscriberResource
ProviderConnectionResource
ProviderAudienceResource
ProviderInterestMappingResource
FormMappingResource
NewsletterTagResource
SegmentResource
ImportBatchResource
SyncAttemptResource
Newsletter overview stats for subscribed, pending, and failed/retry-scheduled sync attempts.
Newsletter settings schema.

Frontend Surfaces

GET /newsletter/confirm/{token} for subscription confirmation.
GET /newsletter/unsubscribe/{token} for unsubscribe requests.
POST /newsletter/providers/{providerConnection}/webhook for provider webhooks.

Public routes should expose only confirmation/unsubscribe/webhook outcomes and must not leak admin labels, provider secrets, subscriber internals, or form-builder mapping details.

Screenshot Plan

Subscribers admin index.
Create/edit subscriber form.
Provider connections admin index and form.
Provider audiences admin index and form.
Provider interest mappings admin index and form.
Form mappings admin index and form.
Newsletter tags admin index and form.
Segments admin index and form.
Import batches admin index.
Sync attempts admin index.
Newsletter overview stats on the admin dashboard.
Confirmation route response.
Unsubscribe route response.

Verification

Package tests: vendor/bin/pest packages/newsletter/tests --configuration=phpunit.xml.
Harness install: composer require capell-app/newsletter:4.x-dev -W, then php artisan package:discover --ansi and php artisan migrate --graceful --ansi.

Known Risks

Screenshot capture needs seeded subscribers, provider connections, form mappings, segments, and sync attempts to avoid empty tables.
Public confirmation/unsubscribe screenshots need disposable public tokens.
Webhook coverage should use a signed or provider-authenticated request scenario rather than a browser-only screenshot.