wordpress-plugin-to-emdash

Maps WordPress plugin concepts to EmDash CMS equivalents for TypeScript plugin porting.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rczamor/rz-emdash --skill wordpress-plugin-to-emdash-rczamor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wordpress-plugin-to-emdash
Source: https://github.com/rczamor/rz-emdash/tree/main/skills/wordpress-plugin-to-emdash
Command: npx skills add https://github.com/rczamor/rz-emdash --skill wordpress-plugin-to-emdash-rczamor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating a WordPress plugin to EmDash CMS requires translating PHP-era concepts like hooks, shortcodes, WP_Query, and the Options API into EmDash's TypeScript plugin model, which is error-prone without a systematic mapping. ## Core Features & Use Cases - Concept Mapping Tables: Provides side-by-side mappings for content types, taxonomies, menus, widgets, admin UI, hooks, and plugin storage between WordPress and EmDash APIs. - Porting Patterns: Includes code examples for converting shortcodes to Portable Text blocks, options to plugin KV, custom tables to storage collections, and WP_Query to collection queries. - Red Flag Detection: Identifies WordPress features without direct equivalents (multisite, cron jobs, direct SQL) that need human architectural decisions. - Use Case: When asked to port a WordPress contact form plugin, use this Skill to map its custom table to an EmDash storage collection, its settings page to admin.settingsSchema, and its shortcode to a Portable Text block. ## Quick Start Port this WordPress plugin to EmDash by mapping its hooks, shortcodes, and database tables to EmDash equivalents.

Frequently Asked Questions about wordpress-plugin-to-emdash

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a WordPress plugin to EmDash CMS?▼

Follow a five-step approach: understand what the plugin does, identify its WordPress concepts, map them to EmDash equivalents using the provided tables, implement in TypeScript as a clean-room rewrite, and test behavior parity rather than line-by-line porting.

How to convert WordPress shortcodes to EmDash?▼

WordPress shortcodes become Portable Text custom block types in EmDash. Shortcode attributes map to block fields declared in definePlugin(), and the shortcode render function is replaced by an Astro component. This is a trusted-plugin-only feature.

What replaces WP_Query and get_option in EmDash?▼

WP_Query maps to getEmDashCollection() with where filters and limits, while get_option/update_option map to the plugin-scoped KV store via ctx.kv.get and ctx.kv.set. Custom database tables become declared storage collections with indexes.

Which WordPress features cannot be ported to EmDash?▼

Multisite features are not supported, and wp_schedule_event cron jobs have no direct equivalent and need platform cron. Deep WP core integration, direct SQL, complex meta queries, and ob_start buffering are flagged for human architectural decisions.

Does EmDash support WordPress-style hooks and filters?▼

EmDash provides equivalent hooks such as plugin:install for init, content:afterSave for save_post, and page:metadata for wp_head. Content filters like the_content are replaced by Portable Text custom block renderers instead of runtime filter chains.