Define scope of UI template about substrate-front-end-template

[shawntabrizi]

So far I've thought of it as 1 and 3 but not 2.

This is correct to me.

I think more than that, it could be a general set of examples using the Polkadot JS API.

The principals to me are:

1. Completely modular design. Every component should be able to be removed or added. Users should be able to paste their "jsx" component into repos or chats, and all you need to do is copy and paste it into this template to work.

2. Dead, stupid, simple. The components in the UI should favor simplicity in how they are designed and implemented. In some cases, this may not reflect "ultimate production level code". For example, two component may query the same API on their own in order to ensure they remain modular.

3. It never breaks no matter the Substrate UI it is hooked up to. See #14

What you wrote seems fine, although I think generally anyone can put any component they want into the assuming they follow item 3.

I was, for example, thinking of embedding our first tutorial demo component in here, such that if you have a POE module, the component would pop up. Otherwise, it would hide itself from the user.