Problem
The industries/ directory exists but has no WordPress guide. WordPress is one of the most common naming contexts — plugin naming has unique technical constraints (permanent slugs, prefix restrictions, directory AI detection, theme vs plugin rules) that general naming guidance doesn't cover.
There are already 18 open issues (#151–#168) proposing WordPress-specific content for individual core files. A dedicated industry file would consolidate WordPress-specific naming context into one loadable reference, following the same pattern as other industry files (#182–#196).
What to include
Following the standard industry file structure (see CONTRIBUTING.md):
- Platform constraints: Plugin slug rules (permanent, lowercase, hyphens only),
wp- prefix reserved, 4+ char code prefix, theme slug rules
- Naming conventions: WordPress.org directory preferences, AI duplicate detection, descriptive vs branded naming in the WP ecosystem
- Audience expectations: WordPress site owners/admins, developers, agencies — different naming priorities for each
- Case studies: Successful WP product names (Wordfence, Jetpack, Yoast, Elementor) and why they work
- Anti-patterns: WP-specific bad patterns (WPAnything, [Feature]Press, generic descriptive slugs)
- Metaphor territories: CMS/content management, site building, publishing — territory maps specific to WordPress products
- WooCommerce extensions: Naming within the WooCommerce sub-ecosystem
- WordPress block/Gutenberg naming: Block naming conventions
Relationship to existing WordPress issues
The existing WordPress issues (#151–#168) propose adding WP content to individual core files (principles.md, metaphor-mapping.md, etc.). This industry file is supplementary — it's the "one-stop shop" loaded during Step 1 when the naming brief identifies WordPress. Some content may appear in both places; the industry file provides consolidated context while core file additions ensure WordPress-specific rules surface even without loading the industry file.
Before submitting
Read CONTRIBUTING.md and run markdownlint-cli2 '**/*.md' before pushing.
Problem
The
industries/directory exists but has no WordPress guide. WordPress is one of the most common naming contexts — plugin naming has unique technical constraints (permanent slugs, prefix restrictions, directory AI detection, theme vs plugin rules) that general naming guidance doesn't cover.There are already 18 open issues (#151–#168) proposing WordPress-specific content for individual core files. A dedicated industry file would consolidate WordPress-specific naming context into one loadable reference, following the same pattern as other industry files (#182–#196).
What to include
Following the standard industry file structure (see CONTRIBUTING.md):
wp-prefix reserved, 4+ char code prefix, theme slug rulesRelationship to existing WordPress issues
The existing WordPress issues (#151–#168) propose adding WP content to individual core files (principles.md, metaphor-mapping.md, etc.). This industry file is supplementary — it's the "one-stop shop" loaded during Step 1 when the naming brief identifies WordPress. Some content may appear in both places; the industry file provides consolidated context while core file additions ensure WordPress-specific rules surface even without loading the industry file.
Before submitting
Read CONTRIBUTING.md and run
markdownlint-cli2 '**/*.md'before pushing.