Don’t see anything wrong with their folder structure or naming!
I hope that helps
When you’re ready, you can use this submission form to share it for potential inclusion in the Vercel Templates Marketplace: Vercel Template Submission Form
Thanks @amyegan , that is really helpful feedback.
The redirect issue is something I struggled with.
In Headlesshost “staging content sites” are transient and users can create multiple versions to suit their needs. These multiple versions of content are rendered by a single staging website (Next.js). The website knows what version of content to render as the version instance id is passed in the url.
So I’m putting the instance id in the route to hold state, which is not ideal. When rendering production content it just uses “knowledgebase” as a placeholder.
I could use query strings but I would need to add them to every navigation link. The route links are relative so they just work.
If you have any suggestions on better ways to handle this I would really appreciate the feedback.