refactor: major restructure

docs/apps/browser-webapp.md

@@ -2,10 +2,10 @@
 title: Web3 Browser Web App
 ---
 
-Link: https://web3browser.io
-
 ![image](/web3-browser-webapp.png)
 
+Link: https://web3browser.io
+
 This is an experimental tech demo to enable HNS and ENS browsing via IPFS.
 
 This demo uses the following technologies:

docs/index.md

@@ -9,28 +9,3 @@ This project was created so that we can have a *true* open web in which we can s
 We are doing `progressive decentralization`. This means that at this time, while the tech itself uses P2P technology and is decentralized, the products we create are semi-centralized.
 
 ---
-
-**The following is an AI generated summary of these docs**
-
-The Lume Web Protocol is an innovative approach to navigating the ever-evolving internet landscape, particularly in the transition from Web 2.0 to Web3. Lume's development was initially inspired while creating a Web3 cloud drive on Nextcloud based on Skynet. However, the focus shifted to addressing the fundamental issue of content access in the Web3 environment.
-
-### Web 2.0 and Web3 Evolution
-
--   **Web 1.0 and 2.0**: The early web (Web 1.0) was open and had unlimited potential, but it eventually led to centralization, especially with the rise of massive social networks around 2005. This centralization meant that users essentially became products, with their personal data monetized by these platforms.
--   **Web3 Ideals**: Web3 aims to shift the focus back to the user, advocating for a creator economy and peer-to-peer interactions, with an emphasis on privacy and data ownership. Despite this, the practical implementation of Web3 has faced challenges, such as reliance on centralized storage and the influence of venture capital, which sometimes contradicts the ethos of decentralization.
--   **Infrastructure Vulnerabilities**: A significant concern in the Web3 space is the centralized nature of key internet infrastructure components like AWS/Google, Cloudflare, and ICANN, which could pose risks to the stability and independence of Web3 initiatives.
--   **Vision for Web3**: The ideal Web3 should be indistinguishable from Web 2.0 in terms of user experience, with an emphasis on open standards and easy access, overcoming the current accessibility barriers.
-
-### Limitations of Web2 and the Shift to Web3
-
--   **Protocols**: Web2 relies on protocols like HTTP, FTP, SMTP, IMAP, POP, and DNS, but these often have single points of failure and are susceptible to control by large technology companies and censorship at various levels.
--   **Web3 Transformations**: Web3 aims to transform these components, with blockchain replacing traditional money ledgers, smart contracts substituting stored procedures, distributed databases taking the place of traditional SQL/NoSQL databases, and P2P networks replacing server-client models. This shift is fundamental to the Web3 architecture, focusing on decentralization and resistance to censorship.
-
-### Lume's Role in the Web3 Landscape
-
--   **P2P Network**: Lume functions as a P2P network using public keys, akin to BitTorrent but tailored for Web3. It's designed as a bridge to service all Web3 needs and is not based on blockchain technology.
--   **Storage and Gateway**: Lume acts as a storage portal, building on Sia for private and public data storage, and serves as a gateway for users to interface with various content networks and blockchains.
--   **Middleware System**: As a middleware system, Lume facilitates access to other networks through a relay network, employing technologies like Hypercore/Dat for anonymous access and providing DNS services.
--   **Frontend and Content Networks**: Lume's browser technology, similar to kernel and kernel modules in Linux, supports light clients, SPV nodes, and DNS resolvers among others. It utilizes content identifiers (CIDs) and supports real-time verified streaming.
-
-In summary, Lume is designed to address the centralization and censorship issues prevalent in Web2, offering a decentralized, user-centric platform that aligns with the ethos of Web3. It bridges traditional internet protocols with their Web3 counterparts, and through its P2P network, storage solutions, and middleware systems, Lume aims to enhance data ownership, decentralization, and accessibility in the digital space.

docs/intro/about.md

@@ -0,0 +1,16 @@
+---
+title: What is Lume?
+---
+
+`What is Lume?` This is something we have often asked ourselves to explain it 😅.
+
+Lume can be broken down into a few major focuses:
+
+- Lume is a **P2P network** that uses public keys instead of torrent hashes to access peers and content.
+    -  Like a BitTorrent, but ready for Web3.  You can also see it to be a bit like IPFS which uses Libp2p, but more light weight.
+        - The goal here is to create a bridge P2P network `to service all of Web3`.
+        - `It's NOT a blockchain`. You don't need one since anyone can provide services with RPC or their own custom protocol, and anyone can query them.
+- Lume is a **storage portal** (think `L2` in blockchain terms).
+    - It builds on Sia and stores your private data, and eventually public. In other words think of it like a paid IPFS service, but its not IPFS.
+- Lume is the **end user gateway**.
+    - It is how you will interface with all content networks, blockchains, or other nets in the future. This could be a browser extension, web browser itself or anything in-between.

docs/intro/components.md

@@ -1,44 +1,6 @@
 ---
-title: Lume
+title: How it works
 ---
