[Idea] Also include third-party add-ons in the demo

[tabacitu]

How do we feel about adding examples of the tested & approved add-ons to the main Backpack demo? @pxpm how do you feel about this - do you think it'd be a good idea or would it over-complicate our lives?

For example:

• adding the the signature field to the Miscellaneous tab in MonstersCRUD;
• adding the the toggle field to the Simple tab in MonstersCRUD;

Code example:

            [
                'name' => 'signature',
                'label' => 'Signature <a href="https://github.com/iMokhles/signature-field-for-backpack" target="_blank"><span class="badge badge-info">Add-on <i class="la la-external-link-alt"></i></span></a>',
                'type' => 'signature',
                'view_namespace' => 'signature-field-for-backpack::fields',
                'fake' => true,
                'tab'  => 'Miscellaneous',
            ],

PROs:

• this would actually show people that those things are possible with Backpack, easily;
• the demo would also function as a reference for what's possible, and links to the add-ons;
• it would help third-party developers, because they don't have to create and host a demo, the main Backpack demo will show the add-on if it's tested and approved;
• we'd make sure that add-ons don't conflict with other features;

CONs:

• it will be more difficult to maintain, since whenever we want to push breaking changes those developers have to be notified and helped to implement the breaking changes; then again, this only happens once/twice a year, the changes are usually small and we'd need for them to add support for the new version anyway;

Overall it sounds to me like there are a lot more benefits than downsides 😄 @pxpm ?

[karandatwani92]

If Yes, we can start with the Import Operation
https://github.com/redsquirrelstudio/laravel-backpack-import-operation