WIP proof of concept for separate data guides

[jenweber]

This PR should not be merged.

If we wanted to pursue this strategy, we would make a new repo or add it to the ember data mono repo.

See the link in CI checks below for a demo URL.

Things that would have to happen for this to ship:

• Handle older versions
• Tests
• subdomain
• redirects/SEO. How do we handle the big hole this would leave in the ember guides? Maybe all pages point to a page that says "go here for the latest" and we call that good enough?
• use a production version of ember-styleguide
• readme, site meta, etc.

challenges

• If I put this into the data mono repo, I get warnings that dependencies are not installed. What to do?

Blockers

• the new styling work needs to ship before this

[jenweber]

Steps to run:

• check out this branch
• npm install
• npm start

Problems? Check your node version

Notes to self about monorepo debugging

[Baltazore]

hey @jenweber and learning team, is there any new thoughts about this PR? EmberData docs in general? What would be preferred approach for EmberData docs? Separate repo ? Part of general Ember Guides ? Please let me know. I want to start working on updates to latest EmberData APIs.
Thanks