Update deployment methods documentation and improve home page content; correct README link for webviewer package

Author: eluce2

apps/docs/content/docs/cli/webviewer/deployment-methods.mdx

@@ -9,16 +9,11 @@ There are many ways to deploy WebViewer code to your FileMaker file, and each me
 
 This technique stores the WebViewer code as **data** directly in your FileMaker file. This is the default method for most WebViewer integrations and the method used when setting up a new project with the ProofKit CLI.
 
-#### Pros
-
-- Simple to setup and understand
-- Works offline
-
-#### Cons
-
-- Doesn't survive data migrations
-- Unable to use server-side JavaScript libraries
-- Updates requires the web developer to have access to the FileMaker file
+| Pros                                   | Cons                                                                 |
+|----------------------------------------|----------------------------------------------------------------------|
+| ✅ Simple to setup and understand      | ⚠️ Doesn't survive data migrations                                   |
+| ✅ Works offline                      | ⚠️ Unable to use server-side JavaScript libraries                    |
+|                                        | ⚠️ Updates requires the web developer to have access to the FileMaker file |
 
 #### Considerations
 
@@ -36,17 +31,11 @@ To get around the data migration issue, you have a few options:
 
 In the other extreme, you can host the WebViewer code like you would any other web application. If you're only using the @proofkit/webviewer library, you can still do this without any security concerns because the data won't load unless the web page is loaded in your FileMaker solution in a WebViewer.
 
-#### Pros
-
-- Code survives data migrations
-- Can use server-side JavaScript libraries
-- Can deploy updates to the web code without a data migration
-
-#### Cons
-
-- Requires a web server, or hosting account with Vercel (or similar)
-- Code is de-coupled from the FileMaker file, which may cause schema to be out of sync if you're not careful
-- Requires a persistent internet connection
+| Pros                                   | Cons                                                                 |
+|----------------------------------------|----------------------------------------------------------------------|
+| ✅ Code survives data migrations       | ⚠️ Requires a web server, or hosting account with Vercel (or similar) |
+| ✅ Can use server-side JavaScript libraries | ⚠️ Code is de-coupled from the FileMaker file, which may cause schema to be out of sync if you're not careful |
+| ✅ Can deploy updates to the web code without a data migration | ⚠️ Requires a persistent internet connection |
 
 #### Implementation
 
@@ -66,13 +55,19 @@ Alternatively, you can just install the `@proofkit/webviewer` library into a sta
 
 This technique is a hybrid of the embedded and hosted methods. Essentially, the code is embedded in the FileMaker file, but you also host a copy of it on another web server. The FileMaker file (or the web code) can check for updates and download the latest version directly to the the neccesary field.
 
-#### Pros
-
-- Enables a self-updating solution
-- Great for non-hosted files, or a vertical-market solution where each copy may need a different version of the WebViewer code
-- Can work offline, after the initial download
-
-#### Cons
-
-- Requires a server to host a copy of the code (but can be a simple static file host or CDN)
-- More complex to setup and maintain
+| Pros                                   | Cons                                                                 |
+|----------------------------------------|----------------------------------------------------------------------|
+| ✅ Enables a self-updating solution    | ⚠️ Requires a server to host a copy of the code (but can be a simple static file host or CDN) |
+| ✅ Great for non-hosted files, or a vertical-market solution where each copy may need a different version of the WebViewer code | ⚠️ More complex to setup and maintain |
+| ✅ Can work offline, after the initial download |                                                                      |
+
+## Comparison Table
+
+| Feature                                    | Embedded         | Hosted           | Downloaded       |
+|--------------------------------------------|------------------|------------------|------------------|
+| **Simple Setup**                           | ✅               | ⚠️ (needs hosting) | ⚠️ (hybrid setup) |
+| **Survives Data Migrations**               | ❌               | ✅               | ✅               |
+| **Works Offline** | ✅           | ❌               | ✅ (after download) |
+| **Web Server Required?**                 | No               | Yes               | Simple (static file host or CDN) |
+| **Can Use Server-side JS Libraries**       | ❌               | ✅               | ❌               |
+| **Update Method** | ⚠️ File migration (downtime) | ✅ Simplest (no downtime) | ✅ Self-updating, no downtime |

apps/docs/content/docs/webviewer/index.mdx

@@ -11,7 +11,7 @@ import { Accordion, Accordions } from "fumadocs-ui/components/accordion";
 
 The goal of this package is to make it easy to work with FileMaker scripts and data when building a custom webviewer integration. @proofkit/webviewer works only inside of webviewer and allows you to interact with your FileMaker solution via local scripts.
 
-This is a **client-side** package, meant to run specifically in a FileMaker WebViewer, but it can still be used in a hosted web app, such as Next.js. However, it will cause errors if loaded in a standard browser. For more information about deployment strategies, see the [Deployment](/docs/deployment) page.
+This is a **client-side** package, meant to run specifically in a FileMaker WebViewer, but it can still be used in a hosted web app, such as Next.js. However, it will cause errors if loaded in a standard browser. For more information about deployment strategies, see the [Deployment](/docs/cli/webviewer/deployment-methods) guide (from the CLI docs).
 
 For web-based applications where you're looking to interact with the Data API using a network request, check out the [@proofkit/fmdapi](/docs/fmdapi) package instead.
 

apps/docs/src/app/(home)/page.tsx

@@ -36,15 +36,21 @@ export default function HomePage() {
         </div>
 
         <div className="mt-8 space-y-8 text-center w-full ">
-          <h1 className="text-4xl font-bold">Welcome</h1>
+          <h1 className="text-4xl font-bold">
+            A collection of tools for FileMaker-aware JavaScript applications
+          </h1>
           <p className="text-xl text-gray-500 font-medium">
-            A collection of tools for building great JavaScript applications
+            For new and experienced developers alike, ProofKit is the best way
+            build web apps connected to FileMaker data, or full interfaces in a
+            FileMaker webviewer.
           </p>
 
           <Cards className="px-4 text-left">
             <Card icon={<Terminal />} title="ProofKit CLI" href="/docs/cli">
               A command line tool to start a new project, or easily apply
-              templates and common patterns.
+              templates and common patterns with{" "}
+              <span className="underline">no JavaScript experience</span>{" "}
+              required.
             </Card>
             <Card icon={<Code />} href="/docs/typegen" title={"Typegen"}>
               Automatically generate runtime validators and TypeScript files
@@ -63,8 +69,8 @@ export default function HomePage() {
               title="FileMaker Webviewer"
               href="/docs/webviewer"
             >
-              Use async functions in WebViewer code to run and get results from
-              FileMaker scripts.
+              Use async functions in WebViewer code to execute and get the
+              result of a FileMaker script.
             </Card>
           </Cards>
 

packages/webviewer/README.md

@@ -4,7 +4,7 @@
 
 This is a fetch replacement for calling a FileMaker script and getting a promise back in return. Or you can use callback if you want instead.
 
-**[Documentation Website](https://proofkit.com/docs/webviewer)**
+**[Documentation Website](https://proofkit.dev/docs/webviewer)**
 
 Install via your package manager of choice:
 

packages/webviewer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@proofkit/webviewer",
-  "version": "3.0.2",
+  "version": "3.0.4",
   "description": "A utility to fetch data from FileMaker webviewer",
   "type": "module",
   "files": [