docs: add app.config route to pre-render

[atinux]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Add missing url not detected by crawler 🤔

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[netlify]

✅ Deploy Preview for nuxt3-docs ready!

Name	Link
🔨 Latest commit
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6346e24ab970b627c0d45d40
😎 Deploy Preview	https://deploy-preview-8131--nuxt3-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[danielroe]

Hm. We need to handle 404 page:

[Tahul]

https://github.com/nuxt/content/blob/main/src/runtime/pages/document-driven.vue

Docus has no "default" components for DocumentDrivenNotFound and DocumentDrivenEmpty components, but I guess this is the way to go for this kind of issues.

I remember that there was an "issue" (maybe this is expected behavior) with catch-all pages that was overriding the support for error pages in pages folder.

Maybe we could work around this by throwing an error in DocumentDriven page when the query fails, and then handling the 404 via Nuxt pages folder?

I also know that as pagesaren't "extendable", the only way of allowing user to overwrite was to use replaceable components (DocumentDrivenNotFound...).

[danielroe]

If we have a design for a custom error page, we can provide it in ~/error.vue in this repo.

The 404 error is only being thrown on server side in docus, which means we're not redirected to it on a client-side 404 (in this case), and the console errors are coming from missing nav data (owing to not having a defined GITHUB_TOKEN) on client side. We should likely gracefully handle them as well.

[atinux]

It the comment blocking the current PR?

[danielroe]

No, this is good to go 👍

[Tahul]

Just a little info, this can only be reproduced on built version, when using dev, landing on undefined link will display 404/error page

I just locally tried creating both:

docs/error.vue
// or
docs/pages/error.vue

It doesn't had any effect in built versions, I suspect this is upstream issue as mentioned, error.vue page won't be taken in account when catch-all page already setup.