- Can I install hampe/zurb-ink-bundle in a Laravel application?
- No. hampe/zurb-ink-bundle is a Symfony bundle that registers a Symfony dependency-injection extension, a Twig namespace, and Symfony-oriented asset handling, none of which Laravel understands. A composer require will usually fail dependency resolution against modern Laravel because the bundle targets old Symfony and Twig constraints, and even if it installed it would not register routes, views, or mail behavior in Laravel. Treat the repository as reference material rather than a runtime dependency.
- Is hampe/zurb-ink-bundle a Laravel package?
- No, it is a Symfony bundle built for Symfony's container and Twig templating layer. Laravel uses service providers and Blade, so there is no automatic view namespace, no Blade directives, and no Laravel mail integration. The only portable parts are the Ink HTML layouts and partials, which you can copy and convert to Blade.
- What does hampe/zurb-ink-bundle actually do?
- It integrates the Zurb Ink responsive email framework into a Symfony project so you can build newsletter and transactional email templates with Ink's CSS grid and components. The bundle mainly supplies Twig-based Ink boilerplate layouts and partials plus Symfony asset handling. It is not a full email-sending library and should not be treated as a CSS inliner.
- Does hampe/zurb-ink-bundle support Laravel 10, 11, or 12?
- There is no Laravel version support because this is a Symfony bundle, and its last release was in February 2018. That release almost certainly constrains Symfony 2, 3, or 4 and Twig 1 or 2, while Laravel 10, 11, and 12 ship Symfony 6 or 7 components and require PHP 8.2 or newer. A straight Composer install will either fail resolution or drag in an ancient Symfony subtree, so do not attempt to run it inside a modern Laravel app.
- How do I use Zurb Ink email templates in Laravel without this bundle?
- Copy the Ink HTML and Twig layouts and partials from the repository into resources/views/vendor/mail, then convert Twig blocks, includes, and variables to Blade sections, includes, and variables. This is mechanical work and usually takes a focused day for a mid-level engineer. Handle CSS inlining with Laravel's Symfony Mailer integration, such as cssToInlineStyles, or with a maintained package like tijsverkoyen/css-to-inline-styles.
- Is hampe/zurb-ink-bundle still maintained?
- No. The last release was on 2018-02-05, it has a single maintainer, and it has zero dependents in the ecosystem. Upstream Zurb Ink was superseded by Foundation for Emails and is no longer actively maintained. That makes the bundle an abandoned dependency with no security response path.
- What are the best alternatives to hampe/zurb-ink-bundle for Laravel email templates?
- Use Laravel's built-in Markdown mail templates, or build custom Blade email views with table-based layouts. For CSS inlining, use Laravel's Symfony Mailer CssInliner support, fedeisas/laravel-mail-css-inliner, or tijsverkoyen/css-to-inline-styles. If you want Ink-style components, port Foundation for Emails or Ink templates into Blade rather than installing the Symfony bundle.
- Does hampe/zurb-ink-bundle handle CSS inlining for emails?
- Probably not. The bundle appears to provide Ink Twig templates and Symfony asset integration, while CSS inlining is normally handled separately by the mail transport layer. In Laravel 9 and later, Symfony Mailer already offers CSS inlining, so the bundle adds little or no unique value for that concern. Verify the repository before assuming it includes an inliner.
- How hard is it to migrate the bundle's Twig templates to Laravel Blade?
- It is straightforward. Replace Twig block tags with Blade section tags, Twig includes with Blade includes, and Twig variables with Blade variables, then move the HTML into resources/views/vendor/mail. The main effort is retesting rendering across Gmail, Outlook, and Apple Mail because the Ink CSS dates from 2018. Budget about one focused day for a typical set of newsletter and transactional templates.
- What production risks come with hampe/zurb-ink-bundle?
- The bundle is an abandoned dependency with no security response path, and it depends on an end-of-life upstream email framework whose CSS has not been tuned for modern email clients. It also conflicts with modern PHP, Symfony, and Twig constraints, so installing it imports supply-chain risk for a problem Laravel already solves. Before using any copied templates, test rendering in Litmus or Email on Acid across Gmail, Outlook 2016 and 365, and Apple Mail. Prefer native Laravel mail and a maintained inliner for production.