-
-Since we defined the limitations of Web2 and building blocks of Web3, let's take a look at what Lume is and where it fits in the grander scale.
-
-### How did it start
-
-Lume started (before we even decided it was a project or the name) while we were trying to create a web3 cloud drive on Nextcloud based on Skynet. We realized that we were going down the wrong path and needed to solve accessing content before doing anything with the content itself.
-
-Skynet in the process had a very rough year, as since 2020, Skynet tried to solve distribution with network of Skynet Portals, but experienced number of obstacles from all levels of internet infrastructure (see [Limitations of Web2](web2-limits.md)) and eventually was shut down.
-
-Sia in the background was trying to support both innovating and Skynets efforts, and things came to a head with Skynet going bankrupt.
-
-In that journey, Lume has pivoted at-least 1 time to meet its goals, and has ended up having to build many building blocks out of necessity, and a few that may go unused 🙃.
-
-Sia has since started rebuilding with new software, and Lume has been building on top.
-
-Sia is the network of the worlds data, and Handshake replaces ICANN while collaborating with the web3 ecosystem. We have discussed Sia a lot so far, but let it also be known the Handshake tribe has had its own share of drama too, and Lume is actively involved in both.
-
-So the rabbit hole of Web3 DNS is where we started as the origin of Lume, which means the `world` or `light` in Romanian. It was our intention from the beginning to contribute to the solution of the web's censorship issues and becoming a bridge (or gateway) to the Web3.
-
-
-### What is Lume? Simple version, please!
-
-`What is Lume?` This is something we have often asked ourselves to explain it 😅.
-
-Lume can be broken down into a few major focuses:
-
-- Lume is a **P2P network** that uses public keys instead of torrent hashes to access peers and content.
-    -  Like a BitTorrent, but ready for Web3.  You can also see it to be a bit like IPFS which uses Libp2p, but more light weight.
-        - The goal here is to create a bridge P2P network `to service all of Web3`.
-        - `It's NOT a blockchain`. You don't need one since anyone can provide services with RPC or their own custom protocol, and anyone can query them.
-- Lume is a **storage portal** (think `L2` in blockchain terms).
-    - It builds on Sia and stores your private data, and eventually public. In other words think of it like a paid IPFS service, but its not IPFS.
-- Lume is the **end user gateway**.
-    - It is how you will interface with all content networks, blockchains, or other nets in the future. This could be a browser extension, web browser itself or anything in-between.
-
-### Ok, I get it. Now how it works under the hood?
-
-
 #### It's a bridge, it's a gateway
 Lume can be seen as a middleware system where you can plug anything in and access it over the relay network. This is done with a help of Hypercore/Dat (see https://docs.holepunch.to which is born from https://dat-ecosystem.org) that allows it to proxy (relay) access to other networks anonymously, and to provide some DNS services. It is also end-to-end encrypted (based on https://noiseprotocol.org).
 
@@ -60,7 +22,6 @@ This is the basis of how you can run light clients, SPV nodes, DNS resolvers, co
 
 With blake3 we can also support real time verified streaming, which means files get verified based on their hash as you download so everything is fully trustless. See https://github.com/n0-computer/abao.
 
-
 #### Path forward
 
 This browser tech can take many forms and Lume will continue evolving to be more advanced over time with its browsing abilities and more importantly, become easy and comfortable to use. That's its biggest problem today and also a reason we already started planning an extension for the most popular browser, Chrome. The end goal is a browser fork, but right now we need to get the foundations right.

docs/intro/history.md

@@ -0,0 +1,18 @@
+---
+title: History
+---
+
+Lume started (before we even decided it was a project or the name) while we were trying to create a web3 cloud drive on Nextcloud based on Skynet. We realized that we were going down the wrong path and needed to solve accessing content before doing anything with the content itself.
+
+Skynet in the process had a very rough year, as since 2020, Skynet tried to solve distribution with network of Skynet Portals, but experienced number of obstacles from all levels of internet infrastructure (see [Limitations of Web2](web2-limits.md)) and eventually was shut down.
+
+Sia in the background was trying to support both innovating and Skynets efforts, and things came to a head with Skynet going bankrupt.
+
+In that journey, Lume has pivoted at-least 1 time to meet its goals, and has ended up having to build many building blocks out of necessity, and a few that may go unused 🙃.
+
+Sia has since started rebuilding with new software, and Lume has been building on top.
+
+Sia is the network of the worlds data, and Handshake replaces ICANN while collaborating with the web3 ecosystem. We have discussed Sia a lot so far, but let it also be known the Handshake tribe has had its own share of drama too, and Lume is actively involved in both.
+
+So the rabbit hole of Web3 DNS is where we started as the origin of Lume, which means the `world` or `light` in Romanian. It was our intention from the beginning to contribute to the solution of the web's censorship issues and becoming a bridge (or gateway) to the Web3.
+

sidebars.js

@@ -15,11 +15,28 @@
 const sidebars = {
   main: [
     "index",
-    "better-web",
+    {
-    "web2-limits",
+      type: "category",
-    "web3-building-blocks",
+      label: "Introduction",
-    "lume",
+      link: null,
-    "browser-webapp",
+      items: ["intro/about", "intro/components", "intro/history"],
+    },
+    {
+      type: "category",
+      label: "Problems We Are Solving",
+      link: null,
+      items: [
+        "problems/better-web",
+        "problems/web2-limits",
+        "problems/web3-building-blocks",
+      ],
+    },
+    {
+      type: "category",
+      label: "Apps",
+      link: null,
+      items: ["apps/browser-webapp"],
+    },
   ],
 };