Monorepo Cleanup

[bmuenzenmeyer]

Successor to #803

• update contribution guidelines

For each converted repo:

• update readme to point to https://github.com/pattern-lab/patternlab-node
• archive
  • cli
  • core
  • edition-node-gulp INTENT TO ARCHIVE edition-node-gulp#124
  • edition-node INTENT TO ARCHIVE edition-node#6
  • engine-handlebars INTENT TO ARCHIVE patternengine-node-handlebars#13
  • engine-liquid INTENT TO ARCHIVE patternengine-node-liquid#1
  • engine-mustache INTENT TO ARCHIVE patternengine-node-mustache#16
  • engine-react INTENT TO ARCHIVE patternengine-node-react#6
  • engine-twig INTENT TO ARCHIVE patternengine-node-twig#4
  • engine-underscore INTENT TO ARCHIVE patternengine-node-underscore#4
  • live-server INTENT TO ARCHIVE live-server#1
  • plugin-tab INTENT TO ARCHIVE plugin-node-tab#25
  • uikit-workshop

The bulk of Pattern Lab links will be within core/README

• fix links

  • cli
  • core
  • edition-node-gulp
  • edition-node
  • engine-handlebars
  • engine-liquid
  • engine-mustache
  • engine-react
  • engine-twig
  • engine-underscore
  • live-server
  • plugin-tab
  • uikit-workshop

• hoist devDependencies like prettier

• Fix links within wiki

• Fix links within patternlab.io

• Fix core documentation generation (if needed)

• update https://github.com/bmuenzenmeyer/patternlab-node-3.0-demo-vanilla

• update https://github.com/bmuenzenmeyer/patternlab-node-3.0-demo-integration

[raphaelokon]

Also fix refrences to styleguidekit and assets to point to uikit-workshop in the default config.

[bmuenzenmeyer]

The remaining work on this issue will not be done until #813 is complete

[bmuenzenmeyer]

@raphaelokon I've largely stayed hands-off with the CLI, but are you okay with me getting it into a more-standard configuration with the rest of the monorepo?

Things like fixing links, removing duplicate files, etc

[raphaelokon]

@bmuenzenmeyer Fine by me.

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[stale]

Issue closed after going stale. It can be re-opened if still relevant.