A fictional arts council publishes a monthly neighborhood art walk. Its planning sheet contains confirmed gallery stops, one tentative outdoor demonstration and a pottery session canceled after the artist became unavailable. Figma Sites CMS can manage collection items and repeat them through CMS lists and pages, but accurate status and publishing decisions require an explicit editorial workflow.
Create an event source of truth
Start with the council’s approved schedule, not a scraped calendar or old poster. Assign each event an ID and a person responsible for its status. A web designer should not convert “artist may attend” into a confirmed appearance merely because a page template expects a title and start time. Keep the editorial sheet and CMS item linked by a stable identifier.
For the fictional schedule, the ceramics demo is canceled, the gallery tour is confirmed and the outdoor lecture remains tentative. Those differences need to be represented as structured data. If the CMS does not by itself enforce your organization’s rules, define the review step outside the design tool and document who can approve changes.
Model a collection with clear fields
Figma’s guide describes a CMS collection as structured items with fields, a CMS list as repeated content and a CMS page as the detail template. Define title, slug, date, start time, venue, accessibility note, description and a reviewed status label. Keep the title and slug stable when an item changes status so existing links can be managed intentionally.
Do not place a cancellation only in the body paragraph while a “Join us” button remains visible in the event card. Use a content convention that the site maintainer can apply consistently. The official Figma CMS guide describes field types and collection management; confirm your plan’s current limits and supported publication workflow before implementation.
Build a reusable card list
Design one readable card with a title, date, venue and short accessibility note. Connect its fields to a CMS collection and repeat it through a list, rather than duplicating separate frames for every event. This helps prevent mismatched date text after schedule changes. A list does not inherently know which events are approved for display.
If a filter for your desired status is available in your product configuration, verify that it behaves as expected. Otherwise maintain a deliberate editorial selection of publishable items. Test the canceled demo and tentative lecture: neither should look identical to a confirmed event with an active signup link.
Create a detail page that keeps its context
Figma Sites CMS pages provide a template-based view for individual items. Map the event title, times, directions and relevant access information to corresponding fields. Keep the template visually consistent, but leave space for a meaningful status warning and a last-reviewed note. A beautiful generic template should not hide a canceled session behind promotional copy.
Check the destination of each list card. A visit to the ceramic-demo URL should not imply the workshop still takes place. Depending on editorial policy, the page may remain with a cancellation notice or be intentionally removed. Choose a policy and verify navigation, search previews and internal links after publishing.
Separate canceled, tentative and confirmed
A three-state review is more useful than a single “on/off” switch. Confirmed events have verified time and venue, tentative events require follow-up, and canceled events must not show an active booking prompt. In the comparison illustration, a canceled item appears mistakenly under “Upcoming,” then moves into a visibly canceled state without a signup action.
Do not treat the sample statuses as evidence of any real art walk. The diagram depicts editorial acceptance rules. Where your CMS field types do not include an automated workflow engine, the site team must enforce these rules through review and publication practice rather than assuming content status becomes a policy automatically.
Audit dates, time zones and venue directions
An event timestamp can be technically valid yet misleading to visitors when a venue closes early or a time zone is wrong. Verify the date and local start time against the current organizer-approved source, then read the finished card as a visitor would. Preserve specific directions from the venue; do not invent an accessible entrance because a map looks plausible.
Check longer addresses, abbreviated months and daylight saving transitions where relevant. The events in this example are intentionally fictional; use official organizer data before publishing an actual calendar. If a location changes, examine not just the detail page but list cards, shared previews, newsletter links and printed QR codes.
Design for keyboard and small screens
A repeated card must remain usable when a long title wraps on mobile. Test heading order, focus visibility, link wording and screen-reader text. Avoid a color-only red/green status indicator: write “Canceled” or “Confirmed” in words. A canceled card should not contain a link styled like a live registration button even when it looks visually muted.
The same collection may appear in a multi-column desktop list and a one-column mobile layout. Inspect both after changing a field value. Make sure dates do not clip, accessible directions are not pushed beneath overlays and the CMS page links identify the specific event rather than saying only “More.”
Understand preview versus publishing
Figma says connected CMS data appears on the canvas and is included when a site is published. An editor looking at updated design content must not assume the public site changed until publication is complete. Establish a release checklist that covers a preview of the live page, a fresh browser session and a direct link to each modified item.
Assign one person to check status and a different reviewer for a final pass when the calendar is sensitive. Record the revision of the source schedule used for publishing. If a cancellation comes after an event announcement was sent, the website update is only one communication channel; the council still needs to update the original invitees.
Maintain the calendar after launch
Set a recurring pre-event review to reconfirm the organizer, start time and accessibility information. Use the collection as a maintainable information system rather than a finished static poster. Remove temporary placeholder language, and treat empty fields as missing data instead of quietly inventing locations or hosts.
The final QA drawing highlights three checks: a verified status, a working detail-page link and a mobile card without a misleading CTA. This workflow is based on documentation and illustrative data; it does not claim a real Figma site was built or tested. Actual capabilities and limits depend on current beta and plan conditions.
How We Research
For this November 2026 guide we consulted the product developers’ primary materials: Figma Guide to Figma Sites CMS, Figma Create a CMS collection, Figma Create a CMS list. We compared documented feature definitions, workflow boundaries, source or state handling, and restrictions on availability. We did not run these vendor APIs, visit an actual museum workshop, deploy a website, or test an interview recording. The people, dates, objects, permissions and outcomes in the examples are fictional; the drawings are original conceptual explanations, not product screenshots or benchmark results. Editorial checks and approval stages are recommended procedures, not guarantees supplied by the service. Review current provider documentation, billing, regional availability, privacy terms and the organization’s own policies before applying the process to sensitive records or live users.
Frequently Asked Questions
No. Editors must update approved collection data and verify the published site and linked communications.
A list repeats summary items from a collection; a page displays the detail template for one item.
Not unless the organizer has authorized registration. Show a clear tentative status instead.
Use explicit text such as “Canceled,” not only color changes or disabled-looking visual styling.
No. The art-walk scenario and interface drawings are illustrative workflow examples.