VELORYZ STUDIO / KNOWLEDGE

Cards, lists and repeaters

Data-driven repeated content and card layouts.

Cards, lists and repeaters

VELORYZ Studio · Components and interactive content Audience: Content authors, designers and frontend integrators Guide type: Design specification and team-managed workflow

Purpose

Cards, lists and repeaters should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Data-driven repeated content and card layouts.

This guide covers data-driven repeated content and card layouts. Use it as an actionable design specification and team-managed workflow: verify the current UI and any provider configuration before relying on a control in production.

Availability and responsibility

The public site contains real links, forms, media, navigation and interactive pages. A customer-accessible component palette is not proven; use these guides as implementation and acceptance references for Studio work.

Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.

Before you begin

  • The content goal, field labels and required interaction outcome
  • Destination URLs, media sources and permissions to use them
  • Error, loading, empty and success copy
  • A short list of measurable success criteria specifically for cards, lists and repeaters.
  • A recovery plan if the proposed change creates a regression.

Recommended procedure

  • Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
  • Define the specific work item for Cards, lists and repeaters: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
  • Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
  • Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
  • After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.

Topic-specific operating procedure

The following steps are specific to Cards, lists and repeaters and supplement the general workflow above. Apply only the controls and roles actually available to your account or deployment.

  • Use cards only when they present meaningful distinct items and destinations.
  • List items should retain predictable reading order and not hide critical details on hover.
  • Repeaters need stable keys and valid empty states when connected to data.
  • Avoid turning informational cards into fake clickable controls.

Evidence to retain

  • A short before/after record of the actual user-visible change or reviewed deliverable.
  • The exact site URL, owner or reviewer, and the approval or release reference.
  • Any unresolved limitation, assigned follow-up, and a safe mitigation.

Configuration and decision points

  • Choose the simplest semantic element: link for navigation, button for an action and form for data submission.
  • Specify labels, validations, disabled states and error recovery before adding animation.
  • Test all controls with mouse, keyboard and touch; do not place functionality only on hover.
  • Document the owner of each external embed, form endpoint and data retention process.

When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.

Verification checklist

  • Each action produces the expected state or gives a clear explanation when unavailable.
  • Form errors are announced and do not discard user-entered data unnecessarily.
  • External destinations have safe protocols and useful descriptive labels.
  • Media includes appropriate alt text or captions rather than decorative descriptions.

Also confirm that the result addresses the original objective: Data-driven repeated content and card layouts.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.

Troubleshooting and recovery

  • If a button appears inert, inspect its intended action and available backend endpoint.
  • If a form fails, verify field validation and API status without leaking credentials.
  • If an embed breaks or blocks performance, remove it or provide a useful fallback.

When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.

Related reading

  • [Component library overview](/docs/studio/components/overview/)
  • [Text, headings and rich text](/docs/studio/components/text/)
  • [Buttons, links and calls to action](/docs/studio/components/buttons-links/)
  • [All VELORYZ documentation](/docs/)
  • [Studio documentation](/docs/studio/)
  • [Help Centre](/help/studio/)
  • [/design/](/design/)
  • [/motion/](/motion/)

Operational note

This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.

Let’s talk
Make your project