With my blog Hugo, I use related that work very well. It’s an excellent choice for automating links, for example at the bottom of an article. I do it with categories, tags and keywords (invisible, but which count for the calculation).
An elegant solution is to use this system, but list the links that are already in the article to exclude them from the related footer. We talked about it with @jmooring here:
For another blog, I just had a very simple idea while out walking in nature. I’ve never seen it here, so I’m sharing it with you.
Use related, as usual, with potentially quite a long list. But that’s the trick: only display it on the development server.
In this way, I can continue to make only selected and assumed links in the body of the text and not use related. But when I’m in development, I always have clearly visible link advice based on my taxonomies.
I think it’s pointless to say that a hugo.IsServer as a condition is all that’s needed 