diff --git a/README.md b/README.md
index d6ea302..fb47f0c 100644
--- a/README.md
+++ b/README.md
@@ -4,12 +4,15 @@ This repository holds all of the packages for creating shareable, perceptually-b
 
 This repository is structured as a yarn monorepo. It contains separate packages for all of the theme generation, management, and applications. To use thematic in your app, you should only need to install the relevant packages for your use case(s).
 
-The webapp package is a guide for everything Thematic. In particular, it comprises:
+The [webapp](./packages/webapp/) package is a guide for everything Thematic. In particular, it comprises:
 
 - A running application for configuring theme parameters
 - An example app using thematic itself, so you can see what controls and charts look like
+- The ability to download theme JSON and text files that are compatible with a variety of platforms (Fluent, Office, Power BI, GIMP)
 - A variety of code examples to explore showing how to use thematic in practice
 
+This webapp is deployed as the [github.io site](https://microsoft.github.io/thematic/) for the repo, so you can use it directly without cloning anything yourself.
+
 ## Organization
 
 Our thematic packages are published under the `@thematic` scope.
@@ -19,18 +22,18 @@ These are the core Thematic libraries, see individual README.md files for greate
 - [@thematic/color](packages/color/README.md) - this contains color conversion and scale generation logic. If you need functions to convert between color spaces, this is the place. This also has the color scheme compute logic that dictates how all of the color scales are generated from a few selected input parameters.
 - [@thematic/core](packages/core/README.md) - this is the main package for working with Themes. You can load them from a Theme JSON specification, then use the attributes directly in your app to apply the generated colors in a consistent way. We've used SVG notation for all of our mark properties (e.g., 'fill').
 - [@thematic/d3](packages/d3/README.md) - this package has helpers to apply the themes to viz created with [d3](https://d3js.org/). We provide a variety of SVG mark primitives that operate on a d3 Selection, so you can apply the theme elements using `selection.call(fn, [params])` as needed.
-- [@thematic/fluent](packages/fluent/README.md) - helpers for applying Thematic to the [Fluent UI library](https://developer.microsoft.com/en-us/fluentui#/controls/web)
+- [@thematic/fluent](packages/fluent/README.md) - helpers for applying Thematic to the [Fluent UI library](https://developer.microsoft.com/en-us/fluentui#/controls/web), including a React context provider that injects a Fluent-compatible theme instance.
 - [@thematic/react](packages/react/README.md) - helpers to bootstrap theming into React-based apps, particularly a provider and context hook (useThematic) for grabbing the theme anywhere it is needed.
 - [@thematic/vega](packages/vega/README.md) - this has a helper that applies our theme spec as default configuration for Vega charts so they automatically adopt the theme.
 - [@thematic/webapp](packages/webapp/README.md) - this is the theme editor webapp that you can run or access at https://microsoft.github.io/thematic.
 
 ## Getting Started
 
-If you want to run locally and work on the app or any theme components, you can run the whole thing from the root folder. The web app will run using `yarn start:webapp` as with our typical development structure, and changes to any of the other packages will be reflected live. See the Available Scripts section below.
+If you want to run locally and work on the app or any theme components, you can run the whole thing from the root folder. The web app will run using `yarn start` as with our typical development structure, and changes to any of the other packages will be reflected live. See the Available Scripts section below.
 
 ## Publishing
 
-Commits to `main` will automatically deploy to the hosted website. Pull requests should use `yarn version check --interactive` to create semantic versioning documents describing the impact of the PR. When a release is ready, run`yarn release_all` to publish packages to npm.
+Commits to `main` will automatically deploy to the hosted website. Pull requests should use `yarn version check --interactive` to create semantic versioning documents describing the impact of a PR. When a release is ready, run `yarn release` to publish packages to npm.
 
 ## Available Scripts
 
@@ -48,13 +51,13 @@ You will also see any lint errors in the console.
 
 Launches the test runner using Jest.
 
-### `yarn build:`
+### `yarn build`
 
-Builds packages for production to their respective `dist` and `lib` folders. Note that the webapp uses a `bundle` command more appropriate to creating an optimized web bundle. CI systems will want to invoke both of these to produce complete
+Builds packages for production to their respective `dist` folders.
 
-### `yarn clean:`
+### `yarn clean`
 
-Cleans out the node_modules and built lib directories for every package.
+Cleans out the node_modules and built dist directories for every package.
 
 # Contributing
 
diff --git a/packages/core/README.md b/packages/core/README.md
index fc49e87..7e23116 100644
--- a/packages/core/README.md
+++ b/packages/core/README.md
@@ -48,3 +48,15 @@ For example:
 	const r0 = scaledCircle.radius(0) // 1
 	const r1 = scaledCircle.radius(1) // 10
 ```
+
+### Default themes
+
+This package includes a handful of default themes to make it easy to get started. You can use the `loadById` function to get one of these by name. Otherwise, additional loader methods are present to generate brand new themes from raw input parameters.
+
+## Extensions
+
+This package also includes a few extensions to create theme objects that are compatible with other systems. These extensions are essentially just transform functions that accept a Theme instance and return any other object. We've included a few that we use in our projects:
+
+- gimp: this generates a [GIMP-compatible](https://docs.gimp.org/en/gimp-concepts-palettes.html) palette text file. Usable in other apps that support this format such as Inkscape.
+- office: this generates a set of standard colors for Microsoft Office themes. It's paricularly useful for generating PowerPoints that share the same colors as data visualizations that you may include. Note that Office does not have an importable JSON feature; we have used custom scripts to merge Thematic Office colors into PowerPoint XML template files.
+- powerbi: this creates a [Power BI-compatible JSON file](https://docs.microsoft.com/en-us/power-bi/create-reports/desktop-report-themes#import-custom-report-theme-files) that can be uploaded into your Power BI reports to set the theme data colors.
diff --git a/packages/fluent/README.md b/packages/fluent/README.md
index 96c4382..36c8060 100644
--- a/packages/fluent/README.md
+++ b/packages/fluent/README.md
@@ -61,3 +61,9 @@ Also included in this package is a Provider component that wraps both ThematicPr
 		)
 	}
 ```
+
+The combined themes will be available throughout your app using the context hook of your choice. Specifically:
+
+- to access it as a Thematic Theme, use `useThematic` from the [react](../react/) package.
+- to access it as a Fluent ITheme, use the `useTheme` [hook](https://github.com/microsoft/fluentui/blob/0fac2d7a6f35c5fcebaf30da68b9604410fe0eb9/packages/react/src/utilities/ThemeProvider/useTheme.ts) provided by Fluent.
+- to access it as a combined theme with both of the above interfaces merged, use the `useThematicFluent` hook in this package (handy for passing to other context providers like styled-components where you may need content from both themes).