basic TypeScript callouts within reference docs

Author: thescientist13

src/pages/docs/reference/appendix.md

@@ -1,11 +1,27 @@
 ---
 layout: docs
-order: 5
+order: 4
 tocHeading: 2
 ---
 
 # Appendix
 
+## Types
+
+In addition to [supporting TypeScript](/docs/resources/typescript/) out of the box, Greenwood also exports a number of useful types that you can use if authoring your configuration files, plugins, etc as TypeScript. You can find all available types for the CLI [here](https://github.com/ProjectEvergreen/greenwood/blob/master/packages/cli/src/types/index.d.ts) including types for configuration, content as data APIs, graph and compilation objects, plugins, and more. Each of Greenwood's plugin will also provide their own set of types within their package at _src/types/index.d.ts_.
+
+For example, here is how to author a TypeScript based configuration file:
+
+```ts
+import type { Config } from "@greenwood/cli";
+
+const config: Config = {
+  prerender: true,
+};
+
+export default config;
+```
+
 ## Build Output
 
 Greenwood produces a consistent build output that typically mirrors the source directory as it persists all file naming, albeit with hashes included. For static content, this can be used by static hosting sites with no additional configuration, on serverless hosting with our adapters, or self-hosted.
@@ -88,7 +104,7 @@ It is fine-tuned for creating Light and Shadow DOM based custom elements. The fu
 - `customElements.define`
 - `attachShadow`
 - `innerHTML`
-- ` [get|set|has]Attribute`
+- `[get|set|has]Attribute`
 - `<template>` / DocumentFragment
 - `addEventListener` (as a no-op)
 - `CSSStyleSheet` (all methods act as no-ops on the server)

src/pages/docs/reference/configuration.md

@@ -11,6 +11,7 @@ This section details all the supported configuration options available with **Gr
 Below is a _greenwood.config.js_ file reflecting default values:
 
 ```js
+/** @type {import('@greenwood/cli').Config} */
 export default {
   activeContent: false,
   basePath: "",

src/pages/docs/reference/plugins-api.md

@@ -10,6 +10,8 @@ tocHeading: 2
 
 Below are the various plugin types you can use to extend and further customize Greenwood.
 
+> Types are available for all plugin constructs. Please see our [reference docs](/docs/reference/appendix/#types) to learn more.
+
 ## Overview
 
 Each plugin must return a function that has the following three properties:
@@ -72,6 +74,7 @@ An adapter plugin is simply an `async` function that gets invoked by the Greenwo
 <app-ctc-block variant="snippet">
 
   ```js
+  /** @type {import("@greenwood/cll").AdapterPlugin} */
   const greenwoodPluginMyPlatformAdapter = () => {
     return {
       type: "adapter",
@@ -93,7 +96,7 @@ An adapter plugin is simply an `async` function that gets invoked by the Greenwo
 
 ### Example
 
-The most common use case is to "shim" in a hosting platform handler function in front of Greenwood's, which is based on two parameters of `Request` / `Response`. In addition, producing any hosting provided specific metadata is also doable at this stage.
+The most common use case is to "shim" in a hosting platform handler function in front of Greenwood's, which is based on standard `Request` / `Response` objects. In addition, producing any hosting provided specific metadata is also doable at this stage.
 
 Here is an example of the "generic adapter" created for Greenwood's own internal test suite.
 
@@ -224,6 +227,7 @@ Your plugin might look like this:
   *     acme-theme-pack.js
   *     package.json
   */
+  /** @type {import("@greenwood/cll").ContextPlugin} */
   export function myContextPlugin() {
     return {
       type: "context",
@@ -259,6 +263,7 @@ This plugin supports providing an array of "paired" URL objects that can either
 <app-ctc-block variant="snippet" heading="my-copy-plugin.js">
 
   ```js
+  /** @type {import("@greenwood/cll").CopyPlugin} */
   export function myCopyPlugin() {
     return {
       type: "copy",
@@ -344,6 +349,7 @@ This plugin expects to be given a path to a module that exports a function to ex
 <app-ctc-block variant="snippet" heading="my-renderer-plugin.js">
 
   ```js
+  /** @type {import("@greenwood/cll").RendererPlugin} */
   const greenwoodPluginMyCustomRenderer = () => {
     return {
       type: "renderer",
@@ -416,6 +422,7 @@ A [resource "interface"](https://github.com/ProjectEvergreen/greenwood/tree/mast
     // lifecycles go here
   }
 
+  /** @type {import("@greenwood/cll").ResourcePlugin} */
   export function myExampleResourcePlugin(options = {}) {
     return {
       type: "resource",
@@ -715,6 +722,7 @@ Simply use the `provider` method to return an array of Rollup plugins:
 
   const packageJson = JSON.parse(fs.readFileSync("./package.json", "utf-8"));
 
+  /** @type {import("@greenwood/cll").RollupPlugin} */
   export function myRollupPlugin() {
     const now = new Date().now();
 
@@ -798,6 +806,7 @@ The below is an excerpt of [Greenwood's internal LiveReload server](https://gith
     }
   }
 
+  /** @type {import("@greenwood/cll").ServerPlugin} */
   export function myServerPlugin(options = {}) {
     return {
       type: "server",
@@ -824,6 +833,7 @@ This plugin supports providing an array of "page" objects that will be added as
 <app-ctc-block variant="snippet" heading="my-source-plugin.js">
 
   ```js
+  /** @type {import("@greenwood/cll").SourcePlugin} */
   export const customExternalSourcesPlugin = () => {
     return {
       type: "source",