diff --git a/README.md b/README.md
index 66b36ed..c73bbb7 100644
--- a/README.md
+++ b/README.md
@@ -5,6 +5,7 @@
 | [![NuGet Package](https://img.shields.io/nuget/v/Ooui.svg)](https://www.nuget.org/packages/Ooui) | [Ooui](https://www.nuget.org/packages/Ooui) | Core library with HTML elements and a server |
 | [![NuGet Package](https://img.shields.io/nuget/v/Ooui.AspNetCore.svg)](https://www.nuget.org/packages/Ooui.AspNetCore) | [Ooui.AspNetCore](https://www.nuget.org/packages/Ooui.AspNetCore) | Integration with ASP.NET Core |
 | [![NuGet Package](https://img.shields.io/nuget/v/Ooui.Forms.svg)](https://www.nuget.org/packages/Ooui.Forms) | [Ooui.Forms](https://www.nuget.org/packages/Ooui.Forms) | Xamarin.Forms backend using Ooui |
+| [![NuGet Package](https://img.shields.io/nuget/v/Ooui.Wasm.svg)](https://www.nuget.org/packages/Ooui.Wasm) | [Ooui.Wasm](https://www.nuget.org/packages/Ooui.Wasm) | Package your app into a web assembly |
 
 Ooui (pronounced *weee!*) is a small cross-platform UI library for .NET that uses web technologies.
 
@@ -84,19 +85,30 @@ With just that code, a web server that serves the HTML and web socket logic nece
 Ooui has been broken up into several packages to increase the variety of ways that it can be used. Here are some combinations to help you decide which way is best for you.
 
 <table>
-<thead><tr><th>Ooui</th><th>Ooui.AspNetCore</th><th>Ooui.Forms</th><th></th></tr></thead>
+<thead><tr><th>Ooui</th><th>Ooui.AspNetCore</th><th>Ooui.Forms</th><th>Ooui.Wasm</th><th></th></tr></thead>
 
 <tr>
-<td>&check;</td><td></td><td></td><td><a href="https://github.com/praeclarum/Ooui/wiki/Write-the-UI-using-the-web-DOM-and-use-the-built-in-web-server">Write the UI using the web DOM and use the built-in web server</a></td>
+<td>&check;</td><td></td><td></td><td></td><td><a href="https://github.com/praeclarum/Ooui/wiki/Write-the-UI-using-the-web-DOM-and-use-the-built-in-web-server">Web DOM with the built-in web server</a></td>
 </tr>
+
 <tr>
-<td>&check;</td><td>&check;</td><td></td><td>Write the UI using the web DOM and serve it with ASP.NET Core</td>
+<td>&check;</td><td>&check;</td><td></td><td></td><td>Web DOM with ASP.NET Core</td>
 </tr>
+
 <tr>
-<td>&check;</td><td>&check;</td><td>&check;</td><td>Write the UI using Xamarin.Forms and serve it with ASP.NET Core</td>
+<td>&check;</td><td>&check;</td><td>&check;</td><td></td><td>Xamarin.Forms with ASP.NET Core</td>
 </tr>
+
 <tr>
-<td>&check;</td><td></td><td>&check;</td><td>Write the UI using Xamarin.Forms and use the built-in web server</td>
+<td>&check;</td><td></td><td>&check;</td><td></td><td>Xamarin.Forms with the built-in web server</td>
+</tr>
+
+<tr>
+<td>&check;</td><td></td><td></td><td>&check;</td><td>Web DOM with Web Assembly</td>
+</tr>
+
+<tr>
+<td>&check;</td><td></td><td>&check;</td><td>&check;</td><td>Xamarin.Forms with Web Assembly</td>
 </tr>
 
 </table>
@@ -108,6 +120,8 @@ When the user requests a page, the page will connect to the server using a web s
 
 When the user clicks or otherwise interacts with the UI, those events are sent back over the web socket so that your code can deal with them.
 
+In the case of web assembly, this same dataflow takes place. However, sockets are not used as all communication is done locally in the browser process.
+
 
 ## Contributing