security-alliance
diff --git a/‎.devcontainer/Dockerfile‎
Lines changed: 0 additions & 14 deletions b/‎.devcontainer/Dockerfile‎
Lines changed: 0 additions & 14 deletions
diff --git a/‎.devcontainer/devcontainer.json‎
Lines changed: 5 additions & 4 deletions b/‎.devcontainer/devcontainer.json‎
Lines changed: 5 additions & 4 deletions
diff --git a/‎.github/PULL_REQUEST_TEMPLATE.md‎
Lines changed: 5 additions & 6 deletions b/‎.github/PULL_REQUEST_TEMPLATE.md‎
Lines changed: 5 additions & 6 deletions
diff --git a/‎.github/workflows/spell-check.yml‎
Lines changed: 25 additions & 31 deletions b/‎.github/workflows/spell-check.yml‎
Lines changed: 25 additions & 31 deletions
diff --git a/‎.gitignore‎
Lines changed: 3 additions & 2 deletions b/‎.gitignore‎
Lines changed: 3 additions & 2 deletions
diff --git a/‎CODE_OF_CONDUCT.md‎
Lines changed: 17 additions & 0 deletions b/‎CODE_OF_CONDUCT.md‎
Lines changed: 17 additions & 0 deletions
@@ -6,8 +6,6 @@ RUN apt-get update && apt-get install -y \
     build-essential \
     pkg-config \
     libssl-dev \
-    aspell \
-    aspell-en \
     curl \
     && apt-get clean \
     && rm -rf /var/lib/apt/lists/*
@@ -19,15 +17,6 @@ RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \
 # Switch to vscode user
 USER vscode
 
-# Install Rust and Cargo for vscode user
-RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
-ENV PATH="/home/vscode/.cargo/bin:${PATH}"
-
-# Install mdBook and mdbook-admonish
-RUN /home/vscode/.cargo/bin/cargo install mdbook mdbook-admonish
-
-# Install just command runner
-RUN /home/vscode/.cargo/bin/cargo install just
 
 # Install markdownlint-cli2 globally via npm (need root for global install)
 USER root
@@ -38,6 +27,3 @@ USER vscode
 
 # Set working directory
 WORKDIR /workspace
-
-# Ensure cargo is in PATH for vscode user
-RUN echo 'export PATH="/home/vscode/.cargo/bin:$PATH"' >> /home/vscode/.bashrc
@@ -12,8 +12,9 @@
         "vscode": {
             "extensions": [
                 "yzhang.markdown-all-in-one",
-                "rust-lang.rust-analyzer",
-                "tamasfe.even-better-toml"
+                "bradlc.vscode-tailwindcss",
+                "ms-vscode.vscode-typescript-next",
+                "esbenp.prettier-vscode"
             ],
             "settings": {
                 "terminal.integrated.defaultProfile.linux": "bash",
@@ -26,9 +27,9 @@
         }
     },
     "forwardPorts": [
-        3000
+        5173
     ],
     "workspaceMount": "source=${localWorkspaceFolder},target=/workspace,type=bind,consistency=cached",
     "workspaceFolder": "/workspace",
-    "postCreateCommand": "echo 'DevContainer ready! Run \"just serve\" to start the mdBook server.' && ip=$(hostname -I | awk '{print $1}'); echo \"After running 'just serve', access the mdBook at http://$ip:3000\""
+    "postCreateCommand": "echo 'DevContainer ready! Run \"npm run docs:dev -- --host port 5173\" to start the Vocs server.' && ip=$(hostname -I | awk '{print $1}'); echo \"After running 'npm run docs:dev', access the site at http://$ip:5173\""
 }
@@ -1,18 +1,17 @@
 ## Frameworks PR Checklist
 
-Thank you for contributing to the Security Frameworks! Before you open a PR, make sure to read [information for contributors](https://frameworks.securityalliance.dev/contribute/contributing.html) and take a look at the following checklist:
+Thank you for contributing to the Security Frameworks! Before you open a PR, make sure to read [information for contributors](https://frameworks.securityalliance.dev/contribute/contributing) and take a look at the following checklist:
 
 - [ ] Describe your changes, substitute this text with the information
 - [ ] If you are touching an existing piece of content, tag current contributors from the attribution list
 - [ ] If there is a steward for that framework, ask the steward to review it
-- [ ] If you're modifying the general outline, make sure to use `src/config/SUMMARY.develop` and not `src/SUMMARY.md`
+- [ ] If you're modifying the general outline, make sure to update it in the `vocs.config.ts` adding the `dev: true` parameter
 - [ ] If you need feedback for your content from the wider community, share the PR in our Discord
 - [ ] Review changes to ensure there are no typos, see instructions below
 
 <!--
 ℹ️ Checking for typos locally
-1. Install [aspell](https://www.gnu.org/software/aspell/) for your platform.
-2. Install [markdownlint-cli2](https://github.com/DavidAnson/markdownlint-cli2)
-3. Install [just](https://github.com/casey/just)
-4. Run `just lint`
+1. Install [markdownlint-cli2](https://github.com/DavidAnson/markdownlint-cli2)
+2. Install [just](https://github.com/casey/just)
+3. Run `npx just lint`
 -->
@@ -22,37 +22,31 @@ jobs:
           ref: ${{ github.event.pull_request.head.sha }}
           fetch-depth: 2
 
-      - name: Install aspell
-        run: sudo apt-get update && sudo apt-get install -y aspell
-
-      - name: Find and check typos in Markdown files
+      - name: Find and check typos in mdx files
         id: find_typos
         run: |
           echo "Checking for typos..."
-          # https://unix.stackexchange.com/a/9500
-          IFS=$'\n'
-          set -f
-          for file in $(find . -name "*.md" ); do
-            output="$(aspell --lang=en_US --mode=markdown --home-dir=. --personal=wordlist.txt --ignore-case=true --camel-case list <$file)"
-            echo "$output"
-            # Exit if aspell has errors
-            if [ $? -ne 0 ]; then
-              exit 1
-            fi
-            if [[ -n "$output" ]]; then
-              # Format output.
-              output=$(echo "$output" | sed 's/^/    1. /')
-              TYPOS+="- 📄 $file:"
-              TYPOS+=$'\n'
-              TYPOS+="$output"
-              TYPOS+=$'\n'
-            fi
-          done
-          {
-            echo 'TYPOS<<EOF'
-            echo "$TYPOS"
-            echo EOF
-          } >> "$GITHUB_ENV"
+          set -o pipefail
+          # Run cspell and capture output, but don't fail yet
+          output=$(npx cspell lint "docs/pages/**/*.mdx" --no-progress --no-summary || true)
+
+          if [[ -n "$output" ]]; then
+            echo "Typos found, formatting output..."
+            formatted=$(echo "$output" | nl -w2 -s'. ')
+            TYPOS+="- 📄 docs/pages:"
+            TYPOS+=$'\n'
+            TYPOS+='```'
+            TYPOS+=$'\n'
+            TYPOS+="$formatted"
+            TYPOS+=$'\n'
+            TYPOS+='```'
+            TYPOS+=$'\n\n'
+            {
+              echo 'TYPOS<<EOF'
+              echo "$TYPOS"
+              echo EOF
+            } >> "$GITHUB_ENV"
+          fi
 
       - name: Comment on pull request
         if: env.TYPOS != ''
