Scorpius : An admin solution built on top of Nuxt.
[issue link]Overview
Transitioning to Nuxt.js from Meteor.js I must say that Nuxt is an amazing framework and I come to appreciate it everyday. With that said , I have a great deal of Meteor.js developers that have followed Scorpius since it’s fork from the previous admin framework Orion. If succesful , Scorpius could potentialy bring other great devs from the Meteor community into the Vue/Nuxt ecosystem.
I have a few preliminary questions that I need to sort out before this dream can become a reality.
-
What is the best way to contribute fragments of a Nuxt application via an npm package?
For instance is there a config option to set, that would allow a user to merge two directories.
EX: All code for the admin solution would live under a directory called scorpius or admin. Scorpius Core will contain all components , logic, and pages relative to the admin panel.
Behavior : Consumer should have the ability to install the package set or define settings either via a Vue Plugin , and/or Nuxt config, then consume the service in their pages directory. This may be better with a Vue Plugin, that accepts options, but then I would need to know what can be passed to the Package and sent back to the Nuxt runtime. Potentially introducemergeDirectoryconfig setting that would merge two directories together such as a directory in the consumers project and the directory in the Scorpius package. -
Would 1. be better if everything is maintained as a Vue plugin , and Vue components, so
<scorpius></scorpius>component would include the entire admin logic with other components such as<scorpius-auth></scorpius-auth>and<scorpius-collection></scorpius-collection>and many others managing the business logic for the admin solution.
As i’m still learning the internals of Nuxt, and researching the best solution to make a distributed approach to extending a consumers Nuxt application. I would like any advice or pointers that could get me going in the right direction.
Thank you,
Ryan.
P.s. this post is not a bug or issue it is only meant to open a dialog with Nuxt devs to get better insights on what is currently possible and what contributions could be made to make other features possible.