SSGS | It allows you to quickly set | Grid library

Either way works in Eleventy, so it’s entirely a question of which way you prefer, which works best for how you like to arrange files and directories, and so on (https://www.zachleat.com/web/introducing-eleventy/#directory-structure-flexibility).

In other SSGs — notably Gatsby, Gridsome, and Hugo — one factor to keep in mind is that images for which you want special processing are best located in the same directories as the Markdown or other content files which “call” them, as relative file paths are required by the appropriate plugins or pipes:

• Gatsby: “If any of the [image] paths used do not resolve to a file[,] Gatsby will not create child nodes, instead leaving the [path] value as a string.” (https://www.orangejellyfish.com/blog/a-comprehensive-guide-to-images-in-gatsby/)

• Gridsome — “Only local, relative image paths will be compressed by Gridsome.” (https://gridsome.org/docs/images/)

• Hugo — “The image is a Page Resource, and the [image] processing methods listed below does not work [sic] on images inside your /static folder.” (https://gohugo.io/content-management/image-processing/)

This is not a consideration with Eleventy, however.

Because lists are mutable data types. And these in Python pass their pointer around (like any regular objects) instead of acting as a single unit like strings or ints. which automatically copy themselves.

This allows you to do just that. Pass a list into a function and modify it from in there. This has a lot of benefits.

So, if you are going to pass a list into a function that is doing something to it, but you do not want the original list changed, you have to copy the original to be used locally in the function only: