- What does the Statamic Autograph addon do?
- Statamic Autograph is a Statamic addon by j-jalving that generates HTML code for email signatures. It integrates with the Statamic control panel and Antlers templates, so you can build signature markup in the CP and output it in your site's templates. It is Composer-installable but has little public usage, so review the source and docs before adopting it.
- How do I install j-jalving/statamic-autograph with Composer?
- Install it with composer require j-jalving/statamic-autograph. Statamic addons normally auto-register their service provider, but confirm the package's composer.json and README for any manual registration or config publishing steps. After installing, clear your config and view caches and check the control panel for the addon's navigation entry.
- Which Statamic and Laravel versions does Statamic Autograph support?
- The exact constraint range is not documented in the available excerpts, so open the package's composer.json and confirm the statamic/cms and laravel/framework requirements match your application. Statamic addons of this era typically target Statamic 3.x or 4.x on Laravel 9 to 11 and PHP 8.1 or newer, but treat that as a hypothesis until verified. A version mismatch is the most common cause of a stalled integration.
- Where in the Statamic control panel do I generate an email signature?
- Once installed, the addon adds its features to the Statamic control panel, which is where you configure and produce the signature output. The precise menu location and workflow should be confirmed against the addon's README or by browsing the CP after installation. If you do not see it, check that the service provider is discovered and that your user role has permission.
- Can I customize the generated email signature HTML?
- Because the addon is described as an HTML code generator for signatures, the output is markup you can copy or render, so customization is likely a matter of editing the view or template the addon publishes. Check whether the package ships publishable views via vendor:publish or config keys that control the template. If views are not publishable, you would need to override them in your own theme or fork the addon.
- Can I render signatures in Antlers templates on the front end?
- The addon is described as integrating with Antlers templates, so you can likely render signature output in your Statamic templates rather than only copying HTML out of the control panel. Confirm the exact tag or variable name in the docs before wiring it into templates. Test the rendered markup in real mail clients, since email HTML rendering differs significantly from browser rendering.
- Is it safe to use j-jalving/statamic-autograph in production?
- Treat it as provisional: the package has no stars, a single maintainer, and very little available evidence beyond a patch-level changelog entry. Do a source review, check the release cadence and last commit date, and read the diff for version 1.5.1 rather than assuming a cosmetic-only change. For low-risk internal tooling it may be fine; for a client-facing production site, vendor or fork it if you depend on it.
- Does the addon need a frontend build step or extra CSS and JS assets?
- Many Statamic addons ship CSS and JS assets that must be published to public/ and versioned. Check the README for vendor:publish tags and whether the addon expects your Tailwind or Vite build to compile its styles. If it bundles compiled assets that reduces coupling; if it relies on host theme classes, you may need to add those to your build's content paths.
- How do I troubleshoot the addon icon or assets not updating after an upgrade?
- If the addon icon or styles look stale after upgrading, republish the addon's public assets, clear the config and view caches, and hard-refresh the control panel. Patch releases such as 1.5.1 can include asset changes, and this one adds a dark mode addon icon, so make sure your browser is not serving cached files. If the icon still fails, check whether a Content-Security-Policy is blocking inline SVG or external asset URLs.
- What are the alternatives to Statamic Autograph for email signatures?
- Alternatives include hand-maintained HTML signature templates in your own Antlers views, reusable Statamic fieldsets or Bard content blocks, or a hosted signature service if you need per-user branding at scale. Compare them on whether you need control-panel editing versus a static template, and on how much control you need over the HTML output. For a small team, a single version-controlled Antlers partial is often simpler and easier to maintain than a little-used addon.