claude-plugin-wordpress-manager 2.1.1 → 2.2.0

package/servers/wp-rest-bridge/build/tools/wc-webhooks.d.ts

@@ -0,0 +1,129 @@
+import { Tool } from '@modelcontextprotocol/sdk/types.js';
+import { z } from 'zod';
+declare const wcListWebhooksSchema: z.ZodObject<{
+    status: z.ZodOptional<z.ZodEnum<["active", "paused", "disabled"]>>;
+}, "strict", z.ZodTypeAny, {
+    status?: "active" | "paused" | "disabled" | undefined;
+}, {
+    status?: "active" | "paused" | "disabled" | undefined;
+}>;
+declare const wcCreateWebhookSchema: z.ZodObject<{
+    name: z.ZodString;
+    topic: z.ZodString;
+    delivery_url: z.ZodString;
+    secret: z.ZodOptional<z.ZodString>;
+    status: z.ZodOptional<z.ZodEnum<["active", "paused", "disabled"]>>;
+}, "strict", z.ZodTypeAny, {
+    name: string;
+    topic: string;
+    delivery_url: string;
+    status?: "active" | "paused" | "disabled" | undefined;
+    secret?: string | undefined;
+}, {
+    name: string;
+    topic: string;
+    delivery_url: string;
+    status?: "active" | "paused" | "disabled" | undefined;
+    secret?: string | undefined;
+}>;
+declare const wcUpdateWebhookSchema: z.ZodObject<{
+    id: z.ZodNumber;
+    name: z.ZodOptional<z.ZodString>;
+    topic: z.ZodOptional<z.ZodString>;
+    delivery_url: z.ZodOptional<z.ZodString>;
+    secret: z.ZodOptional<z.ZodString>;
+    status: z.ZodOptional<z.ZodEnum<["active", "paused", "disabled"]>>;
+}, "strict", z.ZodTypeAny, {
+    id: number;
+    status?: "active" | "paused" | "disabled" | undefined;
+    name?: string | undefined;
+    topic?: string | undefined;
+    delivery_url?: string | undefined;
+    secret?: string | undefined;
+}, {
+    id: number;
+    status?: "active" | "paused" | "disabled" | undefined;
+    name?: string | undefined;
+    topic?: string | undefined;
+    delivery_url?: string | undefined;
+    secret?: string | undefined;
+}>;
+declare const wcDeleteWebhookSchema: z.ZodObject<{
+    id: z.ZodNumber;
+}, "strict", z.ZodTypeAny, {
+    id: number;
+}, {
+    id: number;
+}>;
+export declare const wcWebhookTools: Tool[];
+export declare const wcWebhookHandlers: {
+    wc_list_webhooks: (params: z.infer<typeof wcListWebhooksSchema>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+    wc_create_webhook: (params: z.infer<typeof wcCreateWebhookSchema>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+    wc_update_webhook: (params: z.infer<typeof wcUpdateWebhookSchema>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+    wc_delete_webhook: (params: z.infer<typeof wcDeleteWebhookSchema>) => Promise<{
+        toolResult: {
+            content: {
+                type: string;
+                text: string;
+            }[];
+            isError?: undefined;
+        };
+    } | {
+        toolResult: {
+            isError: boolean;
+            content: {
+                type: string;
+                text: string;
+            }[];
+        };
+    }>;
+};
+export {};

package/servers/wp-rest-bridge/build/tools/wc-webhooks.js

@@ -0,0 +1,142 @@
+import { makeWooCommerceRequest } from '../wordpress.js';
+import { z } from 'zod';
+const wcListWebhooksSchema = z.object({
+    status: z.enum(['active', 'paused', 'disabled']).optional()
+        .describe('Filter webhooks by status'),
+}).strict();
+const wcCreateWebhookSchema = z.object({
+    name: z.string().describe('Webhook name (for identification)'),
+    topic: z.string().describe('Event topic, e.g. "order.created", "product.updated"'),
+    delivery_url: z.string().describe('URL to receive the webhook payload'),
+    secret: z.string().optional().describe('Secret for HMAC-SHA256 signature verification'),
+    status: z.enum(['active', 'paused', 'disabled']).optional()
+        .describe('Webhook status (default: active)'),
+}).strict();
+const wcUpdateWebhookSchema = z.object({
+    id: z.number().describe('Webhook ID to update'),
+    name: z.string().optional().describe('Updated webhook name'),
+    topic: z.string().optional().describe('Updated event topic'),
+    delivery_url: z.string().optional().describe('Updated delivery URL'),
+    secret: z.string().optional().describe('Updated secret'),
+    status: z.enum(['active', 'paused', 'disabled']).optional()
+        .describe('Updated webhook status'),
+}).strict();
+const wcDeleteWebhookSchema = z.object({
+    id: z.number().describe('Webhook ID to delete'),
+}).strict();
+export const wcWebhookTools = [
+    {
+        name: "wc_list_webhooks",
+        description: "Lists all WooCommerce webhooks with their status, topic, and delivery URL",
+        inputSchema: {
+            type: "object",
+            properties: {
+                status: {
+                    type: "string",
+                    enum: ["active", "paused", "disabled"],
+                    description: "Filter webhooks by status",
+                },
+            },
+        },
+    },
+    {
+        name: "wc_create_webhook",
+        description: "Creates a new WooCommerce webhook for event notifications (e.g. order.created, product.updated)",
+        inputSchema: {
+            type: "object",
+            properties: {
+                name: { type: "string", description: "Webhook name (for identification)" },
+                topic: { type: "string", description: "Event topic, e.g. 'order.created', 'product.updated'" },
+                delivery_url: { type: "string", description: "URL to receive the webhook payload" },
+                secret: { type: "string", description: "Secret for HMAC-SHA256 signature verification" },
+                status: {
+                    type: "string",
+                    enum: ["active", "paused", "disabled"],
+                    description: "Webhook status (default: active)",
+                },
+            },
+            required: ["name", "topic", "delivery_url"],
+        },
+    },
+    {
+        name: "wc_update_webhook",
+        description: "Updates an existing WooCommerce webhook (status, delivery URL, topic, etc.)",
+        inputSchema: {
+            type: "object",
+            properties: {
+                id: { type: "number", description: "Webhook ID to update" },
+                name: { type: "string", description: "Updated webhook name" },
+                topic: { type: "string", description: "Updated event topic" },
+                delivery_url: { type: "string", description: "Updated delivery URL" },
+                secret: { type: "string", description: "Updated secret" },
+                status: {
+                    type: "string",
+                    enum: ["active", "paused", "disabled"],
+                    description: "Updated webhook status",
+                },
+            },
+            required: ["id"],
+        },
+    },
+    {
+        name: "wc_delete_webhook",
+        description: "Deletes a WooCommerce webhook (stops notifications to the delivery URL)",
+        inputSchema: {
+            type: "object",
+            properties: {
+                id: { type: "number", description: "Webhook ID to delete" },
+            },
+            required: ["id"],
+        },
+    },
+];
+export const wcWebhookHandlers = {
+    wc_list_webhooks: async (params) => {
+        try {
+            const query = params.status ? `?status=${params.status}` : '';
+            const response = await makeWooCommerceRequest("GET", `webhooks${query}`);
+            return { toolResult: { content: [{ type: "text", text: JSON.stringify(response, null, 2) }] } };
+        }
+        catch (error) {
+            const errorMessage = error.response?.data?.message || error.message;
+            return { toolResult: { isError: true, content: [{ type: "text", text: `Error listing webhooks: ${errorMessage}` }] } };
+        }
+    },
+    wc_create_webhook: async (params) => {
+        try {
+            const { name, topic, delivery_url, secret, status } = params;
+            const body = { name, topic, delivery_url };
+            if (secret)
+                body.secret = secret;
+            if (status)
+                body.status = status;
+            const response = await makeWooCommerceRequest("POST", "webhooks", body);
+            return { toolResult: { content: [{ type: "text", text: JSON.stringify(response, null, 2) }] } };
+        }
+        catch (error) {
+            const errorMessage = error.response?.data?.message || error.message;
+            return { toolResult: { isError: true, content: [{ type: "text", text: `Error creating webhook: ${errorMessage}` }] } };
+        }
+    },
+    wc_update_webhook: async (params) => {
+        try {
+            const { id, ...updates } = params;
+            const response = await makeWooCommerceRequest("PUT", `webhooks/${id}`, updates);
+            return { toolResult: { content: [{ type: "text", text: JSON.stringify(response, null, 2) }] } };
+        }
+        catch (error) {
+            const errorMessage = error.response?.data?.message || error.message;
+            return { toolResult: { isError: true, content: [{ type: "text", text: `Error updating webhook: ${errorMessage}` }] } };
+        }
+    },
+    wc_delete_webhook: async (params) => {
+        try {
+            const response = await makeWooCommerceRequest("DELETE", `webhooks/${params.id}?force=true`);
+            return { toolResult: { content: [{ type: "text", text: JSON.stringify(response, null, 2) }] } };
+        }
+        catch (error) {
+            const errorMessage = error.response?.data?.message || error.message;
+            return { toolResult: { isError: true, content: [{ type: "text", text: `Error deleting webhook: ${errorMessage}` }] } };
+        }
+    },
+};

package/servers/wp-rest-bridge/build/types.d.ts

@@ -233,6 +233,18 @@ export interface WCCoupon {
     minimum_amount: string;
     maximum_amount: string;
 }
+export interface WCWebhook {
+    id: number;
+    name: string;
+    status: string;
+    topic: string;
+    resource: string;
+    event: string;
+    delivery_url: string;
+    secret: string;
+    date_created: string;
+    date_modified: string;
+}
 export interface WPNetworkSite {
     blog_id: number;
     url: string;

package/skills/wordpress-router/references/decision-tree.md

@@ -1,4 +1,4 @@
-# Router decision tree (v8 — development + local environment + operations + multisite + CI/CD + monitoring)
+# Router decision tree (v9 — development + local environment + operations + multisite + CI/CD + monitoring + webhooks + content repurposing)
 
 This routing guide covers WordPress **development**, **local environment**, and **operations** workflows.
 
@@ -14,7 +14,7 @@ Keywords that indicate **local environment**:
 local site, Studio, LocalWP, Local by Flywheel, wp-env, local WordPress, start site, stop site, create local site, local development, symlink plugin, local database, switch PHP version, localhost, local preview, detect environment, WASM, SQLite local
 
 Keywords that indicate **operations**:
-deploy, push to production, audit, security check, backup, restore, migrate, move site, create post, manage content, site status, check plugins, performance check, SEO audit, WooCommerce, prodotto, ordine, coupon, negozio, catalogo, inventario, vendite, carrello, multisite, network, sub-site, sub-sito, domain mapping, super admin, network activate, monitor, uptime, health report, trend, scansione periodica, alerting, performance baseline
+deploy, push to production, audit, security check, backup, restore, migrate, move site, create post, manage content, site status, check plugins, performance check, SEO audit, WooCommerce, prodotto, ordine, coupon, negozio, catalogo, inventario, vendite, carrello, multisite, network, sub-site, sub-sito, domain mapping, super admin, network activate, monitor, uptime, health report, trend, scansione periodica, alerting, performance baseline, fleet, all sites, network health, cross-site, webhook, outbound notification, event propagation, Zapier, content sync, repurpose content, social posts from blog, content atomization, newsletter from posts, content distribution
 
 Keywords that indicate **development**:
 create block, block.json, theme.json, register_rest_route, plugin development, hooks, PHPStan, build, test, scaffold, i18n, translation, accessibility, a11y, headless, decoupled, WPGraphQL, CI, CD, pipeline, GitHub Actions, GitLab CI, deploy automatico, workflow, quality gate
@@ -92,8 +92,12 @@ Priority: `gutenberg` > `wp-core` > `wp-site` > `wp-block-theme` > `wp-block-plu
   → `wp-woocommerce` skill + `wp-ecommerce-manager` agent
 - **Multisite / network / sub-sites / domain mapping / super admin / network activate**
   → `wp-multisite` skill + `wp-site-manager` agent
-- **Monitor / uptime / health report / trend / scansione periodica / alerting / performance baseline / ongoing checks**
+- **Monitor / uptime / health report / trend / scansione periodica / alerting / performance baseline / ongoing checks / fleet / all sites / cross-site comparison**
   → `wp-monitoring` skill + `wp-monitoring-agent` agent
+- **Webhook / outbound notification / event propagation / Zapier / Make / n8n / content sync webhook**
+  → `wp-webhooks` skill + `wp-site-manager` agent
+- **Repurpose content / social posts from blog / newsletter from content / atomize / content distribution / turn blog into social**
+  → `wp-content-repurposing` skill + `wp-content-strategist` agent
 
 ## Step 2c: route by local environment intent (keywords)
 

package/skills/wp-content/SKILL.md

@@ -101,3 +101,6 @@ Tool: assign_terms_to_content — assign terms to content
 ### Reference Files
 - **`references/content-templates.md`** - Templates for different content types
 - **`references/seo-optimization.md`** - On-page SEO patterns for WordPress
+
+### Related Skills
+- **`wp-content-repurposing`** — transform existing content for social media, email, and multi-channel distribution

package/skills/wp-content-repurposing/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: wp-content-repurposing
+description: This skill should be used when the user asks to "repurpose content",
+  "create social posts from blog", "transform content for social media", "email
+  newsletter from posts", "content atomization", "reuse content across channels",
+  "adapt content for different platforms", "turn blog into social", "content
+  distribution", or mentions turning WordPress content into multi-format outputs.
+version: 1.0.0
+---
+
+# WordPress Content Repurposing Skill
+
+## Overview
+
+Content repurposing is the systematic transformation of canonical WordPress content into channel-specific formats. Instead of creating original content for each platform, you extract value from existing posts, pages, and products and reshape it for social media, email newsletters, ad copy, and other distribution channels.
+
+## When to Use
+
+- User has existing WordPress content and wants to distribute it across channels
+- User asks to turn blog posts into social media content
+- User wants to create email newsletters from existing content
+- User needs to atomize long-form content into smaller shareable pieces
+- User wants platform-specific content variants from a single source
+
+## Content Repurposing vs Content Creation
+
+| Need | Skill |
+|------|-------|
+| Create new original content from scratch | `wp-content` |
+| Transform existing content for new channels | `wp-content-repurposing` (this skill) |
+| SEO-optimized blog post creation | `wp-content` |
+| Blog post → social thread + email digest | `wp-content-repurposing` (this skill) |
+
+## Decision Tree
+
+1. **What output format?**
+   - "social posts" / "Twitter thread" / "LinkedIn" / "Instagram" → Social formats (Section 1)
+   - "email" / "newsletter" / "digest" → Email newsletter (Section 2)
+   - "atomize" / "break down" / "content calendar" → Content atomization (Section 3)
+   - "character limits" / "platform specs" / "image sizes" → Platform specifications (Section 4)
+
+2. **Run detection first:**
+   ```bash
+   node skills/wp-content-repurposing/scripts/repurposing_inspect.mjs [--cwd=/path/to/project]
+   ```
+   This identifies existing content volume, social plugins, and email integrations.
+
+## Repurposing Areas
+
+### Section 1: Social Formats
+See `references/social-formats.md`
+- Blog post → Twitter/X thread
+- Blog post → LinkedIn article summary
+- Blog post → Instagram carousel
+- Blog post → Facebook engagement post
+- Product → social proof posts
+
+### Section 2: Email Newsletter
+See `references/email-newsletter.md`
+- Blog post → newsletter digest
+- Product launch → email announcement
+- Content series → drip sequence
+- Subject line and CTA optimization
+
+### Section 3: Content Atomization
+See `references/content-atomization.md`
+- Pillar content → atomic units (quotes, stats, tips)
+- Atomization workflow and content calendar
+- Repurposing matrix (1 post → 5-10 outputs)
+- Quality gates for standalone value
+
+### Section 4: Platform Specifications
+See `references/platform-specs.md`
+- Character limits per platform
+- Image dimensions per platform
+- Hashtag and link strategies
+- Posting frequency recommendations
+
+## Reference Files
+
+| File | Content |
+|------|---------|
+| `references/social-formats.md` | Templates for Twitter, LinkedIn, Instagram, Facebook |
+| `references/email-newsletter.md` | Newsletter digest, drip sequences, subject lines |
+| `references/content-atomization.md` | Atomization workflow, content calendar, repurposing matrix |
+| `references/platform-specs.md` | Character limits, image sizes, posting frequency |
+
+## Recommended Agent
+
+**`wp-content-strategist`** — selects source content via WP REST Bridge, extracts key elements, applies platform templates, and generates formatted outputs for review.
+
+## Related Skills
+
+- **`wp-content`** — content creation and lifecycle management (source content)
+- **`wp-headless`** — headless content delivery for multi-channel architectures
+- **`wp-woocommerce`** — product content for e-commerce repurposing

package/skills/wp-content-repurposing/references/content-atomization.md

@@ -0,0 +1,117 @@
+# Content Atomization
+
+## Overview
+
+Content atomization is the process of breaking down pillar content (long-form blog posts, guides, product pages) into standalone atomic units that each deliver value independently. One pillar post can yield 5-15 atomic pieces for distribution across multiple channels.
+
+## Atomization Workflow
+
+```
+1. SELECT source content (pillar post)
+       |
+2. IDENTIFY atomic elements (quotes, stats, tips, questions)
+       |
+3. EXTRACT and format each atom
+       |
+4. ASSIGN to channels (social, email, ad copy)
+       |
+5. SCHEDULE via content calendar
+       |
+6. DISTRIBUTE and track performance
+```
+
+### Step 1: Select Source Content
+
+Prioritize content that is:
+- **Evergreen**: valuable regardless of timing
+- **Data-rich**: contains statistics, quotes, or unique insights
+- **Popular**: already proven with traffic or engagement
+- **Long-form**: 1,000+ words with multiple sections
+
+Use `list_content` with `orderby: "date"` or traffic data to identify top candidates.
+
+### Step 2: Identify Atomic Elements
+
+| Element Type | What to Look For | Output Count |
+|-------------|-----------------|--------------|
+| Key quotes | Standalone insightful sentences | 2-4 per post |
+| Statistics | Numbers, percentages, data points | 1-3 per post |
+| Tips/How-tos | Actionable advice steps | 3-5 per post |
+| Questions | Thought-provoking questions | 1-2 per post |
+| Lists | Numbered or bulleted lists | 1-2 per post |
+| Definitions | Explained concepts or terms | 1-2 per post |
+
+### Step 3: Extract and Format
+
+For each atom, create a self-contained piece:
+
+```
+ATOM CARD:
+- Source: [post title + URL]
+- Type: [quote / stat / tip / question]
+- Content: [the atomic content, 1-3 sentences]
+- Channel: [Twitter / LinkedIn / Instagram / Email / Ad]
+- Visual needed: [yes/no, description if yes]
+- CTA: [link back to full post]
+```
+
+### Step 4: Assign to Channels
+
+Map atom types to their best channels:
+
+| Atom Type | Best Channels | Format |
+|-----------|--------------|--------|
+| Quote | Twitter, Instagram, LinkedIn | Image with text overlay or plain text |
+| Statistic | Twitter, LinkedIn, Facebook | Data visualization or bold text |
+| Tip | All channels | Step-by-step or bullet list |
+| Question | Twitter, LinkedIn, Facebook | Engagement post |
+| List | Instagram carousel, LinkedIn | Multi-slide or numbered |
+
+## Repurposing Matrix
+
+One blog post (1,500+ words) can produce:
+
+| Output | Count | Channel |
+|--------|-------|---------|
+| Twitter/X thread | 1 | Twitter |
+| Individual tweets | 3-5 | Twitter |
+| LinkedIn post | 1-2 | LinkedIn |
+| Instagram carousel | 1 | Instagram |
+| Facebook post | 1 | Facebook |
+| Email digest section | 1 | Newsletter |
+| Pull quotes for ads | 2-3 | Paid social |
+| **Total outputs** | **10-15** | — |
+
+## Content Calendar Integration
+
+### Weekly Schedule from One Post
+
+| Day | Content | Channel | Atom Type |
+|-----|---------|---------|-----------|
+| Mon | Full thread | Twitter | All key points |
+| Tue | Article summary | LinkedIn | Overview |
+| Wed | Carousel | Instagram | Visual takeaways |
+| Thu | Engagement post | Facebook | Question |
+| Fri | Individual quote | Twitter | Best quote |
+| Sat | — | — | Rest day |
+| Sun | Email digest | Newsletter | Summary + CTA |
+
+### Monthly Cadence
+
+- **Week 1**: Publish pillar post + immediate social promotion
+- **Week 2**: Atomized social content from Week 1 post
+- **Week 3**: Publish new pillar post + atomize Week 1 remainder
+- **Week 4**: Cross-promote best performers + email roundup
+
+## Quality Gates
+
+Each atomic piece must pass these checks:
+
+1. **Standalone value**: Does it make sense without the source article?
+2. **Single idea**: Does it convey exactly one concept?
+3. **Actionable or insightful**: Does it teach, inspire, or provoke thought?
+4. **Channel-appropriate**: Does it fit the platform's format and audience?
+5. **Brand-consistent**: Does it match the brand voice and visual style?
+6. **Attribution**: Does it link back to the source when appropriate?
+
+If an atom fails any gate, revise or discard it.

package/skills/wp-content-repurposing/references/email-newsletter.md

@@ -0,0 +1,136 @@
+# Email Newsletter Templates
+
+## Overview
+
+Templates for transforming WordPress content into email-ready formats. Covers newsletter digests, product announcements, and drip sequences.
+
+## Blog Post → Newsletter Digest
+
+**Template:**
+
+```
+Subject: [Keyword] — [Benefit or curiosity hook]
+Preview text: [First 90 chars that complement the subject line]
+
+---
+
+Hi [first_name],
+
+[1-2 sentence personal intro connecting to the topic]
+
+## [Post Title]
+
+[3-4 sentence excerpt highlighting the most valuable insight]
+
+[Key quote or statistic from the post]
+
+Read the full article: [link]
+
+---
+
+## Quick Tip
+
+[One actionable takeaway from the post that works standalone]
+
+---
+
+[Sign-off]
+[Company/brand name]
+
+[Unsubscribe link]
+```
+
+**Rules:**
+- Subject line: 40-60 characters, include primary keyword
+- Preview text: 40-90 characters, complements (not repeats) subject
+- Body: 200-300 words max
+- One primary CTA (link to post)
+- Mobile-friendly: single column, large buttons
+
+## Product Launch → Email Announcement
+
+**Template:**
+
+```
+Subject: Introducing [Product Name] — [One-line value prop]
+Preview text: [Benefit] + [urgency or exclusivity]
+
+---
+
+Hi [first_name],
+
+We're excited to announce [Product Name].
+
+## What it is
+[2-3 sentences describing the product]
+
+## Why you'll love it
+- [Benefit 1]
+- [Benefit 2]
+- [Benefit 3]
+
+## Special offer
+[Launch pricing, early access, or bonus]
+
+[CTA Button: Shop Now / Learn More]
+
+---
+
+[Social proof: "Join X customers who already..."]
+
+[Sign-off]
+```
+
+## Content Series → Drip Sequence
+
+**Template (3-email sequence from a pillar post):**
+
+```
+Email 1 — Day 0 (Hook):
+Subject: The [topic] guide you've been waiting for
+Body: Introduce the pillar topic, deliver first key insight,
+      tease what's coming in the next emails.
+CTA: Read Part 1
+
+Email 2 — Day 3 (Deep Dive):
+Subject: [Specific technique] from our [topic] guide
+Body: Expand on the most actionable section of the post,
+      provide step-by-step instructions or examples.
+CTA: Read Part 2 / Try it now
+
+Email 3 — Day 7 (Summary + CTA):
+Subject: Everything you need to know about [topic]
+Body: Recap key takeaways, link to full article,
+      offer next step (product, consultation, download).
+CTA: Get the complete guide / Shop related products
+```
+
+## Subject Line Formulas
+
+| Formula | Example |
+|---------|---------|
+| Number + Benefit | "5 ways to reduce sugar intake" |
+| Question | "Is cactus water the healthiest option?" |
+| How-to | "How to save 200 calories a day" |
+| Curiosity gap | "The drink we didn't expect to love" |
+| Urgency | "Last chance: 20% off ends tonight" |
+| Personal | "[Name], we picked this for you" |
+
+## Segmentation Considerations
+
+Match content type to audience segment:
+
+| Content Type | Best Segment | Email Focus |
+|--------------|-------------|-------------|
+| Blog post (educational) | All subscribers | Knowledge + CTA to site |
+| Product update | Past customers | Features + upgrade path |
+| Industry news | Engaged readers | Commentary + discussion |
+| Case study | Prospects | Results + trial CTA |
+| Seasonal content | Active in last 90 days | Timely offers |
+
+## Key Metrics
+
+- **Open rate target**: 20-25% (industry avg)
+- **Click rate target**: 2-5%
+- **Unsubscribe rate**: keep below 0.5% per send
+- **Best send times**: Tuesday-Thursday, 9-11 AM local time