diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
deleted file mode 100644
index 90ed23df3..000000000
--- a/.github/CONTRIBUTING.md
+++ /dev/null
@@ -1,279 +0,0 @@
-# Contributing
-
-## Welcome!
-We're excited for your interest in Greenwood, and maybe even your contribution!
-
-> _We encourage all contributors to first read about the project's vision and motivation's on the website's [About page](https://www.greenwoodjs.io/about/).  Greenwood is opinionated in the sense that it is designed to support development for the modern web platform and aims to deliver a first class developer experience tailored for that expectation.  So if that page is the "why", this page is the "how"._
-
-## Setup
-
-To develop for the project, you'll want to follow these steps:
-
-1. Have [NodeJS LTS](https://nodejs.org) installed and [Yarn](https://yarnpkg.com/)
-1. Clone the repository
-1. Run `yarn install`
-
-If developing with Node Version Manager:
-
-- Windows: [NVM for Windows](https://github.com/coreybutler/nvm-windows/releases)
-- Linux/MacOS: [Node Version Manager](https://github.com/nvm-sh/nvm)
-
-You can confirm by running the following
-
-```sh
-$ nvm use
-Found '/Users/<directory_location>/greenwood/.nvmrc' with version <14.17.0>
-Now using node v14.17.0 (npm v6.14.13)
-```
-
-## Technical Design Overview
-
-The Greenwood GitHub repository is a combination [Yarn workspace](https://classic.yarnpkg.com/en/docs/workspaces/) and [Lerna monorepo](https://github.com/lerna/lerna).  The root level _package.json_ defines the workspaces and shared tooling used throughout the project, like for linting, testing, etc.
-
-The two main directories are:
-- [_packages/_](https://github.com/ProjectEvergreen/greenwood/tree/master/packages) - Packages published to NPM under the `@greenwood/` scope
-- [_www/_](https://github.com/ProjectEvergreen/greenwood/tree/master/www) - [website](https://www.greenwoodjs.io) / documentation code
-
-
-> _This guide is mainly intended to walk through the **cli** package; it being the principal package within the project supporting all other packages._
-
-### CLI
-
-The CLI is the main entry point for Greenwood, similar to how the [front-controller pattern](https://en.wikipedia.org/wiki/Front_controller) works.  When users run a command like `greenwood build`, they are effectively invoking the file _src/index.js_ within the `@greenwood/cli` package.
-
-At a high level, this is how a command goes through the CLI:
-1. Each documented command a user can run maps to a script in the _commands/_ directory.
-1. Each command can invoke any number of lifecycles from the _lifecycles/_ directory.
-1. Lifecycles capture specific steps needed to build a site, serve it, generate a content dependency graph, etc.
-
-
-#### Layout
-The [layout](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/cli/src) of the CLI package is as follows:
-
-- _index.js_ - Front controller
-- _commands/_ - map to runnable userland commands
-- _config/_ - Tooling configuration that Greenwood creates
-- _data/_ - Custom GraphQL server and client side utilities
-- _lib/_ - Custom utility and client facing files
-- _lifecycles/_ - Tasks that can be composed by commands to support the full needs of that command
-- _plugins/_ - Custom default plugins maintained by the CLI project
-- _layouts/_ - Default layouts and / or pages provided by Greenwood.
-
-
-#### Lifecycles
-Aside from the config and graph lifecycles, all lifecycles (and config files and plugins) typically expect a compilation object to be passed in.
-
-Lifeycles include handling:
-- starting a production or development server for a compilation
-- optimizing a compilation for production
-- prerendering a compilation for production
-- fetching external (content) data sources
-
-## Project Management
-
-We take advantage of quite a few features on GitHub to assist in tracking issues, bugs, ideas and more for the project.  We feel that being organized not only helps the team in planning out priorities and ownership, it's also a great way to add visibility and transparency to those following the project.
-
-### Project Boards
-
-Our [sequentially named project boards](https://github.com/ProjectEvergreen/greenwood/projects) help us organize work into quarterly buckets that will generally include a small handful of "top line" goals and objectives we would like to focus on for that particular time box.  It also serves as a catch-all for the usual work and bug fixes that happens throughout general maintenance of the project.  Additionally, we leverage this as a means to shine insight into good opportunities for those interested in contributing as what the Greenwood team would appreciate help with the most.
-
-### Discussions
-
-We believe good collaboration starts with good communication.  As with most of the open source community, Greenwood is a 100% volunteer project and so we understand the importance of respecting everyone's [time and expectations](https://www.jason.af/setting-expectations) when it comes to contributing and investing in a project.  Although we don't mind issues being made, unless the issue is clearly actionable and falls in-line with the motivations and trajectory of the project, then feel free to go ahead an open a [Discussion](https://github.com/ProjectEvergreen/greenwood/discussions) first.
-
-We encourage discussions as we believe it is better to hash out technical discussions and proposals ahead of time since coding and reviewing PRs are very time consuming activities.  As maintainer's, we want to make sure everyone gets the time they are desire for contributing and this this workflow helps us plan our time in advance to best ensure a smooth flow of contributions through the project.
-
-> _Put another way, we like to think of this approach as **measure twice, cut once**._
-
-### Issues
-We like to reserve issues for features and requests that are more or less "shovel" ready with clear implementation details at hand.  This could include prior discussions with the team or action items coming out from an existing discussion.
-
-Our standard issue template requests some of the following information to be prepared (where applicable)
-1. High Level Overview
-1. Code Sample or API Design
-1. Links / references for more context
-
-For bugs, please provide steps to reproduce and expected vs actual behavior including screenshots.
-
-
-### Pull Requests
-Pull requests are the best!  To best help facilitate contributions to the project, here are some requests:
-- We generally prefer an issue be opened first, to help facilitate general discussion outside of the code review process itself and align on the ask and any expectations.  However, for typos in docs and minor "chore" like tasks a PR is usually sufficient.  When in doubt, open an issue.
-- For bugs, please consider reviewing the issue tracker first.
-- For branching, we generally follow the convention `<issue-label>/issue-<number>-<issue-title>`, e.g. _bug/issue-12-fixed-bug-with-yada-yada-yada_
-- To test the CI build scripts locally, run the `yarn` commands mentioned in the below section on CI.
-
-
-## Continuous Integration
-Greenwood makes active use of testing tools like [GitHub Actions](https://github.com/features/actions) and [Netlify deploy previews](https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/) as part of the workflow.  Each time a PR is opened, a sequence of build steps defined _.github/workflows/ci..yml_ are run:
-1. Linting: `yarn lint`
-1. Running unit tests: `yarn test`
-1. Building the Greenwood website:  `yarn build`
-
-A preview is also made available within the status checks section of the PR in GitHub and can be used to validate work in a live environment before having to merge.
-
-
-## Local Development
-To develop for the project, you'll want to follow these steps:
-1. Have [NodeJS LTS](https://nodejs.org) installed (>= 12.x) and [Yarn](https://yarnpkg.com/)
-1. Clone the repository
-1. Run `yarn install`
-1. Run `yarn lerna bootstrap`
-
-### NPM Scripts
-The [Greenwood website](https://www.greenwoodjs.io/) is currently built by Greenwood, and all files for it are located in this repository under the [_www/_ directory](https://github.com/ProjectEvergreen/greenwood/tree/master/www) workspace.  In addition to unit tests, you will want to verify any changes by running the website locally.
-
-Below are the development tasks available for working on this project:
-- `yarn develop` - Develop for the website locally using the dev server at `localhost:1984` in your browser.
-- `yarn build` - Builds the website for production.
-- `yarn serve` - Builds the website for production and runs it on a local webserver at `localhost:8000`
-
-### Packages
-As mentioned above, Greenwood is organized into packages as a monorepo, managed by [Lerna](https://lerna.js.org/) and [Yarn Workspaces](https://yarnpkg.com/lang/en/docs/workspaces/).  You can find all of these in the _packages/_ directory.  Each package will manage its own:
-- Dependencies
-- README
-- Test Cases
-
-Lerna (specifically `lerna publish`) will be used to release all packages under a single version.  Lerna configuration can be found in _lerna.json_.
-
-### Dependencies
-To `yarn add` / `yarn remove` packages from anything in _packages/_ or _www/_, please make sure you `cd` into the directory with the _package.json_ first.
-
-For example
-```shell
-$ cd packages/cli
-$ yarn add <package>
-```
-
-Yarn workspaces will automatically handle installing _node_modules_ in the appropriate directory.
-
-
-## Testing
-[TDD](https://en.wikipedia.org/wiki/Test-driven_development) is the recommended approach for developing for Greenwood and for the style of test writing we use [BDD style testing](https://en.wikipedia.org/wiki/Behavior-driven_development); "cases".  Cases are used to capture the various configurations and expected outputs of Greenwood when running its commands, in a way that mimics how a user would themselves be using Greenwood.
-
-### Running Tests
-To run tests in watch mode, use:
-```shell
-$ yarn test:tdd
-```
-
-To verify compliance with coverage and watermark thresholds (what CI server runs), use:
-```shell
-$ yarn test
-```
-
-Below are some tips to help with running / debugging tests:
-- `describe.only` / `it.only`: only runs this block
-- `xdescribe` / `xit`: don't run this block
-- Uncomment `runner.teardown()` in a case to see the build output without it getting cleaned up post test run
-- Use `new Runner(true)` get debug output from Greenwood when running tests
-
-> **PLEASE DO NOT COMMIT ANY OF THESE ABOVE CHANGES THOUGH**
-
-### Writing Tests
-Cases follow a convention starting with the command (e.g. `build`) and and the capability and features being tested, like configuration with a particular option (e.g. `port`):
-```shell
-<command>.<capability>.<feature>.spec.js
-```
-
-Examples:
-- _build.default.spec.js_ - Would test `greenwood build` with no config and no workspace.
-- _build.config.workspace-custom.spec.js_ - Would test `greenwood build` with a config that had a custom `workspace`
-- _build.config.workspace-dev-server-port.spec.js_ - Would test `greenwood build` with a config that had a custom `workspace` and `devServer.port` set.
-
-### Notes
-Here are some things to keep in mind while writing your tests, due to the asynchronous nature of Greenwood:
-- Make sure to wrap all calls to `TestBed` with `async`
-- All usages of `JSDOM` should be wrapped in `async`
-- Avoid arrow functions in mocha tests (e.g. `() => `) as this [can cause unexpected behaviors.](https://mochajs.org/#arrow-functions).  Just use `function` instead.
-
-## Supplemental Information
-
-Some additional information and context to help assist with developing for and contributing to Greenwood.
-
-### Internet Explorer / Windows
-For situations that require testing Internet Explorer or Edge browser, Microsoft provides [Virtual Machines](https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/) for various combinations of Windows and Internet Explorer versions.  [VirtualBox](https://www.virtualbox.org/) is a good platform to use for these VMs.
-
-To test from a VM, you can
-1. Run `yarn serve`
-1. From the VM, open `http://10.0.2.2:8000` in the browser
-
-You can disable plugins in _webpack.config.prod.js_ to remove production optimizations for testing purposes.
-
-### npx Testing
-[`npx`](https://www.npmjs.com/package/npx) is a useful CLI utility bundled with NodeJS that allows users to run npm packages globally but without having to install them.
-
-```sh
-% npx http-server
-Starting up http-server, serving ./public
-Available on:
-  http://127.0.0.1:8080
-  http://192.168.1.153:8080
-Hit CTRL-C to stop the server
-```
-
-It's featured on the Greenwood website [home page](https://www.greenwoodjs.io/) and in the [Quick Start guide](https://www.greenwoodjs.io/getting-started/quick-start/#command-line) as an option for using Greenwood.  There is a [spec for it](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/cli/test/cases/build.default.quick-start-npx) to try and simulate running it.
-
-You can use it for local development with Greenwood by using [npm link](https://docs.npmjs.com/cli/v7/commands/npm-link) to make `greenwood` available to your local CLI.
-```sh
-# From the root of the Greenwood repo
-$ npm link
-
-# then say in a test case folder
-$ cd packages/cli/test/cases/build.default.quick-start-npx
-$ npx greenwood
--------------------------------------------------------
-Welcome to Greenwood (v0.14.1) ♻️
--------------------------------------------------------
-Running Greenwood with the  command.
-
-          Error: not able to detect command. try using the --help flag if
-          you're encountering issues running Greenwood.  Visit our docs for more
-          info at https://www.greenwoodjs.io/docs/.
-```
-
-### Docker
-A Docker container is available within the project to use as a development environment if you like.  It is configured to use the same image that runs as part of the project's [Continuous Integration environment](https://github.com/ProjectEvergreen/greenwood/blob/master/.github/workflows/ci.yml#L9).
-
-First make sure you have [Docker installed](https://www.docker.com/products/docker-desktop).
-
-Then from the root of this repository do the following:
-1. Build the container: `$ docker build -t nodejs-dev .`
-1. Connect to the container: `$ docker run --name greenwood -v $(pwd):/workspace -i -t nodejs-dev`
-1. Now you can run all the usual commands, e.g.
-  - `$ yarn install`
-  - `$ yarn build`
-  - `$ yarn test`
-
-> _This will create a 2 way binding between your host and the container, so file changes will go both ways between the [host and container](https://gist.github.com/falvarez/71298b07603d32374ceb2845c3eec997)._
-
-When you're done with the container:
-1. Exit the container: `$ exit`
-1. Destroy the container: `$ docker rm greenwood`
-
-Note: If you have issues running tests due to timeouts, you can increase the setting in [package.json](https://github.com/ProjectEvergreen/greenwood/blob/master/package.json#L23)
-
-## Release Management
-
-Lerna is used to manage the publishing of packages within the workspace under a single unified version.  Assuming you are logged into **npm** locally and have 2FA access to publish, the following workflows should be used
-
-After running these commands, Lerna should then prompt you through the steps to pick the version and all packages that will get updated.
-
-### Alpha Release
-
-Greenwood typically works on new minor versions in a dedicated branch and release line called "alpha".  This leverages NPM's concept of dist tags.  While on a release branch, run the following to publish a new _alpha_ release.
-
-```sh
-# from the root of the repo
-$ yarn lerna publish --force-publish --dist-tag alpha
-```
-
-> Typically you will want to select the _Custom Preminor_ option from the list, which Lerna should appropriately yield the expected version.
-
-### Standard Release
-
-For a normal release (e.g. "latest") the following command can be run from the mainline branch of the repo.
-```sh
-# from the root of the repo
-$ yarn lerna publish --force-publish
-```
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 4c51b52e1..67aada496 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -1,12 +1,24 @@
+<!--
+# PLEASE READ FIRST
+If asking a question, looking for help, or you have an idea for Greenwood, please consider opening a discussion first or chatting with us in our Discord.
+-->
+
 ## Type of Change
-<!-- New Feature / Enhancement / Bug / Other -->
+
+<!-- Please select from one of the following options: -->
+<!-- Feature / Bug / Other -->
 
 ## Summary
-<!-- Brief summary of the issue like steps to reproduce for a bug, or motivation and API design if proposing a new feature. -->
+
+<!-- Brief summary of the issue like steps to reproduce for a bug, motivation, or API design -->
 
 ## Details
+
 <!-- 
 Include relevant code samples, example snippets, benefits, complexity, etc.  For feature requests, please make sure to provide an actionable outcome.  If you're unsure what qualifies, please consider starting a Discussion first, we can always transfer it later :).
 
-For bug reports, please include your configuration file and a sample of your workspace with the minimum amount of code needed to reproduce.  For alternative debugging approaches, you can use our test cases as a format to follow for reproducing bugs.
+This is a good post for helping to formulate a good set of details
+https://stackoverflow.com/help/how-to-ask
+
+For bug reports, please include your configuration file, a sample of your workspace with the minimum amount of code needed to reproduce and runtime.  A full repo is even better!
 -->
\ No newline at end of file
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index b7732a0df..6b7668902 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -4,9 +4,16 @@ We love contributions and appreciate any help you can offer!
 -->
 
 ## Related Issue
+
 <!-- Include a link to the issue (e.g. Resolves #12) -->
 
+## Documentation 
+
+<!-- if this issue has been labeled with documentation, please make sure submit a PR to our website repo and link it -->
+<!-- https://github.com/ProjectEvergreen/www.greenwoodjs.dev -->
+
 ## Summary of Changes
+
 <!-- Briefly summarize the changes made, lists are appreciated, ideally with checklists
 
 1. [x] Thing I fixed
diff --git a/.github/workflows/master.yml b/.github/workflows/master.yml
deleted file mode 100644
index e2183f8f0..000000000
--- a/.github/workflows/master.yml
+++ /dev/null
@@ -1,31 +0,0 @@
-name: Master Integration
-
-on:
-  push:
-    branches:
-      - master
-
-jobs:
-
-  build:
-    runs-on: ubuntu-20.04
-
-    strategy:
-      matrix:
-        node: [18]
-
-    steps:
-    - uses: actions/checkout@v1
-    - name: Install Chromium Library Dependencies
-      run: |
-        sh ./.github/workflows/chromium-lib-install.sh
-    - name: Use Node.js ${{ matrix.node }}
-      uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node }}
-    - name: Installing project dependencies
-      run: |
-        yarn install --frozen-lockfile && yarn lerna bootstrap
-    - name: Build
-      run: |
-        yarn clean && yarn build
\ No newline at end of file
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
deleted file mode 100644
index 2706eab8d..000000000
--- a/.github/workflows/release.yml
+++ /dev/null
@@ -1,37 +0,0 @@
-name: Release Branch Integration
-
-on:
-  push:
-    branches:
-      - release/**
-
-jobs:
-
-  build:
-    runs-on: ubuntu-20.04
-
-    strategy:
-      matrix:
-        node-version: [18]
-
-    steps:
-    - uses: actions/checkout@v1
-    - name: Install Chromium Library Dependencies
-      run: |
-        sh ./.github/workflows/chromium-lib-install.sh
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node-version }}
-    - name: Installing project dependencies
-      run: |
-        yarn install --frozen-lockfile && yarn lerna bootstrap
-    - name: Lint
-      run: |
-        yarn lint
-    - name: Test
-      run: |
-        yarn test
-    - name: Build
-      run: |
-        yarn clean && yarn build
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 000000000..0e2cd3cbc
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,269 @@
+# Contributing
+
+## Welcome!
+
+We're excited for your interest in Greenwood, and maybe even your contribution!
+
+> _We encourage all contributors to first read about the project's vision and motivation on our [website](https://www.greenwoodjs.dev/docs/introduction/)._
+
+## Setup
+
+To develop for the project, you'll want to follow these steps:
+
+1. Install [NodeJS LTS](https://nodejs.org) or [NVM](https://github.com/nvm-sh/nvm) (recommended)
+1. Have [Yarn](https://yarnpkg.com/) installed
+1. Clone the repository
+1. For NVM users, run `nvm use`
+1. Run `yarn install`
+1. Run `yarn lerna bootstrap`
+
+## Feature Development
+
+### Patch Package
+
+Generally we prefer to develop new features in the context of a project, working directly within _node_modules_ and validating the behavior or fix first hand.  Since Greenwood runs on plugins, just like any other user of Greenwood, a lot can often be achieved by just creating a custom plugin in a project's _greenwood.config.js_ file.
+
+If changes to _node_modules_ are needed, use [**patch-package**](https://www.npmjs.com/package/patch-package) to create a snapshot of those changes and provide that repo and patch along with your PR.
+
+### Testing
+
+#### Test Cases
+
+Greenwood relies on a large set of test suites that are very behavior based, in that we can scaffold out a full Greenwood project, including a _greenwood.config.js_ and run any of Greenwood's commands over the project files.  Combined with mocha for testing and [**gallinago**](https://github.com/thescientist13/gallinago) for running Greenwood commands, any combination of configuration, project structure, and Greenwood command can be tested for its output.  (in other words, we favor E2E / BDD testing, as opposed to unit testing).
+
+Here an example test case:
+
+```js
+import chai from 'chai';
+import { JSDOM } from 'jsdom';
+import path from 'path';
+import { runSmokeTest } from '../../../../../test/smoke-test.js';
+import { getSetupFiles, getOutputTeardownFiles } from '../../../../../test/utils.js';
+import { Runner } from 'gallinago';
+import { fileURLToPath, URL } from 'url';
+
+const expect = chai.expect;
+
+describe('Build Greenwood With: ', function() {
+  const LABEL = 'Default Greenwood Configuration and Workspace';
+  const cliPath = path.join(process.cwd(), 'packages/cli/src/index.js');
+  const outputPath = fileURLToPath(new URL('.', import.meta.url));
+  let runner;
+
+  before(function() {
+    this.context = {
+      publicDir: path.join(outputPath, 'public')
+    };
+    runner = new Runner();
+  });
+
+  describe(LABEL, function() {
+
+    before(function() {
+      runner.setup(outputPath, getSetupFiles(outputPath));
+      runner.runCommand(cliPath, 'build');
+    });
+
+    runSmokeTest(['public', 'index'], LABEL);
+
+    describe('Default output for index.html', function() {
+      let dom;
+
+      before(async function() {
+        dom = await JSDOM.fromFile(path.resolve(this.context.publicDir, './index.html'));
+      });
+
+      describe('default <head> section content', function() {
+        it('should have a <title> tag in the <head>', function() {
+          const title = dom.window.document.querySelector('head title').textContent;
+
+          expect(title).to.be.equal('My App');
+        });
+
+        // ...
+      });
+    });
+  });
+
+  after(function() {
+    runner.teardown(getOutputTeardownFiles(outputPath));
+  });
+});
+```
+
+### Running Tests
+
+To run tests in watch mode, use:
+
+```shell
+$ yarn test:tdd
+```
+
+To verify compliance with coverage and watermark thresholds (what CI server runs), use:
+
+```shell
+$ yarn test
+```
+
+Below are some tips to help with running / debugging tests:
+- `describe.only` / `it.only`: only runs this block
+- `xdescribe` / `xit`: don't run this block
+- Uncomment `runner.teardown()` in a case to see the build output without it getting cleaned up post test run
+- Use `new Runner(true)` get debug output from Greenwood when running tests
+
+> **PLEASE DO NOT COMMIT ANY OF THESE ABOVE CHANGES THOUGH**
+
+### Writing Tests
+
+Test cases follow a convention starting with the command (e.g. `build`) and and the capability and features being tested, like configuration with a particular option (e.g. `port`):
+
+```shell
+<command>.<capability>.<feature>-<modifier>.spec.js
+```
+
+Examples:
+- _build.default.spec.js_ - Would test `greenwood build` with no config and no workspace.
+- _build.config.workspace-custom.spec.js_ - Would test `greenwood build` with a config that had a custom `workspace`
+- _build.config.workspace-dev-server-port.spec.js_ - Would test `greenwood build` with a config that had a custom `workspace` and `devServer.port` set.
+
+#### Custom Loaders
+
+Test cases that exercise custom loaders (like TypeScript, JSX plugins) for SSR and prerendering use cases, will need to do a couple things:
+
+1. Prefix the test case directory and spec file with _loaders-_
+1. Make sure to pass `true` as the second param to `Runner`
+    ```js
+    before(function() {
+      this.context = {
+        publicDir: path.join(outputPath, 'public')
+      };
+      runner = new Runner(false, true);
+    });
+    ```
+1. Use the `yarn test:loaders` npm script
+
+#### Notes
+
+Here are some things to keep in mind while writing your tests, due to the asynchronous nature of Greenwood:
+- Make sure to wrap all calls to `TestBed` with `async`
+- All usages of `JSDOM` should be wrapped in `async`
+- Avoid arrow functions in mocha tests (e.g. `() => `) as this [can cause unexpected behaviors.](https://mochajs.org/#arrow-functions).  Just use `function` instead.
+
+### Dependencies
+
+To add and remove packages for any workspace, make sure you `cd` into the directory with the _package.json_ first before running `yarn add` or `yarn remove`.
+
+For example:
+
+```shell
+$ cd packages/cli
+$ yarn add <package>
+```
+
+Yarn workspaces will automatically handle installing _node_modules_ in the appropriate directory.
+
+### Continuous Integration
+
+Greenwood makes active use [GitHub Actions](https://github.com/features/actions) and [Netlify deploy previews](https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/) as part of the workflow.  Each time a PR is opened, a sequence of build steps defined _.github/workflows/_ are run for Linux and Windows.
+
+A deploy preview is also made available within the status checks section of the PR in GitHub and can be used to validate work in a live environment before having to merge.
+
+## Technical Design
+
+The Greenwood repo is a combination of [Yarn workspaces](https://classic.yarnpkg.com/en/docs/workspaces/) and a [Lerna monorepo](https://github.com/lerna/lerna).  The root level _package.json_ defines the workspaces and shared tooling used throughout the project, like for linting, testing, etc.
+
+The main workspace is the [_packages/_](https://github.com/ProjectEvergreen/greenwood/tree/master/packages) directory, which is everything we publish to NPM under the **@greenwood** scope.
+
+> _This guide is mainly intended to walk through the **cli** package; it being the principal package within the project supporting all other packages. See our website for documentation on our [Plugin APIs](https://www.greenwoodjs.dev/docs/reference/plugins-api/)._
+
+### CLI
+
+The CLI is the main entry point for Greenwood, similar to how the [front-controller pattern](https://en.wikipedia.org/wiki/Front_controller) works.  When users run a command like `greenwood build`, they are effectively invoking the file _src/index.js_ within the `@greenwood/cli` package.
+
+At a high level, this is how a command goes through the CLI:
+1. Each documented command a user can run maps to a script in the _commands/_ directory.
+1. Each command can invoke any number of lifecycles from the _lifecycles/_ directory.
+1. Lifecycles capture specific steps needed to build a site, serve it, generate a content dependency graph, etc.
+
+#### Package Structure
+
+The [structure](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/cli/src) of the CLI package is as follows:
+
+- _index.js_ - Entry point for the CLI
+- _commands/_ - map to runnable userland commands
+- _config/_ - Tooling configuration
+- _data/_ - Content as data related functionality
+- _lib/_ - Custom utility and client facing files
+- _lifecycles/_ - Individual tasks that can be used by commands to support a full Greenwood lifecycle
+- _plugins/_ - Greenwood plugins maintained by the CLI project
+- _layouts/_ - Default layouts and / or pages provided by Greenwood
+
+#### Lifecycles
+
+Aside from the config and graph lifecycles, all lifecycles (and config files and plugins) typically expect a compilation object to be passed in.
+
+Lifecycle responsibilities include:
+- starting a production or development server for a compilation
+- optimizing a compilation for production
+- prerendering a compilation for production
+- fetching external (content) data sources
+
+## Project Management
+
+We take advantage of quite a few features on GitHub to assist in tracking issues, bugs, ideas and more for the project.  We feel that being organized not only helps the team in planning out priorities and ownership, it's also a great way to add visibility and transparency to those following the project.
+
+### Project Boards
+
+Our [sequentially named project boards](https://github.com/ProjectEvergreen/greenwood/projects) help us organize work into buckets that will generally include a small handful of "top line" goals and objectives we would like to focus on for that particular phase of work.  It also serves as a catch-all for the usual work and bug fixes that happens throughout general maintenance of the project.  Additionally, we leverage this as a means to shine insight into good opportunities for those interested in contributing as to what the Greenwood team would appreciate help with the most.
+
+### Discussions
+
+We believe good collaboration starts with good communication.  As with most of the open source community, Greenwood is a 100% volunteer project and so we understand the importance of respecting everyone's [time and expectations](https://jason.energy/setting-expectations/) when it comes to contributing and investing in a project.  Although we don't mind issues being made, unless the issue is clearly actionable and falls in-line with the motivations and trajectory of the project, then feel free to go ahead an open a [Discussion](https://github.com/ProjectEvergreen/greenwood/discussions) first.
+
+We encourage discussions as we believe it is better to hash out technical discussions and proposals ahead of time since coding and reviewing PRs are very time consuming activities.  As maintainers, we want to make sure everyone gets the time they are desire for contributing and this this workflow helps us plan our time in advance to best ensure a smooth flow of contributions through the project.
+
+> _Put another way, we like to think of this approach as **measuring twice, cut once**._
+
+### Issues
+
+We like to reserve issues for features and requests that are more or less "shovel" ready with clear implementation details at hand and a clear definition of "done".  This could include prior discussions with the team or action items coming out from an existing discussion.
+
+Our standard issue template requests some of the following information to be prepared (where applicable)
+1. High Level Overview
+1. Code Sample or API Design
+1. Links / references for more context
+
+### Pull Requests
+
+Pull requests are the best!  To best help facilitate contributions to the project, here are some requests:
+
+- We generally prefer an issue be opened first, to help facilitate general discussion outside of the code review process itself and align on the ask and any expectations.  However, for typos in docs and minor "chore" like tasks a PR is usually sufficient.  When in doubt, open an issue.
+- For bugs, please consider reviewing the issue tracker first.
+- For branching, we generally follow the convention `<issue-label>/issue-<number>-<issue-title>`, e.g. _bug/issue-12-fixed-bug-with-yada-yada-yada_
+- To test the CI build scripts locally, run the `yarn` commands mentioned in the below section on CI.
+
+
+## Release Management
+
+Lerna (specifically `lerna publish`) will be used to release all packages under a single version.  Lerna configuration can be found in _lerna.json_.
+
+Assuming you are logged into **npm** locally and have 2FA access to publish, the following workflows should be used.  Lerna should then prompt you through the steps to pick the version and all packages that will get updated.
+
+### Alpha Release
+
+Greenwood typically works on new minor versions in a dedicated branch and release line called "alpha".  This leverages NPM's concept of dist tags.  While on a release branch, run the following to publish a new _alpha_ release.
+
+```sh
+# from the root of the repo
+$ yarn lerna publish --force-publish --dist-tag alpha
+```
+
+> Typically you will want to select the _Custom Preminor_ option from the list, which Lerna should appropriately yield the expected version.
+
+### Standard Release
+
+For a normal release (e.g. "latest") the following command can be run from the mainline branch of the repo.
+```sh
+# from the root of the repo
+$ yarn lerna publish --force-publish
+```
\ No newline at end of file
diff --git a/Dockerfile b/Dockerfile
deleted file mode 100644
index 4ad6e5225..000000000
--- a/Dockerfile
+++ /dev/null
@@ -1,9 +0,0 @@
-# See the Contributing.md guide for more information on using this
-# https://github.com/ProjectEvergreen/greenwood/blob/master/.github/CONTRIBUTING.md#docker
-
-FROM thegreenhouse/nodejs-dev:0.4.0
-
-# Set the working directory to /workspace when starting the container
-WORKDIR /workspace
-
-RUN yarn install
\ No newline at end of file
diff --git a/README.md b/README.md
index 1f4b15cd0..af93aa63b 100644
--- a/README.md
+++ b/README.md
@@ -1,47 +1,51 @@
 # Greenwood
 [![Netlify Status](https://api.netlify.com/api/v1/badges/6758148c-5c38-44d8-b908-ca0a1dad0f7c/deploy-status)](https://app.netlify.com/sites/elastic-blackwell-3aef44/deploys)
 [![GitHub release](https://img.shields.io/github/tag/ProjectEvergreen/greenwood.svg)](https://github.com/ProjectEvergreen/greenwood/tags)
-![GitHub Actions status](https://github.com/ProjectEvergreen/greenwood/workflows/Master%20Integration/badge.svg)
-[![GitHub issues](https://img.shields.io/github/issues-pr-raw/ProjectEvergreen/greenwood.svg)](https://github.com/ProjectEvergreen/greenwood/issues)
 [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/ProjectEvergreen/greenwood/master/LICENSE.md)
-[![lerna](https://img.shields.io/badge/maintained%20with-lerna-cc00ff.svg)](https://lerna.js.org/)
 
 ## Overview
-**Greenwood** is your _workbench for the web_; focused on supporting modern web standards and development to help you create your next project. For information on getting started, reviewing our docs, or to learn more about the project and how it works, please [visit our website](https://www.greenwoodjs.io/).
+
+**Greenwood** is your _workbench for the web_, embracing web standards from the ground up to empower your stack from front to back.  For information on getting started, reviewing our docs, or to learn more about the project and how it works, please [visit our website](https://www.greenwoodjs.dev/).
 
 Features:
-- ⚡ [No bundle development](https://www.greenwoodjs.io/about/how-it-works/). Pages are built on the fly.
-- 📝 HTML (and markdown) first [authoring experience](https://www.greenwoodjs.io/docs/layouts/) and ESM friendly.
-- 🎁 [Optimized](https://www.greenwoodjs.io/docs/configuration/#optimization) production builds.
-- 🚫 No JavaScript by default.
-- 📖 Prerendering support for Web Components.
-- ⚒️ Extensible via [plugins](https://www.greenwoodjs.io/plugins/).
-- ⚙️ Supports [SSG, MPA, SPA, and SSR project types](https://www.greenwoodjs.io/docs/layouts/). (or a hybrid!)
+- ⚡ No bundle development. Pages are built on the fly
+- 📝 HTML first authoring experience and ESM friendly
+- 📖 Server rendering and prerendering support for Web Components
+- 📚 Build with friends like Lit, Tailwind and HTMX
+- 🎁 Deploy self-hosted or to platforms like Vercel and Netlify
+- ⚒️ Extensible via plugins
+- ⚙️ Supports SSG, MPA, SPA, SSR and hybrid project types.  Including API Routes.
 
-> Greenwood is currently working towards a [1.0 release](https://github.com/ProjectEvergreen/greenwood/milestone/3).  If you're interested in learning more about the web and web development (at any skill level!), or interested in checking out our high level roadmap and how Greenwood got where it is today, you can read our [State of GreenwoodJS blog post](https://www.greenwoodjs.io/blog/state-of-greenwood-2022/).  We would love to have your help making Greenwood! ✌️
+> Greenwood is currently working towards a [1.0 release](https://github.com/ProjectEvergreen/greenwood/milestone/3). We would love to have your help building Greenwood! ✌️
 
 ## Getting Started
-Our website has a complete [Getting Started](http://www.greenwoodjs.io/getting-started) section that will walk you through creating a Greenwood project from scratch.
 
-You can follow along with, or clone and go, the [companion repo](https://github.com/ProjectEvergreen/greenwood-getting-started).
+Our website has a complete [Getting Started](http://www.greenwoodjs.dev/guides/getting-started/) guide that will walk you through creating a Greenwood project from scratch.
+
+You can follow along with, or clone and go, the [companion repo](https://github.com/ProjectEvergreen/greenwood-getting-started) or try it out live on [Stackblitz](https://stackblitz.com/github/projectevergreen/greenwood-getting-started).
 
 ## Installation
+
 Greenwood can be installed with your favorite JavaScript package manager.
+
 ```bash
 # npm
-npm install @greenwood/cli --save-dev
+npm i -D @greenwood/cli
 
 # yarn
 yarn add @greenwood/cli --dev
+
+# pnpm
+pnpm add -D @greenwood/cli
 ```
 
-Then in your _package.json_, add the `type` field and `scripts` for the CLI, like so:
+Then in your _package.json_, add the `type` field and `scripts` for the CLI:
 ```json
 {
   "type": "module",
   "scripts": {
     "build": "greenwood build",
-    "start": "greenwood develop",
+    "dev": "greenwood develop",
     "serve": "greenwood serve"
   }
 }
@@ -49,27 +53,16 @@ Then in your _package.json_, add the `type` field and `scripts` for the CLI, lik
 
 - `greenwood build`: Generates a production build of your project
 - `greenwood develop`: Starts a local development server for your project
-- `greenwood serve`: Generates a production build of your project and runs it on a NodeJS based web server
+- `greenwood serve`: Runs a production server for a production build
 
 ## Documentation
-All of our documentation is on our [website](https://www.greenwoodjs.io/) (which itself is built by Greenwood!).  See our website documentation to learn more about:
-- Configuration
-- Pages
-- Templates
-- Component Model
-- Styles and Assets
 
-## Contributing
-We would love your [contribution](.github/CONTRIBUTING.md) to Greenwood!  Please check out our issue tracker for "good first issue" labels or feel to reach out to us on [Slack](https://join.slack.com/t/thegreenhouseio/shared_invite/enQtMzcyMzE2Mjk1MjgwLTU5YmM1MDJiMTg0ODk4MjA4NzUwNWFmZmMxNDY5MTcwM2I0MjYxN2VhOTEwNDU2YWQwOWQzZmY1YzY4MWRlOGI) in the room _"Greenwood"_ or on [Twitter](https://twitter.com/PrjEvergreen).
+All of our documentation is on our [website](https://www.greenwoodjs.dev/), which [itself](https://github.com/ProjectEvergreen/www.greenwoodjs.dev) is built by Greenwood.
 
-## Built With Greenwood
-| Site  | Repo  | Project Details  |
-|-------|-------|------------------|
-| [The Greenhouse I/O](https://www.thegreenhouse.io/)  | [thegreenhouseio/www.thegreenhouse.io](https://github.com/thegreenhouseio/www.thegreenhouse.io)  | Personal portfolio / blog website for @thescientist13 (Greenwood maintainer). |
-| [Contributary](https://www.contributary.community/)  | [ContributaryCommunity/www.contributary.community](https://github.com/ContributaryCommunity/www.contributary.community)  | A website (SPA) for browsing open source projects that are open to contributions. Built with Lit and hosted with AWS (S3 / CloudFront). |
-| [Analog Studios](https://www.analogstudios.net/)  | [AnalogStudiosRI/www.analogstudios.net](https://github.com/AnalogStudiosRI/www.analogstudios.net)  | A local music studio SPA website, originally written in Angular 2, recently migrated to Lit.  It is currently transitioning to a [hybrid static + serverless website](https://github.com/AnalogStudiosRI/www.analogstudios.net/discussions/37) showing off the full potential of Greenwood and Web Components.  Follow along for all the fun! 🤘 |
+## Contributing
 
-> Built a site with Greenwood?  Open a PR and add it here!
+We would love your [contribution](.github/CONTRIBUTING.md) to Greenwood!  To get involved, you can check out our issue tracker for the ["good first issue" label](https://github.com/ProjectEvergreen/greenwood/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22), reach out to us on [Discord](https://discord.gg/bsy9jvWh), or start a discussion in our [GitHub repo](https://github.com/ProjectEvergreen/www.greenwoodjs.dev).
 
 ## License
+
 See the [LICENSE](LICENSE.md) file for license rights and limitations (MIT).
diff --git a/netlify.toml b/netlify.toml
index 5b5829366..df6dbdd7f 100644
--- a/netlify.toml
+++ b/netlify.toml
@@ -8,9 +8,200 @@
 [build.environment]
   NODE_VERSION = "18.12.1"
 
+[[redirects]]
+  from = "/"
+  to = "https://www.greenwoodjs.dev"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/cloudflare-workers-deployment/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/cloudflare/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/firebase/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/github-pages/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/github/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/netlify-deploy/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/netlify/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/netlify-cms/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/netlify/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/now/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/vercel/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/s3-cloudfront/"
+  to = "https://www.greenwoodjs.dev/guides/hosting/aws/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/guides/theme-packs/"
+  to = "https://www.greenwoodjs.dev/guides/tutorials/theme-packs/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/getting-started/"
+  to = "https://www.greenwoodjs.dev/guides/getting-started/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/about/*"
+  to = "https://www.greenwoodjs.dev/docs/introduction/about/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/"
+  to = "https://www.greenwoodjs.dev/docs/references/plugins-api/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/adapter/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#adapter"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/context/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#context"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/copy/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#copy"
+  status = 301
+
+[[redirects]]
+  from = "/plugins/renderer/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#renderer"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/resource/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#resource"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/rollup/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#rollup"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/server/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#server"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/source/"
+  to = "https://www.greenwoodjs.dev/docs/reference/plugins-api/#source"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/plugins/custom-plugins/"
+  to = "https://www.greenwoodjs.dev/docs/plugins/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/component-model/"
+  to = "https://www.greenwoodjs.dev/docs/introduction/web-standards/#web-components"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/configuration/"
+  to = "https://www.greenwoodjs.dev/docs/reference/configuration/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/front-matter/"
+  to = "https://www.greenwoodjs.dev/docs/resources/markdown/#frontmatter"
+  status = 301
+
+[[redirects]]
+  from = "/docs/markdown/"
+  to = "https://www.greenwoodjs.dev/docs/resources/markdown/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/scripts/"
+  to = "https://www.greenwoodjs.dev/docs/resources/scripts/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/css-and-images/"
+  to = "https://www.greenwoodjs.dev/docs/resources/styles/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/layouts/"
+  to = "https://www.greenwoodjs.dev/docs/pages/layouts/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/server-rendering/"
+  to = "https://www.greenwoodjs.dev/docs/pages/server-rendering/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/api-routes/"
+  to = "https://www.greenwoodjs.dev/docs/pages/api-routes/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/menus/"
+  to = "https://www.greenwoodjs.dev/docs/content-as-data/collections/"
+  status = 301
+  force = true
+
+[[redirects]]
+  from = "/docs/data/"
+  to = "https://www.greenwoodjs.dev/docs/content-as-data/"
+  status = 301
+  force = true
+
 [[redirects]]
   from = "/docs/tech-stack/"
   to = "/about/tech-stack/"
+  status = 200
 
 [[redirects]]
   from = "/docs/menus/:splat"
diff --git a/packages/cli/README.md b/packages/cli/README.md
index 150858c6d..c5d943fd9 100644
--- a/packages/cli/README.md
+++ b/packages/cli/README.md
@@ -1,31 +1,39 @@
 # @greenwood/cli
 
 ## Overview
-CLI package for Greenwood.  For more information and complete docs, please visit the [Greenwood website](https://www.greenwoodjs.io/docs).
+
+CLI package for Greenwood.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 ## Installation
-You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
+Greenwood can be installed with your favorite JavaScript package manager.
+
 ```bash
 # npm
-npm install @greenwood/cli --save-dev
+$ npm i -D @greenwood/cli
 
 # yarn
-yarn add @greenwood/cli --dev
+$ yarn add @greenwood/cli --dev
+
+# pnpm
+$ pnpm add -D @greenwood/cli
 ```
 
 ## Usage
-Then in your _package.json_, add the `type` field and `scripts` for the CLI like so:
+
+Then in your _package.json_, add the `type` field and `scripts` for the CLI:
+
 ```json
 {
   "type": "module",
   "scripts": {
     "build": "greenwood build",
-    "start": "greenwood develop"
+    "dev": "greenwood develop",
+    "serve": "greenwood serve"
   }
 }
 ```
 
-- `npm run build`: generates a static build of your project
-- `npm start`: starts a local development server for your project
\ No newline at end of file
+- `greenwood build`: Generates a production build of your project
+- `greenwood develop`: Starts a local development server for your project
+- `greenwood serve`: Runs a production server for a production build
\ No newline at end of file
diff --git a/packages/cli/package.json b/packages/cli/package.json
index c0895db91..a7219ab9c 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -10,7 +10,9 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
     "HTML",
     "CSS",
diff --git a/packages/cli/src/index.js b/packages/cli/src/index.js
index 22fc77cc0..a928d6a4d 100755
--- a/packages/cli/src/index.js
+++ b/packages/cli/src/index.js
@@ -83,7 +83,7 @@ const run = async() => {
         console.warn(`
           Error: not able to detect command. try using the --help flag if 
           you're encountering issues running Greenwood.  Visit our docs for more 
-          info at https://www.greenwoodjs.io/docs/.
+          info at https://www.greenwoodjs.dev/.
         `);
         break;
 
diff --git a/packages/init/README.md b/packages/init/README.md
index c6a82f497..646bb14a8 100644
--- a/packages/init/README.md
+++ b/packages/init/README.md
@@ -2,28 +2,28 @@
 
 ## Overview
 
-Init package for scaffolding out a new Greenwood project.  For more information and complete docs, please visit the [Greenwood website](https://www.greenwoodjs.io/docs).
+Init package for scaffolding out a new Greenwood project.  For more information and complete docs, please visit the [Greenwood website](https://www.greenwoodjs.dev).
 
 ## Usage
 
-Run the `init` command to scaffold a minimal Greenwood project into a directory of your choosing.
+Run the `init` command to scaffold a minimal Greenwood project.
 
 ```bash
-# providing an output directory of my-app
-npx @greenwood/init@latest my-app
+$ npx @greenwood/init@latest
 ```
 
-This will then output your project files into a directory called _my-app_
+This will then output your project files into a directory called _my-app_:
+
 ```bash
-my-app
-├── .gitignore
-├── greenwood.config.js
-├── package.json
-└── src/
-     └─ ...
+./
+  .gitignore
+  greenwood.config.js
+  package.json
+  src/
+    # ...
 ```
 
-## API
+## Options
 
 ### Project Name
 
@@ -31,52 +31,5 @@ By providing a name as the first argument, the `init` command will output the pr
 
 ```bash
 # example
-npx @greenwood/init@latest my-app
-```
-
-> _Omitting my-app will install project files into the current directory._
-
-### Template
-
-To scaffold your new project based on one of [Greenwood's starter templates](https://github.com/orgs/ProjectEvergreen/repositories?q=greenwood-template-&type=all&language=&sort=), pass the `--template` flag and then follow the prompts to complete the scaffolding.
-
-```bash
-# example
-npx @greenwood/init@latest --template
-
--------------------------------------------------------
-Initialize Greenwood Template ♻️
--------------------------------------------------------
-? Which template would you like to use? (Use arrow keys)
-❯ blog 
-```
-
-You can also pass the template you want from the CLI as well.
-```bash
-# example
-npx @greenwood/init@latest --template=blog 
-```
-
-### NPM Install
-
-To automatically run `npm install` after scaffolding, pass the `--install` flag.
-
-```bash
-# example
-npx @greenwood/init@latest --install
-```
-
-### Yarn Install
-
-To automatically run `yarn install` after scaffolding, pass the `--yarn` flag.
-
-```bash
-# example
-npx @greenwood/init@latest --yarn
-```
-
-> _Flags can be chained together!_
-> ```sh
-> # This will use Yarn, install dependencies, and scaffold from the blog template
-> $ npx @greenwood/init@latest --template --yarn --install
-> ```
\ No newline at end of file
+$ npx @greenwood/init@latest my-app
+```
\ No newline at end of file
diff --git a/packages/init/package.json b/packages/init/package.json
index 6739498c7..c16a42a9b 100644
--- a/packages/init/package.json
+++ b/packages/init/package.json
@@ -10,11 +10,16 @@
   "type": "module",
   "keywords": [
     "Greenwood",
+    "Scaffolding",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
-    "Scaffolding"
+    "HTML",
+    "CSS",
+    "JavaScript",
+    "NodeJS"
   ],
   "bin": {
     "init": "./src/index.js"
diff --git a/packages/init/src/template/src/pages/index.html b/packages/init/src/template/src/pages/index.html
index a519f44b2..dc446c5fe 100644
--- a/packages/init/src/template/src/pages/index.html
+++ b/packages/init/src/template/src/pages/index.html
@@ -78,17 +78,17 @@ <h1>Edit <code>src/pages/index.html</code> to start making changes</h1>
       <div class="card-wrapper">
         <div class="card">
           <h2>Getting Started</h2>
-          <p>Follow our <a href="https://www.greenwoodjs.io/getting-started/">guide</a> on learning Greenwood for the first time.</p>
+          <p>Follow our <a href="https://www.greenwoodjs.dev/guides/getting-started/">guide</a> on learning Greenwood for the first time.</p>
         </div>
 
         <div class="card">
           <h2>Docs</h2>
-          <p>Learn about Greenwood's <a href="https://www.greenwoodjs.io/docs/">features and capabilities</a>.</p>
+          <p>Learn about Greenwood's <a href="https://www.greenwoodjs.dev/docs/">features and capabilities</a>.</p>
         </div>
 
         <div class="card">
           <h2>Guides</h2>
-          <p>Walkthroughs on ways to <a href="https://www.greenwoodjs.io/guides/">build and deploy</a> with Greenwood.</p>
+          <p>Walkthroughs on ways to <a href="https://www.greenwoodjs.dev/guides/">build and deploy</a> with Greenwood.</p>
         </div>
 
         <div class="card">
diff --git a/packages/plugin-adapter-netlify/README.md b/packages/plugin-adapter-netlify/README.md
index 9b6c3bfb2..4ed2aed22 100644
--- a/packages/plugin-adapter-netlify/README.md
+++ b/packages/plugin-adapter-netlify/README.md
@@ -1,13 +1,14 @@
 # @greenwood/plugin-adapter-netlify
 
 ## Overview
-This plugin enables usage of the [Netlify](https://www.netlify.com/) platform for hosting a Greenwood application.
+
+This plugin enables usage of the [Netlify](https://www.netlify.com/) platform for hosting a Greenwood application.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Features
 
-In addition to publishing a project's static assets to the Netlify CDN, this plugin adapts Greenwood [API routes](https://www.greenwoodjs.io/docs/api-routes/) and [SSR pages](https://www.greenwoodjs.io/docs/server-rendering/) into Netlify [Serverless functions](https://docs.netlify.com/functions/overview/) using their [custom build](https://docs.netlify.com/functions/deploy/?fn-language=js#custom-build-2) approach
+In addition to publishing a project's static assets to the Netlify CDN, this plugin adapts Greenwood [API routes](https://www.greenwoodjs.dev/docs/pages/api-routes/) and [SSR pages](https://www.greenwoodjs.dev/docs/docs/pages/server-rendering/) into Netlify [Serverless functions](https://docs.netlify.com/functions/overview/) using their [custom build](https://docs.netlify.com/functions/deploy/?fn-language=js#custom-build-2) approach.
 
 This plugin will automatically generate a custom [__redirects_](https://docs.netlify.com/routing/redirects/) file to correctly map your SSR page and API route URLs to the corresponding Netlify function endpoint (as a rewrite).  You can continue to customize your Netlify project using your _netlify.toml_ file as needed.
 
@@ -15,15 +16,18 @@ This plugin will automatically generate a custom [__redirects_](https://docs.net
 
 
 ## Installation
+
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-adapter-netlify --save-dev
+$ npm i -D @greenwood/plugin-adapter-netlify
 
 # yarn
-yarn add @greenwood/plugin-adapter-netlify --dev
+$ yarn add @greenwood/plugin-adapter-netlify --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-adapter-netlify
 ```
 
 
@@ -45,13 +49,14 @@ Set the `AWS_LAMBDA_JS_RUNTIME` environment variable [in your Netlify UI](https:
 
 
 ## Usage
-Add this plugin to your _greenwood.config.js_.
+
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginAdapterNetlify } from '@greenwood/plugin-adapter-netlify';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginAdapterNetlify()
@@ -59,7 +64,9 @@ export default {
 }
 ```
 
-Optionally, your API routes will have access to Netlify's `context` object as the second parameter to the `handler` function.  For example:
+Optionally, your API routes will have access to Netlify's `context` object as the second parameter to the `handler` function.
+
+For example:
 ```js
 export async function handler(request, context = {}) {
   console.log({ request, context });
@@ -82,6 +89,7 @@ Then when you run it, you will be able to run and test a production build of you
 > _Please see caveats section for more information on this feature. 👇_
 
 ## Caveats
+
 1. [Edge runtime](https://docs.netlify.com/edge-functions/overview/) is not supported ([yet](https://github.com/ProjectEvergreen/greenwood/issues/1141)).
 1. Netlify CLI / Local Dev
     - [`context` object](https://docs.netlify.com/functions/create/?fn-language=js#code-your-function-2) not supported when running `greenwood develop` command
diff --git a/packages/plugin-adapter-netlify/package.json b/packages/plugin-adapter-netlify/package.json
index b2e3ef295..4e5f41aab 100644
--- a/packages/plugin-adapter-netlify/package.json
+++ b/packages/plugin-adapter-netlify/package.json
@@ -9,10 +9,11 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
-    "SSR",
+    "Server Side Rendering",
     "Full Stack Web Development",
-    "Netlify",
     "Serverless",
+    "Web Components",
+    "Netlify",
     "Edge"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-adapter-vercel/README.md b/packages/plugin-adapter-vercel/README.md
index d8f3458a2..4850eeb91 100644
--- a/packages/plugin-adapter-vercel/README.md
+++ b/packages/plugin-adapter-vercel/README.md
@@ -1,30 +1,34 @@
 # @greenwood/plugin-adapter-vercel
 
 ## Overview
-Enables usage of Vercel Serverless runtimes for API routes and SSR pages.
+
+Enables usage of [Vercel](https://vercel.com/) hosting for API routes and SSR pages.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Features
 
-In addition to publishing a project's static assets to the Vercel's CDN, this plugin adapts Greenwood [API routes](https://www.greenwoodjs.io/docs/api-routes/) and [SSR pages](https://www.greenwoodjs.io/docs/server-rendering/) into Vercel [Serverless functions](https://vercel.com/docs/concepts/functions/serverless-functions) using their [Build Output API](https://vercel.com/docs/build-output-api/v3).
+In addition to publishing a project's static assets to the Vercel's CDN, this plugin adapts Greenwood Greenwood [API routes](https://www.greenwoodjs.dev/docs/pages/api-routes/) and [SSR pages](https://www.greenwoodjs.dev/docs/docs/pages/server-rendering/) into Vercel [Serverless functions](https://vercel.com/docs/concepts/functions/serverless-functions) using their [Build Output API](https://vercel.com/docs/build-output-api/v3).
 
 > _**Note:** You can see a working example of this plugin [here](https://github.com/ProjectEvergreen/greenwood-demo-adapter-vercel)_.
 
 
 ## Installation
+
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-adapter-vercel --save-dev
+$ npm i -D @greenwood/plugin-adapter-vercel
 
 # yarn
-yarn add @greenwood/plugin-adapter-vercel --dev
+$ yarn add @greenwood/plugin-adapter-vercel --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-adapter-vercel
 ```
 
-You will then want to create a _vercel.json_ file, customized to match your project.  Assuming you have an npm script called `build`
+You will then want to create a _vercel.json_ file, customized to match your project.  Assuming you have an npm script called `build`:
 ```json
 {
   "scripts": {
@@ -33,7 +37,8 @@ You will then want to create a _vercel.json_ file, customized to match your proj
 }
 ```
 
-This would be the minimum _vercel.json_ configuration you would need
+This would be the minimum _vercel.json_ configuration you would need:
+
 ```json
 {
   "buildCommand": "npm run build"
@@ -41,13 +46,14 @@ This would be the minimum _vercel.json_ configuration you would need
 ```
 
 ## Usage
+
 Add this plugin to your _greenwood.config.js_.
 
 ```javascript
 import { greenwoodPluginAdapterVercel } from '@greenwood/plugin-adapter-vercel';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginAdapterVercel()
@@ -55,7 +61,6 @@ export default {
 }
 ```
 
-
 ## Caveats
 1. [Edge runtime](https://vercel.com/docs/concepts/functions/edge-functions) is not supported ([yet](https://github.com/ProjectEvergreen/greenwood/issues/1141)).
 1. The Vercel CLI (`vercel dev`) is not compatible with Build Output v3.
diff --git a/packages/plugin-adapter-vercel/package.json b/packages/plugin-adapter-vercel/package.json
index 809bf31e4..25625edb4 100644
--- a/packages/plugin-adapter-vercel/package.json
+++ b/packages/plugin-adapter-vercel/package.json
@@ -9,10 +9,11 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
-    "SSR",
+    "Server Side Rendering",
     "Full Stack Web Development",
-    "Vercel",
     "Serverless",
+    "Web Components",
+    "Vercel",
     "Edge"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-babel/README.md b/packages/plugin-babel/README.md
index 5996e6d29..c9522bce2 100644
--- a/packages/plugin-babel/README.md
+++ b/packages/plugin-babel/README.md
@@ -1,30 +1,35 @@
 # @greenwood/plugin-babel
 
 ## Overview
-A Greenwood plugin for using [**Babel**](https://babeljs.io/) and applying it to your JavaScript.
+
+A Greenwood plugin for using [**Babel**](https://babeljs.io/) and applying it to your JavaScript. For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Installation
+
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-babel --save-dev
+$ npm i -D @greenwood/plugin-babel
 
 # yarn
-yarn add @greenwood/plugin-babel --dev
+$ yarn add @greenwood/plugin-babel --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-babel
 ```
 
 ## Usage
-Add this plugin to your _greenwood.config.js_.
+
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginBabel } from '@greenwood/plugin-babel';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginBabel()
@@ -32,7 +37,7 @@ export default {
 }
 ```
 
-Create a _babel.config.cjs_ in the root of your project with your own custom plugins / settings that you've installed and want to use.
+Create a _babel.config.cjs_ in the root of your project with your own custom plugins / settings that you've installed and want to use:
 
 ```javascript
 module.exports = {
@@ -48,18 +53,12 @@ This will then process your JavaScript with Babel using the configured plugins a
 > _For now Babel configuration needs to be in CJS.  Will we be adding ESM support soon!_
 
 ## Options
+
 This plugin provides a default _babel.config.js_ that includes support for [**@babel/preset-env**](https://babeljs.io/docs/en/babel-preset-env) using [**browserslist**](https://github.com/browserslist/browserslist) with reasonable [default configs](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/plugin-babel/src/) for each.
 
 If you would like to use it, either standalone or with your own custom _babel.config.js_, you will need to take the following extra steps:
 
-1. Install `@babel/runtime` and `regenerator-runtime` as direct dependencies of your project
-    ```bash
-    # npm
-    npm install @babel/runtime regenerator-runtime
-
-    # yarn
-    yarn add @babel/runtime regenerator-runtime
-    ```
+1. Install `@babel/runtime` and `regenerator-runtime` as dependencies to your project
 1. When adding `greenwoodPluginBabel` to your _greenwood.config.js_, enable the `extendConfig` option
     ```js
     import { greenwoodPluginBabel } from '@greenwood/plugin-babel';
diff --git a/packages/plugin-babel/package.json b/packages/plugin-babel/package.json
index 68ba08bb5..40c2c50ab 100644
--- a/packages/plugin-babel/package.json
+++ b/packages/plugin-babel/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "Babel"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-css-modules/README.md b/packages/plugin-css-modules/README.md
index 8cabc12ae..16b8bc97b 100644
--- a/packages/plugin-css-modules/README.md
+++ b/packages/plugin-css-modules/README.md
@@ -4,7 +4,7 @@
 
 A Greenwood plugin for authoring [**CSS Modules ™️**](https://github.com/css-modules/css-modules).  It is a modest implementation of [the specification](https://github.com/css-modules/icss).  🙂
 
-This is NOT to be confused with [CSS Module _Scripts_](https://web.dev/articles/css-module-scripts), which Greenwood already supports.
+This is NOT to be confused with [CSS Module _Scripts_](https://web.dev/articles/css-module-scripts), which Greenwood already supports.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
@@ -12,24 +12,26 @@ This is NOT to be confused with [CSS Module _Scripts_](https://web.dev/articles/
 
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm i -D @greenwood/plugin-css-modules
+$ npm i -D @greenwood/plugin-css-modules
 
 # yarn
-yarn add @greenwood/plugin-css-modules --dev
+$ yarn add @greenwood/plugin-css-modules --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-css-modules
 ```
 
 ## Usage
 
-Add this plugin to your _greenwood.config.js_.
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginCssModules } from '@greenwood/plugin-css-modules';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginCssModules()
@@ -37,7 +39,7 @@ export default {
 }
 ```
 
-Now you can create a CSS file that ends in _.module.css_
+Now you can create a CSS file that ends in _.module.css_:
 
 ```css
 /* header.module.css */
@@ -65,7 +67,7 @@ Now you can create a CSS file that ends in _.module.css_
 ```
 
 
-And reference that in your (Light DOM) HTML based Web Component
+And reference that in your (Light DOM) HTML based Web Component:
 
 ```js
 // header.js
diff --git a/packages/plugin-css-modules/package.json b/packages/plugin-css-modules/package.json
index 9da41e5a9..f2d873db4 100644
--- a/packages/plugin-css-modules/package.json
+++ b/packages/plugin-css-modules/package.json
@@ -9,7 +9,9 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
     "CSS Modules"
   ],
diff --git a/packages/plugin-google-analytics/README.md b/packages/plugin-google-analytics/README.md
index 6554cdaa8..7fc196e54 100644
--- a/packages/plugin-google-analytics/README.md
+++ b/packages/plugin-google-analytics/README.md
@@ -1,28 +1,27 @@
 # @greenwood/plugin-google-analytics
 
 ## Overview
-A Greenwood plugin adding support for [Google Analytics](https://developers.google.com/analytics/) JavaScript tracker. It assumes you already have your own Tracking ID(s) and [can either filter out tracking for everything but your production environment](https://stackoverflow.com/a/1251931/417806) so that local testing doesn't interfere with production data, or use a conditional based `analyticsId` using an environment variable, ex.
-<!-- eslint-disable no-unused-vars -->
-```js
-const analyticsId = process.env.NODE_ENV === 'xxx' ? 'UA-123...' : 'UA-345...';
-```
-
-> _For more information and complete docs about Greenwood, please visit the [Greenwood website](https://www.greenwoodjs.io/)._
+A Greenwood plugin adding support for [Google Analytics](https://developers.google.com/analytics/) JavaScript tracker. It assumes you already have your own Tracking ID(s) and [can either filter out tracking for everything but your production environment](https://stackoverflow.com/a/1251931/417806) so that local testing doesn't interfere with production data, or use a conditional based `analyticsId` using an environment variable.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
+> This package assumes you already have `@greenwood/cli` installed.
 
 ## Installation
+
 You can use your favorite JavaScript package manager to install this package.  This package assumes you already have `@greenwood/cli` installed.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-google-analytics --save-dev
+$ npm i -D @greenwood/plugin-google-analytics
 
 # yarn
-yarn add @greenwood/plugin-google-analytics --dev
+$ yarn add @greenwood/plugin-google-analytics --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-google-analytics
 ```
 
 ## Usage
+
 Use this plugin in your _greenwood.config.js_ and pass in your Google Analytics ID, which can either be a
 * Measurement ID (**recommended**): ex. `G-XXXXXX`
 * Tracking ID (legacy): ex. `UA-XXXXXX`
@@ -31,7 +30,7 @@ Use this plugin in your _greenwood.config.js_ and pass in your Google Analytics
 import { greenwoodPluginGoogleAnalytics } from '@greenwood/plugin-google-analytics';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginGoogleAnalytics({
@@ -46,10 +45,12 @@ This will then add the Google Analytics [JavaScript tracker snippet](https://dev
 > _Learn more about [Measurement and Tracking IDs](https://support.google.com/analytics/answer/9539598)_.
 
 ## Options
+
 - `analyticsId` (required) - Your Google Analytics ID
 - `anonymous` (optional) - Sets if tracking of IPs should be done anonymously.  Default is `true`
 
 ### Outbound Links
+
 For links that go outside of your domain, the global function [`getOutboundLink`](https://support.google.com/analytics/answer/7478520) is available for you to use.
 
 Example:
diff --git a/packages/plugin-google-analytics/package.json b/packages/plugin-google-analytics/package.json
index a345ae9ee..8df7ee589 100644
--- a/packages/plugin-google-analytics/package.json
+++ b/packages/plugin-google-analytics/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "Google Analytics"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-graphql/README.md b/packages/plugin-graphql/README.md
index fb136e301..120fe0c4a 100644
--- a/packages/plugin-graphql/README.md
+++ b/packages/plugin-graphql/README.md
@@ -2,14 +2,14 @@
 
 ## Overview
 
-A plugin for Greenwood to support using [GraphQL](https://graphql.org/) to query Greenwood's [content graph](https://www.greenwoodjs.io/docs/data/) with our optional [pre-made queries](https://www.greenwoodjs.io/docs/data/#data-client).  It runs [**apollo-server**](https://www.apollographql.com/docs/apollo-server/) on the backend at build time and provides a **"read-only"** [**@apollo/client** _"like"_](https://www.apollographql.com/docs/react/api/core/ApolloClient/#ApolloClient.readQuery) interface for the frontend that you can use.
+A plugin for Greenwood to support using [GraphQL](https://graphql.org/) to query Greenwood's [content graph](https://www.greenwoodjs.dev/docs/content-as-data/) with our optional pre-made queries custom for GraphQL.  It runs [**apollo-server**](https://www.apollographql.com/docs/apollo-server/) on the backend at build time and provides a **"read-only"** [**@apollo/client** _"like"_](https://www.apollographql.com/docs/react/api/core/ApolloClient/#ApolloClient.readQuery) interface for the frontend that you can use.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Caveats
 
-As of now, this plugin requires some form of [prerendering](https://www.greenwoodjs.io/docs/server-rendering/#render-vs-prerender) either through:
-1. Enabling [custom imports](https://www.greenwoodjs.io/docs/server-rendering/#custom-imports) or
+As of now, this plugin requires some form of [prerendering](https://www.greenwoodjs.dev/docs/reference/rendering-strategies/) either through:
+1. Enabling [custom imports](https://www.greenwoodjs.dev/docs/pages/server-rendering/#custom-imports), or
 1. Installing the [Puppeteer renderer plugin](https://github.com/ProjectEvergreen/greenwood/tree/master/packages/plugin-renderer-puppeteer).
 
 ## Installation
@@ -18,10 +18,13 @@ You can use your favorite JavaScript package manager to install this package.
 
 ```bash
 # npm
-npm install @greenwood/plugin-graphql --save-dev
+$ npm i -D @greenwood/plugin-graphql
 
 # yarn
-yarn add @greenwood/plugin-graphql --dev
+$ yarn add @greenwood/plugin-graphql --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-graphql
 ```
 
 ## Usage
@@ -90,8 +93,6 @@ class HeaderComponent extends HTMLElement {
 customElements.define('app-header', HeaderComponent);
 ```
 
-> _For more general purpose information on content with data in Greenwood, [please see our docs](https://www.greenwoodjs.io/docs/data/)._
-
 ## Schema
 
 The basic page schema follow the structure of the [page data]() structure.   Currently, the main "API" is just a list of all pages in your _pages/_ directory, represented as a `Page` [type definition](https://graphql.org/graphql-js/basic-types/).   This is called Greenwood's `graph`.
@@ -122,9 +123,7 @@ The Graph query returns an array of all pages.
 import client from '@greenwood/plugin-graphql/src/core/client.js';
 import GraphQuery from '@greenwood/plugin-graphql/src/queries/graph.gql';
 
-.
-.
-.
+//
 
 async connectedCallback() {
   super.connectedCallback();
@@ -138,15 +137,13 @@ async connectedCallback() {
 
 ### Collections
 
-Based on [our Collections feature](http://www.greenwoodjs.io/docs/data/#collections) for querying based on collections.
+Based on [our Collections feature](http://www.greenwoodjs.dev/docs/content-as-data/collections/) for querying based on collections.
 
 ```javascript
 import client from '@greenwood/plugin-graphql/src/core/client.js';
 import CollectionQuery from '@greenwood/plugin-graphql/src/queries/collection.gql';
 
-.
-.
-.
+// ...
 
 async connectedCallback() {
   super.connectedCallback();
@@ -163,15 +160,13 @@ async connectedCallback() {
 
 ### Children 
 
-This will return a set of pages under a specific route and is akin to using [`getContentByRoute`](http://www.greenwoodjs.io/docs/data/#data-client).
+This will return a set of pages under a specific route and is akin to using [`getContentByRoute`](http://www.greenwoodjs.dev/docs/content-as-data/data-client/#content-by-route).
 
 ```javascript
 import client from '@greenwood/plugin-graphql/src/core/client.js';
 import ChildrenQuery from '@greenwood/plugin-graphql/src/queries/children.gql';
 
-.
-.
-.
+// ...
 
 async connectedCallback() {
   super.connectedCallback();
@@ -200,7 +195,8 @@ query {
 }
 ```
 
-Or within your component
+Or within your component:
+
 ```javascript
 import gql from 'graphql-tag';  // comes with Greenwood
 
diff --git a/packages/plugin-graphql/package.json b/packages/plugin-graphql/package.json
index ee4fab929..be3f76a4f 100644
--- a/packages/plugin-graphql/package.json
+++ b/packages/plugin-graphql/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "GraphQL",
     "Apollo"
   ],
diff --git a/packages/plugin-import-commonjs/README.md b/packages/plugin-import-commonjs/README.md
index 216f7c83c..c02baa994 100644
--- a/packages/plugin-import-commonjs/README.md
+++ b/packages/plugin-import-commonjs/README.md
@@ -1,30 +1,36 @@
 # @greenwood/plugin-import-commonjs
 
 ## Overview
-A plugin for Greenwood for loading CommonJS based modules (`require` / `module.exports`) in the browser using ESM (`import` / `export`) syntax.  _**Note**: It is highly encouraged that you favor ESM based packages for the cleanest / fastest interop and developer experience.  Additional processing time and dependencies are required to handle the conversion._
+
+A plugin for Greenwood for loading CommonJS based modules (`require` / `module.exports`) in the browser using ESM (`import` / `export`) syntax.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
+
+_**Note**: It is highly encouraged that you favor ESM based packages for the cleanest / fastest interop and developer experience.  Additional processing time and dependencies are required to handle the conversion._
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Installation
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-import-commonjs --save-dev
+$ npm i -D @greenwood/plugin-import-commonjs
 
 # yarn
-yarn add @greenwood/plugin-import-commonjs --dev
+$ yarn add @greenwood/plugin-import-commonjs --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-import-commonjs
 ```
 
 ## Usage
-Add this plugin to your _greenwood.config.js_ and spread the `export`.
+
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginImportCommonJs } from '@greenwood/plugin-import-commonjs';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginImportCommonJs()
@@ -32,14 +38,13 @@ export default {
 }
 ```
 
-This will then allow you to use a CommonJS based modules in the browser.   For example, here is how you could use [**lodash**](https://lodash.com/) (although as mentioned above, in this case, you would want to use [**lodash-es**](https://www.npmjs.com/package/lodash-es) instead.)
+This will then allow you to use a CommonJS based modules in the browser.   For example, here is how you could use [**lodash**](https://lodash.com/) (although as mentioned above, in this case, you would want to use [**lodash-es**](https://www.npmjs.com/package/lodash-es) instead)
 
 ```javascript
 // <script src="my-file.js">
 import _ from 'lodash';
 
-.
-.
+// ...
 
 console.log(_.defaults({ 'a': 1 }, { 'a': 3, 'b': 2 }));  // { 'a': 1, 'b': 2 }
 ```
\ No newline at end of file
diff --git a/packages/plugin-import-commonjs/package.json b/packages/plugin-import-commonjs/package.json
index f93c52446..7ea677123 100644
--- a/packages/plugin-import-commonjs/package.json
+++ b/packages/plugin-import-commonjs/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "CommonJS"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-import-jsx/README.md b/packages/plugin-import-jsx/README.md
index f9dab1e06..a3e1e5938 100644
--- a/packages/plugin-import-jsx/README.md
+++ b/packages/plugin-import-jsx/README.md
@@ -1,30 +1,35 @@
 # @greenwood/plugin-import-jsx
 
 ## Overview
-Enables usage of `import` syntax for loading [JSX rendering Web Components](https://merry-caramel-524e61.netlify.app/docs/#jsx) compatible with [**WCC**](https://github.com/ProjectEvergreen/wcc).  (This is _**not**_ React JSX!)
+Enables usage of `import` syntax for loading [JSX rendering Web Components](https://merry-caramel-524e61.netlify.app/docs/#jsx) compatible with [**WCC**](https://github.com/ProjectEvergreen/wcc). For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
+
+_Note: This is _**not**_ React JSX!_
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Installation
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-import-jsx --save-dev
+$ npm i -D @greenwood/plugin-import-jsx
 
 # yarn
-yarn add @greenwood/plugin-import-jsx --dev
+$ yarn add @greenwood/plugin-import-jsx --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-import-jsx
 ```
 
 ## Usage
-Add this plugin to your _greenwood.config.js_.
+
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginImportJsx } from '@greenwood/plugin-import-jsx';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginImportJsx()
@@ -32,7 +37,7 @@ export default {
 }
 ```
 
-This will then allow you to use `import` to include [WCC](https://merry-caramel-524e61.netlify.app/docs/#jsx) compatible JSX rendering Web Components.
+This will then allow you to use `import` to include [WCC](https://merry-caramel-524e61.netlify.app/docs/#jsx) compatible JSX rendering Web Components:
 ```js
 export default class FooterComponent extends HTMLElement {
   connectedCallback() {
diff --git a/packages/plugin-import-jsx/package.json b/packages/plugin-import-jsx/package.json
index 0a0ed00ca..74cc2ddec 100644
--- a/packages/plugin-import-jsx/package.json
+++ b/packages/plugin-import-jsx/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "JSX",
     "WCC"
   ],
diff --git a/packages/plugin-import-raw/README.md b/packages/plugin-import-raw/README.md
index 61c33e867..aa486d71e 100644
--- a/packages/plugin-import-raw/README.md
+++ b/packages/plugin-import-raw/README.md
@@ -2,24 +2,28 @@
 
 ## Overview
 
-A Greenwood plugin to use ESM (`import`) syntax to load any file contents as a string exported as a JavaScript module.  Inspired by **webpack**'s [raw loader](https://v4.webpack.js.org/loaders/raw-loader/).
+A Greenwood plugin to use ESM (`import`) syntax to load any file contents as a string exported as a JavaScript module.  Inspired by **webpack**'s [raw loader](https://v4.webpack.js.org/loaders/raw-loader/).  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
 ## Installation
+
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-import-raw --save-dev
+$ npm i -D @greenwood/plugin-import-raw
 
 # yarn
-yarn add @greenwood/plugin-import-raw --dev
+$ yarn add @greenwood/plugin-import-raw --dev
+
+# npm
+$ pnpm add -D @greenwood/plugin-import-raw
 ```
 
 ## Usage
-Add this plugin to your _greenwood.config.js_ and spread the `export`.
+
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginImportRaw } from '@greenwood/plugin-import-raw';
diff --git a/packages/plugin-import-raw/package.json b/packages/plugin-import-raw/package.json
index 44e1ba2c0..8c09181ea 100644
--- a/packages/plugin-import-raw/package.json
+++ b/packages/plugin-import-raw/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "ESM"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-include-html/README.md b/packages/plugin-include-html/README.md
index 424fdd5af..a193a945b 100644
--- a/packages/plugin-include-html/README.md
+++ b/packages/plugin-include-html/README.md
@@ -1,18 +1,39 @@
 # @greenwood/plugin-include-html
 
 ## Overview
+
 In the spirit of the since [abandoned HTML Imports spec](https://www.html5rocks.com/en/tutorials/webcomponents/imports/) that was originally part of the init Web Components "feature suite", and given the renewed [interest in bringing it back](https://github.com/whatwg/html/issues/2791), this plugin adds experimental support to realize the HTML Includes "spec" as a build time templating system for HTML.  The goal here is to enable developers the ability to ship more static HTML while allowing the authoring context to be JavaScript **and** leveraging standard semantics and web expectations. 💚
 
-> **Note**: I think if you want this feature in its most strictest sense of the word, I would recommend the [**<html-include>**](https://github.com/justinfagnani/html-include-element) custom element, which provides a runtime implementation of this as a Web Component.
+If you want this feature in its most strictest sense of the word, I would recommend the [**<html-include>**](https://github.com/justinfagnani/html-include-element) custom element, which provides a runtime implementation of this as a Web Component.
+
+For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
+
+> This package assumes you already have `@greenwood/cli` installed.
+
+## Installation
+
+You can use your favorite JavaScript package manager to install this package.
+
+```bash
+# npm
+$ npm i -D @greenwood/plugin-include-html
+
+# yarn
+$ yarn add @greenwood/plugin-include-html --dev
+
+# npm
+$ pnpm add -D @greenwood/plugin-include-html
+```
 
 ## Usage
-Add this plugin to your _greenwood.config.js_ and spread the `export`.
+
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginIncludeHtml } from '@greenwood/plugin-include-html';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginIncludeHtml()
@@ -20,9 +41,10 @@ export default {
 }
 ```
 
-> _It should be noted that this plugin would more or less be another way to achieve what the [`static` optimization setting](https://www.greenwoodjs.io/docs/configuration/#optimization) already does._
+> _It should be noted that this plugin would more or less be another way to achieve what the [`static` optimization setting](https://www.greenwoodjs.dev/docs/reference/configuration/#optimization) already does._
 
 ### `<link>` Tag (HTML only)
+
 This is the simplest "flavor" and follows the spec more closely to address the use case where you have static HTML that you want to reuse across your pages, like a global header or footer.  The location of this file can be anywhere in your workspace, I just chose to put it in an _includes/_ directory for the sake of this example.
 
 So given a snippet of HTML, e.g.
@@ -78,8 +100,8 @@ And Greenwood will statically generate this
 <html>
 ```
 
-
 ### Custom Element (JavaScript)
+
 For more advanced use cases where customization of the output may need to be done in a programmatic fashion, the custom element flavor supports declaring functions for generating markup and data that Greenwood will then build the HTML for on the fly.  This effectively aims to fill the gap where just static HTML alone would not be sufficient enough.
 
 So using the [Greenwood footer as an example](https://github.com/ProjectEvergreen/greenwood/blob/master/www/includes/footer.js), that displays the project version based on reading the contents of a _package.json_ file, create a JS file that `export`s two functions; `getTemplate` and `getData`
diff --git a/packages/plugin-include-html/package.json b/packages/plugin-include-html/package.json
index 59bca6327..3101b8ac0 100644
--- a/packages/plugin-include-html/package.json
+++ b/packages/plugin-include-html/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "HTML",
     "HTML Include"
   ],
diff --git a/packages/plugin-polyfills/README.md b/packages/plugin-polyfills/README.md
index 89b79527a..ed9fb321a 100644
--- a/packages/plugin-polyfills/README.md
+++ b/packages/plugin-polyfills/README.md
@@ -9,30 +9,34 @@ As of right now, you will likely need this plugin to load additional polyfills i
 - Mobile Browsers
 - Declarative Shadow DOM
 
-See Greenwood's [browser support](https://www.greenwoodjs.io/about/how-it-works#browser-support) and [evergreen build](https://www.greenwoodjs.io/about/how-it-works#evergreen-build) docs for more information on how Greenwood handles browser support out of the box.  Or visit [caniuse.com](https://caniuse.com/) to look up specific support for specific browsers.
+For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
-> _For more information and complete docs about Greenwood, please visit the [Greenwood website](https://www.greenwoodjs.io/)._
+> This package assumes you already have `@greenwood/cli` installed.
 
 ## Installation
+
 You can use your favorite JavaScript package manager to install this package.  This package assumes you already have `@greenwood/cli` installed.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-polyfills --save-dev
+$ npm i -D @greenwood/plugin-polyfills
 
 # yarn
-yarn add @greenwood/plugin-polyfills --dev
+$ yarn add @greenwood/plugin-polyfills --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-polyfills
 ```
 
 ## Usage
-Use this plugin in your _greenwood.config.js_.
+
+Use this plugin in your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginPolyfills } from '@greenwood/plugin-polyfills';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginPolyfills()
@@ -57,7 +61,7 @@ You can adjust either of these default behaviors by providing `true` or `false`
 import { greenwoodPluginPolyfills } from '@greenwood/plugin-polyfills';
 
 export default {
-  ...
+  // ...
 
   // default values shown here
   plugins: [
diff --git a/packages/plugin-polyfills/package.json b/packages/plugin-polyfills/package.json
index 95440a07d..fd3f08886 100644
--- a/packages/plugin-polyfills/package.json
+++ b/packages/plugin-polyfills/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "Polyfills"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-postcss/README.md b/packages/plugin-postcss/README.md
index 999904150..904837c03 100644
--- a/packages/plugin-postcss/README.md
+++ b/packages/plugin-postcss/README.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-A Greenwood plugin for loading [**PostCSS**](https://postcss.org/) configuration and applying it to your CSS.
+A Greenwood plugin for loading [**PostCSS**](https://postcss.org/) configuration and applying it to your CSS.  For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
@@ -10,24 +10,26 @@ A Greenwood plugin for loading [**PostCSS**](https://postcss.org/) configuration
 
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-postcss --save-dev
+$ npm i -D @greenwood/plugin-postcss
 
 # yarn
-yarn add @greenwood/plugin-postcss --dev
+$ yarn add @greenwood/plugin-postcss --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-postcss
 ```
 
 ## Usage
 
-Add this plugin to your _greenwood.config.js_.
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginPostCss } from '@greenwood/plugin-postcss';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginPostCss()
@@ -46,7 +48,7 @@ export default {
 };
 ```
 
-> Note: Greenwood provides the postcss-import behavior out of the box.
+> Note: Greenwood provides the behavior of postcss-import out of the box.
 
 ## Options
 
diff --git a/packages/plugin-postcss/package.json b/packages/plugin-postcss/package.json
index 4b79aca7b..8dd533253 100644
--- a/packages/plugin-postcss/package.json
+++ b/packages/plugin-postcss/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "PostCSS"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-renderer-lit/README.md b/packages/plugin-renderer-lit/README.md
index d8dbe81c9..d14217df2 100644
--- a/packages/plugin-renderer-lit/README.md
+++ b/packages/plugin-renderer-lit/README.md
@@ -2,23 +2,23 @@
 
 ## Overview
 
-A Greenwood plugin for using [**Lit**'s SSR capabilities](https://github.com/lit/lit/tree/main/packages/labs/ssr) as a custom server-side renderer.  Although support is experimental at this time, this plugin also gives the ability to statically render entire pages and layouts to output completely static sites.
-
-_We are still actively working on SSR features and enhancements for Greenwood [as part of our 1.0 release](https://github.com/ProjectEvergreen/greenwood/issues?q=is%3Aissue+is%3Aopen+label%3Assr+milestone%3A1.0) so please feel free to test it out and report your feedback._  🙏
+A Greenwood plugin for using [**Lit**'s SSR capabilities](https://github.com/lit/lit/tree/main/packages/labs/ssr) as a custom server-side renderer instead of Greenwood's default renderer (WCC). This plugin also gives the ability to statically render entire pages and layouts to output completely static sites. For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
-
 ## Prerequisite
 
 This packages depends on the Lit package as a `peerDependency`.  This means you must have Lit already installed in your project.  You can install anything following the `3.x` release line.
 
 ```sh
 # npm
-$ npm install lit --dev
+$ npm -i lit
 
 # yarn
-$ yarn add lit --dev
+$ yarn add lit
+
+# pnpm
+$ pnpm add lit
 ```
 
 ## Installation
@@ -27,10 +27,13 @@ You can use your favorite JavaScript package manager to install this package.
 
 ```bash
 # npm
-npm install @greenwood/plugin-renderer-lit --save-dev
+$ npm i -D @greenwood/plugin-renderer-lit
 
 # yarn
-yarn add @greenwood/plugin-renderer-lit --dev
+$ yarn add @greenwood/plugin-renderer-lit --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-renderer-lit
 ```
 
 ## Caveats
@@ -46,13 +49,13 @@ yarn add @greenwood/plugin-renderer-lit --dev
 
 ## Usage
 
-Add this plugin to your _greenwood.config.js_.
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginRendererLit } from '@greenwood/plugin-renderer-lit';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginRendererLit()
@@ -60,7 +63,7 @@ export default {
 }
 ```
 
-Now, you can author [SSR pages](/docs/server-rendering/) using Lit templates and components using Greenwood's [`getBody` API](https://www.greenwoodjs.io/docs/server-rendering/#usage).  The below is an example of generating a template of LitElement based `<app-card>` web components.
+Now, you can author [SSR pages](/docs/server-rendering/) using Lit templates and components using Greenwood's [`getBody` API](https://www.greenwoodjs.dev/docs/pages/server-rendering/#body).  The below is an example of generating a template of LitElement based `<app-card>` web components.
 
 ```js
 // src/pages/products.js
@@ -98,7 +101,7 @@ By default, this plugin sets `isolation` mode to `true` for all SSR pages.  If y
 export const isolation = false;
 ```
 
-> _See the [isolation configuration](https://www.greenwoodjs.io/docs/configuration/#isolation) docs for more information._
+> _See the [isolation configuration](https://www.greenwoodjs.dev/docs/reference/configuration/#isolation-mode) docs for more information._
 
 ### Hydration
 
@@ -117,7 +120,7 @@ The plugin provides a setting that can be used to override Greenwood's [default
 import { greenwoodPluginRendererLit } from '@greenwood/plugin-renderer-lit';
 
 export default {
-  ...
+  // ...
 
   plugins: [
     greenwoodPluginRendererLit({
diff --git a/packages/plugin-renderer-lit/package.json b/packages/plugin-renderer-lit/package.json
index 5d0c56fd4..9e6386243 100644
--- a/packages/plugin-renderer-lit/package.json
+++ b/packages/plugin-renderer-lit/package.json
@@ -10,9 +10,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "Lit",
     "SSR"
   ],
diff --git a/packages/plugin-renderer-puppeteer/README.md b/packages/plugin-renderer-puppeteer/README.md
index 6b28e7645..69e428921 100644
--- a/packages/plugin-renderer-puppeteer/README.md
+++ b/packages/plugin-renderer-puppeteer/README.md
@@ -2,17 +2,52 @@
 
 ## Overview
 
-A Greenwood plugin for using [**Puppeteer**](https://pptr.dev) as a custom [_pre-rendering_ solution](/docs/server-rendering/#render-vs-prerender).  As Puppeteer is a headless browser, it provides a lot more power and capabilities for fully rendering things like Web Components, GraphQL calls, and other very browser dependent features.
+A Greenwood plugin for using [**Puppeteer**](https://pptr.dev) as a custom [_pre-rendering_ solution](/docs/server-rendering/#render-vs-prerender).  As Puppeteer is a headless browser, it provides a lot more power and capabilities for fully rendering things like Web Components, GraphQL calls, and other very browser dependent features. For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
-### Caveats
+> This package assumes you already have `@greenwood/cli` installed.
+
+## Installation
+
+You can use your favorite JavaScript package manager to install this package.
+
+```bash
+# npm
+$ npm i -D @greenwood/plugin-renderer-puppeteer
+
+# yarn
+$ yarn add @greenwood/plugin-renderer-puppeteer --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-renderer-puppeteer
+```
+
+## Usage
+
+Add this plugin to your _greenwood.config.js_:
+
+```javascript
+import { greenwoodPluginRendererPuppeteer } from '@greenwood/plugin-renderer-puppeteer';
+
+export default {
+  // ...
+
+  plugins: [
+    greenwoodPluginRendererPuppeteer()
+  ]
+}
+```
+
+Now, when running `greenwood build`, all your pages will get run through Puppeteer and any JavaScript / Web Components that you author will get a one time pass execution and the resulting HTML generated from that process will be captured and further optimized through Greenwood's build pipeline.
 
-#### Limitations
+## Caveats
+
+### Limitations
 Given this plugin instruments an entire browser, this plugin _only_ supports Greenwood's [`prerender` configuration](/docs/configuration/#prerender) option and so will NOT be viable for any [SSR](/docs/server-rendering/) or [Serverless and Edge](https://github.com/ProjectEvergreen/greenwood/discussions/626) features.  Instead, Greenwood will be focusing on making [**WCC**](https://github.com/ProjectEvergreen/wcc) the default and recommended first-party solution.
 
 In addition, **puppeteer** also leverages npm `postinstall` scripts which in some environments, like [Stackblitz](https://github.com/ProjectEvergreen/greenwood/discussions/639), would be disabled and so [YMMV](https://dictionary.cambridge.org/us/dictionary/english/ymmv).
 
 
-#### Dependencies
+### Dependencies
 
 You may need to install additional Operating System level libraries and dependencies depending on the system you are running on to support headless Chrome. For example, for a Docker based environment like [GitHub Actions](https://github.com/ProjectEvergreen/greenwood/blob/master/.github/workflows/master.yml#L19), you would need to add [this below setup script (or similar)](https://github.com/ProjectEvergreen/greenwood/blob/master/.github/workflows/chromium-lib-install.sh) to your runner
 ```shell
@@ -31,9 +66,6 @@ sudo apt-get update \\
 
 ```yml
 
-.
-.
-
 jobs:
  build:
    runs-on: ubuntu-latest
@@ -44,40 +76,8 @@ jobs:
          sh path/to/your/chromium-lib-install.sh
       - uses: actions/setup-node@v1
         with:
-           node-version: "14.x"
-      .
-      .
-```
-
-See the Puppeteer [Troubleshooting docs](https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md) for more info on setting up your specific environment.
-
-## Installation
-
-You can use your favorite JavaScript package manager to install this package.
-
-```bash
-# npm
-npm install @greenwood/plugin-renderer-puppeteer --save-dev
-
-# yarn
-yarn add @greenwood/plugin-renderer-puppeteer --dev
-```
+           node-version: "18.x"
 
-> This package assumes you already have `@greenwood/cli` installed.
-
-## Usage
-Add this plugin to your _greenwood.config.js_.
-
-```javascript
-import { greenwoodPluginRendererPuppeteer } from '@greenwood/plugin-renderer-puppeteer';
-
-export default {
-  ...
-
-  plugins: [
-    greenwoodPluginRendererPuppeteer()
-  ]
-}
 ```
 
-Now, when running `greenwood build`, all your pages will get run through Puppeteer and any JavaScript / Web Components that you author will get a one time pass execution and the resulting HTML generated from that process will be captured and further optimized through Greenwood's build pipeline.
\ No newline at end of file
+See the Puppeteer [Troubleshooting docs](https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md) for more info on setting up your specific environment.
\ No newline at end of file
diff --git a/packages/plugin-renderer-puppeteer/package.json b/packages/plugin-renderer-puppeteer/package.json
index 221698e9f..5181ae762 100644
--- a/packages/plugin-renderer-puppeteer/package.json
+++ b/packages/plugin-renderer-puppeteer/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "Puppeteer"
   ],
   "main": "src/index.js",
diff --git a/packages/plugin-typescript/README.md b/packages/plugin-typescript/README.md
index c99533b4a..c6539ccfc 100644
--- a/packages/plugin-typescript/README.md
+++ b/packages/plugin-typescript/README.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-A Greenwood plugin for writing [**TypeScript**](https://www.typescriptlang.org/).   There is still a [little more work](https://github.com/ProjectEvergreen/greenwood/issues/658) we would like to do but this plugin should be suitable for general usage.
+A Greenwood plugin for writing [**TypeScript**](https://www.typescriptlang.org/). For more information and complete docs on Greenwood, please visit [our website](https://www.greenwoodjs.dev).
 
 > This package assumes you already have `@greenwood/cli` installed.
 
@@ -10,18 +10,20 @@ A Greenwood plugin for writing [**TypeScript**](https://www.typescriptlang.org/)
 
 You can use your favorite JavaScript package manager to install this package.
 
-_examples:_
 ```bash
 # npm
-npm install @greenwood/plugin-typescript --save-dev
+$ npm i -D @greenwood/plugin-typescript
 
 # yarn
-yarn add @greenwood/plugin-typescript --dev
+$ yarn add @greenwood/plugin-typescript --dev
+
+# pnpm
+$ pnpm add -D @greenwood/plugin-typescript
 ```
 
 ## Usage
 
-Add this plugin to your _greenwood.config.js_.
+Add this plugin to your _greenwood.config.js_:
 
 ```javascript
 import { greenwoodPluginTypeScript } from '@greenwood/plugin-typescript';
@@ -35,7 +37,7 @@ export default {
 };
 ```
 
-Then, you can write some TypeScript!
+Now, you can write some TypeScript!
 ```ts
 import { html, css, LitElement, customElement, property } from 'lit-element';
 
diff --git a/packages/plugin-typescript/package.json b/packages/plugin-typescript/package.json
index aaf3922d8..636971016 100644
--- a/packages/plugin-typescript/package.json
+++ b/packages/plugin-typescript/package.json
@@ -9,9 +9,10 @@
   "keywords": [
     "Greenwood",
     "Static Site Generator",
+    "Server Side Rendering",
     "Full Stack Web Development",
+    "Serverless",
     "Web Components",
-    "NodeJS",
     "TypeScript"
   ],
   "main": "src/index.js",
diff --git a/www/README.md b/www/README.md
index a26ed4b88..8640e13ad 100644
--- a/www/README.md
+++ b/www/README.md
@@ -1,6 +1,8 @@
 # @greenwood/www
 
+> _**THIS PACKAGE HAS BEEN DEPRECATED**_.  New repo for the Greenwood website located at https://github.com/ProjectEvergreen/www.greenwoodjs.dev
+
 ## Overview
 Website "package" for Greenwood.  This is a private package / workspace used for maintaining the dependencies and source code for the [Greenwood website](https://www.greenwoodjs.io/).  
 
-> This project has a lot of great oppourtunities for first time contributors.  If you are interested, please check out our [related list of good first issues](https://github.com/ProjectEvergreen/greenwood/issues?utf8=%E2%9C%93&q=label%3A%22good+first+issue%22+label%3Awebsite) and review our [contributing docs](https://github.com/ProjectEvergreen/greenwood/blob/master/.github/CONTRIBUTING.md) for how to get started.
\ No newline at end of file
+> This project has a lot of great opportunities for first time contributors.  If you are interested, please check out our [related list of good first issues](https://github.com/ProjectEvergreen/greenwood/issues?utf8=%E2%9C%93&q=label%3A%22good+first+issue%22+label%3Awebsite) and review our [contributing docs](https://github.com/ProjectEvergreen/greenwood/blob/master/.github/CONTRIBUTING.md) for how to get started.
\ No newline at end of file
diff --git a/www/layouts/app.html b/www/layouts/app.html
index 34e6cbacb..422c2b7dc 100644
--- a/www/layouts/app.html
+++ b/www/layouts/app.html
@@ -7,8 +7,8 @@
     <meta name="description" content="Your workbench for the web, focused on supporting modern web standards and development to help you create your next project."/>
     <meta name="twitter:site" content="@PrjEvergreen"/>
     <meta property="og:type" content="website"/>
-    <meta property="og:url" content="https://www.greenwoodjs.io"/>
-    <meta property="og:image" content="https://www.greenwoodjs.io/assets/greenwood-logo-og.png"/>
+    <meta property="og:url" content="https://www.greenwoodjs.dev"/>
+    <meta property="og:image" content="https://www.greenwoodjs.dev/assets/greenwood-logo-og.png"/>
     <meta property="og:description" content="Your workbench for the web, focused on supporting modern web standards and development to help you create your next project."/>
     <meta name="viewport" content="width=device-width, initial-scale=1"/>
     <meta name="mobile-web-app-capable" content="yes"/>