Skip to content
StorycardsInfographics
Create

Product guide

Publish a Smart Embed.

Review the visual, publish an immutable version and place one responsive embed that can receive future reviewed updates.

5 stepsCMS access helpfulVersioned delivery

A Smart Embed separates website placement from visual production. The page keeps one embed while your team reviews and publishes new project versions in Storycards.

1

Run the publishing preflight

Open Preview and check the visual as a reader will experience it.

  • Confirm the headline, labels, source line and dates.
  • Test buttons, tooltips, search, scrolling and other interactions.
  • Review desktop and narrow widths.
  • Confirm that private notes or credentials are not present in project content.
Connected source?Validate a sample and confirm that the public visual receives only the sanitized fields it needs.
2

Publish a reviewed version

Open Publish and create a version only after the preflight is complete. The published version is an immutable record of what readers received.

Publish centerProject ready
PUBLISH VERSION 3Reader snapshot is ready

Responsive preview checked · data validated · source note present

Publish
3

Copy the Smart Embed

Choose the embed option and copy the generated code. Keep the title attribute meaningful for the page and preserve the responsive wrapper when one is provided.

Do not expose a data-source URLUse the Storycards embed. Readers should not receive the private Sheet or authenticated API address.
4

Place it in the CMS and test the real page

Paste the embed into the article or landing page, then preview the complete page—not only the visual in isolation.

  1. Check the available width and surrounding margins.
  2. Test the smallest width used by the publication.
  3. Verify that the embed does not sit inside another fixed-height container.
  4. Load the page as a logged-out reader.
Article preview375 px · mobile
↔Responsive embedThe visual follows the article column and keeps its reader controls available.
5

Publish updates—or roll back

Edit the project and publish the next reviewed version. The page can continue using the same Smart Embed.

  • Preview the new version before making it current.
  • For live data, let validation protect the last good snapshot.
  • If a published change is wrong, select the appropriate earlier version and roll back.
Keep the embed stableReplacing the embed for routine updates creates unnecessary CMS work and makes recovery harder.

Questions

After it goes live.

Does the embed URL change after an update?

Routine reviewed versions publish to the same project, so the page can keep the same Smart Embed.

What if a live refresh fails validation?

The last good sanitized snapshot remains available instead of silently replacing it with an invalid response.

Can we preview before rollback?

Yes. Review the preserved version, then restore the appropriate published state.

Continue learning

FEATURESmart publishingExplore the complete delivery model.NEXT GUIDEConnect Google SheetsKeep a published visual current.TRUSTSecurity architectureUnderstand the private-to-public boundary.