Skip to content
Merged
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
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
9 changes: 0 additions & 9 deletions .changeset/whats-new-in-3-1.md

This file was deleted.

Binary file added dist/docs/2.5.3/adcp-flows.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added dist/docs/2.5.3/adcp_flows.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
40 changes: 40 additions & 0 deletions dist/docs/2.5.3/community/working-group.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: Working Group
---


The Ad Context Protocol Working Group is an open community of platform providers, advertisers, agencies, and developers working together to shape the future of AI-powered advertising.

## Join the Discussion

Our primary collaboration happens through Slack:

**[→ Join the AdCP Community on Slack](https://join.slack.com/t/agenticads/shared_invite/zt-3h15gj6c0-FRTrD_y4HqmeXDKBl2TDEA)**

## What We Discuss

- **Protocol Development**: Propose and discuss new features and improvements
- **Implementation Questions**: Get help implementing AdCP in your platform
- **Use Cases**: Share how you're using AdCP in real-world scenarios
- **Best Practices**: Learn from others' experiences and share your own
- **Future Direction**: Help shape the roadmap for AdCP

## How to Participate

1. **Start a Discussion**: Share ideas, ask questions, or propose changes
2. **Join Conversations**: Comment on existing discussions
3. **Share Experiences**: Tell us about your implementation journey
4. **Help Others**: Answer questions and share your expertise

## Stay Updated

- **Join Slack Channels**: Participate in topic-specific discussions
- **Follow Announcements**: Important updates are posted in the #announcements channel
- **Star the Project**: Show your support on GitHub and stay connected

## Other Ways to Connect

- **Email**: For private inquiries, reach out to hello@adcontextprotocol.org
- **GitHub Issues**: Report bugs or request features in the [issue tracker](https://github.com/adcontextprotocol/adcp/issues)

We look forward to collaborating with you!
84 changes: 84 additions & 0 deletions dist/docs/2.5.3/contributing/testable-examples-demo.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
---
testable: true
---

# Testable Documentation Examples

This page demonstrates the testable documentation feature with complete, working code examples that execute against the live test agent.

## JavaScript Example

### List Creative Formats

```javascript
import { testAgent } from '@adcp/client/testing';

const result = await testAgent.listCreativeFormats({});

console.log(`✓ Found ${result.data?.formats?.length || 0} creative formats`);
```

## Python Example

### List Creative Formats

```python
import asyncio
from adcp import test_agent

async def list_formats():
result = await test_agent.simple.list_creative_formats()
print(f"✓ Found {len(result.formats)} supported creative formats")

asyncio.run(list_formats())
```

## CLI Example

### Using uvx (Python CLI)

```bash
uvx adcp \
https://test-agent.adcontextprotocol.org/mcp \
list_creative_formats \
'{}' \
--auth 1v8tAhASaUYYp4odoQ1PnMpdqNaMiTrCRqYo9OJp6IQ
```

## How Testable Documentation Works

When `testable: true` is set in the frontmatter, ALL code blocks on this page are extracted and executed during testing.

### Running Tests

```bash
# Run all tests including snippet validation
npm run test:all
```

### Requirements for Testable Pages

Every code block must:
- Be complete and self-contained
- Import all required dependencies
- Execute without errors
- Produce output confirming success

### When to Mark Pages as Testable

Mark a page `testable: true` ONLY when:
- ALL code blocks are complete working examples
- No code fragments or incomplete snippets
- All examples use test agent credentials
- Dependencies are installed (`@adcp/client`, `adcp`)

### When NOT to Mark Pages as Testable

Do NOT mark pages testable that contain:
- Code fragments showing patterns
- Incomplete examples
- Conceptual pseudocode
- Examples requiring production credentials
- Mixed testable and non-testable content

See [Testable Snippets Guide](./testable-snippets.md) for complete documentation.
Loading
Loading