The Changelog

What's new around here?

Succinct and informative updates about Flux.
RSS feed
November 19, 2026
A profile item with an avatar and an Edit profile button, above a group of settings rows: a two-factor switch, a language menu, a next payment amount, and a sign out button
Meet Item: a row with a heading, a line of supporting text, and a control at the end.
It's the row you've built a hundred times for settings pages, account details, billing screens, and team lists. Now it's one component, with the alignment and spacing already worked out.
Copy to clipboard
<flux:item>    <flux:item.heading>Two-factor authentication</flux:item.heading>    <flux:item.subheading>Ask for a code when you sign in on a new device.</flux:item.subheading>    <flux:item.actions>        <flux:switch aria-label="Two-factor authentication" checked />    </flux:item.actions></flux:item>

Group them up

Wrap items in flux:item.group and they share one bordered surface, with a faint rule between each row:
Copy to clipboard
<flux:item.group>    <flux:item>...</flux:item>    <flux:item>...</flux:item>    <flux:item>...</flux:item></flux:item.group>
The surface matches a default card, so groups sit comfortably next to the new Card. And a lone item draws that same surface itself. No wrapper needed.

Anything at the end

flux:item.actions takes buttons, a switch, a dropdown, a badge, or just a value. It sits at the end of the row, centered on the heading and subheading no matter how tall either side gets. Put several things in there and they sit side by side.
Copy to clipboard
<flux:item>    <flux:item.heading>Next payment</flux:item.heading>    <flux:item.subheading>December 4, 2026</flux:item.subheading>    <flux:item.actions>        <flux:heading>$60.00</flux:heading>    </flux:item.actions></flux:item>
The subheading is optional. Without one, an item is a single line that's still as tall as a small button, so a row with a switch and a row with just a value stay even in the same group.

Lead with media

A team list of items, each led by an avatar, with an Owner label, an Admin role menu, and an options button at the end of each row
Put an avatar, an icon, or anything else in flux:item.media to lead the row. It's centered on the text beside it, with the spacing already set:
Copy to clipboard
<flux:item>    <flux:item.media>        <flux:avatar size="sm" circle src="..." />    </flux:item.media>    <flux:item.heading>Josh Hanley</flux:item.heading>    <flux:item.subheading>[email protected]</flux:item.subheading>    <flux:item.actions>        <flux:dropdown align="end">            <flux:button size="sm" variant="ghost" icon:trailing="chevron-down" inset="right">Admin</flux:button>            <flux:menu>...</flux:menu>        </flux:dropdown>    </flux:item.actions></flux:item>

Fits wherever you put it

A narrow item group where the Browse and Install buttons have moved below the text, while the switch on the next row stays at the end
On a narrow item, a labeled button moves under the text so the heading keeps its room. Switches, values, menus, and icon buttons are compact enough to stay at the end of the row.
The item goes by its own width, not the screen's. It's a container query under the hood, so the same markup does the right thing on a phone, in a modal, or tucked into a sidebar.

All. The. Details.

Long text wraps: Long words and email addresses break onto the next line instead of running under the actions.
Real headings: Pass level to flux:item.heading to render an actual h2, h3, and so on, so your page outline stays meaningful.
Ready-made examples: The docs include copy-and-paste examples for team members, connected apps, billing, notifications, and a danger zone.
And of course, Item is built from plain, semantic markup. The controls you put inside it, like switches, buttons, and dropdowns, keep all of their keyboard navigation, focus behavior, and screen reader support.
Item is part of free Flux, available in v2.22.0.

October 22, 2026
Flux datetime picker reading Oct 22, 2026 at 10:30 AM, open to a calendar with the 22nd selected and a list of times beside it with 10:30 AM selected
Meet the new Datetime picker: a date and a time, picked together from a single field. Perfect for scheduling events, publishing posts, setting reminders, or booking a window of time.
Copy to clipboard
<flux:datetime-picker wire:model="startsAt" />
Choose a day from the calendar and a time from the list beside it. Picking a time closes the picker, and changing just the date updates the value straight away. No extra clicks.
On the Livewire side, type hint a Carbon property and you're done:
Copy to clipboard
public ?Carbon $startsAt;

Made for mobile

The datetime picker on a phone, with the calendar on top, a time dropdown below it, and Cancel and Select buttons at the bottom
A calendar and a time list don't fit side by side on a phone, so on small screens the time moves into a dropdown below the calendar. Selections are confirmed with a "Select" button, so a stray tap never changes the value.

Ranges, with a time on each end

Range mode selecting October 26 through 31 across two months, with a 9:00 AM start time, a 5:00 PM end time, and a Select range button
Add mode="range" for event schedules, maintenance windows, or bookings. Each end of the range gets its own time, and the range is applied when "Select range" is pressed:
Copy to clipboard
<flux:datetime-picker mode="range" wire:model="schedule" />
Bind it to a Flux\DateTimeRange and you get Carbon instances for the start and end. It's a CarbonPeriod under the hood, so you can pass it straight to whereBetween():
Copy to clipboard
$deploys = Deploy::whereBetween('deployed_at', $this->schedule)->get();
When most ranges share the same hours, set them once with default-time and users only need to pick dates:
Copy to clipboard
<flux:datetime-picker mode="range" default-time="09:00/17:00" />

