search

gohugoio / hugo

The world’s fastest framework for building websites.
https://gohugo.io
Apache License 2.0
73.57k stars 7.39k forks source link

Output folder of rendered images of AsciiDoctor Diagram extension #12419

Open jrauschenbusch opened 2 months ago

jrauschenbusch commented 2 months ago

Diagrams should get rendered to an output folder below resources/_gen/images. Otherwise one needs to add content/**/*.png|jpg|svg|... to the .gitignore file to avoid Git changes in the worktree which need to get reverted after each site build.

Currently if one is working with workingFolderCurrent: true the images are generated besides their origin *.adoc files. This is required when you want to have working relative AsciiDoc cross references and AsciiDoc includes. But it would be totally fine to have generated images in resources/_gen/images, as they are combined in Hugo's union file system. It would just be necessary that the folder structure under content would be reflected so that image references are fine. Also for permalinks of course.

Maybe there is a way to achieve this with the current AsciiDoctor integration.

I think the imagesoutdir attribute would need to be configured per file in a way that resources/_gen/images is used as prefix and content/path/to/image/origin/file.adoc is converted to path/to/image/origin/ and concatenated with the prefix.

resources/_gen/images/path/to/image/origin/

@jmooring What do you think?

jmooring commented 2 months ago

What do you think?

I think this sounds like a lot of work with a low ROI, but maybe I'm missing something.

jrauschenbusch commented 2 months ago

Hmm. Maybe you’re right. Alternative is to use a naming pattern for generated images of AsciiDoc and add it as pattern to the .gitignore file. Otherwise you’ll see 100s of changes each time for large pages. And i don’t want to commit generated images.