Feature: Add fallback routing for localized p5.sound reference pages (currently doesn’t exist)

[mikhailbond1]

Increasing Access

This feature improves access by preventing dead-end pages for non-English users. Instead of seeing a “page does not exist” message, users can still view the English documentation with a clear notice, making important resources like the p5.sound reference easier to find and use regardless of language.

Most appropriate sub-area of p5.js?

Reference

Feature request details

Feature: Fallback to English for localized p5.sound reference pages

Summary

The p5.sound reference only exists in English. When visiting localized routes like:

• https://p5js.org/es/reference/p5.sound/
• https://p5js.org/ko/reference/p5.sound/
• ... all languages other non english languages

the site shows a “page does not exist” message instead of displaying the English content.

---

Current behaviour

• Localized p5.sound routes show a “does not exist” page
• The English content is not shown

---

Expected behaviour

• Render the English version of the page
• Show a notice like:

This page is not available in [language]. Showing the English version.

---

Why this helps

• Prevents dead-end pages
• Makes existing content accessible from localized routes
• Clearly communicates missing translations

[mikhailbond1]

I’d like to work on this if it’s okay

[ksen0]

Hi @mikhailbond1 thank you for finding and reporting this! The issue makes sense and you're welcome to work on it. However instead of the proposed, could you please default to English without "This page is not available in [language]. Showing the English version.". That is the policy across the site, to fallback to English when no translation exists.

I've noticed the en fallback works for individual pages https://p5js.org/ko/reference/p5.PeakDetect/isDetected/ but not for the sound reference landing ad you wrote. So maybe there is something there to investigate.

[mikhailbond1]

Thanks! That makes sense.

I’ll look into why the fallback works for individual reference pages but not for the p5.sound reference landing page, and try to make it consistent with the existing behaviour.