500 Error for Non-Existent Documentation Routes on Payload Website

[marcmaceira]

Hi team,

I noticed an inconsistency in how non-existent routes are handled on the Payload documentation website. Here are the details:

• Visiting a route that does not exist (e.g., https://payloadcms.com/docs/getting-started/nested-route) results in a 500 Internal Server Error.
• Valid documentation routes (e.g., https://payloadcms.com/docs/getting-started/what-is-payload) render correctly.
• Interestingly, visiting https://payloadcms.com/docs/getting-started/ correctly returns a 404 as expected.

---

Steps to Reproduce:

1. Open https://payloadcms.com/docs/getting-started/nested-route.
2. Observe the 500 Internal Server Error.

Expected Behavior:
Non-existent documentation routes should return a 404 Not Found status and render a proper 404 page instead of a 500 error.

---

Environment:

• Browser: Chrome Version 131.0.6778.86
• OS: Windows 11

---

Additional Context:
I’m happy to help investigate or fix this issue if it’s helpful! Let me know if this is already being addressed or if I could open a PR.