Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/dprk-it-workers/general-information.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "DPRK IT Workers Overview | Security Alliance"
title: "DPRK IT Workers: General Information | Security Alliance"
description: "What are DPRK IT Workers? Learn their operational structure, goals, and the average profile indicators to watch for."
tags:
- Security Specialist
Expand Down
4 changes: 2 additions & 2 deletions docs/pages/dprk-it-workers/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ title: "Dprk It Workers"

## Pages

- [Insider Threats (DPRK)](/dprk-it-workers/overview)
- [DPRK IT Workers Overview](/dprk-it-workers/general-information)
- [DPRK IT Workers](/dprk-it-workers/overview)
- [DPRK IT Workers: General Information](/dprk-it-workers/general-information)
- [DPRK IT Worker TTPs](/dprk-it-workers/techniques-tactics-and-procedures)
- [Mitigating DPRK IT Worker Threats](/dprk-it-workers/mitigating-dprk-it-workers)
- [DPRK IT Worker Case Studies](/dprk-it-workers/case-studies)
Expand Down
2 changes: 1 addition & 1 deletion docs/pages/dprk-it-workers/overview.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "Insider Threats (DPRK) | Security Alliance"
title: "DPRK IT Workers | Security Alliance"
description: "DPRK IT Workers Framework: Protect your organization from North Korean insider threats. Recognize hacker-freelancers, harden hiring processes, and mitigate supply-chain compromise risks."
tags:
- Security Specialist
Expand Down
1 change: 1 addition & 0 deletions docs/pages/intro/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,4 @@ title: "Intro"
- [Overview Of Each Framework](/intro/overview-of-each-framework)
- [What It Is](/intro/what-is-it)
- [What It Isn't](/intro/what-it-isnt)
- [LLMs | Security Alliance Frameworks](/intro/llms)
4 changes: 4 additions & 0 deletions docs/pages/intro/introduction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,10 @@ public good for the Web3 ecosystem, its supporting technologies, and communities
desire to foster a safer, more informed digital landscape. We do this by designing innovative projects, engaging elite
technologists, and coordinating on the social layer to ensure meaningful adoption.

:::info[AI-friendly documentation]
All framework content is available in LLM-friendly format following the [llms.txt](https://llmstxt.org/) standard - one file per framework, plus a routing index. See the [LLMs page](/intro/llms) for the full list.
:::

---

</TagProvider>
Expand Down
35 changes: 35 additions & 0 deletions docs/pages/intro/llms.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
title: LLMs | Security Alliance Frameworks
description: LLM-friendly documentation for the Security Alliance Frameworks, following the llms.txt standard.
---

# LLMs

The Security Alliance Frameworks documentation is available in LLM-friendly format following the [llms.txt](https://llmstxt.org/) standard. These files are generated at build time and designed to be fetched by AI assistants and coding tools to provide accurate, up-to-date framework content as context.

## How to use

AI assistants should start with [`/llms.txt`](https://frameworks.securityalliance.org/llms.txt), the routing index. It lists every available framework file with descriptions and a full table of contents, so the AI can identify the single best match and fetch only that file. Each framework file is self-contained.

## File structure

There is one file per framework, generated automatically from the framework's source pages in sidebar order:

```
/llms.txt routing index - lists all framework files
/llms-{framework-name}.txt full content of that framework
```

The `{framework-name}` maps directly to the framework's folder name in the repository. For example, the Wallet Security framework lives at `docs/pages/wallet-security/` and its llms file is at `/llms-wallet-security.txt`.

## What each file contains

Each framework file is structured as follows:

1. **Header** - framework title, description, and link to its documentation
2. **AI instructions** - how the AI should cite and use the content
3. **Pages** - every sidebar-listed page in the framework, in sidebar order, with:
- Page title and source URL
- Full markdown content

New frameworks are picked up automatically on the next build. The routing index is always up to date.
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"test": "echo \"Error: no test specified\" && exit 1",
"docs:dev": "pnpm run generate-tags && pnpm run generate-indexes && pnpm run mermaid-wrapper && vocs dev --host 0.0.0.0 --port 5173",
"docs:build": "pnpm run generate-tags && pnpm run generate-indexes && pnpm run mermaid-wrapper && pnpm run generate-printables && pnpm run generate-cert-data && vocs build",
"postdocs:build": "node utils/searchbar-indexing.js && node utils/sitemap-generator.js",
"postdocs:build": "node utils/searchbar-indexing.js && node utils/sitemap-generator.js && node utils/generate-llms.js",
"docs:preview": "vocs preview",
"generate-tags": "node utils/tags-fetcher.js",
"mermaid-wrapper": "node utils/mermaid-block-wrapper.js",
Expand Down
Loading
Loading