joeyjoejoejr
commented
9 years ago We may not end up going with this, but I'm putting it in the 1.0.0 milestone so we can decide. I see Cardboard as it is having the following structure that would lend itself to a suite of plugins.
Admin Panel (really simple but the base)
- CMS (Could/should be a separate plugin many projects don't need a cms)
- Resource Generators (I think we probably need a solutions that is automatic(like Rails Admin) as well as one that is more like what we have here, this could get complicated and probably should be made into one or more
- Potentially a default pack of third-party plugins (select2 bootstrap etc) should be added as a pugin so people have the option to opt-out
Let's begin a discussion of an architecture that will work best for splitting cardboard into plugins:
The end goal here, is to keep cardboard core minimal and split out cms, resource-generators, possibly a suite of third-party plugins (datepickers, select2, etc). This would also allow for more projects to contribute back when they have different, but generalizable needs (ie e-commerce dashboard, tabbed pages, actual dashboard widgets, an api).