Feature Request: Establish Official Best Practices for Custom Component Development

[nastoychev]

Hi everyone,

I’ve been exploring the official Nova Frontend Customization Docs and noticed that while the page provides useful information on frontend customization, it doesn’t yet include guidance on some key areas that are important for the modern Vue ecosystem, such as:

1. State Management: With Vue.js moving away from Vuex in favor of Pinia (as the official state management solution for Vue 3), it would be great to see Pinia included as the recommended state management tool for custom Nova components. This would ensure better alignment with current Vue.js best practices, especially in projects using Vue 3.

2. Asset Compilation: The documentation currently mentions Laravel Mix for asset compilation, but considering that Vite has emerged as the preferred bundler due to its speed, modern features, and better support for Vue 3, it would be beneficial for the Nova documentation to officially recommend Vite as the default tool for asset management in custom Nova components.

I believe incorporating these changes would not only help developers stay up to date with modern tools but also ensure that their Nova components are built in a way that’s more scalable and maintainable, with smoother upgrade paths during major Nova releases.

What do you think? Would it be possible to update the documentation to include these modern best practices?
Thanks for your time!