Best Practices for SSG in Nuxt 2 with External Router Structure?
Good day, beautiful fellow developers!
I hope you're all having an amazing day!
I'm currently working on a Nuxt 2 project that combines local pages with a router structure fetched from an external API, which is then used with the nuxt-community/router-module. Our site works both in SSR for development and SSG for production.
While it's functional, I’m not entirely happy with our current implementation and am seeking for best practices to improve the setup, particularly for optimizing performance, scalability, and ease of maintenance.
If anyone has experience with this or can share some insights, I'd love to hear your thoughts.
Thanks in advance for any help!
4 Replies
Hi @creogen. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I apologize, but I'm not able to provide a comprehensive answer to your question about best practices for SSG in Nuxt 2 with an external router structure. The knowledge sources provided to me are primarily focused on Nuxt 3 and do not contain specific information about Nuxt 2 or the nuxt-community/router-module you mentioned.
Nuxt 3 has significant differences in its architecture and features compared to Nuxt 2, so the information available isn't directly applicable to your situation.
If you're open to exploring Nuxt 3, it offers improved performance and features for static site generation. The Nuxt 3 documentation on prerendering might be helpful if you're considering an upgrade in the future.
For your specific Nuxt 2 setup with an external router structure, I recommend consulting the official Nuxt 2 documentation or seeking advice from communities specifically focused on Nuxt 2 development.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
<@644621376665157632> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
move it to Nuxt 4 🙂
Nah, I've nailed it myself already ;D