I’ve thought more about this. It would be really handy to render content outside of the current content pane using the plugin API. The limited frame the plugin API works within prevents us from extending the dashboard and implementing more advanced functionality like a visual composer / live editor.
Providing a new section that we could render an iframe within outside of the content region might be a possible solution which you could do with some minor additions to the SDK.
Main Menu Pane (Plugin Method)
Providing a method via the SDK that could trigger a toggle on the pane. As of now this is handled manually both hovering and clicking the chevron (<).
Main Content Pane (Plugin Method)
The main content pane which contains the model fields, modular content etc is positioned in the center by default. If the SDK could provide a method to set positioning of this pane (left / right).
New Content Pane
The new content pane would need to be appropriately rendered according to position set by the Main content pane (above). Some additional methods provided for this could include a “Jump To” option to switch between models.
Referencing Data (live site preview)
Depending on the projects type this can be handled many different ways. For a global approach where all static site generators could be supported you could employ attribute references on elements contained within the DOM that represent editable data. If a site is using Github you could hook into the Github API and reference code in a particular branch which the live editor could inject. Developers would need to figure it out in most cases.
- User activates new content pane via button
- Main menu pane is toggled (hidden)
- Main content pane position is se, eg: left
- New content pane is rendered
I was able to generate this by adjusting a few elements via inspector and of course it takes more than that to provide such a feature but given how well the admin architected injecting a pane was very simple. Some food for thought.