Build docs from PlanExe2 docs/website/ instead of PlanExe v1

Drop the v1 nav, component README copying, nav-status CSS and proposals
nav injection. v1 docs remain readable in PlanExe/docs on GitHub.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: neoneye

.github/workflows/deploy.yml

@@ -5,7 +5,7 @@ on:
     branches:
       - main
   workflow_dispatch:
-  # Trigger on changes to PlanExe repo (requires repository_dispatch or manual trigger)
+  # Trigger on changes to the source repo (requires repository_dispatch or manual trigger)
   repository_dispatch:
     types: [docs-updated]
 
@@ -22,10 +22,10 @@ jobs:
         with:
           fetch-depth: 0
 
-      - name: Checkout PlanExe (source)
+      - name: Checkout PlanExe2 (source)
         uses: actions/checkout@v4
         with:
-          repository: PlanExeOrg/PlanExe
+          repository: PlanExeOrg/PlanExe2
           path: planexe-source
           token: ${{ secrets.GITHUB_TOKEN }}
 
@@ -40,7 +40,7 @@ jobs:
       
       - name: Build documentation
         run: |
-          PLANEXE_REPO=planexe-source DOCS_SOURCE_DIR=docs python build.py
+          PLANEXE_REPO=planexe-source DOCS_SOURCE_DIR=docs/website python build.py
       
       - name: Deploy to GitHub Pages
         uses: peaceiris/actions-gh-pages@v3

AGENTS.md

@@ -173,4 +173,5 @@ If you're unsure where to start or have questions:
 
 - **Tone**: keep docs factual and direct; avoid marketing language.
 - **Social cards**: configured in `mkdocs.yml` via the `social` plugin; titles come from page front matter (`title:`) when needed.
-- **Branding**: social cards use the PlanExe logo from `PlanExe/docs/assets/logo.svg` (copied during build).
+- **Source**: pages live in `PlanExe2/docs/website/`; only that directory is copied into the build.
+- **Branding**: social cards use the PlanExe logo from `PlanExe2/docs/website/assets/logo.svg` (copied during build).

README.md

