Weave Code
Statamic Ai Writer Laravel Package
muench-dev/statamic-ai-writer
A Statamic addon that brings AI-assisted writing into the control panel, helping you draft and generate content without leaving the CMS. It streamlines copywriting for entries and fields, speeding up editorial workflows for Statamic sites.
The addon brings intelligent content modification, generation, and accessibility tooling directly into the Statamic Control Panel. It allows content creators to highlight text in both Bard and Markdown editors to shorten, expand, rephrase, summarize, translate (including post titles), and classify content into tags and categories.
Frequently asked questions about Statamic Ai Writer
- What does muench-dev/statamic-ai-writer do?
- It is a Statamic addon that adds AI-assisted writing tools directly to the Control Panel. Editors can highlight text in Bard and Markdown fields to shorten, expand, rephrase, summarize, translate, and classify content into tags or categories. It is aimed at speeding up editorial workflows without leaving the CMS.
- How do I install statamic-ai-writer in a Laravel Statamic application?
- Install it with Composer in your Laravel application and let Statamic register the addon through its normal addon discovery. After updating, clear the relevant Statamic and Laravel caches and views. Publishing translation overrides is optional and only needed if you want custom Control Panel wording.
- Which Laravel and Statamic versions does statamic-ai-writer v2.1.0 support?
- The v2.1.0 release notes do not publish explicit Laravel or Statamic version constraints, so treat the package composer.json as the source of truth. Verify compatibility against your pinned Statamic version, especially around Control Panel locale handling and view composer behavior. Run the Composer update in staging before promoting it to production.
- Does statamic-ai-writer v2.1.0 introduce breaking changes or require a migration?
- The release notes indicate no breaking API, configuration, or migration changes for v2.1.0. It should be treated as a minor feature and fix upgrade rather than a disruptive version. The main work is a Composer update plus optional translation publishing and locale verification.
- How does statamic-ai-writer handle Control Panel translations?
- Version 2.1.0 adds English and German Control Panel translations and makes the package UI follow the Statamic CP locale independently of content generation settings. It also fixes assistant script translation resolution so translations are resolved against the explicit CP locale. This addresses English fallback translations being loaded before assistant scripts resolve their strings.
- Can I override the package's English or German Control Panel translations?
- Yes, the package supports publishable translation overrides for teams that need controlled UI wording without forking it. If you publish overrides, your team becomes responsible for keeping them aligned with future upstream package changes. After updates, verify that your overrides still win and are not shadowed by the new package translations.
- Does the Control Panel locale change the language used for AI content generation?
- No, v2.1.0 reinforces the separation between the Control Panel interface locale and content generation settings. The Statamic CP locale controls the package UI text, while content generation language may be configured separately. This distinction should be documented for editors who expect both languages to match automatically.
- What editing workflows does statamic-ai-writer support in Bard and Markdown?
- Editors can highlight content in Bard and Markdown editors and run actions such as shorten, expand, rephrase, summarize, and translate, including post titles. The addon also supports classifying content into tags and categories, and it exposes alt-text actions alongside notifications and permissions in the Control Panel. These tools are designed for in-place editorial workflows rather than replacing the CMS.
- How should I test the v2.1.0 upgrade before production?
- Update via Composer in a staging environment, clear the appropriate caches and views, and confirm the Statamic CP locale settings. Test the assistant and editor integrations in both English and German if German editors are in scope, including notifications, permissions, and alt-text actions. Use a controlled provider failure to verify that package-owned error messages render in the expected CP language, and confirm any custom translation overrides still take precedence.
- Is statamic-ai-writer production-ready and what maintenance does it require?
- For most Laravel and Statamic teams it is low-maintenance, and v2.1.0 is a translation-focused release with no meaningful runtime scaling impact. Teams that publish translation overrides take on responsibility for keeping those overrides aligned with upstream changes. Ongoing operational concerns are mainly tied to the existing AI provider integration, so regression-test locale behavior after Statamic upgrades.
Weaver
How can I help you explore Laravel packages today?