Footer card

A bar the full width of the screen, flush to the bottom edge, rolls up the small things a screen needs. The left and right slots each show one item: words, a tag, a clock, the weather now, an icon, the date, a status dot, your logo, a countdown, a number, the page you are on or a quiet alert that turns warm or red. The middle carries a message that sits still, crawls when it is long or turns through up to eight pages. You set the items and the message and change them while the bar plays; it keeps its place on every screen.

Live card

Category: Messages. Tags: Lobbies and reception, Offices and workplaces, Stores.

Layouts

This bar card is placed as a footer: a full-width bar, 80 high, flush to the bottom edge. It takes no layout or anchor.

Layouts: footer. Forms: strip.

Card layouts, themes and publishing. Browse the cards.

Data and privacy

Feed: screenrig.weather/v1.

Feed documents carry source attribution. The Player supplies the feed to the card.

Weather attribution: Weather data by Weatherbit, as named in the feed document.

Properties

For theme, background and accent, see Common properties. A bar card has no layout or anchor property: it is always placed as its footer.

Set static properties in params. Bind data to a project card data key for live values; that document holds only dynamic properties. Without a data key, put the complete configuration in params. Nested rows describe the contents of their parent property.

Static properties

Dynamic properties

Canvas example

Add this item to a playlist page’s primitives. Publish the playlist and assign a screen.

{
  "id": "footer",
  "primitive": "card",
  "card": "footer",
  "major": 1,
  "layout": "footer",
  "params": {
    "theme": "neomustard",
    "location": {
      "name": "Vancouver",
      "latitude": 49.25,
      "longitude": -123.0
    }
  },
  "content_fit": "fill",
  "data": "example-key"
}

Write live data

The canvas example binds its data field to example-key. That value is a data key: a name this canvas item chooses, not the name of the card. Give each canvas item its own key when items should show different data, or share one key when they should show the same data. Keys are scoped to the project, follow the K/V key grammar, and cannot start with feed:.

Create this document before showing the card, then replace it to update the screen without republishing. Writes to a key that live canvas items bind are checked against each bound card’s dynamic properties. Use the same project as the playlist.

Save the document as card-data.json. The CLI reads the document itself, with no wrapper:

{
  "left": null,
  "right": null,
  "middle": null
}

screenrig card-data put example-key --file card-data.json

Or call the API directly. The API wraps the same document in a document field. An agent token already names its project, so no project header is sent; if you send ScreenRig-Project, it must match the token’s project. Supply your API authorization through the environment; see API authentication.

curl --request PUT "https://api.screenrig.ai/api/card-data/example-key" \
  --header "Authorization: Bearer $SCREENRIG_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"document":{"left":null,"right":null,"middle":null}}'