Design
Asset Download is a list of one or more downloadable assets — brochures, catalogues, PDFs, images that the user is expected to save to their device. Each row carries a label with the file extension, the file size, and a download glyph; the browser handles the actual download via a native <a download>.
When to use it (and when not to)
Section titled “When to use it (and when not to)”Use Asset Download for:
- A small set of supporting documents alongside primary content (vehicle brochures, technical specs, terms).
- Any place where the meaningful action is “save this file” and the file URL is consumer-supplied.
- Composed inside the Alternate Content pattern where one pane lists downloads.
Avoid Asset Download when:
- The link should open a page or document in-browser instead of downloading. Use a Link or Button with the file URL instead.
- The list is long enough to need filtering, sorting, or pagination — that’s a Table or a custom list.
- The action triggers something other than a static asset download (e.g. dynamic generation). Asset Download leans on browser-native download; bespoke flows belong elsewhere.
Quick summary of accessibility & consistency
Section titled “Quick summary of accessibility & consistency”- The link’s accessible name is the visible text by default (“Brochure .JPG 100 MB”). Override with an explicit
aria-labelonly when a surface needs a different announcement. - Items are visually separated by dividers — the Divider component recognises
.tng-asset-downloaddirectly, so the wrapping markup stays simple.