Document new API and deprecate old

[alanshaw]

In #591 we switched to a new simplier API with new packages. Due to time constraints we didn't document the new packages or deprecate the old packages yet (they still work but with older versions of w3up).

cc @travis

[Honour-d-dev]

 ⨯ node_modules\@w3ui\react\build\esm\index.js (17:7) @ commonjsRequire
 ⨯ unhandledRejection: Error: Could not dynamically require "url". Please configure the dynamicRequireTargets or/and ignoreDynamicRequires option of @rollup/plugin-commonjs appropriately for this require call to work.
    at commonjsRequire (webpack-internal:///(ssr)/./node_modules/@w3ui/react/build/esm/index.js:40:11)
    at __wbg_init (webpack-internal:///(ssr)/./node_modules/@w3ui/react/build/esm/index.js:18202:124)
    at eval (webpack-internal:///(ssr)/./node_modules/@w3ui/react/build/esm/index.js:18236:21)
    at eval (webpack-internal:///(ssr)/./node_modules/@w3ui/react/build/esm/index.js:47:9)
    at eval (webpack-internal:///(ssr)/./node_modules/@w3ui/react/build/esm/index.js:48:7)
    at eval (webpack-internal:///(ssr)/./node_modules/@w3ui/react/build/esm/index.js:29511:3)

code runs fine on the browser without errors after @rollup config but still throws on terminal and during build. this is with the new w3ui api

[Honour-d-dev]

its also possible i didn't do the rollup configuration right, so perhaps an example on that would be appreciated
my config

import commonjs from "@rollup/plugin-commonjs";

export default {
  input: "src/index.js",
  output: {
    dir: "output",
    format: "cjs",
  },
  plugins: [
    commonjs({
      dynamicRequireTargets: ["node_modules/@w3ui/*.js"],
      ignoreDynamicRequires: true,
      strictRequires: true,
    }),
  ],
};

[Winter-Soren]

Hey @alanshaw, I’d love to work on this issue and improve the documentation, can you assign this to me.

[travis]

Hi @Winter-Soren I'm glad to hear you're excited about this! Unfortunately I believe the documentation updates this PR imagined are mostly done - we do have barebones docs in place for the "newer" w3ui modules. I think the packages this issue refers to still need to be deprecated, but I think that's something I'm going to need to do with admin privileges on our NPM account.

If you're interested in working on the docs I do think they could use a refresh, but I'd like to coordinate that with our developer relations lead @jamiechicago312 - we're in the middle of some structural changes to this repo and will likely rename the package one more time and I'd like to make sure we don't throw away work you do on this.

Could you give me a sense of what you're excited to work on in this vein? Please feel free to create another issue describing documentation improvements you'd like to make and I can get it assigned and sorted in our tracking system.