Update AdoPipelineViewReadme.md

Author: 1RedOne

AdoPipelineViewReadme.md

@@ -1,11 +1,13 @@
-# 🔧 Deployment Notes: AdoPipelineView SPA and Blog Integration
+# 🔧 Deployment Notes: AdoPipelineView and other Single page app (SPA) and Blog Integration Details
 
 ## 🧠 Context
 
-This repository is part of a two-repo setup used to host:
+The FoxDeploy blog  is part of a multi-repo setup used to host:
 
 - 📰 A **Jekyll-based blog** at **https://www.foxdeploy.com/**
-- ⚙️ A **standalone Single Page App (SPA)** at **https://www.foxdeploy.com/AdoPipelineView/**
+- ⚙️ Some **standalone Single Page Applications (SPA)** at:
+- - **https://www.foxdeploy.com/AdoPipelineView/**
+- - **https://www.foxdeploy.com/ArmJsonOsTargetingConditionParser/**
 
 The SPA and blog are hosted via **GitHub Pages**, but they live in **separate repositories** for clarity and cleaner dev workflows.
 
@@ -17,6 +19,7 @@ The SPA and blog are hosted via **GitHub Pages**, but they live in **separate re
 |-----|---------|-------------|
 | `https://www.foxdeploy.com/` | Main Jekyll blog | [`1redone.github.io`](https://github.com/1RedOne/1redone.github.io) |
 | `https://www.foxdeploy.com/AdoPipelineView/` | Deployed SPA | [`AdoPipelineView`](https://github.com/1RedOne/AdoPipelineView) |
+| `https://www.foxdeploy.com/ArmJsonOsTargetingConditionParser/` | Deployed SPA | [`OS Condition Targeting Parser`](https://github.com/1RedOne/ArmJsonOsTargetingConditionParser/tree/main) |
 
 ---
 
@@ -25,30 +28,72 @@ The SPA and blog are hosted via **GitHub Pages**, but they live in **separate re
 The SPA source code is **NOT inside the blog repo** (`1redone.github.io`) — instead, it is located in its own repository:
 
 > [`1RedOne/AdoPipelineView`](https://github.com/1RedOne/AdoPipelineView)
+> [`1RedOne/ArmJsonParser`](https://github.com/1RedOne/ArmJsonOsTargetingConditionParser)
 
-This repo builds a single-page app (`index.html`, etc.) and publishes it to GitHub Pages using either:
-
-- The `gh-pages` branch (recommended), OR
-- The `/docs` folder, OR
-- GitHub Actions with Pages deployment (e.g., `pages-build-deployment`)
+This repo builds a single-page app (`index.html`, etc.) and publishes it to GitHub Pages using the classic GitHub pages *DeployFromBranch* model, deploying from the `main` or `master` branches.
 
 You can confirm it is published successfully at:
 
 >https://github.com/1RedOne/AdoPipelineView/settings/pages
-
+>https://github.com/1RedOne/ArmJsonOsTargetingConditionParser/deployments/github-pages
 
 ---
 
-## 🔍 Why is this split across two repos?
+## 🔍 Why is this split across multiple repos?
+
+Keeping the SPA separate helps because the main repo for the blog is already bound to the root of the FoxDeploy.com domain name.
+
+These additional repos automatically inherit the FoxDeploy.com domain name when Pages are enabled, allowing their repo name to handle routing.  Some other benefits are :
 
-Keeping the SPA separate helps with:
-- Clean dev workflows (the SPA can use its own toolchain, like React, Vue, or Vite)
 - Independent deployments (no interference with Jekyll builds)
 - Smaller repos, faster CI
 - Easier separation of concerns
 
 The blog can safely link to the SPA without needing to embed or bundle it.
 
+#### Traffic Flow Chart
+```mermaid
+flowchart TD
+    %% Main Flow
+    A[User types<br>FoxDeploy.com] --> B[GoDaddy DNS/Hosting]
+    B -->|Redirects to| C[GitHub Pages<br>1redone.github.io]
+
+    %% Root Blog
+    C --> D[Root Repo: Blog]
+    D -->|Served at| E[https://www.FoxDeploy.com/]
+    E -->|Source of Truth| H[https://github.com/1RedOne/1redone.github.io]
+
+    %% Single Page Apps
+    C --> F[GitHub Repos for SPAs]
+
+    F --> SPA1[FoxDeploy.com/<span style="color:red">AdoPipelineView</span>]
+    SPA1 -->|Source of Truth| R1[https://github.com/1RedOne/AdoPipelineView]
+
+    F --> SPA2[FoxDeploy.com/<span style="color:red">JsonViewer</span>]
+    SPA2 -->|Source of Truth| R2[https://github.com/1RedOne/JsonViewer]
+
+    %% Future SPA
+    F --> FUTURE[FoxDeploy.com/<span style="color:red">RepoName</span>]
+    FUTURE -->|Future Source of Truth| RFUTURE[https://github.com/1RedOne/RepoName]
+
+    %% Styling with black text forced
+    style A fill:#f9f,stroke:#333,stroke-width:2px,color:#000
+    style B fill:#ffd580,stroke:#333,stroke-width:2px,color:#000
+    style C fill:#a0d2eb,stroke:#333,stroke-width:2px,color:#000
+    style D fill:#c1e1c1,stroke:#333,stroke-width:2px,color:#000
+    style E fill:#baffc9,stroke:#333,stroke-width:2px,color:#000
+    style H fill:#baffc9,stroke:#333,stroke-width:2px,color:#000
+
+    style F fill:#fce2ce,stroke:#333,stroke-width:2px,color:#000
+    style SPA1 fill:#fff2b2,stroke:#333,stroke-width:2px,color:#000
+    style SPA2 fill:#fff2b2,stroke:#333,stroke-width:2px,color:#000
+    style FUTURE fill:#f4c2c2,stroke:#333,stroke-width:2px,color:#000
+
+    style R1 fill:#cce5ff,stroke:#333,stroke-width:2px,color:#000
+    style R2 fill:#cce5ff,stroke:#333,stroke-width:2px,color:#000
+    style RFUTURE fill:#e0ccff,stroke:#333,stroke-width:2px,color:#000
+
+```
 
 
 ## 🧪 How to test changes to the SPA
@@ -111,6 +156,7 @@ Announce the new tool 🎉
 
 Explain what it does
 
+
 Link to https://www.foxdeploy.com/CoolNewViewer/
 
-Boom — you're done. Your new app is live, linked, and documented.
+Boom — you're done. Your new app is live, linked, and documented.