Initial nowake.ai website

Author: Revolution1

.github/workflows/ci.yml

@@ -0,0 +1,31 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build website
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: latest
+          check-latest: true
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build

.github/workflows/cloudflare-pages.yml

@@ -0,0 +1,53 @@
+name: Deploy Cloudflare Pages
+
+on:
+  workflow_dispatch:
+
+# Enable automatic production deploys after Cloudflare secrets and the Pages
+# project are configured:
+#
+# on:
+#   push:
+#     branches:
+#       - main
+#   workflow_dispatch:
+
+permissions:
+  contents: read
+  deployments: write
+
+concurrency:
+  group: cloudflare-pages-production
+  cancel-in-progress: true
+
+jobs:
+  deploy:
+    name: Deploy website
+    runs-on: ubuntu-latest
+    environment:
+      name: cloudflare-pages
+      url: ${{ steps.deploy.outputs.deployment-url }}
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: latest
+          check-latest: true
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build
+
+      - name: Deploy to Cloudflare Pages
+        id: deploy
+        uses: cloudflare/wrangler-action@v3
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
+          command: pages deploy dist --project-name=nowake-ai-website --branch=main

.gitignore

@@ -0,0 +1,3 @@
+node_modules/
+dist/
+.astro/

AGENTS.md

@@ -0,0 +1,33 @@
+# Website Agent Instructions
+
+## Dependency Policy
+
+The `website/` directory is the nowake.ai site repository.
+
+This site currently has no legacy compatibility burden.
+
+When adding or upgrading tools, frameworks, libraries, runtimes, or build dependencies, prefer the latest stable version by default.
+
+Do not pin to older major versions for compatibility unless there is a clear, documented reason, such as:
+
+- the latest stable version is incompatible with the target runtime or hosting platform;
+- the latest stable version has a known blocking bug or security issue;
+- a project-specific integration explicitly requires an older version.
+
+If an older dependency version is chosen, document the reason near the dependency change or in the relevant project notes.
+
+## Project Page Content Rules
+
+When creating or revising a project page, follow `PROJECT_PAGE_STANDARD.md`. Project pages must share nowake.ai visual language, but each project needs a page structure tailored to its own product shape; do not reuse one fixed page template across projects.
+
+For every project page, do both jobs well:
+
+- Explain the project principle clearly enough that a new visitor can understand how it works.
+- Put the core product selling points near the top, in concise and concrete language.
+
+Do not let architecture explanation bury the value proposition. Project pages should make the main benefit obvious before deeper implementation details.
+
+Current emphasis:
+
+- `kube-insight`: treat it as a foundational AIOps infrastructure component with large future surface area. Its page can use more eye-catching, forceful copy, but the claims must stay grounded in concrete retained-evidence workflows, performance proof, and current shipped capabilities. Highlight that it is agent-friendly, supports multiple operating/storage modes, and can be dramatically faster than broad live `kubectl` investigation workflows because it queries retained, pre-extracted evidence.
+- `svc-lb-mux`: treat it as a narrow, original, operations-first tool for teams that need to expose many TCP/UDP services through provider L4 load balancers while caring about cost, quota, IP, forwarding rule, or port pressure. Its copy should be plain and specific: make the use case, user, product advantage, provider limits, and migration path obvious before controller internals.

DEPLOYMENT.md

@@ -0,0 +1,36 @@
+# Deployment
+
+The nowake.ai website is a static Astro site designed for Cloudflare Pages.
+
+## Cloudflare Pages Project
+
+Recommended project settings:
+
+- Project name: `nowake-ai-website`
+- Production branch: `main`
+- Build command: `npm run build`
+- Build output directory: `dist`
+- Node.js version: latest stable Node.js available in the build environment
+
+## GitHub Actions Direct Upload
+
+This repository includes `.github/workflows/cloudflare-pages.yml`, which deploys `dist` with Wrangler after a successful build. It is intentionally manual-only until the Cloudflare Pages project and GitHub secrets are configured. Enable the commented `push` trigger after the first successful manual deployment.
+
+Required GitHub Actions secrets:
+
+- `CLOUDFLARE_API_TOKEN`: Cloudflare API token with Cloudflare Pages edit/deploy permission for the target account.
+- `CLOUDFLARE_ACCOUNT_ID`: Cloudflare account ID.
+
+The workflow deploys with:
+
+```console
+wrangler pages deploy dist --project-name=nowake-ai-website --branch=main
+```
+
+## Dashboard Git Integration Alternative
+
+If using Cloudflare Pages Git integration instead of GitHub Actions direct upload, connect `nowakeai/website` and use the same project settings above.
+
+## Custom Domain
+
+After the Pages project exists, add `nowake.ai` and optionally `www.nowake.ai` as custom domains in Cloudflare Pages. Keep DNS proxied through Cloudflare.