Hello!
I'm playing around with Pelican as a SSG for a blog site and trying to use image-process to optimise images and generate srcsets.
Each blog post is a "bundle" of a markdown page and several images that are stored locally in the same directory as the MD file.
content/blog/cat-post-1 -> cat-post.md, cat_fooling_around.jpg
Images are linked in markdown with {attach} directive as per Pelican docs, i.e.
{: .process-image-large-photo }
When image-process tries to find cat_fooling_around.jpg image, it's looking in content folder (which is the source folder for blog files). However, it's using a path that is defined in ARTICLES_SAVE_AS setting of Pelican (i.e. /blog/2025/04/09/my-cat-post). This path does exist, but it's in the output folder, where generated site files are stored.
I'm not sure whether it's a bug or expected behaviour, but it seems that with using image process with {attach} is currently broken.
Hello!
I'm playing around with Pelican as a SSG for a blog site and trying to use image-process to optimise images and generate srcsets.
Each blog post is a "bundle" of a markdown page and several images that are stored locally in the same directory as the MD file.
Images are linked in markdown with {attach} directive as per Pelican docs, i.e.
{: .process-image-large-photo }When image-process tries to find
cat_fooling_around.jpgimage, it's looking incontentfolder (which is the source folder for blog files). However, it's using a path that is defined in ARTICLES_SAVE_AS setting of Pelican (i.e./blog/2025/04/09/my-cat-post). This path does exist, but it's in theoutputfolder, where generated site files are stored.I'm not sure whether it's a bug or expected behaviour, but it seems that with using image process with {attach} is currently broken.