You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea behind this module is never to have to worry about the media solution used on any given project.
tnd-media/Get
We should rely on a single partial tnd-media/Get which will retrieve a given asset, process it if transformation are used and return an object
Return
Permalink
RelPermalink
Width
Height?
MediaType
Extensions
Alt
Title
Note that Width and Height will be useful for SEO metas
Parameters
The partial would take parameters just like the tnd-imgix/GetSRC partial:
A lone string (path to retrieve the media info without transformation)
A map with
src (or path) pointing to the file location within the media storage location
any transformation key (width, height etc...)
Logic
The partial will look for tier service setup. (For now only imgix will be supported using the tnd-imgix module)
If found, the service own logic will be used to retrieve to apply transformation and return the resulting permalinks etc...
If no service is found, the partial will use Hugo's own Page Bundle transformation tooling to apply transformations requests (if given method is available and then return the data.
Challenges
Hugo transformation is about different methods. So one needs depending on the list of transformation requests to potentially find the proper method and settings.
Storages
There are three types of storage avaible:
static
With static, transformation is only possible with Imgix and minimal media data can be returned through Get.
assets
With assets, transformations are possible through imgix and hugo.
Documentation should point out that only the media submitted to code (not those simply added to the storage) will be published and there's no way around that.
bundle
With bundle, transformations are possible through imgix and hugo.
Documentation should point out that only the media submitted to code (not those simply added to the storage) will be published unless user set _build options to the given bundle.
The text was updated successfully, but these errors were encountered:
The idea behind this module is never to have to worry about the media solution used on any given project.
tnd-media/Get
We should rely on a single partial
tnd-media/Get
which will retrieve a given asset, process it if transformation are used and return an objectReturn
Note that
Width
andHeight
will be useful for SEO metasParameters
The partial would take parameters just like the tnd-imgix/GetSRC partial:
src
(orpath
) pointing to the file location within the media storage locationwidth
,height
etc...)Logic
The partial will look for tier service setup. (For now only
imgix
will be supported using thetnd-imgix
module)If found, the service own logic will be used to retrieve to apply transformation and return the resulting permalinks etc...
If no service is found, the partial will use Hugo's own Page Bundle transformation tooling to apply transformations requests (if given method is available and then return the data.
Challenges
Hugo transformation is about different methods. So one needs depending on the list of transformation requests to potentially find the proper method and settings.
Storages
There are three types of storage avaible:
static
With static, transformation is only possible with Imgix and minimal media data can be returned through
Get
.assets
With assets, transformations are possible through imgix and hugo.
Documentation should point out that only the media submitted to code (not those simply added to the storage) will be published and there's no way around that.
bundle
With bundle, transformations are possible through imgix and hugo.
Documentation should point out that only the media submitted to code (not those simply added to the storage) will be published unless user set _build options to the given bundle.
The text was updated successfully, but these errors were encountered: