Figma Sites CMS: content and publishing

Check how Figma Sites manages CMS collections and published pages. Separate that workflow from design prototypes, Figma Make and commerce records.

Figma Sites CMS manages reusable content in collections and publishes it through lists and item pages. It suits a retail team building content-led pages, such as buying guides, with a shared design. Editing the collection changes the site file. Publishing makes those changes available to customers.

Identify Figma Sites and the other products

Figma Sites is the website-publishing product with its own content management system (CMS). Figma’s Sites CMS guide distinguishes a collection of content from the list and page that display it. A design prototype is a different deliverable: sharing a prototype doesn’t establish a published collection or public guide URL.

Figma Make has a separate application workflow. Figma’s Make backend documentation describes creating a Payload-powered backend and managing its records through the CMS tab in Make. That documentation belongs to Make. Don’t transfer its database or access-control features to Sites collections.

Identify the actual file and product before choosing an editing procedure. If the team manages content through a Payload admin panel in Make, assess that application and its data model. The Payload CMS guide covers the separate content platform.

Build a collection-driven page

Build a collection around a repeatable guide format, then connect its fields to the design. Consider a hypothetical homewares retailer publishing care guides. Each guide needs its own title and URL, with advice and links to the relevant store products.

The collection documentation lists required Title and Slug fields. It also supports plain text and rich text, plus image and link fields. Use rich text for the care advice and a link field for the destination in your store. A copied price in a text field needs its own maintenance process.

  1. Open CMS in the Sites file and choose Add collection. Create a collection for care guides and add the fields the format needs.
  2. Add guide items with distinct slugs. Keep the same field meaning across items so one template can display them consistently.
  3. Create a CMS list for the guide index. Connect the card’s text and image layers to their matching fields.
  4. Create a CMS page for the guide’s full content. Connect the advice and product link, then link each index item to its corresponding page.

Figma’s CMS list instructions explain those field connections and list-to-page links. The list documentation says filtering and sorting aren’t supported. Reordering items in the collection changes their order across CMS lists, so assess that shared ordering before promising separate category views.

The CMS page uses one design for an item’s detail view, with a distinct URL for each item. Review a short guide and a long guide at the intended screen widths. Check that empty fields don’t leave an incomplete instruction or misleading product link.

Update published store guidance

Edit the guide’s collection item, review its connected page and publish the site to release the change. Figma’s collection-editing instructions state that collection changes appear on the public site only after republishing.

For the care-guide example, correct the advice in the item’s rich text field. Review the full guide and its index card before the publisher releases it. Keep the slug stable for an ordinary correction so the existing link continues to identify the guide.

Make publication a named responsibility in your team. Figma’s publishing instructions warn that every webpage on the canvas is included, including dynamic subpages. Keep unfinished pages in a separate file instead of treating the publish action as approval for only the guide you just edited.

After publishing, open the guide’s public URL and confirm the correction appears. Follow the product link through to the store and check the page on a phone. A change visible on the canvas alone doesn’t confirm a released update.

If a connected answer service uses the guide, make the published page or a separately maintained content feed its explicit source. Confirm that service has received the revised advice. Publishing a page doesn’t establish that another service has refreshed its own copy.

Check commerce and portability limits

Keep the content site’s responsibilities separate from the store’s transactional records. For the care-guide setup, Sites publishes advice and links customers to product pages. Your commerce system remains the owner of stock and orders, with checkout handled by the store. An external product link is a navigation connection, not evidence of catalogue synchronisation.

Figma’s publishing documentation says site code cannot be exported for external publishing. Choose Sites with that hosting dependency understood. Keep an independent copy of approved guide content and its media so moving the information doesn’t depend on extracting the published design.

Importing content has specific constraints. The CSV import guide limits a collection to 200 items during the beta, with an import file under 2 MB. CSV means comma-separated values. Import support alone doesn’t establish a matching export workflow.

Figma’s Sites availability guidance requires a Full seat to edit and publish site files. Publishing to a live domain requires an eligible paid or Education plan. Include editor access and domain arrangements in the operating budget, without assuming every teammate can release changes.

Recovery also has a boundary. Figma warns that deleting a CMS collection is permanent and that file version history cannot recover it. A previously published site version can be republished, but that action doesn’t restore the editable canvas. Keep publication recovery and content backup as separate tasks.

Choose Sites when its collection structure and publication controls fit the guides your team maintains. If external hosting or a larger content application is required, resolve that requirement before moving the store’s approved guidance into collections.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup