Skip to content

docs(landing): align with three-pillar spine #855

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danielmeppiel merged 1 commit into from
Apr 22, 2026
+10 −10
Merged

docs(landing): align with three-pillar spine #855

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
20 changes: 10 additions & 10 deletions docs/src/content/docs/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,22 +20,22 @@ import { Card, CardGrid, Tabs, TabItem } from '@astrojs/starlight/components';

**An open-source dependency manager for AI agents.** Think `package.json`, `requirements.txt`, or `Cargo.toml` — but for AI agent configuration.

AI coding agents need context and capabilities to be useful — instructions, skills, prompts, plugins, MCP servers. But today, every developer configures theirs differently. Copying files, writing instructions from scratch, sharing knowledge in Slack threads. None of it is portable. None of it is versioned.
AI coding agents need context and capabilities to be useful — instructions, skills, prompts, plugins, MCP servers. But today every developer configures theirs differently. Nothing is portable. Nothing is reproducible. Nothing is governed.

APM fixes this. You declare your project's agent configuration once in `apm.yml` — skills, prompts, instructions, agents, hooks, plugins, MCP servers — and every developer who clones your repo gets a fully configured agent setup in seconds. New developer joins the team? `git clone`, `cd`, `apm install`. Done.
APM fixes this. You declare your project's agent configuration once in `apm.yml` — and every developer who clones your repo gets a fully configured agent setup in seconds, locked to exact versions, scanned for hidden threats, and gated by the policies your organization defines.
Comment on lines 21 to +25
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-ASCII punctuation (em dashes) is used in these lines. Per the repo's encoding rules, docs must stay within printable ASCII to avoid cross-platform encoding issues; please replace these with ASCII alternatives (e.g., "--" or "-" and adjust spacing as needed).

This issue also appears in the following locations of the same file:

  • line 29
  • line 34

Copilot generated this review using guidance from repository custom instructions.

<CardGrid>
<Card title="One Manifest, Every Agent" icon="document">
`apm.yml` declares skills, instructions, prompts, agents, hooks, plugins, and MCP servers — deployed to Copilot, Claude Code, Cursor, OpenCode, and Codex from a single source of truth.
<Card title="Portable by manifest" icon="document">
One `apm.yml` declares skills, instructions, prompts, agents, hooks, plugins, and MCP servers. Transitive dependencies resolve like npm or pip; `apm.lock.yaml` pins exact versions for reproducible installs across Copilot, Claude Code, Cursor, OpenCode, and Codex.
</Card>
<Card title="Dependencies That Resolve" icon="random">
Packages depend on packages. APM resolves the full tree — transitive dependencies just work, like npm or pip.
<Card title="Secure by default" icon="approve-check-circle">
Skills, prompts, instructions, hooks — everything agents execute is an attack surface. `apm install` scans packages for hidden Unicode and other tampering before they reach your agents; `apm audit` reports the full chain of trust.
</Card>
<Card title="Any Git Host" icon="github">
Install from GitHub, GitLab, Bitbucket, Azure DevOps, GitHub Enterprise, or any self-hosted git server.
<Card title="Governed by policy" icon="setting">
`apm-policy.yml` lets platform teams allow-list dependencies, restrict deploy targets, and enforce trust rules at install time — across every repo, from a single source of truth. See the [Governance Guide](/apm/enterprise/governance-guide/).
Copy link

Copilot AI Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This copy says policy can "restrict deploy targets", but the policy engine's target restrictions are expressed as compilation targets (the target field in apm.yml, enforced by the compilation-target check). Consider rewording to "restrict compilation targets" (or similar) to match the actual schema and checks.

Suggested change
`apm-policy.yml` lets platform teams allow-list dependencies, restrict deploy targets, and enforce trust rules at install time — across every repo, from a single source of truth. See the [Governance Guide](/apm/enterprise/governance-guide/).
`apm-policy.yml` lets platform teams allow-list dependencies, restrict compilation targets, and enforce trust rules at install time -- across every repo, from a single source of truth. See the [Governance Guide](/apm/enterprise/governance-guide/).

Copilot uses AI. Check for mistakes.
</Card>
<Card title="Supply Chain Security" icon="approve-check-circle">
Skills, prompts, instructions, hooks — everything agents execute is an attack surface. APM scans packages before deployment, blocking threats before they reach your agents.
<Card title="Any git host" icon="github">
Install from GitHub, GitLab, Bitbucket, Azure DevOps, GitHub Enterprise, or any self-hosted git server. No registry to run, no central service to depend on.
</Card>
</CardGrid>

Expand Down
Loading