Some nice features coming in the Skuid Summer 14 release relevant to this are the ability to set, globally for an org, which Skuid Page Components are available in the Page Composer, via a feature called “Component Packs”. So you could, in effect, do any of the following:
- hide all the standard Skuid components - just show specific components you’d like (i.e. just Table and Field Editor, or just Calendar and three custom components you’ve made, etc.) - categorize components into Folders / Groups
This is managed via a new Custom Setting. So you could ship a stripped-down Component Pack with your app. But if you want to add on / improve the feature set, you could reenable the Skuid Core Component Pack (or some other Component Pack that ships with your app), when you are assisting the customer.
2. I don’t see this being a problem, although using Page Assignments would be another alternative.
3.This is another area for potential improvement in the future, we have some ideas about letting you show a Notification in the Page Composer if there’s a “new version” of your managed page available for you to upgrade to — which would proactively encourage your users to get back on board with your standard offering. Just ideas right now…
