...
A card is a UI component that contains content and actions about a single subject. In this case, it represents the Generic Card is a highly configurable component used to render a single row from of a Synapse Table or View.
Here are a few examples:
...
*type: Indicates the object type, for example “Project”. Icons are automatically mapped for some types.
*title: Column name to use for the title.
link: Column name that contains an URL to make the title a link.
subTitle: Column name to use for the sub-title.
description: Column name to use for the description.
descriptionLinkConfig: Indicate if the description is markdown.
icon: Column name that contains the name of the icon to use in this card.
imageFileHandleColumnName: Column name that contains the FileHandleID of a custom image to be displayed on the card.
ctaButtonLinkConfig: Configure the CTA button link. Define what the button text should be, and the link configuration (column to use for the image in the cardvalue, and how to create the internal link).
secondaryLabelslabelLinkConfig: Instruct the card on how to render create links in the secondary labels. Columns may contain markdown, or perhaps their value should could be used to create a an internal link (to a details page for example).
dataTypeIconNames: Column name that contains the list of data types to show as additional icons.iconOptions: For all cards in a list, use a custom icon mapping.
backgroundColor: Background color of the card.
isHeader: Indicate if the card should be rendered as a Header.
How are cards used?
What are the components within a card (e.g. Data type icons, custom image, CTA button link, etc) and how iconOptions: For all cards in a list, use a custom icon mapping.
How would someone set these up in Synapse?
...