@@ -4,11 +4,13 @@ This repository contains the built documentation for [PlanExe](https://planexe.o
 
 ## Overview
 
-The documentation source files are maintained in the main [PlanExe repository](https://github.com/PlanExeOrg/PlanExe) in the `docs` directory. This repository contains the compiled output from MkDocs Material, which is automatically deployed to GitHub Pages.
+The documentation source files are maintained in the [PlanExe2 repository](https://github.com/PlanExeOrg/PlanExe2) in the `docs/website/` directory. Only that directory is published; the rest of `PlanExe2/docs/` is internal. This repository contains the build configuration; MkDocs Material output is deployed to GitHub Pages.
+
+The PlanExe v1 documentation is no longer published here; it remains readable in [PlanExe/docs](https://github.com/PlanExeOrg/PlanExe/tree/main/docs).
 
 ## Architecture
 
-- **Source**: [PlanExeOrg/PlanExe/docs](https://github.com/PlanExeOrg/PlanExe/tree/main/docs)
+- **Source**: [PlanExeOrg/PlanExe2/docs/website](https://github.com/PlanExeOrg/PlanExe2/tree/main/docs/website)
 - **Build Tool**: MkDocs Material
 - **Output**: This repository (deployed to GitHub Pages)
 - **Domain**: docs.planexe.org
@@ -39,8 +41,8 @@ The documentation source files are maintained in the main [PlanExe repository](h
    git clone https://github.com/PlanExeOrg/PlanExe-docs.git
    cd PlanExe-docs
 
-   # Clone the PlanExe repo (adjust path as needed)
-   git clone https://github.com/PlanExeOrg/PlanExe.git ../PlanExe
+   # Clone the PlanExe2 repo (adjust path as needed)
+   git clone https://github.com/PlanExeOrg/PlanExe2.git ../PlanExe2
    ```
 
 4. Build the documentation:
@@ -50,8 +52,8 @@ The documentation source files are maintained in the main [PlanExe repository](h
 
    Or manually:
    ```bash
-   # Copy docs from PlanExe repo
-   cp -r ../PlanExe/docs/* docs/
+   # Copy docs from PlanExe2 repo
+   cp -r ../PlanExe2/docs/website/* docs/
 
    # Build
    mkdocs build
@@ -65,10 +67,10 @@ The documentation source files are maintained in the main [PlanExe repository](h
 
 ### Custom Build Paths
 
-If your PlanExe repo is in a different location:
+If your PlanExe2 repo is in a different location:
 
 ```bash
-PLANEXE_REPO=/path/to/PlanExe DOCS_SOURCE_DIR=docs python build.py
+PLANEXE_REPO=/path/to/PlanExe2 DOCS_SOURCE_DIR=docs/website python build.py
 ```
 
 ## Deployment
@@ -96,15 +98,15 @@ PLANEXE_REPO=/path/to/PlanExe DOCS_SOURCE_DIR=docs python build.py
 
 See `.github/workflows/deploy.yml` for GitHub Actions automation.
 
-**Why doesn’t the site rebuild when I push docs changes in PlanExe?**
+**Why doesn’t the site rebuild when I push docs changes in PlanExe2?**
 
-The docs site is built and deployed from **this** repo (PlanExe-docs). Pushing to the **PlanExe** repo does not run workflows here. Rebuilds happen when:
+The docs site is built and deployed from **this** repo (PlanExe-docs). Pushing to **PlanExe2** does not run workflows here. Rebuilds happen when:
 
-1. **Someone pushes to `main` on PlanExe-docs** (this repo), or  
-2. **Someone manually runs** the “Deploy Documentation” workflow in PlanExe-docs (Actions → Deploy Documentation → Run workflow), or  
-3. **The PlanExe repo triggers a rebuild** when `docs/` changes on `main`.
+1. **Someone pushes to `main` on PlanExe-docs** (this repo), or
+2. **Someone manually runs** the “Deploy Documentation” workflow in PlanExe-docs (Actions → Deploy Documentation → Run workflow), or
+3. **A `repository_dispatch` of type `docs-updated`** is sent to this repo.
 
-For (3), the [PlanExe repo](https://github.com/PlanExeOrg/PlanExe) has a workflow (`.github/workflows/docs-update.yml`) that sends a `repository_dispatch` to this repo when files under `docs/` change. For that to work you must configure a secret in the **PlanExe** repo named **`PLANEXE_DOCS_DISPATCH_TOKEN`** (PlanExe → Settings → Secrets and variables → Actions).
+PlanExe2 has no workflow that sends (3) yet, so after merging docs changes in PlanExe2, use (2). To automate it, add a workflow to PlanExe2 that sends the dispatch when `docs/website/**` changes on `main`, with a secret named **`PLANEXE_DOCS_DISPATCH_TOKEN`** (PlanExe2 → Settings → Secrets and variables → Actions). The PlanExe v1 repo has such a workflow (`.github/workflows/docs-update.yml`) that can be used as a template; while it is active, v1 docs changes also trigger a (harmless) rebuild of this site.
 
 **Token value:** use a GitHub Personal Access Token that can trigger workflows in this repo. A **fine-grained** token is recommended (narrower permissions). Fine-grained tokens have a **maximum expiration of 1 year**, so the secret must be renewed annually.
 
@@ -114,20 +116,20 @@ For (3), the [PlanExe repo](https://github.com/PlanExeOrg/PlanExe) has a workflo
 2. **Generate new token** (or open an existing one to regenerate/check expiry).
 3. **Token name:** e.g. `PlanExe docs dispatch`.
 4. **Expiration:** set the maximum (1 year); add a calendar reminder to renew before it expires.
-5. **Resource owner:** your user or the org that owns PlanExe.
+5. **Resource owner:** your user or the org that owns PlanExe2.
 6. **Repository access:** Only select repositories → choose **PlanExeOrg/PlanExe-docs**.
 7. **Permissions → Repository permissions:** set **Contents** to **Read and write** (required for the `repository_dispatch` API; Actions alone is not enough).
-8. Generate the token, copy it (it is shown only once), then in the **PlanExe** repo update the **`PLANEXE_DOCS_DISPATCH_TOKEN`** secret with this value.
+8. Generate the token, copy it (it is shown only once), then in the source repo update the **`PLANEXE_DOCS_DISPATCH_TOKEN`** secret with this value.
 
 **Alternative:** a [classic PAT](https://github.com/settings/tokens) with **`repo`** scope also works and can have a longer or no expiration.
 
-If the secret is missing or expired, the “Notify docs deploy” job in PlanExe will fail and the site will not rebuild. Until the token is set, use option (2) and manually run “Deploy Documentation” in PlanExe-docs after merging docs changes.
+If the secret is missing or expired, the “Notify docs deploy” job in the source repo will fail and the site will not rebuild. Until then, use option (2).
 
 **Troubleshooting deployment**
 
 The main place to check is the **PlanExe-docs Actions** page: **[github.com/PlanExeOrg/PlanExe-docs/actions](https://github.com/PlanExeOrg/PlanExe-docs/actions)**. There you can see all workflow runs: “Deploy Documentation” (builds the site and deploys to GitHub Pages) and “pages build and deployment” (GitHub’s Pages publish). Runs triggered by a docs change in PlanExe show the event **docs-updated** and “Repository dispatch triggered by …”. Use this page to confirm a deploy ran, re-run a failed workflow, or manually start “Deploy Documentation” (Actions → Deploy Documentation → Run workflow).
 
-- **Site didn’t update after pushing to PlanExe/docs?** Open the [PlanExe-docs Actions](https://github.com/PlanExeOrg/PlanExe-docs/actions) page. If there is no “Deploy Documentation” run for your push, the trigger from PlanExe likely failed — check the [PlanExe Actions](https://github.com/PlanExeOrg/PlanExe/actions) tab: a failed “Notify docs deploy” job will show the API error (e.g. token missing **Contents: Read and write**). If “Deploy Documentation” ran but failed, open that run and fix the error shown in the logs. If it succeeded, wait a minute or two for GitHub Pages to update and try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or a private window to avoid cache.
+- **Site didn’t update after pushing to PlanExe2/docs/website?** Open the [PlanExe-docs Actions](https://github.com/PlanExeOrg/PlanExe-docs/actions) page. If there is no “Deploy Documentation” run for your push, the trigger from PlanExe likely failed — check the [PlanExe Actions](https://github.com/PlanExeOrg/PlanExe/actions) tab: a failed “Notify docs deploy” job will show the API error (e.g. token missing **Contents: Read and write**). If “Deploy Documentation” ran but failed, open that run and fix the error shown in the logs. If it succeeded, wait a minute or two for GitHub Pages to update and try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R) or a private window to avoid cache.
 - **“Notify docs deploy” succeeded in PlanExe, but no “Deploy Documentation” run appears in PlanExe-docs?** The dispatch API may have rejected the request (e.g. 403). Fine-grained tokens need **Contents: Read and write** on PlanExe-docs; **Actions** alone is not enough. Update the token with that permission and update **`PLANEXE_DOCS_DISPATCH_TOKEN`** in the PlanExe repo. After the change, the PlanExe workflow fails the job and prints the API response when the dispatch is rejected, so the exact error will appear in [PlanExe Actions](https://github.com/PlanExeOrg/PlanExe/actions).
 
 ## Configuration
@@ -136,15 +138,15 @@ The MkDocs configuration is in `mkdocs.yml`. Key settings:
 
 - **Site URL**: https://docs.planexe.org
 - **Theme**: Material for MkDocs
-- **Source**: Points to PlanExe repo's `docs` directory
+- **Source**: Points to PlanExe2 repo's `docs/website` directory
 
 ## Contributing
 
 To contribute to the documentation:
 
-1. Edit files in the [PlanExe repository's `docs` directory](https://github.com/PlanExeOrg/PlanExe/tree/main/docs)
+1. Edit files in the [PlanExe2 repository's `docs/website` directory](https://github.com/PlanExeOrg/PlanExe2/tree/main/docs/website)
 2. Build and test locally using the instructions above
-3. Submit a pull request to the PlanExe repository
+3. Submit a pull request to the PlanExe2 repository
 4. After merging, rebuild and deploy to this repository
 
 ## License

build.py

@@ -1,7 +1,7 @@
 #!/usr/bin/env python3
 """
 Build script for PlanExe documentation.
-This script builds the docs from the PlanExe repo and outputs to this repo.
+This script builds the docs from the PlanExe2 repo (docs/website/) and outputs to this repo.
 """
 
 import os
@@ -10,7 +10,6 @@
 import subprocess
 import tempfile
 from pathlib import Path
-import yaml
 
 # ANSI color codes
 GREEN = '\033[0;32m'
@@ -27,19 +26,19 @@ def print_colored(message: str, color: str = NC):
 def main():
     """Main build function."""
     # Configuration
-    planexe_repo = Path(os.environ.get("PLANEXE_REPO", "../PlanExe"))
-    docs_source_dir = os.environ.get("DOCS_SOURCE_DIR", "docs")
+    planexe_repo = Path(os.environ.get("PLANEXE_REPO", "../PlanExe2"))
+    docs_source_dir = os.environ.get("DOCS_SOURCE_DIR", "docs/website")
     output_dir = "site"
 
     print_colored("Building PlanExe documentation...", GREEN)
 
     # Check if PlanExe repo exists
     if not planexe_repo.exists() or not planexe_repo.is_dir():
         print_colored(
-            f"Error: PlanExe repo not found at {planexe_repo}",
+            f"Error: PlanExe2 repo not found at {planexe_repo}",
             RED
         )
-        print("Set PLANEXE_REPO environment variable to point to the PlanExe repository")
+        print("Set PLANEXE_REPO environment variable to point to the PlanExe2 repository")
         sys.exit(1)
 
     # Check if docs source directory exists
@@ -78,95 +77,9 @@ def main():
         )
         shutil.copytree(docs_source_path, docs_dir, dirs_exist_ok=True)
 
-        # Ensure custom CSS for nav status icons exists (PlanExe-docs override).
-        nav_css_path = docs_dir / "assets" / "stylesheets" / "nav-status.css"
-        nav_css_path.parent.mkdir(parents=True, exist_ok=True)
-        nav_css_path.write_text(
-            ".md-nav__link .md-status--proposal { display: none; }\n",
-            encoding="utf-8",
-        )
-        
-        # Copy component READMEs into docs/developer/ so they are part of the built docs
-        developer_dir = docs_dir / "developer"
-        developer_dir.mkdir(exist_ok=True)
-        component_readmes = [
-            ("open_dir_server", "README.md"),
-            ("worker_plan", "README.md"),
-            ("frontend_single_user", "README.md"),
-            ("database_postgres", "README.md"),
-            ("worker_plan_database", "README.md"),
-            ("frontend_multi_user", "README.md"),
-            ("mcp_local", "README.md"),
-            ("mcp_cloud", "README.md"),
-        ]
-        for component, readme_name in component_readmes:
-            src = planexe_repo / component / readme_name
-            dst = developer_dir / f"{component}.md"
-            if src.exists():
-                shutil.copy2(src, dst)
-            else:
-                print_colored(
-                    f"Warning: {src} not found, skipping for docs",
-                    YELLOW
-                )
-        
         # Copy mkdocs.yml to temp directory
         shutil.copy2(mkdocs_yml, temp_docs_path / "mkdocs.yml")
 
-        # Inject proposals into nav (alphabetical) if proposals dir exists.
-        proposals_dir = docs_dir / "proposals"
-        if proposals_dir.exists():
-            class _IgnoreUnknownTagLoader(yaml.SafeLoader):
-                pass
-
-            def _construct_undefined(loader, node):
-                return node.value
-
-            _IgnoreUnknownTagLoader.add_constructor(None, _construct_undefined)
-
-            mkdocs_temp_path = temp_docs_path / "mkdocs.yml"
-            with open(mkdocs_temp_path, "r") as f:
-                mkdocs_config = yaml.load(f, Loader=_IgnoreUnknownTagLoader)
-
-            def _collect_proposals(directory: Path, url_prefix: str) -> list:
-                entries = []
-                files = sorted(
-                    [
-                        p for p in directory.glob("*.md")
-                        if p.name.lower() != "agents.md"
-                    ],
-                    key=lambda p: p.name.lower(),
-                )
-                for proposal_path in files:
-                    title = proposal_path.stem.replace("_", " ").replace("-", " ").strip()
-                    entries.append({title: f"{url_prefix}{proposal_path.name}"})
-                return entries
-
-            proposals_nav = _collect_proposals(proposals_dir, "proposals/")
-
-            for subdir_name, label in (("archive", "Archive"), ("done", "Done")):
-                subdir = proposals_dir / subdir_name
-                if subdir.exists():
-                    sub_entries = _collect_proposals(subdir, f"proposals/{subdir_name}/")
-                    if sub_entries:
-                        proposals_nav.append({label: sub_entries})
-
-            nav = mkdocs_config.get("nav", [])
-            for entry in nav:
-                if isinstance(entry, dict) and "Development" in entry:
-                    dev_items = entry["Development"]
-                    if isinstance(dev_items, list):
-                        dev_items = [
-                            item for item in dev_items
-                            if not (isinstance(item, dict) and "Proposals" in item)
-                        ]
-                        dev_items.append({"Proposals": proposals_nav})
-                        entry["Development"] = dev_items
-                    break
-
-            with open(mkdocs_temp_path, "w") as f:
-                yaml.safe_dump(mkdocs_config, f, sort_keys=False)
-        
         # Build the documentation
         print_colored("Building with mkdocs...", YELLOW)
 

mkdocs.yml

@@ -1,63 +1,16 @@
-site_name: PlanExe Documentation
+site_name: PlanExe2 Documentation
 site_description: From a single goal statement to a full strategic plan. Free and open source.
 site_url: https://docs.planexe.org
-repo_url: https://github.com/PlanExeOrg/PlanExe
-repo_name: PlanExeOrg/PlanExe
-edit_uri: edit/main/docs/
+repo_url: https://github.com/PlanExeOrg/PlanExe2
+repo_name: PlanExeOrg/PlanExe2
+edit_uri: edit/main/docs/website/
 
 nav:
-  - Getting started:
-    - Welcome: index.md
-    - Start here: start_here.md
-    - Getting started: getting_started.md
-    - Prompt writing guide: prompt_writing_guide.md
-    - Plan output anatomy: plan_output_anatomy.md
-    - Costs and models: costs_and_models.md
-    - FAQ: faq.md
-    - Statistics: statistics.md
-  - MCP:
-    - Welcome: mcp/mcp_welcome.md
-    - MCP setup: mcp/mcp_setup.md
-    - MCP registry publishing: mcp/mcp_registry.md
-    - MCP Inspector: mcp/inspector.md
-    - Claude: mcp/claude.md
-    - Cursor: mcp/cursor.md
-    - Codex: mcp/codex.md
-    - Antigravity: mcp/antigravity.md
-    - Windsurf: mcp/windsurf.md
-    - LM Studio: mcp/lm_studio.md
-    - MCP details: mcp/mcp_details.md
-    - MCP troubleshooting: mcp/mcp_troubleshooting.md
-    - PlanExe MCP interface: mcp/planexe_mcp_interface.md
-    - Autonomous agent guide: mcp/autonomous_agent_guide.md
-  - Development:
-    - Developer plan: plan.md
-    - Docker: docker.md
-    - Developer install: install_developer.md
-    - OAuth setup: oauth.md
-    - LLM config: llm_config.md
-    - Token counting: token_counting.md
-    - Components:
-      - open_dir_server: developer/open_dir_server.md
-      - worker_plan: developer/worker_plan.md
-      - frontend_single_user: developer/frontend_single_user.md
-      - database_postgres: developer/database_postgres.md
-      - worker_plan_database: developer/worker_plan_database.md
-      - frontend_multi_user: developer/frontend_multi_user.md
-      - mcp_local: developer/mcp_local.md
-      - mcp_cloud: developer/mcp_cloud.md
-    - AI providers:
-      - OpenRouter: ai_providers/openrouter.md
-      - Anthropic: ai_providers/anthropic.md
-      - Ollama: ai_providers/ollama.md
-      - LM Studio: ai_providers/lm_studio.md
-      - Mistral: ai_providers/mistral.md
-    - Status: status.md
-    - Railway: railway.md
-    - Deployment and hosting: deployment_hosting.md
-    - Docs style guide: docs_style_guide.md
-    - Troubleshooting:
-      - Stuck pipeline: troubleshooting_stuck_pipeline.md
+  - Welcome: index.md
+  - Getting started: getting_started.md
+  - The report: report.md
+  - Commands: commands.md
+  - How it works: how_it_works.md
 
 theme:
   name: material
@@ -114,7 +67,6 @@ extra_javascript:
 
 extra_css:
   - assets/stylesheets/copy-all.css
-  - assets/stylesheets/nav-status.css
 
 extra:
   analytics: