Push landing + docusaurus

.github/workflows/deploy.yml

@@ -1,4 +1,4 @@
-name: Deploy Dapp to GitHub Pages
+name: Deploy Dapp & Docs to GitHub Pages
 
 on:
   push:
@@ -27,7 +27,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'   # keep your choice
+          node-version: '20'
 
       - name: Enable Corepack & pnpm
         run: |
@@ -50,18 +50,39 @@ jobs:
       - name: Install dependencies (workspace root)
         run: pnpm install --frozen-lockfile
 
+      # ---- Build internal packages if needed ----
       - name: Build SDK
         run: pnpm -w --filter "@trustswap/sdk" run build
 
-      - name: Build with Vite (web)
+      # ---- Build Web (Vite) ----
+      - name: Build Web app
         run: pnpm -w --filter "./apps/web" run build
 
+      # ---- Build Docusaurus ----
+      # We force baseUrl to /docs/ so it serves under /docs on Pages.
+      - name: Build Docs (Docusaurus)
+        run: pnpm -w --filter "./apps/docus" run build
+
+      # ---- Assemble a single artifact for GitHub Pages ----
+      # Resulting structure:
+      #   ./.gh-pages/            => Web app (root)
+      #   ./.gh-pages/docs/       => Docusaurus site
+      - name: Prepare Pages artifact
+        run: |
+          rm -rf .gh-pages
+          mkdir -p .gh-pages
+          cp -r apps/web/dist/* .gh-pages/
+          mkdir -p .gh-pages/docs
+          cp -r apps/docus/build/* .gh-pages/docs/
+
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
         with:
-          path: apps/web/dist
+          path: .gh-pages
 
   deploy:
+    # For PRs, this creates a Pages "Preview" deployment automatically.
+    # For pushes to main, it updates the production Pages site.
     environment:
       name: github-pages
       url: ${{ steps.deployment.outputs.page_url }}

apps/docus/.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

apps/docus/README.md

@@ -0,0 +1,41 @@
+# Website
+
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
+
+## Installation
+
+```bash
+yarn
+```
+
+## Local Development
+
+```bash
+yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+## Build
+
+```bash
+yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+## Deployment
+
+Using SSH:
+
+```bash
+USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```bash
+GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

apps/docus/blog/2025-09-19-the-beginning.md

@@ -0,0 +1,50 @@
+---
+slug: the-beginning
+title: The beginning
+authors: [james, florian]
+tags: []
+---
+
+
+## Why We’re Building TrustSwap
+
+A few months ago, **Florian** and I started talking about the idea of launching a project together. The opportunity came when **Intuition** announced a one-week hackathon to spark development on its blockchain.
+
+We decided to experiment with building a **minimalist DEX**. The development progressed quickly, teamwork was smooth and efficient and by the end of the hackathon, we had a **fully functional DEX**.
+
+That’s when we decided to **keep going**, to turn this experiment into something bigger and explore how **Intuition’s protocol** could power a new kind of DEX.
+
+---
+
+## From Experiment to Vision
+
+We began thinking about features that would align our DEX with **Intuition’s technology and philosophy**.
+During our research, we discovered other protocols that resonated perfectly with our vision — such as **Colony** (for fair, reputation-based DAO governance) and **GBM Auctions** (for transparent and engaging token launches).
+
+These discoveries highlighted a recurring problem across most DEXs:
+**voting power is too often concentrated in the hands of a few whales.**
+In many models, governance simply decides where rewards go, not how the protocol should truly evolve, leaving most of the community on the sidelines.
+
+---
+
+## Our Difference
+
+With **TrustSwap**, we want to build **something different**.
+Our goal is to put the **community back at the center**, establish a more balanced governance system, and go beyond simple yield distribution.
+
+TrustSwap is not just another DEX:
+
+* It’s a space where **trust** is the core value.
+* A platform that leverages innovative protocols to bring **transparency and fairness**.
+* A project **built with the community — not just for it.**
+
+---
+
+## What’s Next
+
+Today, we’ve restructured our codebase and deployed the **first official version of TrustSwap**.
+
+This blog will serve as our **public build journal**, every week, we’ll share updates on our progress, document our choices, and keep our community fully informed.
+
+Welcome to the **TrustSwap adventure.**
+

apps/docus/blog/2025-09-26-logbook.md

@@ -0,0 +1,56 @@
+---
+slug: logbook-09-26-2025
+title: Logbook 09/26
+authors: [james, florian]
+tags: []
+---
+
+## Weekly Update #1 — First Steps with TrustSwap
+
+Welcome to the very first **TrustSwap Weekly Update!**
+Each week, we’ll share the progress of the project to maintain full **transparency** and keep the **community at the center** of this journey.
+
+---
+
+## Conversations with GBM
+
+This week kicked off with a **call with the GBM team**.
+We presented TrustSwap, our vision, and explored how their protocol could be integrated into our ecosystem.
+The synergy is clear: a **fair and engaging auction system** could greatly enhance TrustSwap’s community-driven dimension.
+
+Their protocol isn’t open-source yet, so there will be a few **technical prerequisites** before we can fully implement it, but things are moving in the right direction.
+We don’t plan to prioritize this integration before the mainnet launch, but it’s already **on our roadmap**.
+
+---
+
+## Brainstorming & Design
+
+We also spent time **brainstorming** and **designing upcoming pages** for the application.
+The goal: to deliver a **clear, modern, and intuitive interface** that reflects our vision of a community-first DEX.
+
+---
+
+## Tracking & Documentation
+
+* Added a **web analytics tracker** to monitor user activity on the app.
+* Began setting up **Docusaurus** to create our **litepaper** and this **blog**.
+
+This documentation will serve as the foundation of our communication and become a **knowledge hub** for the community.
+
+---
+
+## Technical Progress
+
+* **James** implemented the tracker and structured the Docusaurus documentation.
+* **Florian** has been developing an **indexer in Ruby on Rails**, which will offer a **graphical view of tokens and other on-chain data** — improving both user experience and data visualization. He’s also working on a **landing page**.
+
+We also started researching **limit order integration** and **MEV (Maximal Extractable Value) protection mechanisms**, to help users **avoid inflated fees** and **maximize LP yields**.
+
+---
+
+## What’s Next
+
+Next week, we plan to **publish the litepaper** alongside the new **landing page**.
+We’ll also begin development of the **portfolio and charting views**, and if progress goes smoothly, start preparing the first core feature of our DEX: the **Voting Overlay**.
+
+Stay tuned, the adventure is just beginning! 🚀

apps/docus/blog/2025-10-10-logbook.md

@@ -0,0 +1,48 @@
+---
+slug: logbook-09-10-2025
+title: Logbook 10/10
+authors: [james, florian]
+tags: []
+---
+
+## Weekly Update #2–3 — Litepaper, Landing Page and First Intuition Integration  
+
+The past two weeks have marked an **important milestone** in the development of the TrustSwap project.  
+Between design, documentation, and technical integration, we’ve been laying the groundwork for the future ecosystem.  
+
+---
+
+## Writing the Litepaper  
+We focused on writing the **Litepaper**, hosted directly on **Docusaurus**.  
+This document establishes the foundation of our vision, architecture, and the future direction of TrustSwap.  
+Our goal: to make the project **clear, credible, and transparent** for both users and partners.  
+
+---
+
+## Building the Landing Page  
+A brand-new **landing page** was created, designed as the main entry point into the TrustSwap ecosystem.  
+It highlights the key aspects of the protocol, our partners, and our core values:  
+> Trust, Transparency, and Community.  
+
+---
+
+## Brainstorming Future Features  
+We also took time to **brainstorm new features** and explore the direction we want the platform to take.  
+These discussions are shaping what TrustSwap will become in the long term —  
+a **community-governed DEX** built on transparency and trust-based metrics.  
+
+---
+
+## Integrating Intuition — The Trust Gauge  
+On the technical side, we started the first real integration of the **Intuition protocol** into TrustSwap.  
+This integration introduces the **Trust Gauge**, a visual indicator that reflects the **community’s confidence** in each token.  
+
+This feature will allow users to:  
+- **Visualize “For” and “Against” votes** directly on each token,  
+- Display a **dynamic trust score**,  
+- And eventually feed these insights into **governance and listing decisions**.  
+
+---
+
+
+The ecosystem is taking shape, a big week ahead ! TRUST 🚀  

apps/docus/blog/authors.yml

@@ -0,0 +1,21 @@
+florian:
+  name: Florian Tribout
+  title: TrustSwap — Builder
+  image_url: https://github.com/Florian-THP.png
+  page: true
+  socials:
+    x: Dev_TrustSwap
+    linkedin: florian-tribout-6202b1237
+    github: Florian-THP
+
+james:
+  name: James Barthée
+  title: TrustSwap — Builder
+  image_url: https://github.com/JamesDev292.png
+  page:
+    # customize the url of the author page at /blog/authors/<permalink>
+    permalink: '/all-james-barthee-articles'
+  socials:
+    x: 0xJmsDev
+    linkedin: james-barthee-386a5913b
+    github: JamesDev292

apps/docus/blog/tags.yml

@@ -0,0 +1,19 @@
+facebook:
+  label: Facebook
+  permalink: /facebook
+  description: Facebook tag description
+
+hello:
+  label: Hello
+  permalink: /hello
+  description: Hello tag description
+
+docusaurus:
+  label: Docusaurus
+  permalink: /docusaurus
+  description: Docusaurus tag description
+
+hola:
+  label: Hola
+  permalink: /hola
+  description: Hola tag description

apps/docus/docs/litepaper/01-introduction.md

@@ -0,0 +1,30 @@
+---
+title: Introduction
+sidebar_position: 1
+---
+
+
+
+
+The current DEX ecosystem focuses mainly on **DeFi mechanics** , routing efficiency, new AMM curves, **impermanent loss** protection, **yield** incentives, and so on. These advances are essential, but they overlook another crucial layer: **trust**.
+
+**TrustSwap** introduces a complementary approach, adding a **trust and reputation layer** on top of proven DeFi primitives. From day one, we integrate **Colony** to establish **meritocratic governance** (non-purchasable reputation, domain-based roles) and adopt **lazy voting** principles to avoid “theatrical” governance and streamline decision-making. This foundation puts every participant on the **same ladder of opportunity**: contribute → earn reputation → gain influence.
+
+On the **trust & data** side, the integration of **Intuition** brings **on-chain reputation** and collective knowledge directly into the DEX: *for/against* listing votes, community signals weighted by reputation, and transparency through a graph of claims (audits, team, history, etc.). We’re not replacing liquidity or algorithms, we’re **enhancing** their relevance through verifiable social signals.
+
+For **token launches**, we remain advocates of truly fair, open processes. **GBM Auctions** (bid-to-earn, transparent participation) is an excellent option, but we’re **open to other formats** , such as **LBPs** or **CoinMachine** , to achieve **greater simplicity and faster execution** depending on each project’s context. The goal: more equitable listings.
+
+TrustSwap keeps the **strengths of modern DEXs** while adding a **meritocratic layer of trust and reputation**.
+
+
+![Docs Intro](./img/image-intro.png)
+
+
+
+
+
+
+
+
+
+

apps/docus/docs/litepaper/02-probleme.md

@@ -0,0 +1,14 @@
+---
+title: Issue
+sidebar_position: 2
+---
+
+Despite the major progress made by DEXs, several **structural limitations** remain:
+
+* **Listing transparency:** While the blockchain itself is permissionless, most DEX interfaces are not. Visibility often depends on **whitelists or tokenlists** curated by teams (developers, aggregators). In practice, being “listed” means being **approved by maintainers**, based on subjective criteria, update delays, and with no reliable **trust signals** for users.
+
+* **Lack of reputation and historical context:** Today, a wallet is just an **address without context**, no native trust score, no weighting for longevity, behavior, contribution, or audits. On the project side (deployers, multisig signers, team wallets), **trust isn’t codified**: it’s hard to link a new token to a verifiable **track record**.
+
+* **Limited access for new projects:** Many emerging tokens struggle to secure both **initial liquidity** and **visibility** to attract early users, reinforcing the dominance of already-established tokens.
+
+* **Weak community involvement in governance:** Although many protocols claim to be “decentralized,” actual user participation in decision-making remains minimal, often reduced to symbolic votes on low-stakes proposals.