lighthouse-web3 · nandit123 · Dec 13, 2025 · Dec 13, 2025 · Dec 13, 2025 · Dec 13, 2025
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,8 @@
+node_modules
+.build
+build
+.DS_Store
+.env
+npm-debug.log*
+yarn-error.log
+**/.docusaurus
diff --git a/.npmrc b/.npmrc
@@ -0,0 +1 @@
+registry=https://registry.npmmirror.com
diff --git a/README.md b/README.md
@@ -1,81 +1,76 @@
----
-description: An overview to Lighthouse
----
-
-# 👋 Introduction
-
-<img src=".gitbook/assets/Screenshot 2023-10-21 at 9.41.08 AM.png" alt="" data-size="original">
-
-***
-
-### What is Lighthouse?
-
-Lighthouse is a **permanent, decentralized storage protocol** powered by **Filecoin and IPFS**.\
-It allows individuals, developers, and enterprises to store data **forever** with a simple, one-time payment model—eliminating recurring cloud costs while ensuring verifiable, tamper-proof security.
-
-With Lighthouse, your files are stored across a decentralized network of Filecoin miners and can be accessed anytime through **dedicated IPFS gateways** optimized for speed, media delivery, and scalability.
-
-***
-
-### Why Lighthouse?
-
-* **Perpetual Storage**\
-  Pay once and preserve your files permanently without renewals.
-* **Decentralized Security**\
-  Your data is stored on IPFS + Filecoin, ensuring immutability and reliability.
-* **Encryption & Access Control**\
-  Use **Kavach Threshold Encryption** and token-gating to keep data private and grant access via tokens, NFTs, passkeys, or zkTLS.
-* **Dedicated IPFS Gateways**\
-  Fast retrieval for files, including **4K video streaming** at scale.
-* **Decentralized Image Resizing**\
-  Optimize images on retrieval—save bandwidth without losing quality.
-* **Flexible Payments**\
-  Choose annual or lifetime plans, pay with credit/debit cards or on-chain tokens.
-* **No Vendor Lock-In**\
-  Retrieve and migrate data anytime with full user control.
-
-***
-
-### Tools for Developers
-
-* **Lighthouse SDK** – Libraries, APIs, and docs to integrate decentralized storage into apps.
-* **Lighthouse CLI** – Manage files directly from your terminal with simple commands.
-* **Encryption SDK** – Easily secure and token-gate private files across chains and networks.
-
-***
-
-### Expanding the Data Economy
-
-Lighthouse doesn’t just store data—it powers new ecosystems:
-
-* **Data DAOs** – Create decentralized organizations to preserve, govern, and monetize data.
-* **AI Data Monetization** – Store datasets, apply access control, and enable AI model training.
-* **Private Processing** – Compute over private data while keeping it encrypted.
-* **Cross-Ecosystem Support** – Built for AI, DePIN, NFTs, gaming, L1/L2 blockchains, and more.
-
-***
-
-### Backed by Trusted Partners
-
-Lighthouse is already integrated into leading ecosystems like **SingularityNet, Cardano, and OKContract**, and is trusted for secure storage in the **NFT, modular blockchain, and AI data markets**.
-
-***
-
-### Why It Matters
-
-Traditional cloud providers rent your data back to you. Lighthouse redefines storage with **permanent, affordable, and verifiable solutions**, enabling the next generation of apps, DAOs, and AI systems to thrive on **secure and censorship-resistant infrastructure**.
-
-**With Lighthouse, your data doesn’t expire—it lives forever.**
-
-***
-
-### IPFS and Filecoin
-
-While both IPFS (InterPlanetary File System) and Filecoin are pivotal technologies in decentralized storage, they serve distinct but complementary roles:
-
-* **IPFS**: A peer-to-peer hypermedia protocol designed to store and share files in a distributed file system. It uses content-addressing to uniquely identify each file in a global namespace, making it efficient for retrieving cached data and sharing files.
-* **Filecoin**: A decentralized storage network that incentivizes storage providers and clients to offer and use storage space. While IPFS handles the distribution and retrieval of files, Filecoin ensures that those files are stored reliably over time through economic incentives.
-
-By leveraging IPFS with Filecoin underneath, Lighthouse leverages the strengths of both technologies: the efficient file retrieval, immutability of IPFS with the reliable, incentivized storage of Filecoin. This combination ensures low-cost, verifiable, and perpetual storage solutions.
-
-***
+# Lighthouse Docs (Docusaurus)
+
+This repository now uses [Docusaurus](https://docusaurus.io/) to render the Lighthouse documentation.
+
+## Getting started
+
+1. Install dependencies:
+   ```bash
+   npm install
+   ```
+2. Start a local dev server:
+   ```bash
+   npm run start
+   ```
+   The site will open at http://localhost:3000/ with hot reloading.
+3. Build a production bundle:
+   ```bash
+   npm run build
+   ```
+4. Preview the production build locally:
+   ```bash
+   npm run serve
+   ```
+
+### Troubleshooting installs/builds
+
+- If `npm install` fails with a 403 from the registry, ensure any corporate proxy variables are unset (`npm config delete proxy` and `npm config delete https-proxy`) and retry.
+- Set an explicit registry if needed:
+  ```bash
+  npm config set registry https://registry.npmjs.org
+  ```
+- Some environments block the default registry outright. You can also try the included `.npmrc` mirror (`https://registry.npmmirror.com`), but if the registry itself is blocked you will need network access to an allowed npm mirror before running `npm run build`.
+
+## Deploying to Vercel
+
+The repository already includes `vercel.json` with the correct defaults for Docusaurus. Use either the dashboard or the CLI:
+
+### Deploy from the Vercel dashboard (recommended)
+
+1. Create a new project and connect this Git repository.
+2. In **Project Settings → General** set:
+   - **Framework Preset:** `Docusaurus` (or `Other` if unavailable)
+   - **Install Command:** `npm install`
+   - **Build Command:** `npm run build`
+   - **Output Directory:** `build`
+3. Save the settings and trigger a new deployment. The site will be served from the URL shown in the Vercel dashboard and should match the `url` in `docusaurus.config.ts` (currently `https://lighthouse-docs.vercel.app`).
+
+### Deploy from the Vercel CLI (alternative)
+
+1. Install the Vercel CLI if needed:
+   ```bash
+   npm install -g vercel
+   ```
+2. Log in and link the project (requires a Vercel account):
+   ```bash
+   vercel login
+   vercel link
+   ```
+3. Deploy using the configuration in `vercel.json`:
+   ```bash
+   vercel --prod
+   ```
+   The CLI will build the site, upload the `build/` directory, and print the production URL.
+
+## Project structure
+
+- `docs/` contains all documentation content (migrated from GitBook).
+- `static/` holds static assets such as images and the site favicon.
+- `src/pages/` and `src/css/` contain the homepage and styling overrides.
+- `docusaurus.config.ts` and `sidebars.ts` configure the Docusaurus site.
+
+## Adding or updating docs
+
+1. Create or edit Markdown files inside `docs/`.
+2. Update `sidebars.ts` to add new pages to the navigation.
+3. Run `npm run start` to verify the pages render correctly.
diff --git a/account-delegation.md → docs/account-delegation.md b/account-delegation.md → docs/account-delegation.md
diff --git a/concepts/glossary.md → docs/concepts/glossary.md b/concepts/glossary.md → docs/concepts/glossary.md
diff --git a/concepts/ipfs-cid-transition-to-v1.md → docs/concepts/ipfs-cid-transition-to-v1.md b/concepts/ipfs-cid-transition-to-v1.md → docs/concepts/ipfs-cid-transition-to-v1.md
diff --git a/filecoin-first/deal-verification.md → docs/filecoin-first/deal-verification.md b/filecoin-first/deal-verification.md → docs/filecoin-first/deal-verification.md
diff --git a/filecoin-first/pay-per-deal.md → docs/filecoin-first/pay-per-deal.md b/filecoin-first/pay-per-deal.md → docs/filecoin-first/pay-per-deal.md
diff --git a/filecoin-first/podsi.md → docs/filecoin-first/podsi.md b/filecoin-first/podsi.md → docs/filecoin-first/podsi.md
@@ -6,7 +6,7 @@ hidden: true
 
 **Proof of Data Segment Inclusion (PoDSI)** is like a certificate of authenticity. It assures that your file is safely tucked inside a special package, known as a "deal", made by the Lighthouse Node. This node combines several files, gives them a unique ID, offers proof of their inclusion, and even throws a mini-proof of the entire package's structure.
 
-<figure><picture><source srcset="../.gitbook/assets/Group 1707478178.png" media="(prefers-color-scheme: dark)"><img src="../.gitbook/assets/Api de.png" alt=""></picture><figcaption></figcaption></figure>
+<figure><picture><source srcset="/img/Group 1707478178.png" media="(prefers-color-scheme: dark)" /><img src="/img/Api de.png" alt="" /></picture><figcaption></figcaption></figure>
 
 {% hint style="warning" %}
 The time between uploading and being able to get your PoDSI varies from testnet from mainnet. Ideally it would be 6hr in testnet and 1 day in mainnet. You can get the PoDSI for your file by calling the `getProof` function in one of the following ways:

diff --git a/filecoin-first/section-a.md → docs/filecoin-first/section-a.md b/filecoin-first/section-a.md → docs/filecoin-first/section-a.md
diff --git a/filecoin-first/section-b.md → docs/filecoin-first/section-b.md b/filecoin-first/section-b.md → docs/filecoin-first/section-b.md
diff --git a/filecoin-first/self-hosted-raas.md → docs/filecoin-first/self-hosted-raas.md b/filecoin-first/self-hosted-raas.md → docs/filecoin-first/self-hosted-raas.md
@@ -14,7 +14,7 @@ Start an instance of the self-hosted RaaS by deploying a contract that inherits
 
 The [RaaS Starter Kit](https://github.com/filecoin-project/raas-starter-kit) comes with a frontend that allows you to upload your file to Lighthouse, get a CID for the uploaded file, then seamlessly submit the CID to the smart contract (accessible via `yarn start`).
 
-![RaaS Starter Kit Frontend](../.gitbook/assets/Frontend.png)
+![RaaS Starter Kit Frontend](/img/Frontend.png)
 
 If you're hosting your own RaaS service (specifically, the one in the [RaaS Starter Kit](https://github.com/filecoin-project/raas-starter-kit)), there's an event listener inside that you can use to listen for new deal requests.
 

diff --git a/filecoin-first/usage.md → docs/filecoin-first/usage.md b/filecoin-first/usage.md → docs/filecoin-first/usage.md
diff --git a/how-to/ai/README.md → docs/how-to/ai/index.md b/how-to/ai/README.md → docs/how-to/ai/index.md
diff --git a/how-to/ai/mcp-protocol.md → docs/how-to/ai/mcp-protocol.md b/how-to/ai/mcp-protocol.md → docs/how-to/ai/mcp-protocol.md
diff --git a/how-to/check-for-filecoin-deals.md → docs/how-to/check-for-filecoin-deals.md b/how-to/check-for-filecoin-deals.md → docs/how-to/check-for-filecoin-deals.md
diff --git a/how-to/create-a-datacoin.md → docs/how-to/create-a-datacoin.md b/how-to/create-a-datacoin.md → docs/how-to/create-a-datacoin.md
@@ -16,15 +16,15 @@ In short: **DataCoins turn raw data into a tradable, liquid asset.**
 
 ### **Step 1: Connect Wallet**
 
-<figure><img src="../.gitbook/assets/Screenshot_2025-09-26_at_8.56.13_AM.webp" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/Screenshot_2025-09-26_at_8.56.13_AM.webp" alt="" /><figcaption></figcaption></figure>
 
 Connect wallet and click on create data coin.
 
 ***
 
 ### **Step 2: Enter Personal Information**
 
-<figure><img src="../.gitbook/assets/Screenshot_2025-09-26_at_8.58.04_AM.webp" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/Screenshot_2025-09-26_at_8.58.04_AM.webp" alt="" /><figcaption></figcaption></figure>
 
 Fill out the form with the following details:
 
@@ -40,7 +40,7 @@ The website link should point to your **DataDAO app**, which defines the logic f
 
 ### **Step 3: Add Social Information**
 
-<figure><img src="../.gitbook/assets/Screenshot_2025-09-26_at_9.01.40_AM.webp" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/Screenshot_2025-09-26_at_9.01.40_AM.webp" alt="" /><figcaption></figcaption></figure>
 
 Provide your social links such as **Telegram, Farcaster, X, GitHub, and LinkedIn**.
 
@@ -50,7 +50,7 @@ All fields are optional—you can fill in whichever ones you prefer.
 
 ### **Step 4: Configure Tokenomics** of your choice.
 
-<figure><img src="../.gitbook/assets/Screenshot_2025-09-26_at_9.04.07_AM.webp" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/Screenshot_2025-09-26_at_9.04.07_AM.webp" alt="" /><figcaption></figcaption></figure>
 
 Set up the economics of your data coin:
 
@@ -76,7 +76,7 @@ Once configured, click **Submit Data Coin**. Two transactions will follow:
 
 ### **Step 5: View and Manage Your Coin**
 
-<figure><img src="../.gitbook/assets/Screenshot_2025-09-26_at_9.17.17_AM.webp" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/Screenshot_2025-09-26_at_9.17.17_AM.webp" alt="" /><figcaption></figcaption></figure>
 
 After successful creation, you’ll be able to view your coin’s details.
 

diff --git a/how-to/create-an-api-key.md → docs/how-to/create-an-api-key.md b/how-to/create-an-api-key.md → docs/how-to/create-an-api-key.md
diff --git a/how-to/delete-file.md → docs/how-to/delete-file.md b/how-to/delete-file.md → docs/how-to/delete-file.md
diff --git a/...ion-features/access-control-conditions.md → ...ion-features/access-control-conditions.md b/...ion-features/access-control-conditions.md → ...ion-features/access-control-conditions.md
diff --git a/...ncryption-features/access-control-node.md → ...ncryption-features/access-control-node.md b/...ncryption-features/access-control-node.md → ...ncryption-features/access-control-node.md
diff --git a/...ion-features/access-control-with-zktls.md → ...ion-features/access-control-with-zktls.md b/...ion-features/access-control-with-zktls.md → ...ion-features/access-control-with-zktls.md
diff --git a/...n-features/account-delegation-tutorial.md → ...n-features/account-delegation-tutorial.md b/...n-features/account-delegation-tutorial.md → ...n-features/account-delegation-tutorial.md
diff --git a/...o/encryption-features/chains-supported.md → ...o/encryption-features/chains-supported.md b/...o/encryption-features/chains-supported.md → ...o/encryption-features/chains-supported.md
diff --git a/...ion-features/decrypt-file/decrypt-file.md → ...ion-features/decrypt-file/decrypt-file.md b/...ion-features/decrypt-file/decrypt-file.md → ...ion-features/decrypt-file/decrypt-file.md
diff --git a/...ncryption-features/decrypt-file/README.md → ...encryption-features/decrypt-file/index.md b/...ncryption-features/decrypt-file/README.md → ...encryption-features/decrypt-file/index.md
diff --git a/...tures/decrypt-file/nodejs-decrypt-file.md → ...tures/decrypt-file/nodejs-decrypt-file.md b/...tures/decrypt-file/nodejs-decrypt-file.md → ...tures/decrypt-file/nodejs-decrypt-file.md
diff --git a/...ryption-features/get-access-conditions.md → ...ryption-features/get-access-conditions.md b/...ryption-features/get-access-conditions.md → ...ryption-features/get-access-conditions.md
diff --git a/how-to/encryption-features/README.md → docs/how-to/encryption-features/index.md b/how-to/encryption-features/README.md → docs/how-to/encryption-features/index.md
diff --git a/how-to/encryption-features/revoke-access.md → ...w-to/encryption-features/revoke-access.md b/how-to/encryption-features/revoke-access.md → ...w-to/encryption-features/revoke-access.md
diff --git a/how-to/encryption-features/share-file.md → .../how-to/encryption-features/share-file.md b/how-to/encryption-features/share-file.md → .../how-to/encryption-features/share-file.md
diff --git a/how-to/file-info.md → docs/how-to/file-info.md b/how-to/file-info.md → docs/how-to/file-info.md
diff --git a/how-to/get-balance.md → docs/how-to/get-balance.md b/how-to/get-balance.md → docs/how-to/get-balance.md
diff --git a/how-to/ipns-handle-mutable-data.md → docs/how-to/ipns-handle-mutable-data.md b/how-to/ipns-handle-mutable-data.md → docs/how-to/ipns-handle-mutable-data.md
diff --git a/how-to/list-files.md → docs/how-to/list-files.md b/how-to/list-files.md → docs/how-to/list-files.md
diff --git a/how-to/migrations/google-drive.md → docs/how-to/migrations/google-drive.md b/how-to/migrations/google-drive.md → docs/how-to/migrations/google-drive.md
diff --git a/how-to/migrations/README.md → docs/how-to/migrations/index.md b/how-to/migrations/README.md → docs/how-to/migrations/index.md
diff --git a/how-to/migrations/ipfs-provider.md → docs/how-to/migrations/ipfs-provider.md b/how-to/migrations/ipfs-provider.md → docs/how-to/migrations/ipfs-provider.md
@@ -18,7 +18,7 @@ Navigate to [Files Dapp](https://files.lighthouse.storage/) and either register
 
 Click on the `migration` option in the left panel.
 
-<figure><img src="../../.gitbook/assets/image (2).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/image (2).png" alt="" /><figcaption></figcaption></figure>
 
 ### Step 3: Create a New Migration
 
@@ -32,7 +32,7 @@ Select the `Create Migration` button to start the process.
 
 Enter the CID (Content Identifier) for your content. Alternatively, if you have multiple CIDs, you can upload a CSV file with all the CIDs listed.
 
-<figure><img src="../../.gitbook/assets/image (4).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/image (4).png" alt="" /><figcaption></figcaption></figure>
 
 ### Step 5: Execute Migration
 

diff --git a/how-to/overview.md → docs/how-to/overview.md b/how-to/overview.md → docs/how-to/overview.md
@@ -49,7 +49,7 @@ The following commands are available with the Lighthouse CLI tool
 
 :frame\_photo:**CLI Commands**
 
-<figure><img src="../.gitbook/assets/Screenshot 2023-10-20 195553.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/Screenshot 2023-10-20 195553.png" alt="" /><figcaption></figcaption></figure>
 
 ## Go SDK CLI Tool
 
@@ -159,4 +159,4 @@ Run the following command to see all available commands:
 lhctl --help
 ```
 
-<figure><img src="../.gitbook/assets/go-cli.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/go-cli.png" alt="" /><figcaption></figcaption></figure>
diff --git a/how-to/pay-per-use.md → docs/how-to/pay-per-use.md b/how-to/pay-per-use.md → docs/how-to/pay-per-use.md
diff --git a/how-to/pin-cid.md → docs/how-to/pin-cid.md b/how-to/pin-cid.md → docs/how-to/pin-cid.md
diff --git a/how-to/resize-image.md → docs/how-to/resize-image.md b/how-to/resize-image.md → docs/how-to/resize-image.md
diff --git a/how-to/retrieve-file.md → docs/how-to/retrieve-file.md b/how-to/retrieve-file.md → docs/how-to/retrieve-file.md
diff --git a/how-to/upload-data/buffer.md → docs/how-to/upload-data/buffer.md b/how-to/upload-data/buffer.md → docs/how-to/upload-data/buffer.md
diff --git a/how-to/upload-data/file.md → docs/how-to/upload-data/file.md b/how-to/upload-data/file.md → docs/how-to/upload-data/file.md
diff --git a/docs/how-to/upload-data/index.md b/docs/how-to/upload-data/index.md
@@ -0,0 +1,12 @@
+# 🔼 Upload Data
+
+This section covers the steps to upload a file to Lighthouse. You can upload a file, buffer, or text/JSON payload.
+
+1. [Upload File](file.md)
+2. [Upload Text/JSON](text-json.md)
+3. [Upload Buffer](buffer.md)
+
+> Looking for Filecoin Virtual Machine workflows? Use the Filecoin Virtual Machine interface as shown below when you need on-chain execution alongside Lighthouse storage.
+
+![Uploading via FVM](/img/Screenshot 2023-10-21 at 10.39.34 AM.png)
+
diff --git a/how-to/upload-data/text-json.md → docs/how-to/upload-data/text-json.md b/how-to/upload-data/text-json.md → docs/how-to/upload-data/text-json.md
diff --git a/how-to/upload-encrypted-data/file.md → docs/how-to/upload-encrypted-data/file.md b/how-to/upload-encrypted-data/file.md → docs/how-to/upload-encrypted-data/file.md
diff --git a/how-to/upload-encrypted-data/README.md → docs/how-to/upload-encrypted-data/index.md b/how-to/upload-encrypted-data/README.md → docs/how-to/upload-encrypted-data/index.md
diff --git a/...avach-encryption-authentication/README.md → ...kavach-encryption-authentication/index.md b/...avach-encryption-authentication/README.md → ...kavach-encryption-authentication/index.md
diff --git a/...authentication/method-1-signed-message.md → ...authentication/method-1-signed-message.md b/...authentication/method-1-signed-message.md → ...authentication/method-1-signed-message.md
diff --git a/...encryption-authentication/method-2-jwt.md → ...encryption-authentication/method-2-jwt.md b/...encryption-authentication/method-2-jwt.md → ...encryption-authentication/method-2-jwt.md
diff --git a/...yption-authentication/method-3-passkey.md → ...yption-authentication/method-3-passkey.md b/...yption-authentication/method-3-passkey.md → ...yption-authentication/method-3-passkey.md
diff --git a/how-to/upload-encrypted-data/text-json.md → ...how-to/upload-encrypted-data/text-json.md b/how-to/upload-encrypted-data/text-json.md → ...how-to/upload-encrypted-data/text-json.md
diff --git a/how-to/using-pdp-with-lighthouse.md → docs/how-to/using-pdp-with-lighthouse.md b/how-to/using-pdp-with-lighthouse.md → docs/how-to/using-pdp-with-lighthouse.md
diff --git a/interacting-with-node/web-sockets.md → docs/interacting-with-node/web-sockets.md b/interacting-with-node/web-sockets.md → docs/interacting-with-node/web-sockets.md
diff --git a/...ing-with-smart-contracts/code-examples.md → ...ing-with-smart-contracts/code-examples.md b/...ing-with-smart-contracts/code-examples.md → ...ing-with-smart-contracts/code-examples.md
diff --git a/...ing-with-smart-contracts/key-functions.md → ...ing-with-smart-contracts/key-functions.md b/...ing-with-smart-contracts/key-functions.md → ...ing-with-smart-contracts/key-functions.md
diff --git a/docs/intro.md b/docs/intro.md
@@ -0,0 +1,83 @@
+---
+title: Introduction
+description: An overview to Lighthouse
+slug: /
+---
+
+# 👋 Introduction
+
+<img src="/img/Screenshot 2023-10-21 at 9.41.08 AM.png" alt="" data-size="original">
+
+***
+
+### What is Lighthouse?
+
+Lighthouse is a **permanent, decentralized storage protocol** powered by **Filecoin and IPFS**.\
+It allows individuals, developers, and enterprises to store data **forever** with a simple, one-time payment model—eliminating recurring cloud costs while ensuring verifiable, tamper-proof security.
+
+With Lighthouse, your files are stored across a decentralized network of Filecoin miners and can be accessed anytime through **dedicated IPFS gateways** optimized for speed, media delivery, and scalability.
+
+***
+
+### Why Lighthouse?
+
+* **Perpetual Storage**\
+  Pay once and preserve your files permanently without renewals.
+* **Decentralized Security**\
+  Your data is stored on IPFS + Filecoin, ensuring immutability and reliability.
+* **Encryption & Access Control**\
+  Use **Kavach Threshold Encryption** and token-gating to keep data private and grant access via tokens, NFTs, passkeys, or zkTLS.
+* **Dedicated IPFS Gateways**\
+  Fast retrieval for files, including **4K video streaming** at scale.
+* **Decentralized Image Resizing**\
+  Optimize images on retrieval—save bandwidth without losing quality.
+* **Flexible Payments**\
+  Choose annual or lifetime plans, pay with credit/debit cards or on-chain tokens.
+* **No Vendor Lock-In**\
+  Retrieve and migrate data anytime with full user control.
+
+***
+
+### Tools for Developers
+
+* **Lighthouse SDK** – Libraries, APIs, and docs to integrate decentralized storage into apps.
+* **Lighthouse CLI** – Manage files directly from your terminal with simple commands.
+* **Encryption SDK** – Easily secure and token-gate private files across chains and networks.
+
+***
+
+### Expanding the Data Economy
+
+Lighthouse doesn’t just store data—it powers new ecosystems:
+
+* **Data DAOs** – Create decentralized organizations to preserve, govern, and monetize data.
+* **AI Data Monetization** – Store datasets, apply access control, and enable AI model training.
+* **Private Processing** – Compute over private data while keeping it encrypted.
+* **Cross-Ecosystem Support** – Built for AI, DePIN, NFTs, gaming, L1/L2 blockchains, and more.
+
+***
+
+### Backed by Trusted Partners
+
+Lighthouse is already integrated into leading ecosystems like **SingularityNet, Cardano, and OKContract**, and is trusted for secure storage in the **NFT, modular blockchain, and AI data markets**.
+
+***
+
+### Why It Matters
+
+Traditional cloud providers rent your data back to you. Lighthouse redefines storage with **permanent, affordable, and verifiable solutions**, enabling the next generation of apps, DAOs, and AI systems to thrive on **secure and censorship-resistant infrastructure**.
+
+**With Lighthouse, your data doesn’t expire—it lives forever.**
+
+***
+
+### IPFS and Filecoin
+
+While both IPFS (InterPlanetary File System) and Filecoin are pivotal technologies in decentralized storage, they serve distinct but complementary roles:
+
+* **IPFS**: A peer-to-peer hypermedia protocol designed to store and share files in a distributed file system. It uses content-addressing to uniquely identify each file in a global namespace, making it efficient for retrieving cached data and sharing files.
+* **Filecoin**: A decentralized storage network that incentivizes storage providers and clients to offer and use storage space. While IPFS handles the distribution and retrieval of files, Filecoin ensures that those files are stored reliably over time through economic incentives.
+
+By leveraging IPFS with Filecoin underneath, Lighthouse leverages the strengths of both technologies: the efficient file retrieval, immutability of IPFS with the reliable, incentivized storage of Filecoin. This combination ensures low-cost, verifiable, and perpetual storage solutions.
+
+***
diff --git a/javascript/functions/add-cid.md → docs/javascript/functions/add-cid.md b/javascript/functions/add-cid.md → docs/javascript/functions/add-cid.md
diff --git a/...cript/functions/get-encryption-keypair.md → ...cript/functions/get-encryption-keypair.md b/...cript/functions/get-encryption-keypair.md → ...cript/functions/get-encryption-keypair.md
diff --git a/quick-start.md → docs/quick-start.md b/quick-start.md → docs/quick-start.md
@@ -1,16 +1,17 @@
 ---
+title: Quick Start
 icon: hammer
 ---
 
 # Quick Start
 
 In this section, we will see how to
 
-1. [Create an API Key](quick-start.md#create-an-api-key)
-2. [Upload a file](quick-start.md#upload-a-file)
-3. [View the file](quick-start.md#view-file)
-4. [Get Filecoin deals](quick-start.md#get-filecoin-deal)
-5. [What's Next?](quick-start.md#id-5.-whats-next)
+1. [Create an API Key](#create-an-api-key)
+2. [Upload a file](#upload-a-file)
+3. [View the file](#view-file)
+4. [Get Filecoin deals](#get-filecoin-deal)
+5. [What's Next?](#id-5.-whats-next)
 
 This Quick Start guide walks you through the essentials: creating an API key, uploading a file, viewing it, and tracking its storage status. While the examples below use Node.js, you can easily adapt them for other environments using our How-To section
 
@@ -26,7 +27,7 @@ This Quick Start guide walks you through the essentials: creating an API key, up
 You can also generate the API key from CLI
 {% endhint %}
 
-<figure><img src=".gitbook/assets/api key.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="/img/api key.png" alt="" /><figcaption></figcaption></figure>
 
 ### 2. Upload a File
 

diff --git a/support/contact.md → docs/support/contact.md b/support/contact.md → docs/support/contact.md