@@ -61,7 +55,7 @@ jobs:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           script: |
             const author = '${{github.event.pull_request.user.login}}';
-            const typos = `${{ env.TYPOS }}`;
+            const typos = process.env.TYPOS;
             const body = `
             Hi @${author},
 
@@ -72,11 +66,11 @@ jobs:
             ## ℹ️ Here's how to fix them:
             - **Fix typos:** Open the relevant files and fix any identified typos.
             - **Update wordlist:** If a flagged word is actually a project-specific term add it to \`wordlist.txt\` in the project root.
-                Each word should be listed on a separate line. [Learn more.](http://aspell.net/man-html/Format-of-the-Personal-and-Replacement-Dictionaries.html)
+              Each word should be listed on a separate line.
             - **🚧 Remember:**
               - When adding new words it MUST NOT have any spaces or special characters within or around it.
               - \`wordlist\` is NOT case sensitive.
-              - Use backticks to quote code variables so as to not bloat the \`wordlist\`.
+              - If code variables are flagged, wrap them in backticks instead of adding them to the \`wordlist\`. This way they are treated as code and won’t bloat the \`wordlist\` with project-specific identifiers.
             `;
 
             github.rest.issues.createComment({
 
@@ -26,8 +26,9 @@ claude-code
 
 # Node.js dependencies
 node_modules/
-package.json
-package-lock.json
 
 # Claude Code configuration
 CLAUDE.md
+
+# Build folder
+**/dist/
@@ -12,6 +12,23 @@ and orientation.
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
 
+## Alignment with the Security Alliance (SEAL) Code of Conduct
+
+This initiative follows the [Security Alliance (SEAL) Code of Conduct](https://www.securityalliance.org/news/Code_of_conduct), which sets expectations for all members and contributors across the organization.
+
+At SEAL, we commit to:
+
+- **Be Accountable** – Take responsibility for commitments and actions.
+- **Act Ethically** – Never exploit skills or information for malicious advantage.
+- **Protect Sensitive Information** – Handle confidential data responsibly.
+- **Speak the Truth** – Be honest in communications, reporting, and attribution.
+- **Respect Others** – Treat colleagues, users, and competitors with respect.
+- **Stay Informed** – Continuously learn and share knowledge to protect others.
+
+**How This Applies to Our Initiative:**
+
+SEAL’s Code establishes the baseline expectations for all contributors. In this initiative, you are expected to meet SEAL’s standards ***and*** the additional guidelines outlined below.
+
 ## Our Standards
 
 Examples of behavior that contributes to a positive environment for our