This page is Work-in-Progress
The content of this page is subject to change. Please do not use it on your production.
One of the main goals of introducing /trips v3 was to architect a flexible infrastructure that allows sherpa° to continue to add information that goes beyond COVID-19, making the information more relatable and engaging to your travellers.
When implementing any application that leverages sherpa° API, it is essential to use generic logic to avoid issues when inevitably information is added, removed or modified.
The approach outlined here will replace the previous static iconography guide.
Information groupings, groups, restrictions and procedures may include an
Icon attribute that currently carries a
name. The icon name is contextualized to the information object containing it, so you should use this name to locate the appropriate icons from your application resources.
Keep in mind that alt attribute can be inferred from the IconName directly.
You can fetch an icon from sherpa°'s CDN directly by referencing
Icons assets provided by sherpa° are best served as a backup alternative. We highly recommend using icons that are custom creations of your team, and match the design/theme/palette of your application.
Updated 5 months ago