diff --git a/pagefind/index/en-US_8a90e1c.pf_index b/pagefind/index/en-US_8a90e1c.pf_index
new file mode 100644
index 0000000..c15c7cb
Binary files /dev/null and b/pagefind/index/en-US_8a90e1c.pf_index differ
diff --git a/pagefind/pagefind-entry.json b/pagefind/pagefind-entry.json
index ddabde3..1d6f507 100644
--- a/pagefind/pagefind-entry.json
+++ b/pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"1.2.0","languages":{"en-US":{"hash":"en-US_78d61b444c90f","wasm":"en-US","page_count":9}}}
\ No newline at end of file
+{"version":"1.2.0","languages":{"en-US":{"hash":"en-US_8e1b8a1382818","wasm":"en-US","page_count":7}}}
\ No newline at end of file
diff --git a/pagefind/pagefind.en-US_8e1b8a1382818.pf_meta b/pagefind/pagefind.en-US_8e1b8a1382818.pf_meta
new file mode 100644
index 0000000..23e342b
Binary files /dev/null and b/pagefind/pagefind.en-US_8e1b8a1382818.pf_meta differ
diff --git a/presentations/presentation1.html b/presentations/presentation1.html
index 415daae..208608c 100644
--- a/presentations/presentation1.html
+++ b/presentations/presentation1.html
@@ -114,20 +114,21 @@ <h1 class="title">Metadata Tools</h1>
 <h1>What is the Metadata Tools Project?</h1>
 <ul>
 <li>An ESM (ECMAScript Module) for working with identifiers used by
-libraries and archives</li>
+libraries and archives in TypeScript</li>
 </ul>
 </div>
 <div id="why-create-the-metadata-tools-project"
 class="slide section level1">
 <h1>Why create the Metadata Tools Project?</h1>
 <p>If you working in Python you can use <a
-href="https://idutils.readthedocs.io/">idutils</a>. The problem is it is
-only for Python. I needed a similar capability I can use server side
-(via Deno) and browser side (via transpiled JavaScript). I can even use
-a WASM compiled version of Metadata Tools in other languages, even in
-Python!</p>
-<p>Metadata Tools seeks to be very portable to the langauge or
-environment you need to use it in.</p>
+href="https://idutils.readthedocs.io/">idutils</a>. I needed a similar
+capabilities in non-Python code spaces like my web browser or <a
+href="https://deno.com">Deno</a>. With Metadata Tools perform similar
+function server side (via Deno) and browser side, in other languages via
+compile to WASM or in the web browser via transpilation to
+JavaScript.</p>
+<p>Metadata Tools seeks to be very portable across languages that
+support WASM, native binary executables and in web browsers.</p>
 </div>
 <div id="what-identifiers-does-it-support" class="slide section level1">
 <h1>What identifiers does it support?</h1>
@@ -190,5 +191,14 @@ <h1>Example output</h1>
 ORCID https://ror.org/00mpvse27 -&gt; is valid? true -&gt; verfied? true
 ORCID 10.1128/jmbe.00128-21 -&gt; is valid? true -&gt; verfied? true</code></pre>
 </div>
+<div id="roadmap" class="slide section level1">
+<h1>Roadmap?</h1>
+<p>Metadata Tools is still at the early experimental stage. Some ideas
+for future directions include targetting WASM in additional to a native
+binary for <code>mdt</code> cli. This would allow Metadata Tools to be
+used from languages that can import and run WASM modules (e.g. Rust,
+Python and Go).</p>
+<p>Add additional identifier support as needed.</p>
+</div>
 </body>
 </html>
diff --git a/presentations/presentation1.md b/presentations/presentation1.md
index be2c449..52aded7 100644
--- a/presentations/presentation1.md
+++ b/presentations/presentation1.md
@@ -9,11 +9,10 @@ urlcolor: blue
 linkstyle: bold
 aspectratio: 169
 createDate: 2024-12-06
-#updateDate: 2024-11-06
+updateDate: 2024-11-09
 draft: true
 #pubDate: 2024-11-15
 place: Caltech
-#date: November 15, 2024
 section-titles: false
 toc: true
 keywords: [ "metadata", "identifiers", "normalizaiton", "validation", "verification", "TypeScript", "Deno" ]
@@ -22,14 +21,15 @@ url: "https://caltechlibrary.github.io/metadatatools"
 
 # What is the Metadata Tools Project?
 
-- An ESM (ECMAScript Module) for working with identifiers used by libraries and archives
+- An ESM (ECMAScript Module) for working with identifiers used by libraries and archives in TypeScript
 
 # Why create the Metadata Tools Project?
 
-If you working in Python you can use [idutils](https://idutils.readthedocs.io/). The problem is it is only for Python.  I needed a similar capability I can use server side (via Deno) and browser side (via transpiled JavaScript). I can even
-use a WASM compiled version of Metadata Tools in other languages, even in Python!
+If you working in Python you can use [idutils](https://idutils.readthedocs.io/). I needed a similar capabilities in non-Python code spaces
+like my web browser or [Deno](https://deno.com). With Metadata Tools perform similar function server side (via Deno) and browser side,
+in other languages via compile to WASM or in the web browser via transpilation to JavaScript.
 
-Metadata Tools seeks to be very portable to the langauge or environment you need to use it in.
+Metadata Tools seeks to be very portable across languages that support WASM, native binary executables and in web browsers.
 
 # What identifiers does it support?
 
@@ -94,4 +94,12 @@ ORCID https://ror.org/00mpvse27 -> is valid? true -> verfied? true
 ORCID 10.1128/jmbe.00128-21 -> is valid? true -> verfied? true
 ```
 
+# Roadmap?
+
+Metadata Tools is still at the early experimental stage.  Some ideas
+for future directions include targetting WASM in additional to a native
+binary for `mdt` cli. This would allow Metadata Tools to be used from
+languages that can import and run WASM modules (e.g. Rust, Python and Go).
+
+Add additional identifier support as needed.