I’ve a feedback button and i passed the link as below in config.toml.
Is it possible to pass page title and link to the below href ? I mean TITLE should be the title of page and LINK should be the link of hugo page.
[params.ui.feedback]
enable = true
# The responses that the user sees after clicking "yes" (the page was helpful) or "no" (the page was not helpful).
yes = 'Glad to hear it!'
no = 'Sorry to hear that. Please <a href="https://mydomain.com/new-topic?tags=documentation&title=Documentation%20feedback%20for%20{{TITLE}}&body=Link:%20{{LINK}}%0AFeedback:%20">tell us how we can improve</a>.'
OK, I figured out how to do this, but it’s not simple.
config.toml
[params.ui.feedback]
enable = true
# The responses that the user sees after clicking "yes" (the page was helpful) or "no" (the page was not helpful).
yes = 'Glad to hear it!'
no = 'Sorry to hear that. Please <a href="https://mydomain.com/new-topic?tags=documentation&title=Documentation%20feedback%20for%20{{ .Title }}&body=Link:%20{{ .RelPermalink }}%0AFeedback:%20">tell us how we can improve</a>.'
Appreciate for your support. I tried but seems it could not able to get value. When I inspect the href, it parses <no value>
<a href="https://oneapi-discourse.dot.daimler.com/new-topic?tags=documentation&title=Documentation%20feedback%20for%20<no value>&body=Link:%20<no value>%0AFeedback:%20">tell us how we can improve</a>.
Here what I did.
config.toml
[params.ui.feedback]
enable = true
yes = 'Glad to hear it!'
no = 'Sorry to hear that. Please <a href="https:/mydomain.com/new-topic?tags=documentation&title=Documentation%20feedback%20for%20{{ .Title }}&body=Link:%20{{ .RelPermalink }}%0AFeedback:%20">tell us how we can improve</a>.'
Include a link to the source code repository of your project, because we really need the context of seeing your templates and partials to be able to help you. It is trivial to do a quick git clone on your repo, then run hugo server in your project, to help you out. On the other hand, recreating your code from screenshots, or sort of guessing at it, is not.
If you can’t share your repository for whatever reason, consider creating a dummy repo that you can share, which reproduces the problem you’re experiencing.