Mailerlite Laravel Package

Product Decisions This Supports

• Feature delivery: Enables newsletter capture, subscriber management, and email-list growth directly inside a Statamic-powered site without building a bespoke MailerLite API client. Relevant features: signup forms, embedded/gated content capture, lead-magnet delivery, list segmentation surfaced in the CMS.
• Build vs. buy: The integration layer (auth, API calls, CP configuration, error handling) is commodity work. This package lets the team buy/vendor that layer and spend engineering capacity on content and conversion features instead.
• Roadmap fit: The v2.x line is the current supported track. v2.0.1 confirms the maintainer is actively patching dependencies and vulnerabilities, which is the signal you want when an integration sits in a customer-facing signup path.
• Vendor decision support: If MailerLite is on the shortlist for ESP, this package materially reduces the cost of trying it — a low-risk spike instead of a multi-sprint integration project.
• Risk posture: The patch-level release (dependency updates + vulnerability fixes) is a maintenance signal, not a capability signal. Do not treat it as a feature milestone; treat it as evidence of hygiene.

When to Consider This Package

Adopt when:

• The site is on Statamic (confirm the supported major versions against the v2.x requirements) and MailerLite is the chosen or candidate ESP.
• The team wants subscriber capture configurable by content editors rather than hard-coded by engineers.
• You want a Composer-managed, patch-maintained dependency with a small surface area rather than an in-house integration.
• Time-to-market matters more than deep customization of the subscriber flow.

Look elsewhere when:

• You are not on Statamic — the value here is the CMS integration, not the MailerLite API itself; a plain SDK or HTTP client is the better fit.
• You need a multi-ESP abstraction layer or plan to switch ESPs, which argues for an agnostic integration.
• Requirements include enterprise compliance artefacts, complex marketing automation/journey orchestration, or high-volume transactional email — those belong in MailerLite's own platform or a dedicated provider.
• You need capabilities not exposed by the addon; verify the current feature surface before committing, since the release notes do not describe functional scope.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost integration that lets our Statamic site talk to MailerLite for newsletter signups and list growth, without custom development. The latest release (v2.0.1) is a maintenance patch — dependency bumps and security fixes, with no breaking changes or new features — so it signals the package is being looked after rather than abandoned. The commercial risk is contained: it is one Composer dependency, and the fallback is a straightforward in-house API integration if we ever need to walk away.

For engineering: v2.0.1 is a patch release containing dependency/vulnerability remediation plus changelog and README updates. There are no breaking changes, migrations, or API surface changes called out, so the upgrade path from v2.0.0 should be routine. Two caveats worth flagging: the release notes are terse about which vulnerabilities and dependencies were addressed, so review the diff and run the dependency audit before merging; and because this is a patch on the existing v2.0.0 line, we should confirm the addon's supported Statamic/PHP version matrix against our stack rather than assuming compatibility. Overall: adopt behind a normal dependency-review gate; the package's small surface area keeps the blast radius low.