Add a .Markdownify on Page

[bep]

Find a better name, but this is related to #5975 -- the markdownify has no page context so it just renders the content as "Blackfriday markdown", which is not ... perfect if in a shortcode and the surrounding content is Asciidoc.

[larzza]

To me markdownify is a misleading function name. All other -ify and -ize functions do what the name says but markdownify does the opposite (maybe this matter has been up for discussion before).

[cluck]

I always understood it like Markdown is mark-down because it is stripped from the mark-up added in HTML (which stands for Hyperthext-Markup-Language). Given that, the verb to transform Markdown to HTML... shouldn't it be... «markup»?

[bep]

@cluck you are right.

[regisphilibert]

Continuing from #6545. Ideally we would need to choose which page to use as a Page context on any string rendered with markdownify and when in need for this we could use .Markdowify but, we could also introduce a second optional argument to markdownify for a Page context.

We should test that second argument type before using it as the Page context though because a lot of people are already using Go Pipes:

{{ .Params.body | markdownify }}

Which is fine as long as the function only take one argument, but once it takes two, that .Params.body will be considered the last arg and be used as the Page context and could break a lot of people's code...

[bep]

This is fixed in e625088 method is .RenderString.

[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.