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
Currently, HugoPhotoSwipe allows for three output sizes: large, small, and thumbnail. Additionally it supports the coverimage output using the cover output size. A feature idea I had was to generalize this to allow users to specify more different sizes. This would change the configuation from the current form (v0.0.15):
dim_max_cover: 600x600dim_max_large: 1200dim_max_small: 600dim_max_thumb: 256x256dirname_large: largedirname_small: smalldirname_thumb: thumb
In this setup, cover would have a special role, but for all the other sizes the name of the size will correspond to the old dirname_ setting, and there is the added option of using smartcrop for other sizes too. Additional sizes can be added by adding an item under the sizes setting. This could allow users to add other sizes for their specific website design, such as a super size for downloading a really large version of the image for instance. A side benefit for this setup is that it would simplify the code of HugoPhotoSwipe.
Currently, HugoPhotoSwipe allows for three output sizes: large, small, and thumbnail. Additionally it supports the coverimage output using the
cover
output size. A feature idea I had was to generalize this to allow users to specify more different sizes. This would change the configuation from the current form (v0.0.15):to something like this:
In this setup,
cover
would have a special role, but for all the other sizes the name of the size will correspond to the olddirname_
setting, and there is the added option of using smartcrop for other sizes too. Additional sizes can be added by adding an item under thesizes
setting. This could allow users to add other sizes for their specific website design, such as asuper
size for downloading a really large version of the image for instance. A side benefit for this setup is that it would simplify the code of HugoPhotoSwipe.Is this a feature that you find interesting and useful? If so, leave a 👍 reaction to this issue
Ideas on how it could be implemented differently? Let me know below!
The text was updated successfully, but these errors were encountered: