feat: Show Scenario Config about angular-playground

[isaacplmann]

We could potentially hide this behavior behind a flag somewhere, if you don't want it to be the default behavior.

[jschwarty]

Sorry I haven't got back to you on this yet. I need to make some time to digest this one. Will try and do that this evening. :)

[isaacplmann]

Here are some pictures, so you can see what I'm talking about:

Collapsed:

Expanded:

Breaking up the config into multiple <details> sections:

The main goal of this feature is that other developers can easily see - if I put in these inputs, the component will look like this.

[jschwarty]

What we'd like to do is keep the Playground app as lean as possible in it's default state. We explained our approach to the Playground in this thread to try and explain how we use the tool in our workflow and to define how we want to approach it's usage and it's growth going forward.

Since then we have added the embed and deep link ability to provide a way to leverage content from Playground in a separate "documentation/discovery" type app. We have thought about potentially exposing the "sandboxOf/scenario" data (like you show in the screenshots) through a url like the embed concept.

But thinking about things a bit further based on the request you made here...we are thinking that a plugin architecture might be the best approach. Provide a way for people to run their own plugins within Playground. That way the base install can be the tool we need for our workflow, but can be extended to meet the needs of others who want to use it for other purposes.

I created a feature issue for more discussion on a plugin system. #19