Skip to content
StorycardsInfographics

Smart publishing

Publish once. Stay in control after launch.

Place one responsive Smart Embed in the page, publish reviewed versions to the same project and keep readers on the last good snapshot when live data changes.

  • Responsive embeds
  • Immutable versions
  • Safe rollback
  • Live snapshots
Publish centerEmbed health · stable
LIVE · LAST REFRESH 2 MIN AGO
3
Current published versionLive source validated · responsive layout checked
LIVE
2
Previous versionAvailable for preview or rollback
READY
ReviewPublish snapshotSmart EmbedValidate updatesRollback if needed

One publishing lifecycle

The embed stays stable while the story evolves.

Update the project, validate the next snapshot and publish without asking the newsroom or website team to replace code.

01

Check the visual

Review content, sources, interactions and the responsive layout before release.

02

Publish a version

Create a reviewable, immutable version of the visual that readers can receive.

03

Place one embed

Copy the Smart Embed into the article, landing page or Storycards experience.

04

Update safely

Publish the next reviewed version to the same project, or roll back when needed.

Responsive by design

One visual, ready for the space around it.

The embed adapts to its container while the project preserves the layout and interaction choices made in Studio.

Smart Embed

Publish into the page, not beside the workflow.

Keep the live visual independent from the CMS while preserving a stable placement for editors and developers.

  • Responsive container sizing
  • Share page and embed delivery
  • Same placement across future versions
Embed previewReady to publish
THE DATA STORY

Demand moved faster than supply

Interactive chart · responsive height · reader controls

<iframe src="https://infographics.storycards.com/p/…" title="Interactive data story" loading="lazy"></iframe>

Live, with guardrails

Fresh data does not need to mean fragile delivery.

Resolve private sources on the server, validate the shape of each update and let the public viewer read a sanitized snapshot.

01

Private source boundary

Readers never connect directly to the private Sheet or authenticated supplier.

02

Last good snapshot

An incomplete or malformed refresh does not silently replace the valid published data.

03

Version recovery

Preview earlier versions and restore the right one without changing the embed placement.

Questions

Publishing without surprises.

Do we replace the embed after every update?

No. Publish reviewed versions to the same project and keep the Smart Embed in place.

What happens when live data is invalid?

Server-side validation protects the public visual. The last good sanitized snapshot remains available instead of exposing a broken supplier response.

Can we return to an earlier version?

Yes. Published versions are preserved for review and rollback.

Storycards Infographics

Put the visual live. Keep the controls.

Publish responsive data stories that can change safely after launch.

Start creating