Progressively Enhanced Capabilities content

[thescientist13]

In #57 , the capabilities content on the home page is managed via JavaScript, with the content being embedded / hidden on the page and changed via JavaScript/

<div class="capabilities-content item1">
  <span>Hybrid Routing</span>
  <i>html.svg</i>
  <p>Greenwood is HTML first by design.  Start from just an <em>index.html</em> file or leverage <strong>hybrid, file-system based routing</strong> to easily achieve static and dynamic pages side-by-side.  Single Page Applications (SPA) also supported.</p>

```shell
src/
  pages/
    api/
      search.js       # API route
    index.html        # Static (SSG)
    products.js       # Dynamic (SSR), or emit as static with pre-rendering
    about.md          # markdown also supported
```

</div>

Not sure how to do it, but would be great if there was a way to progressively enhance and still make this work without JavaScript. (might mean having a purely static fallback with everything displayed at once 🤔 )

[thescientist13]

Now with HTML Web Components coming to WCC, this might be more viable, see ProjectEvergreen/wcc#155