Make p tags optional for render-image to enable use of figure elements

[andrewd72]

Hello!
I'd like a config option to turn off the wrapping of markdown images with p tags.
I wanted to give my perspective and experience dealing with the way it currently works as a new Hugo user with photography blogs.

There was some discussion here:
-->](#6748 (comment))

It came down to this (and was closed):
"In this issue's original example, the render hook for a markdown image was coded to return a figure. This seems like we are hijacking the render hook, asking it do something for which it was not designed."
I disagree.

An image is an image

When writing my markdown content I just want to be able to add an image.
Having the render hooks in hugo is awesome, I could make figure elements from my existing content files with a simple template, awesome. An image is now the same image but can have retina, webp, responsive versions.

I just get them wrapped in unwanted p tags.

Being able to override the p tag wrapping would be to:

"override certain parts of the default Markdown rendering"
(Hugo docs description of a render hook)

Shortcodes are not the answer

the suggestion in the issue linked above was to use shortcodes
i) I have hundreds of articles with a few thousand images between them, swapping markdown image to shortcodes would have to be done programmatically or take weeks.
ii) the idea of having my content as markdown was to make it platform independent and it worked
iii) shortcodes don't show the content if you write with a markdown app with a preview

Coming from grav

I had the same issue in grav but there is a solution with a plugin which makes images into figure elements and it removes the p tags e.g.
-->](https://github.com/OleVik/grav-plugin-imgcaptions)
I don't think it can be just me with a need for this, trying to come up with a solution to match what I could do with grav I found people with solutions to strip p tags from images in other projects e.g. jekyll and wordpress

Workaround

I've spent quite some time trying to work around this.
This is what I came up with for a workaround (seemed simpler than some suggestions)
i) Since we get an unwanted

before the figure I close it immediately by starting the render hook with

And do the same idea at the end, finishing with

which gets wrapped in the unwanted

ii) I use a grunt task to remove /

\n?</p> from all the html files in the public folder

Thanks for your time.

[bep]

Somewhat related #8362

[andrewd72]

Amazing, look forward to testing it out.
I am really enjoying working with hugo and to have this is the icing on the cake.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.