Publish the designer, too

Author: mekanix

.github/workflows/pages.yml

@@ -22,11 +22,24 @@ jobs:
       - name: Check out repository
         uses: actions/checkout@v4
 
+      - name: Check out designer repository
+        uses: actions/checkout@v4
+        with:
+          repository: freenit-framework/designer
+          path: designer
+
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
           python-version: "3.12"
 
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+          cache: npm
+          cache-dependency-path: designer/package-lock.json
+
       - name: Install documentation dependencies
         run: |
           python -m pip install --upgrade pip
@@ -36,9 +49,27 @@ jobs:
             mkdocs-awesome-pages-plugin \
             pymdown-extensions
 
+      - name: Install designer dependencies
+        working-directory: designer
+        run: npm ci
+
+      - name: Generate designer components
+        working-directory: designer
+        run: OFFLINE=yes ./bin/components.sh
+
+      - name: Build designer
+        working-directory: designer
+        run: npm run build
+
       - name: Build site
         run: mkdocs build --strict
 
+      - name: Add designer to published site
+        run: |
+          mkdir -p site/design
+          cp -R designer/build/. site/design/
+          touch site/.nojekyll
+
       - name: Upload Pages artifact
         uses: actions/upload-pages-artifact@v3
         with:

README.md

@@ -25,8 +25,10 @@ The MkDocs deployment guide explains that user/organization Pages deployments wi
 Instead, publishing is handled by GitHub Actions in [`.github/workflows/pages.yml`](/home/meka/repos/freenit-framework.github.io/.github/workflows/pages.yml). On each push to `master`, the workflow:
 
 1. installs MkDocs and the required plugins,
-2. builds the site with `mkdocs build --strict`,
-3. deploys the generated `site/` output to GitHub Pages.
+2. checks out and builds the `freenit-framework/designer` repository,
+3. builds the site with `mkdocs build --strict`,
+4. copies the designer static build into `site/design/`,
+5. deploys the generated `site/` output to GitHub Pages.
 
 ## One-time GitHub configuration