build: mapping global documentation to explicit Open Source distribution channels (npm & jsdelivr CDN)

Author: Corey B

README.md

@@ -40,19 +40,24 @@ The OpenFDD ecosystem provides a full suite of typescript/javascript libraries t
 ### 1. Composing & Building (`node-fdd`)
 To build an `.fdd` file from your backend, you pack your Cryptographic JSON, your Mutable JSON, and your HTML template securely into the unified `.fdd` document wrapper:
 ```bash
-node lib/node-fdd/src/pack.js template.html fdd-data.json user-notes.json output.fdd
+# Install the Official OpenFDD CLI globally
+npm install -g node-fdd
+
+# Pack the payload securely into the FDD container
+fdd-pack template.html fdd-data.json user-notes.json output.fdd
 ```
 
 ### 2. Cryptographic Signing
 If you are the official Issuer (e.g. a Bank), you must mathematically sign the JSON payload before packing it:
 ```bash
-node lib/node-fdd/src/sign.js path/to/privateKey.pem fdd-data.json 
+fdd-sign path/to/privateKey.pem fdd-data.json 
 ```
 
 ### 3. Parsing & Viewing Natively (`fdd-js`)
-To seamlessly render `.fdd` containers natively on your own web-platform without requiring plugins, simply reference the native layout library within your DOM. It evaluates the No-JS constraints, routes Ephemeral State actions securely, and renders the Document safely!
+To seamlessly render `.fdd` containers natively on your own web-platform without requiring plugins, simply reference the native layout library via our global jsDelivr CDN inside your DOM. It evaluates the No-JS constraints, routes Ephemeral State actions securely, and renders the Document safely!
 ```html
-<script src="/path/to/lib/fdd-js/src/fdd.js"></script>
+<!-- Hosted securely out of explicit version tags to prevent un-authorized layout breaking -->
+<script src="https://cdn.jsdelivr.net/gh/Spuds0588/open-fdd@v1.1.0/lib/fdd-js/src/fdd.js"></script>
 ```
 
 ### 4. Viewing Locally (`Chrome Extension`)

examples/court_judgment.fdd

@@ -42,7 +42,7 @@
         .history { list-style-type: none; padding: 0; font-size: 1.1rem; }
         .history li { border-left: 3px solid #ccc; margin-bottom: 10px; padding-left: 15px; }
         .history .date { font-weight: bold; color: #444; margin-right: 15px;}
-        .notes-area { width: 100%; height: 80px; margin-top: 5px; box-sizing: border-box; border-radius: 8px; border: 1px dashed #cbd5e1; padding: 10px; font-family: Arial; resize: none; background: #fdfdfd;}
+        .notes-area { width: 100%; height: 80px; margin-top: 5px; box-sizing: border-box; border-radius: 8px; border: 1px dashed #cbd5e1; padding: 10px; font-family: Arial; resize: none; background: #fdfdfd; color: #111;}
       </style>
       <div class="verified">✓ Official Court Record • Cryptographically Sealed Header</div>
       <h1 style="text-transform: uppercase;">State of Minnesota</h1>

lib/node-fdd/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-fdd",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Server-side utility for OpenFDD signing and packing",
   "main": "src/pack.js",
   "type": "module",

site/index.html

@@ -178,15 +178,15 @@ <h2>Tooling & Ecosystem Guide</h2>
             <ul class="points-list">
                 <li>
                     <strong>1. Composing & Building (<code>node-fdd</code>)</strong>
-                    To build an `.fdd` file from your backend, you seamlessly pack your Cryptographic JSON, your Mutable JSON, and your HTML template securely into the unified wrapper using the CLI runtime pipeline.
+                    To build an `.fdd` file natively on your backend, utilize the official <code>npm install -g node-fdd</code> library. You seamlessly pass your Cryptographic JSON, your Mutable JSON, and your HTML template securely via the <code>fdd-pack</code> CLI pipeline.
                 </li>
                 <li>
                     <strong>2. Cryptographic Signing</strong>
-                    Official Issuers securely map Ed25519 signatures hashing the exact JSON payload blocks guaranteeing complete 100% data integrity bindings.
+                    Official Issuers simply bind Ed25519 signatures directly against the <code>#fdd-data</code> block using the <code>fdd-sign</code> utility, guaranteeing mathematically verified data integrity.
                 </li>
                 <li>
                     <strong>3. Parsing & Viewing Natively (<code>fdd-js</code>)</strong>
-                    Seamlessly render `.fdd` containers natively on your own web-platform by referencing the native library within your DOM. It evaluates No-JS constraints and securely routes Ephemeral State actions dynamically.
+                    To seamlessly render `.fdd` single-file applications effortlessly inside your own products, simply load the native parser via the global CDN! Pinning the tag to the verified release (e.g., <code>https://cdn.jsdelivr.net/gh/Spuds0588/open-fdd@v1.1.0/lib/fdd-js/src/fdd.js</code>) guarantees flawless declarative constraint routing!
                 </li>
                 <li>
                     <strong>4. Viewing Locally (`Chrome Extension`)</strong>