|
3 | 3 | <head> |
4 | 4 | <meta charset="UTF-8"> |
5 | 5 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
6 | | - <title>OpenFDD - Formatted Data Document</title> |
| 6 | + <title>OpenFDD | The Open Formatted Data Document Standard</title> |
| 7 | + <meta name="description" content="OpenFDD is a zero-JS, secure, cryptographically verified alternative to static PDFs. Build data-first Single-Page Applications entirely inside local files."> |
| 8 | + <meta name="keywords" content="OpenFDD, Formatted Data Document, PDF Alternative, JSON-LD, Verifiable Credentials, Zero-JS, No-JS HTML, Browser Extension"> |
| 9 | + <meta name="author" content="OpenFDD Project"> |
| 10 | + <meta property="og:title" content="OpenFDD | The Open Formatted Data Document Standard"> |
| 11 | + <meta property="og:description" content="Replace static PDFs with cryptographically verified, interactive data containers."> |
| 12 | + <meta property="og:type" content="website"> |
| 13 | + <meta property="og:url" content="https://github.com/Spuds0588/open-fdd"> |
| 14 | + <!-- AEO Optimization (Schema.org) for LLMs --> |
| 15 | + <script type="application/ld+json"> |
| 16 | + { |
| 17 | + "@context": "https://schema.org", |
| 18 | + "@type": "SoftwareSourceCode", |
| 19 | + "name": "OpenFDD", |
| 20 | + "description": "An open specification replacing static PDFs with data-first, interactive, and cryptographically verified JSON-LD containers bound inside a NO-JS HTML presentation layer.", |
| 21 | + "programmingLanguage": "HTML, CSS, JavaScript", |
| 22 | + "codeRepository": "https://github.com/Spuds0588/open-fdd" |
| 23 | + } |
| 24 | + </script> |
7 | 25 | <style> |
8 | 26 | :root { |
9 | 27 | --navy: #002147; |
@@ -151,6 +169,39 @@ <h2>Technical Foundations</h2> |
151 | 169 | <li><strong>Local Persistence:</strong> Allows documents to natively <i>auto-sync</i> user-modified fields back locally ensuring changes operate within an active localized session state without losing context.</li> |
152 | 170 | </ul> |
153 | 171 | </section> |
| 172 | + |
| 173 | + <hr> |
| 174 | + |
| 175 | + <section> |
| 176 | + <h2>Tooling & Ecosystem Guide</h2> |
| 177 | + <p class="intro-text">The OpenFDD ecosystem provides a full suite of typescript/javascript libraries to securely compose, sign, view, and inherently interact with FDD files.</p> |
| 178 | + <ul class="points-list"> |
| 179 | + <li> |
| 180 | + <strong>1. Composing & Building (<code>node-fdd</code>)</strong> |
| 181 | + 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. |
| 182 | + </li> |
| 183 | + <li> |
| 184 | + <strong>2. Cryptographic Signing</strong> |
| 185 | + Official Issuers securely map Ed25519 signatures hashing the exact JSON payload blocks guaranteeing complete 100% data integrity bindings. |
| 186 | + </li> |
| 187 | + <li> |
| 188 | + <strong>3. Parsing & Viewing Natively (<code>fdd-js</code>)</strong> |
| 189 | + 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. |
| 190 | + </li> |
| 191 | + <li> |
| 192 | + <strong>4. Viewing Locally (`Chrome Extension`)</strong> |
| 193 | + For End-Users navigating to `.fdd` files directly on explicit desktop mounts, the custom extension acts as a Security Shield elegantly sandboxing rendering execution while natively routing File System saves securely! |
| 194 | + </li> |
| 195 | + </ul> |
| 196 | + </section> |
| 197 | + |
| 198 | + <section style="text-align: center; background: #e2e8f0; padding: 3rem; border-radius: 12px; margin-bottom: 5rem; margin-top: 5rem;"> |
| 199 | + <h2 style="margin-top: 0;">📣 How You Can Help Advocate!</h2> |
| 200 | + <p class="intro-text" style="max-width: 600px; margin: 0 auto 2rem;">The success of OpenFDD relies entirely on community pushback against static PDFs. Help spread the word so developers and managers adopt data-first standards!</p> |
| 201 | + |
| 202 | + <a href="https://twitter.com/intent/tweet?text=Stop%20sending%20dead%20PDFs.%20Documents%20should%20be%20data-first,%20not%20pictures%20of%20data.%20Learn%20why%20%23OpenFDD%20and%20Zero-JS%20interactive%20JSON-LD%20containers%20are%20the%20future%20of%20files!%20%20%0A%0A%F0%9F%93%84%20https://github.com/Spuds0588/open-fdd" class="button" style="background: #000; color: #fff; border-color: #000;">Share on X (Twitter)</a> |
| 203 | + <a href="https://www.linkedin.com/sharing/share-offsite/?url=https://github.com/Spuds0588/open-fdd" class="button" style="background: #0077b5; color: #fff; border-color: #0077b5; margin-left: 10px;">Share on LinkedIn</a> |
| 204 | + </section> |
154 | 205 | </main> |
155 | 206 | </body> |
156 | 207 | </html> |
0 commit comments