chore: update tests to use site-generator-beta

.github/workflows/test.yaml

@@ -7,10 +7,8 @@ on:
 jobs:
   build:
     runs-on: ubuntu-latest
-    container: python:3.8
+    container: node:20
     steps:
       - uses: actions/checkout@v3
-      - name: Install the site-generator
-        run: pip install -r requirements.txt
-      - name: Build the site.
-        run: aep-site-gen . /out
+      - name: Generate all static pages, and build site.
+        run: ./scripts/build.sh

CONTRIBUTING.md

@@ -42,76 +42,18 @@ Some tips:
 ## Development Environment
 
 If you are contributing AEP content (rather than code) and want to be able to
-view it in your browser, the easiest way to do so is to run the provided
-development server.
+view it in your browser, the easiest way to do so is to run the site-generator
+script.
 
 We use [GitHub Pages][1] to make this documentation available, and a specific
 [site generator][2] to build the site.
 
-If you have [Docker][3] installed, clone this repository and run the `serve.sh`
-file at the root of the repository. This script does two things:
+Run `./scripts/serve.sh` to:
 
-- It builds the provided Docker image (unless you already have it) and tags it
-  as `aep-site`.
-- It runs the `aep-site` image.
-
-The development server uses port 4000; point your web browser to
-`http://localhost:4000`, and you should see the site.
-
-**Note:** After building the Docker image for the first time, you may
-experience issues if Python dependencies change underneath you. If this
-happens, remove your Docker image (`docker rmi aep-site`) and run `serve.sh`
-again.
-
-### Arguments
-
-Any arguments provided to `serve.sh` (or `docker run`) are forwarded (however,
-the current site generator does not honor any; this may change in the future).
+- clone the site-generator repository.
+- run the appropriate npm commands.
+- begin the dev server at port 4321.
 
 ### Hot reloading
 
-The development server recognizes when files change (including static files)
-and local changes will be automatically reflected in your browser upon reload.
-
-### Local Installation
-
-It is possible to run the development server locally also. The general gist of
-how to do so correctly is:
-
-- Install Python 3.8 if you do not already have it (direct install is fine, but
-  [pyenv][5] is probably the best way if you have other Python projects).
-- Create a Python 3.8 [venv][6]. Once it is created, activate it in your shell
-  (`source path/to/venv/bin/activate`).
-- `pip install git+https://github.com/aep-dev/site-generator.git`
-- `aep-site-serve .`
-
-## Contributor License Agreement
-
-Signing a Contributor License Agreement (CLA) is not required at this time.
-
-## Code reviews
-
-All submissions, including submissions by project members, require review. We
-use GitHub pull requests for this purpose. Consult
-[GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
-information on using pull requests.
-
-### Formatting
-
-We use [prettier][4] to format Markdown, JavaScript, and (most) HTML, in order
-to ensure a consistent style throughout our source. You can add prettier as a
-plugin in most development environments.
-
-Once it is installed, you can fix formatting by running the following in the
-root aep.dev directory:
-
-```sh
-prettier -w .
-```
-
-[1]: https://pages.github.com/
-[2]: https://github.com/aep-dev/site-generator
-[3]: https://docker.com/
-[4]: https://prettier.io/
-[5]: https://github.com/pyenv/pyenv
-[6]: https://docs.python.org/3/library/venv.html
+The development server currently does not support hot reloading.

scripts/build.sh

@@ -0,0 +1,18 @@
+#!/usr/bin/env bash
+set -x
+export AEP_LOCATION="${PWD}"
+export SG_DIRECTORY="/tmp/site-generator-beta"
+export AEP_LINTER_LOC="${SG_DIRECTORY}/api-linter"
+if [ ! -d "${SG_DIRECTORY}" ]; then
+    git clone https://github.com/aep-dev/site-generator-beta.git "${SG_DIRECTORY}"
+fi
+
+if [ ! -d "${AEP_LINTER_LOC}" ]; then
+    git clone https://github.com/aep-dev/api-linter.git "${AEP_LINTER_LOC}"
+fi
+cd "${SG_DIRECTORY}" || exit
+# make rules / website folder
+mkdir -p src/content/docs/tooling/linter/rules
+mkdir -p src/content/docs/tooling/website
+npm install
+npm run generate

scripts/serve.sh

@@ -0,0 +1,4 @@
+#!/usr/bin/env bash
+set -x
+. ./scripts/build.sh
+npm run preview