How are variants written?

In the wizard you write a Default and any number of named variants (typical: 2 to 5). Each variant has its own threshold settings. The text uses placeholders like {{winner}}, {{leaderPct}}, {{lead}} that fill in from the bound data at read time.

What are the eight trigger conditions?

Leader changes, close races, vote thresholds, archetype shifts (clear winner / competitive split / fragmented), chart metric changes, chart metric thresholds, trend reversals, and claim staleness. Combine any of them per variant.

What is the hysteresis buffer?

Two settings together: a stability window (how many consecutive evaluations a new variant must win) and a percentage buffer (how far past the threshold it must clear). They prevent flip-flopping on noisy data, so a variant has to earn the switch.

What's the difference between proactive and reactive mode?

Proactive: you write the variants upfront and the block selects whichever fits. Reactive: monitoring is on, and when data drifts in ways your variants do not cover, the system drafts an AI-written variant for your review. Most blocks run hybrid, with reactive corrections graduating into proactive variants over time.

Can readers see why a particular variant is showing?

Yes. Turn on the Live Badge and readers get a "Why am I seeing this?" affordance that explains in plain language which condition is active right now.

Which CMSes are supported?

First-class integrations for WordPress, Ghost, Shopify, Webflow, Contentful, Sanity, and Notion. Any other CMS works via the iframe snippet: paste, save, done.

LiquiChart

Prose that moves with the data.

A Living Content block is a paragraph that holds several variants at once. When the data behind it shifts past your threshold, the block switches to the variant that fits. Hysteresis buffers the change so the reader never sees a flip-flop.

See a Variant Switch Open the Builder

app.liquichart.com/living/work-trends-intro

yoursite.com/blog/state-of-remote-work-2026

How developers actually want to work in 2026

According to our running survey of 2,847 developers, remote-first arrangements leads at 44%, ahead of hybrid by 9 points and widening month over month. Office-only sits at 17%, down 4 points year over year.

Hover any underlined slot to see which claim it pulls from

Switch history

v.1212 days ago

Remote-first overtakes

auto · leader flip detected

v.113 weeks ago

Hybrid leads at 38%

auto · scheduled refresh

The same paragraph,
14 months apart.

Left: how prose ages on most blogs. Right: how it ages with a Living Block.

Static prose

According to our running survey of 1,247 developers, hybrid arrangements lead at 38%, narrowly ahead of remote-first by just 2 points.

4 facts have shifted since publish

×1,247 → 2,847 votes
×Leader flipped: hybrid → remote-first
×Lead margin: 2pp → 13pp
×No human noticed for 14 months

Living Content

According to our running survey of 2,847 developers, remote-first arrangements lead at 46%, ahead of hybrid by 13 points and accelerating.

14 variant switches since publish

✓Switched between default ↔ clear-leader 9 times
✓Leader flipped once · close-race variant activated
✓Hysteresis buffered 3 candidate switches as noise
✓Reactive mode proposed 2 new variants for review

Every block has the same six parts.

Hover the labels to highlight each piece.

LivingBlock work-trends-intro

01 · Variants

Default · “{{totalVotes}} votes so far, results emerging”

Clear leader · “{{winner}} leads at {{winnerPct}}%, +{{lead}}pp”

Close race · “{{winner}} and {{runnerUp}} within {{lead}}pp”

02 · Triggers

Poll → #143 · top_option, total_votes

Chart → #19 · q1-2026 series

Claim → polls/work-2026.leader

03 · Conditions

On leader_change

On votes ≥ 1000

On archetype → clear_winner

04 · Hysteresis

Stability: 3 checks

Buffer: 5%

Window: 24h

05 · Reactive

Monitoring: on

Proposes: new variants

Approval: required

06 · Switch history

v.14 · just now · clear_leader → close_race

v.13 · 12 days ago · default → clear_leader

v.12 · 28 days ago · reactive proposal

Variants

The 2 to 5 text alternatives the block can render. A Default plus named variants like Clear Leader, Close Race, or Stale Source.

Triggers

Bound data sources, a poll, a chart series, a claim, or several at once. The block evaluates them on every read.

Conditions

One of eight types: leader change, vote threshold, archetype shift, chart metric change, trend reversal, claim staleness, confidence crossing, stability signal.

Hysteresis

A stability window plus a percentage buffer. A new variant has to clear both before the block switches, so no flip-flopping on noisy data.

Reactive mode

Optional. When drift outruns your variants, the system drafts an AI-written replacement variant for review. You approve before publish.

Switch history

Every variant switch logged with the condition that triggered it. Roll back, compare, or graduate a reactive proposal into a permanent variant.

It rewrites like a person would.

Conditional variants

Write 2 to 5 versions. The block picks the right one.

Compose a Default, plus variants like "Clear Leader" or "Close Race" with their own thresholds. The block evaluates on every read and renders whichever variant the data currently fits.

Eight triggers

Leader change, threshold cross, archetype shift, and five more.

Bind to a poll, chart, or claim. Trigger on leader changes, close races, vote thresholds, archetype shifts, chart metric changes, chart metric thresholds, trend reversals, or claim staleness.

Hysteresis

A variant has to earn the switch.

A new variant must hold past your stability window and clear a percentage buffer before the block flips. No flip-flopping on noisy data, no whiplash for the reader, no rewrite for a one-day blip.

Reactive mode

When drift breaks the variants, it proposes a new one.

Turn on reactive monitoring and the system watches for data shifts that no variant covers. It drafts an AI-written replacement variant for review, and you approve before publish.

One snippet. Always the right variant.

Drop a Living Content embed anywhere in your CMS. The block evaluates its conditions on every read and renders whichever variant currently fits the data. Switches are buffered by hysteresis, so the reader never sees a flip-flop.

Conditions evaluated on every read
Hysteresis prevents flip-flopping on noisy data
Optional "Why am I seeing this?" affordance for readers
First-class: WordPress, Ghost, Shopify, Webflow, Contentful, Sanity, Notion

<!-- paste anywhere in your CMS -->
<iframe
  src="https://app.liquichart.com/living/work-trends-intro/embed"
  width="100%" height="auto"></iframe>

<!-- block evaluates conditions on every read and switches variants -->

iframe · variant switches buffered · live badge optional

Six paragraphs
that should never go stale.

Refresh evergreen posts

A paragraph in a five-year-old reference article stays current. When the data underneath shifts past your threshold, the block switches to a fresher variant.

Sync prose with poll results

When the leader flips or a vote count crosses a threshold, your launch post switches to the matching variant, without you opening the editor.

Annotate a chart in words

A paragraph below the chart that mirrors the deltas. Variants for "metric up", "metric down", and "no change worth mentioning", so the chart and the sentence never disagree.

Frame a close vs decisive race

One paragraph for a clear winner, another for a competitive split. Hysteresis prevents flipping back and forth on small daily noise.

Brief the team on shifts

Internal living docs that watch your real data, so morning standup reads the truth, not last week's truth.

Let reactive mode do the work

Turn on reactive monitoring and the system proposes a new variant whenever drift catches your existing variants out of date. You stay in the loop, approval-first.

FAQ

Write the paragraph once.

Let it stay accurate for years. Free to start, no card required.

Join the Waitlist Open the Builder