Weave Code
Twill Laravel Package
area17/twill
Twill is an open source Laravel package for building custom, beautiful CMS admin consoles fast. It standardizes common publishing features with pre-built Vue.js UI components, no lock-in, and full flexibility.
Twill is an open source CMS toolkit for Laravel that helps developers rapidly create a custom admin console that is intuitive, powerful and flexible.
Frequently asked questions about Twill
- What is Twill CMS for Laravel and what does it include?
- Twill is an open source Laravel package by AREA 17 for rapidly building custom CMS admin consoles. It provides CRUD modules, form and table builders, a media library, blocks and repeaters, revisions, publishing workflows, permissions, authentication with 2FA, navigation, and a Vue/Blade admin UI. It is not a generic admin panel; it standardizes common CMS features while keeping Eloquent models and front-end choices open.
- How do I install area17/twill in a Laravel application?
- Install via Composer with composer require area17/twill, then publish Twill's config, migrations, and assets and run migrations. Twill provides Artisan commands to scaffold modules and admin routes. It is designed for Laravel/PHP apps and expects a supported database, storage, image driver, and queue setup for media processing.
- Which Laravel and PHP versions does Twill support?
- Twill 3.5.3 explicitly supports Laravel 12 and PHP 8.4–8.5 in CI. The package is Laravel-focused and Composer-based, so check the current requirements and changelog for exact supported Laravel, PHP, database, cache, queue, filesystem, and image-processing versions before upgrading. Older Twill versions may target earlier Laravel and PHP releases.
- Can I use Twill with an existing Laravel app and existing users?
- Integration is possible but medium effort for an existing Laravel app with established auth, admin routes, and user models. You can adapt existing Eloquent models, but expect Twill traits and schema additions around slugs, publishing state, revisions, media pivots, and permissions. Review admin route namespace, middleware, and auth model conflicts explicitly, and decide whether existing users, roles, and permissions remain authoritative.
- Is Twill headless or does it require Blade for the front end?
- Twill does not force a Blade-rendered public site; headless use is feasible because it can manage content while your front end consumes Laravel APIs or models. The admin UI itself uses Vue.js and Blade components. You keep control of front-end assumptions and can use Twill within a Laravel app or as a content management layer.
- How do Twill blocks, repeaters, and media library work?
- Twill includes reusable blocks and repeaters for flexible content models, with application-owned schema and migration concerns for custom blocks. Its media library handles storage, image processing, queue, and filesystem dependencies, so plan object or local storage and image drivers. Front-end developers should follow Twill conventions for blocks, repeaters, browsers, and media.
- Do I need to display the Made with Twill attribution?
- Twill's code is Apache-2.0 licensed, but its UI assets are CC-BY 4.0 and the admin console must display a linked Made with Twill attribution unless you obtain permission. Trademark restrictions also apply. Have legal review attribution and trademark terms before shipping a client-facing or white-labeled admin.
- How risky are Twill upgrades and version migrations?
- The main risk is convention coupling rather than runtime instability because Twill owns a significant admin surface. Major upgrades can be material: Twill 3.0 renamed Admin namespaces to Twill, aligned config names, made datetimes timezone-aware, standardized BigInt, and introduced new form and table builders. Plan upgrade cadence, review the changelog, and spike the migration before committing.
- Is Twill a good alternative to a generic Laravel admin panel?
- Twill is intentionally not a generic admin panel; it fits best when the product needs a content-heavy Laravel admin surface and aligns with Twill's publishing primitives such as pages, articles, media, taxonomies, reusable blocks, and editorial workflows. It offers high value when its conventions match your content model and lower value when the admin UX or domain model is highly bespoke. Compare it against generic admin builders only after mapping your content types and workflows.
- How should I test Twill in production and assess support?
- Validate with a hands-on spike and check Packagist downloads and references because the dependents metric is not reliable for this package type. Test media processing with queue workers, storage, filesystem, and image-processing dependencies in a production-like environment. Review security for the admin surface and 2FA, and decide whether community support is enough or you need commercial support from AREA 17.
Weaver
How can I help you explore Laravel packages today?