activitypub-integrations

Automattic's avatarfrom Automattic

Third-party WordPress plugin integration patterns. Use when adding new integrations, debugging compatibility with other plugins, or working with existing integrations.

⭐556stars🔀83forks📁View on GitHub🕐Updated Jan 1, 2026

When & Why to Use This Skill

This Claude skill provides comprehensive design patterns and boilerplate code for integrating the WordPress ActivityPub plugin with third-party extensions. It streamlines the development of federated features by offering standardized templates for post-type support, custom transformers, and activity modification, ensuring seamless compatibility and high-quality PHP implementation within the WordPress ecosystem.

Use Cases

  • Custom Post Type Federation: Quickly enable ActivityPub support for non-standard WordPress content such as WooCommerce products, The Events Calendar events, or bbPress forum topics.
  • Plugin Compatibility Debugging: Use established integration patterns to identify and resolve conflicts between ActivityPub and other active WordPress plugins.
  • Advanced Data Transformation: Implement custom PHP transformers to map specific WordPress metadata to ActivityPub object properties, ensuring rich content display on platforms like Mastodon.
  • Standardized Integration Development: Follow best practices for file naming, namespacing, and hook priority to build maintainable and scalable integration modules.
nameactivitypub-integrations
descriptionThird-party WordPress plugin integration patterns. Use when adding new integrations, debugging compatibility with other plugins, or working with existing integrations.

ActivityPub Integrations

This skill provides guidance on integrating the ActivityPub plugin with other WordPress plugins.

Quick Reference

Integration Location

All integrations live in the integration/ directory.

File naming: class-{plugin-name}.php (following PHP conventions)

Available Integrations

  • BuddyPress
  • bbPress
  • WooCommerce
  • Jetpack
  • The Events Calendar
  • WP User Avatars
  • And 13+ more

For complete directory structure and naming conventions, see PHP Class Structure.

Creating New Integration

Basic Integration Class

<?php
namespace Activitypub\Integration;

class Plugin_Name {
    public static function init() {
        \add_filter( 'activitypub_transformer', array( self::class, 'custom_transformer' ), 10, 2 );
        \add_filter( 'activitypub_post_types', array( self::class, 'add_post_types' ) );
    }

    public static function custom_transformer( $transformer, $object ) {
        // Return custom transformer if needed.
        return $transformer;
    }

    public static function add_post_types( $post_types ) {
        // Add plugin's post types.
        $post_types[] = 'plugin_post_type';
        return $post_types;
    }
}

Integration Patterns

Adding Post Type Support

public static function add_post_types( $post_types ) {
    $post_types[] = 'event';
    $post_types[] = 'product';
    return $post_types;
}

Custom Transformers

public static function transformer( $transformer, $object ) {
    if ( 'custom_type' === get_post_type( $object ) ) {
        require_once __DIR__ . '/transformer/class-custom.php';
        return new Transformer\Custom( $object );
    }
    return $transformer;
}

Modifying Activities

\add_filter( 'activitypub_activity_object', function( $object, $post ) {
    if ( 'product' === get_post_type( $post ) ) {
        $object['type']  = 'Product';
        $object['price'] = get_post_meta( $post->ID, 'price', true );
    }
    return $object;
}, 10, 2 );

Testing Integrations

Verify Integration Loading

// Check if integration is active.
if ( class_exists( '\Activitypub\Integration\Plugin_Name' ) ) {
    // Integration loaded.
}

Test Compatibility

  1. Install target plugin
  2. Activate ActivityPub
  3. Check for conflicts
  4. Verify custom post types work
  5. Test federation of plugin content

Common Integration Issues

Plugin Detection

// Multiple detection methods.
if ( defined( 'PLUGIN_VERSION' ) ) { }
if ( function_exists( 'plugin_function' ) ) { }
if ( class_exists( 'Plugin_Class' ) ) { }

Hook Priority

// Use appropriate priority.
add_filter( 'hook', 'callback', 20 ); // After plugin's filter.

Namespace Conflicts

// Use fully qualified names.
$object = new \Plugin\Namespace\Class();

Existing Integrations

BuddyPress

  • Adds BuddyPress activity support
  • Custom member transformers
  • Group activity federation

WooCommerce

  • Product post type support
  • Order activity notifications
  • Customer review federation

bbPress

  • Forum topic federation
  • Reply activities
  • User forum profiles

Best Practices

  1. Always check if plugin is active before adding hooks
  2. Use late priority for filters to override plugin defaults
  3. Test with multiple plugin versions
  4. Document compatibility requirements
  5. Handle plugin deactivation gracefully