"photos"
and/or "videos"
arrays of objects within their GeoJSON properties, which is where the media metadata is read from. we didn't use links to web pages/articles and i can't remember if that sub-feature was updated from the Pattrn v1 codebase, but i'll have a look
metadata.yaml
or metadata.json
file for the instance is needed - i will add documentation for this)
[
{
"source": "UNESCO",
"src": "/data/unesco-bosra/media/photos/0010/0001.jpg",
"subhtml": "Pas de dégâts apparents sur le cliché oblique diffusé par la nouvelle Direction des Antiquités de Bosra.",
"thumb": "/data/unesco-bosra/media/photos/0010/0001.jpg",
"caption": "Pas de dégâts apparents sur le cliché oblique diffusé par la nouvelle Direction des Antiquités de Bosra."
}
]
[
{
"source": "UNESCO",
"src": "https://www.youtube.com/watch?v=-Yyz4wKmcQY",
"subhtml": "état des lieux en mars 2013.",
"thumb": "https://i.ytimg.com/vi/-Yyz4wKmcQY/hqdefault.jpg",
"caption": "état des lieux en mars 2013."
}
]
src
and thumb
properties of the object above are simply used as relative to the current site's root. you should be able to just use arbitrary HTTP/HTTPS URIS, depending on CORS and other policies, though i would generally recommend to package things up with your Pattrn instance if you can (licenses etc.) so that you can keep photos alongside the rest of your instance's content (and benefit from CDN etc if you publish your Pattrn app to Netlify or any other service that includes a CDN)
v2.0.1
) in my personal clone here: https://github.com/hotzeplotz/pattrn/tree/development/v2.0.1