jonathanbossenger

WordPress/wp-feature-notifications weekly status: 2026-10-23 – 2026-11-01

One significant change landed this week: the notification repository is now scoped per user, which lays groundwork for the REST API. Apart from that, a README note and four Dependabot bumps were merged. A batch of community PRs (fixes, tooling and PHP test-matrix updates) is open and waiting for review.

Highlights

• Notification repository is now user-scoped (#626, elphizu). The Notification_Repository interface was rewritten so every lookup takes a user_id. find_by_id() now finds a message by its message ID for a specific user, and new find_by_user() and count_by_user() methods support filtering by status, channel, context, after/before (for polling), expiry and pagination. The wpdb implementation was updated to match, the legacy interface-notification.php was removed, and new PHPUnit coverage was added. Users can now only reach their own notif

jonathanbossenger

WordPress/wp-feature-notifications weekly status: 2026-10-16 – 2026-10-23

A maintenance week on develop: 24 PRs merged, 23 of them Dependabot updates, plus one README note about the demo plugin. The more interesting activity is in review: 16 new contributor PRs opened this week. They cover new REST endpoints, a v2 database schema, data-model fixes and tooling clean-up.

Highlights

• README now points to the demo plugin (#648, jonathanbossenger): adds a note telling developers where to find the demo code plugin for trying out the feature.
• Big dependency catch-up: 23 Dependabot PRs merged, including a grouped update of 37 @wordpress/* packages (#598). Another 17 stale Dependabot PRs were closed without merging (usually because a newer version replaced them).
• Strong contributor pipeline: open PRs now cover the REST API (GET, POST and DELETE on notifications

jonathanbossenger

<?php
/**
 * Plugin Name: WP Feature Notifications Demo
 * Description: Temporary demo data and test tools for manually testing the WP Feature Notifications client. Not part of the plugin, never shipped in the release zip.
 * Author:      WP Feature Notifications Contributors
 * License:     GPLv2 or later
 *
 * Restores the v0.2.0 demo removed in #304 (PR #308), adapted to the current
 * client. It exists only until the real emit API (#303), repositories and
 * REST endpoints land, at which point this directory should be deleted.

jonathanbossenger

# Build Plan: "Simple Contact Block" WordPress Plugin

## Decisions locked in for this build

- **Scaffolding tool:** `@wordpress/create-block` (official WordPress package)  
- **Plugin slug / namespace:** `simple-contact-block`  
- **Block name:** `simple-contact-block/contact-form`  
- **Block render type:** Dynamic (server-side rendered via `render.php`)  
- **Form submission:** Custom WordPress REST API endpoint, called from JS using `@wordpress/api-fetch` (not raw `fetch()`)  
- **Storage:** Custom post type `contact_submission`  

jonathanbossenger

import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

// Create an MCP server
const server = new McpServer({
  name: "My Support Server",
  version: "1.0.0",
});

jonathanbossenger

Abilities API and Connectors: Developer Guide

WordPress is introducing two new interconnected systems for AI integration: the Abilities API and the Connectors system. Together, they provide a standardized way to define executable WordPress capabilities and manage API credentials for external AI providers.

This guide covers both systems from a developer perspective, including architecture, API reference, and practical examples.

Table of Contents

• Overview
• Abilities API

jonathanbossenger

WordPress AI Client Developer Guide

A comprehensive guide to the WP AI Client and Abilities API for plugin and theme developers.

Table of Contents

1. Introduction and Architecture Overview
2. Setting Up Connectors (API Key Management)
3. Your First AI Prompt (Quick Start)
4. The Prompt Builder In Depth

jonathanbossenger

{
    "steps": [
        {
            "step": "installPlugin",
            "pluginData": {
                "resource": "wordpress.org/plugins",
                "slug": "sqlite-database-integration"
            }
        },
        {

jonathanbossenger

<!-- wp:group {"layout":{"type":"flex","flexWrap":"nowrap"}} -->
<div class="wp-block-group"><!-- wp:paragraph -->
<p>Author</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p></p>
<!-- /wp:paragraph --></div>
<!-- /wp:group -->

jonathanbossenger

# ✨ Set up Copilot instructions

Configure instructions for this repository as documented in [Best practices for Copilot coding agent in your repository](https://gh.io/copilot-coding-agent-tips).

<Onboard this repo>