Improve URL handling for special characters in database and view names

Ideas & Features
1

I’d like to provide feedback about how Fibery currently handles special characters in URLs, particularly for database names and views.

Current behavior: When creating a database with accented characters or special characters, the URL encodes these characters rather than converting them to ASCII equivalents. For example:

Database name: “Protocolo de Saúde” Results in URL: space/Sa%C3%BAde_Familiar/database/Protocolo_de_Sa%C3%BAde

Expected behavior: A more user-friendly approach would be to automatically “slugify” these URLs by converting special characters to their non-accented equivalents:

Database name: “Protocolo de Saúde” Preferred URL: space/saude_familiar/database/protocolo_de_saude

Why this matters:

  1. Current URLs are difficult to read, share, and manually type
  2. URL-encoded characters make links less professional when shared externally
  3. For users working in languages with many special characters (Portuguese, Spanish, French, etc.), this creates consistently poor URL experiences
  4. Implementing automations, scripts, formulas, using Fibery Module on Make and so on are Case Sensitive, that’s one more issue allowing URLs being messy.

Suggested solutions:

  1. Implement automatic transliteration of special characters in URLs (ú → u, ã → a, etc.)
  2. Add an optional field when creating databases to specify a custom URL slug
  3. Include URL preview when naming items to help users understand how URLs will appear
  4. Or, use IDs for everything, spaces, databases and views…that could solve everything. If I rename a database, I would have no issue later or break scripts/automations.

This change would significantly improve the user experience for international users while maintaining all functionality.

2 Likes