Improve kick-the-tires experience

[apetro]

One reasonable thing to do is

1. clone the repo
2. skim to the part of the readme where you get to try something
3. npm run static:dev

Do this, and you get chastised about not having permission to see stuff or something.

Replace with positive, friendly, welcoming initial render experience.

[apetro]

Turns out in app-config.js the thing to do is set

`widgetApi': { 
   'entry': 'staticFeeds/', 

[ChristianMurphy]

should

`widgetApi': { 
   'entry': 'staticFeeds/', 

be set at the default?

[apetro]

It's a nuanced problem.

Naively setting not-appropriate-for-production defaults creates opportunities for applications using the framework to overlook the need to override those not-appropriate-for-production-defaults and ship something to production configured to use goofy stub data. (This has actually happened in MyUW.)

This is not to say that this cannot be navigated carefully and thoughtfully, to both provide good kick-the-tires experiences and good developing-using-the-framework-for-real experiences. It is to say there are potholes and trip hazards in neighborhood of this feature.

[apetro]

#821 would improve the README slightly to help people realize the opportunity to configure for a better demo.