Business hours and booked slots

Use min and max to limit which dates can be picked, and min-time and max-time to limit the times of day. Together they cover things like "any future time between 9 AM and 5 PM":
Copy to clipboard
<flux:datetime-picker min="now" min-time="09:00" max-time="17:00" />
The unavailable prop blocks out whole days, the same times on every day, or individual slots on a specific day. You can mix them freely:
Copy to clipboard
<flux:datetime-picker unavailable="2026-12-25, 12:00-13:00, 2026-10-14T10:00" />
It also takes an array of Carbon instances, so blocking out existing bookings is one line:
Copy to clipboard
<flux:datetime-picker    wire:model="startsAt"    :unavailable="$bookings->pluck('starts_at')"/>

Down to the minute

The time list steps in 30-minute intervals by default. Change it with interval, or set time="input" when users need to type an exact time. The input still suggests times in a dropdown:
Copy to clipboard
<flux:datetime-picker interval="15" /><flux:datetime-picker time="input" />

All. The. Details.

Localized: Month names, weekdays, date formats, and the 12 or 24-hour clock follow the user's locale. Override them with locale and time-format.
Your calendar options: Everything you know from the date picker works here too, like with-today, selectable-header, week-numbers, and start-day.
Bring your own trigger: Open the picker from any button using the trigger slot. Handy for a "Schedule" button in a toolbar.
Wall-clock times: The value works like a native datetime-local input, 2026-10-14T10:30, with no hidden timezone conversions.
And of course, we went to great lengths to make sure this component honors expected keyboard navigation, focus behavior, and proper aria-labels so that screen readers can use it just as well.
Datetime picker is available in Flux Pro v2.21.0.

September 28, 2026
Three populated Flux cards: a profile card, a media card, and a usage card, each built from headers, bodies, and footers that share spacing and corners
We've rebuilt Flux's Card to give your app beautifully aligned cards, with the spacing, surfaces, and corners already figured out.
We're proud of the details in this one. Buttons sit just right in headers, inner corners follow outer curves, and each layout gets its own carefully tuned spacing.
Compose a card from headers, bodies, and footers, and those details come with it:
Copy to clipboard
<flux:card body="inset" variant="soft">    <flux:card.header>        <flux:card.heading>Notifications</flux:card.heading>        <flux:card.subheading>Choose what you hear about</flux:card.subheading>    </flux:card.header>    <flux:card.body class="space-y-4">        <flux:switch label="Product updates" checked />        <flux:switch label="Weekly digest" />    </flux:card.body></flux:card>
Every part is optional. Use only the pieces a card needs, or put content straight inside and it's padded evenly.

Surfaces

Flux cards in the default, muted, soft, outline, and filled surfaces, shown on zinc-50 and zinc-950 backgrounds
The variant prop gives you five surfaces. The default has a shadow in light mode and elevation in dark mode, while outline keeps the border without either. muted and soft offer quieter tints, and filled drops the border entirely. The tints adapt to the background underneath, with colors tuned for light and dark mode. Mix them freely without losing consistency.

Body treatments

Two rows of soft Storage cards comparing seamless, divided, separated, inset, and flush body treatments
The body prop changes how the parts meet. seamless keeps everything on one surface, divided adds lines, separated adds tinted bands, and inset or flush gives the body its own panel.
Each treatment has its own spacing for a reason. With no boundaries between parts, seamless cards can sit tighter. Dividers and panels need more room so nothing feels crammed.

Headers and corners

Close-up of a card header where a button sits in the corner with equal space from the top and side edges, its label aligned with the heading, above a flush body that reaches the card’s sides
Small buttons in flux:card.actions hang into the header's padding, with equal space from the top and side edges. Their labels line up with the heading text without making the header taller. Bigger controls get the space they need, and actions placed before the heading move to the leading side.
Look at the profile card in the hero: its body is inset, with corners rounded concentrically to the card's, so the gap between the curves stays even all the way around.
Headers and footers also work on their own outside a card, or as sub-sections nested inside a body.

Sizes

Card comes in four sizes: xs, sm, md, and lg. Each has individually tuned padding, typography, corners, and gaps, from compact sidebar cards to roomy settings forms.

Bleed

A compact media card with a forest image filling its inset body, above a footer with a filename and download action
Let images fill the body, right up to its rounded edges, while the footer keeps its own padding and room for actions. Wrap the image in flux:card.bleed and the card handles the fit. Tables have a bleed prop too: rows run edge to edge while their content stays aligned with the rest of the card.
We tuned every size, color, border, and line of text by hand, across each surface and body treatment. And since every card is built from the same few parts, your design holds together whether you're writing the markup yourself or an LLM is generating it. All those little decisions are now yours to reuse. 👌
Card is part of free Flux.
Copyright © 2026 Wireable LLC ·Terms of Service
Built with by
Caleb Porzio and Hugo Sainte-Marie