Skip to main content
All guides
Assets and data

Images, files, and data, all in sync

A website is more than words. It is photos and illustrations from the design team, and data like prices, store hours, and inventory that change often. Root.js keeps both organized and up to date, without copy and paste.

The Root.js CMS asset library, showing a folder of spring harvest images synced from Figma, a subfolder synced from Google Drive, and upload and sync actions.

One library for every asset

The asset library is a shared home for images and files, organized in folders. Upload in bulk, search by name, and reuse the same image across many pages, with a record of who changed each file and when.

Stay in sync with design

Any folder in the library can be connected to a Figma file or a Google Drive folder. When the design team updates an illustration, one click on Sync pulls in new and changed files — no exporting and re-uploading by hand. Pages that use a changed image are updated in draft, ready to review and publish.

Sync runs with each person’s own Figma or Google access, so only people who can see the source files can import them.

Fast images, automatically

Uploaded images are served through an image service that resizes and converts them for each screen. Editors upload one high-resolution original, and visitors on phones download a small, fast version.

Bring your data along

Data sources connect the website to information that lives elsewhere: a Google Sheet of prices maintained by the merchandising team, or a feed of store hours from an internal system. The CMS syncs the data on demand or on a schedule (hourly, daily, weekly, and so on), shows when it was last updated, and publishes it on its own, automatically after each sync, or as part of a release, so new prices go live at the same moment as the campaign that announces them.

The Data Sources page in the Root.js CMS, listing Google Sheets and HTTP JSON feeds with their publish status and when each was last synced and published.
Data sources from Google Sheets and an API, with their sync and publish status.

Frequently asked questions

Can our designers keep working in Figma?
Yes. Assets can be synced from Figma and Google Drive into the asset library.
Can non-developers update data such as prices?
Yes. Keep the data in a Google Sheet, and the CMS syncs and publishes it, including as part of a scheduled release.
Do editors need to resize images?
No. Upload the original; the image service creates the right size for each screen.
Next guideCollaboration and review
1
2
3
4
5
6
7
8
9
10
11
12
Breakpoint: