Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Tailwind Fieldtype Laravel Package

krakero/tailwind-fieldtype

A Statamic fieldtype for selecting Tailwind CSS classes in the control panel. Give editors a searchable, configurable list of utilities so they can style content without memorizing class names or hand-typing long strings.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Build vs. buy for editor-facing styling controls: krakero/tailwind-fieldtype is a Statamic addon that gives content editors a structured way to select Tailwind utility classes rather than hand-typing arbitrary class strings. This is a narrow, well-bounded capability — adopting it avoids building and maintaining a custom fieldtype, class-safelist tooling, and the accompanying editor UI.
  • Tailwind migration planning: The 3.0.0-beta.1 release adds Tailwind 4 support alongside Statamic 6 support. This is a signal for roadmap sequencing: if your design system or CMS upgrade is moving to Tailwind 4 and/or Statamic 6, this package is tracking that path; if you are staying on Tailwind 3 / Statamic 5 for now, 3.x is not yet your target line.
  • CMS-editor autonomy vs. design-system guardrails: The fieldtype lets you constrain the class surface editors can pick from, which supports decisions about how much styling freedom to grant non-engineers. Useful when evaluating whether marketing/content teams can ship landing pages without engineering involvement.
  • Vendor/dependency risk for a small, single-maintainer package: A major version in beta is a moment to reassess bus-factor and long-term maintenance exposure. This is a low-blast-radius dependency (a fieldtype, not core rendering logic), which keeps the risk contained but non-zero.
  • Upgrade timing: Because 3.0.0-beta.1 is a pre-release with breaking changes implied by the major bump, adopting it is a deliberate "early adopter" decision, not a drop-in patch. Treat it as an opt-in pilot, not a default upgrade.

When to Consider This Package

Consider adoption when:

  • You are on (or actively migrating to) Statamic 6 and Tailwind 4, and you need editor-friendly class selection for Tailwind utilities.
  • You want a small, single-purpose addon rather than a broader page-builder or style-system plugin.
  • Your team is comfortable running a beta dependency in a non-production or pilot capacity, and can absorb a follow-up upgrade when 3.0.0 reaches stable.
  • You can pin the version explicitly (^3.0@beta) and isolate the integration so a rollback is cheap.

Look elsewhere / defer when:

  • You are still on Statamic 5 or Tailwind 3 — 3.x targets the newer stack; stay on the prior major line and revisit at stable release.
  • You require stable, supported releases only (regulated environments, client-facing SLAs). Beta channel is a disqualifier until GA.
  • You need richer content-modelling, responsive/variant-aware class management, or design-token governance — validate whether this fieldtype's scope covers that, or whether a more comprehensive solution is warranted.
  • You are not on Statamic at all; this is Statamic-specific and does not apply to plain Laravel projects.

Before committing: read CHANGELOG.md and UPGRADE.md for the actual breaking-change list, confirm the addon's Tailwind 4 class handling matches your safelist/build setup, and verify release cadence and maintainer responsiveness.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost addon that lets our content team apply Tailwind styling through a guided interface instead of editing code. It removes a recurring engineering dependency for routine page styling and avoids us building that capability ourselves. The new 3.0 beta aligns it with our Statamic 6 and Tailwind 4 direction, but it is currently a beta — we recommend piloting it rather than standardizing on it until a stable release lands. Risk is contained: it is a single fieldtype, easily removed.

For engineering: krakero/tailwind-fieldtype 3.0.0-beta.1 adds Statamic 6 and Tailwind 4 support. It is a major version bump and a pre-release — install with composer require krakero/tailwind-fieldtype:^3.0@beta only in environments already on (or migrating to) Statamic 6 / Tailwind 4. Breaking changes are documented in UPGRADE.md and CHANGELOG.md; review both before upgrading, and expect churn until GA. Keep the dependency pinned and version-isolated so we can revert cleanly if the beta proves unstable.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
3mdikram/worldmoneywords
snowsoft/config
itmosoft/laravel-subscriptions
larva/laravel-ai-qwen
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib