<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Embeddings on /var/log/janio</title><link>https://devops.sarmento.org/en/tags/embeddings/</link><description>Recent content in Embeddings on /var/log/janio</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Apr 2026 10:41:00 +0000</lastBuildDate><atom:link href="https://devops.sarmento.org/en/tags/embeddings/index.xml" rel="self" type="application/rss+xml"/><item><title>Munin: internal links for Hugo with AI</title><link>https://devops.sarmento.org/en/posts/munin-internal-links-for-hugo-with-ai/</link><pubDate>Fri, 17 Apr 2026 10:49:00 +0000</pubDate><guid>https://devops.sarmento.org/en/posts/munin-internal-links-for-hugo-with-ai/</guid><description>&lt;p&gt;In the &lt;a href="https://devops.sarmento.org/en/posts/hugin-tags-and-summaries-for-hugo-with-ai/"&gt;post about Hugin&lt;/a&gt; I explained how I solved the tag and summary problem on my Hugo blog. But there was another problem, less obvious and more annoying: internal links. Those links that connect one post to another, help readers navigate related content, and that Google loves to see on a well-structured site.&lt;/p&gt;
&lt;p&gt;The truth is nobody links anything. You write a post about systemd timers, another about cron, another about launchd — and none of the three mentions the others. They&amp;rsquo;re content islands that could be connected. The obvious solution is to reread every post, remember which others exist, and manually insert links. With 30 posts, it&amp;rsquo;s doable. With 400, it&amp;rsquo;s insane.&lt;/p&gt;</description></item></channel></rss>