Merge branch 'main' into feat/roadmap-page

Author: adrianboros

.github/copilot-instructions.md

@@ -22,11 +22,14 @@ This is the Interledger Developers Portal, a documentation site built with [Astr
 - **Important**: Build output is copied to `_netlify/builders/developers/` to serve at `/developers/` path
 - Redirect rules route `/developers/*` to `/developers/index.html` for client-side routing
 
-### Production (Google Cloud)
-- Deployed to `https://interledger.org/developers/` via Google Cloud Storage
-- Triggered automatically on merge to `main` by `.github/workflows/deploy_gcs.yml`
-- Process: Build → Deploy to GCS → Rebuild nginx-rewrite Cloud Run service → Invalidate CDN
-- **Legacy**: `deploy.yml` exists but is deprecated - use `deploy_gcs.yml`
+### Production (Netlify, fronted by GCP)
+- Built and hosted by Netlify at `https://interledger-org-developers.netlify.app/developers/`
+- Users reach it at `https://interledger.org/developers/` via the GCP load balancer, which proxies `/developers/*` through a Cloud Run nginx service (`nginx-rewrite`) to Netlify
+- The address bar stays on `interledger.org` — it is **not** a redirect
+- GCP Cloud CDN sits in front of the proxy (default TTL 1 hour)
+- **After a content deploy**, if you need changes live immediately, manually run the **Invalidate CDN** workflow in the Actions tab
+- The `Deploy nginx proxy to Cloud Run` workflow (`.github/workflows/deploy_gcs.yml`) only rebuilds the proxy container and triggers on changes under `ci/nginx-rewrite/**`
+- The nginx config itself lives in `ci/nginx-rewrite/` (Dockerfile + nginx.conf)
 
 ## Key Development Notes
 

.github/workflows/deploy_gcs.yml

@@ -1,28 +1,21 @@
-name: Deploy to GCS
+name: Deploy nginx proxy to Cloud Run
 
 on:
-  # Trigger the workflow every time you push to the `main` branch
-  # Using a different branch name? Replace `main` with your branch's name
   push:
     branches: [main]
-  # Allows you to run this workflow manually from the Actions tab on GitHub.
+    paths:
+      - 'ci/nginx-rewrite/**'
   workflow_dispatch:
 
-# Allow this job to clone the repo and create a page deployment
 permissions:
   contents: read
-  pages: write
-  id-token: write
 
 jobs:
   deploy:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout your repository using git
-        uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
-        with:
-          node-version: 18
+        uses: actions/checkout@v4
 
       - name: Authenticate to Google Cloud
         uses: google-github-actions/auth@v2
@@ -32,15 +25,6 @@ jobs:
       - name: Set up Cloud SDK
         uses: google-github-actions/setup-gcloud@v2
 
-      - uses: oven-sh/setup-bun@v1
-      - name: Install dependencies
-        run: bun install
-      - name: Test build website
-        run: bun run build
-
-      - name: Deploy to GCS
-        run: gsutil -m rsync -r -d ./dist/ gs://${{ secrets.GCS_BUCKET }}/developers
-
       - name: Build nginx container
         run: |
           cd ci/nginx-rewrite
@@ -59,9 +43,3 @@ jobs:
             --min-instances 0 \
             --max-instances 10 \
             --quiet
-
-      - name: Invalidate CDN cache
-        run: |
-          gcloud compute url-maps invalidate-cdn-cache interledger-org \
-            --path "/developers/*" \
-            --async

.github/workflows/invalidate-cdn.yml

@@ -0,0 +1,25 @@
+name: Invalidate CDN
+
+on:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  invalidate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Authenticate to Google Cloud
+        uses: google-github-actions/auth@v2
+        with:
+          credentials_json: ${{ secrets.GSA_JSON }}
+
+      - name: Set up Cloud SDK
+        uses: google-github-actions/setup-gcloud@v2
+
+      - name: Invalidate CDN cache for /developers/*
+        run: |
+          gcloud compute url-maps invalidate-cdn-cache interledger-org \
+            --path "/developers/*" \
+            --async

.github/workflows/test-build.yml

@@ -16,10 +16,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout your repository using git
-        uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+        uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
         with:
-          node-version: 18
+          node-version: 22
 
       - uses: oven-sh/setup-bun@v1
       - name: Install dependencies

.nvmrc

@@ -1 +1 @@
-lts/iron
+22

README.md

@@ -81,18 +81,21 @@ This project has two deployment mechanisms:
 
 Every pull request automatically generates a preview deployment on Netlify at `https://deploy-preview-{PR_NUMBER}--developers-preview.netlify.app/developers/`. This allows reviewers to see changes before they're merged. The Netlify configuration is defined in `netlify.toml`.
 
-### Production Deployments (Google Cloud Storage)
+### Production Deployments (Netlify + GCP proxy)
 
-The real production deployment is served through Google Cloud Storage (GCS) at `https://interledger.org/developers/` as part of the main Interledger website. This is a transparent proxy configuration - the developers portal is hosted separately but appears as part of the main domain.
+The production site is built and hosted on Netlify, but users access it at `https://interledger.org/developers/` via the main Interledger load balancer. A small nginx service on Cloud Run proxies `/developers/*` requests from the GCP load balancer to the Netlify-hosted site, so the browser URL stays on `interledger.org`.
 
-When a PR is merged to the `main` branch, the `.github/workflows/deploy_gcs.yml` GitHub Actions workflow automatically:
+When a PR is merged to `main`, Netlify builds and publishes the new site automatically. GCP's Cloud CDN sits in front of the nginx proxy and caches responses for up to 1 hour.
 
-1. Builds the site using Bun
-2. Deploys the built files to Google Cloud Storage (`gs://interledger-websites-public/developers`)
-3. Rebuilds and deploys the nginx-rewrite Cloud Run service (which handles the `/developers` proxy routing)
-4. Invalidates the CDN cache to ensure new content is served immediately
+#### Invalidating the CDN after a deploy
 
-**Note:** There is a legacy `deploy.yaml` workflow in `.github/workflows/` which is being deprecated. New deployments should use `deploy_gcs.yml`.
+Because GCP Cloud CDN caches `/developers/*`, newly deployed content may take up to an hour to appear on `interledger.org/developers/`. If you need changes to go live immediately, manually trigger the **Invalidate CDN** workflow:
+
+1. Go to the repo's **Actions** tab on GitHub.
+2. Select the **Invalidate CDN** workflow.
+3. Click **Run workflow** on the `main` branch.
+
+This runs `gcloud compute url-maps invalidate-cdn-cache` against `/developers/*` and typically propagates within a minute.
 
 For more information about the main Interledger.org infrastructure and deployment pipeline, see the [`interledger.org-v4`](https://github.com/interledger/interledger.org-v4) repository.
 

astro.config.mjs

@@ -27,7 +27,10 @@ export default defineConfig({
         starlightLinksValidator({
           exclude: ['/participation-guidelines']
         }),
-        starlightFullViewMode({ leftSidebarEnabled: false })
+        starlightFullViewMode({
+          leftSidebarEnabled: true,
+          rightSidebarEnabled: true
+        })
       ],
       head: [
         {