-
-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for a 'backlinks' widget #315
Comments
I'm afraid there will be a performance issue of the implementation. And it doesn't work well with |
Okay, let me think more about this. I'll try asking the author of that blog post if there is a better way to do it that works with ref and relref.
Yes. Previous discussions I found on this topic had the same concern. For example, gohugoio/hugo#8077 (comment) Just trying to brainstorm some ideas below:
|
|
Update: |
Hmm... thank you for thinking about this. I can't think of any other options. So for now, we could close this issue as "will not implement. I'll try to write a python script that will read the markdown files and append a backlinks section at their end, containing lists of refs/relrefs. This script can be executed before Hugo is executed.. so that Hugo does not need to do anything.. it'll be as if the source files Hugo processes has all the correct backlinks already present in them. |
OK, I keep it closed until we found a better solution. |
This feature request is related to the use case of creating a 'Digital Garden' mentioned in #314 .
It would be great to have a couple of cards that can be placed either in the right sidebar (like the taxonomy cards) or under a post (like the related posts card).
One of these cards would list all the "forward/outgoing links" from the blog post/single page i.e. all the hyperlinks (to internal or external pages) present in the blog post/single page.
The second of these cards would list all the "back links" to the blog post/single page i.e. which other posts/pages contain a link to this page?
Examples/Inspiration
The text was updated successfully, but these errors were encountered: