just some questions about functionality..

this is a forever later question, skipped all the other stuff because... TL;DR...
i just want to cut tothe chase before spending 20 hours deep diving the docs.

TL;DR version>>

Simple question:
how can i have a conversation with someone who knows a fair bit about this grid system's features and functions?

long version:

i'm wondering 4 things.

1. - can each grid item be a different widget calling different api's with their own auth, IE: grid item 1 uses oauth2.0, and needs 2factor authentication, and receives a refresh token which the grid widget can send and store in a user database, grid item 2 is simply basic auth user/pass, and that gets saved along with grid item properties as well. (grid items foreach, holds props for min/max size, widget components like lists, file uploads, messengers, an e-mail inbox., etc.. all in a container) ie: can each container contain pretty much a functional app with it's own auth and api calls and components, in a way that doesn't interfere with any other container, and yet all containers can be pushed a common theme?

2. Can a multitenant app exist where each user has their own grid configuration stating the widgets/grid items in use by that user and the layoout that they created by dragging and dropping, adding/removing different widgets, and store the grid item choices and positions in a database inside their profile?

3. Can the grid items themselves be containers that are skinnable, theme-able... with a theme switcher like semantic-ui to alter the overall look of the app, the frames containing the widgets, and pass the theme information to the components inside the containers making up the widgets?

4. is there the option for min/max sizes on grid items, as well as max items on a grid, and can you have say, 2 grids on separate tabs, and drag and drop a grid item off the grid and onto a tab to have it moved to a different grid, and still have the above three queries of mine functional.

No files, tests, or entry points are named. Start by reviewing the Packery documentation and the existing issue context to map the questions about independent widget authentication, per-user layouts, theming, size limits, and moving items between grids to supported functionality. Done would require a clear response identifying what is supported or what would need separate feature work.

Written by the indexing model from the issue text.