<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Slugify on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/slugify/</link>
    <description>Recent content in Slugify on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/slugify/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>python-slugify vs slugify vs limax in 2026: Which Slug Library Won&#39;t Break Your URLs?</title>
      <link>https://www.pistack.xyz/posts/2026-09-25-slugify-libraries-python-slugify-simov-slugify-limax-comparison/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-25-slugify-libraries-python-slugify-simov-slugify-limax-comparison/</guid>
      <description>&lt;p&gt;A slug library looks like the least risky dependency in your stack. It takes a title, returns a hyphenated string, and you forget about it. Then one day you upgrade it, or you enable the &amp;ldquo;modern algorithm&amp;rdquo; flag, or a user posts a title in Japanese — and every URL in your sitemap changes at once. Search engines see a site-wide 404, your analytics drop off a cliff, and the root cause is a one-line configuration default you never read.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
