✨ URL Slug - Replace URI terminology with user-friendly wording across TinaCMS

Requested by: @tiagov8 via YakShaver.ai 🦬
cc: @wicksipedia, @tiagov8, @adamcogan, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 51 sec)

  Url from screen share: https://github.com/SSWConsulting/SSW.Rules.Content/pull/12321

Pain

Update TinaCMS UI text, Copilot-generated descriptions, and related rules to use the industry-standard term "URL slug" instead of "URI". This improves clarity for non-technical users and aligns terminology with common platforms such as WordPress and TinaCMS conventions. The change should be applied consistently across all existing rules and documentation, and supported by a new rule explaining correct terminology usage.

Acceptance Criteria

• 1. TinaCMS - All user-facing references to "URI" in TinaCMS UI and Copilot-generated descriptions are replaced with "URL slug" or "slug" where appropriate.
• 2. Rules.Content - Existing rules that reference "URI" are updated to use the new terminology consistently.
• 3. Rules.Content - A new rule exists that explains the correct use of terms (URI vs URL vs slug), including examples (e.g. URI can include mailto links).
• 4. Rules.Content - The new terminology rule links bidirectionally with the existing rule about keeping URLs short and readable.
• 5. Rules.Content - The terminology rule includes an explanation that "slug" is the industry-standard term, with examples referencing WordPress and ⭐ TinaCMS.
• 6. Rules.Content - A screenshot demonstrating the updated terminology in TinaCMS is included in the rule.

Screenshot

Figure: Label uses URI instead of URL/slug, causing unclear terminology

Search the repository for user-facing and Copilot-generated occurrences of “URI”, beginning with the TinaCMS UI and related Rules.Content entries. Replace the terminology with “URL slug” or “slug” where appropriate, then verify that no relevant user-facing references remain and that the terminology matches the completed Rules.Content examples.