🌐 Website Issue | Breadcrumbs don't respect capitalization of acronyms #1551
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1551
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
https://www.privacytools.io/providers/dns/: DNS -> Dns
https://www.privacytools.io/providers/vpn/ VPN -> Vpn
I had difficulties understanding this issue, but apparently the problem is in navigation.
The reason for this is the breadcrumbs code takes the names from the permalink rather than the page title, and uses capitalize to make it look better. This makes sense for some pages, for example https://ipv6.privacytools.io/providers/email/ shows the breadcrumbs as "Home > Providers > Email", and not "Home > Providers > Best Secure Email Providers for Privacy" (which IMO is not useful navigation or SEO-wise), but obviously doesn't work well for others.
We could have a breadcrumb attribute in the YAML front matter for each page to solve cases where the breadcrumbs would have conflicting titles like that, instead of trying to figure them out automatically based on the permalink. I'd imagine that's the best solution here.