Skip to content

Add WordPress ecosystem note to distinctiveness principle#246

Merged
glacierphonk merged 1 commit into
mainfrom
166-wp-exception
Mar 21, 2026
Merged

Add WordPress ecosystem note to distinctiveness principle#246
glacierphonk merged 1 commit into
mainfrom
166-wp-exception

Conversation

@glacierphonk
Copy link
Copy Markdown
Owner

Summary

  • Adds a WordPress-specific note after the existing Wordfence exception in Section 7 ("Distinctiveness Over Descriptiveness") of principles.md
  • The wp.org plugin directory is search-driven, creating pressure toward descriptive plugin names (Advanced Custom Fields, Contact Form 7)
  • But the most memorable WordPress plugins are distinctive (Yoast, Elementor, Jetpack, Akismet) — their discoverability comes from tagline/description fields, not keyword-stuffing the name
  • One paragraph, inserted between the existing exception and the "AI prefix trap" subsection

Test plan

  • markdownlint-cli2 '**/*.md' passes (0 errors)

Closes #166

wp.org directory is search-driven, creating pressure toward
descriptive names. The note explains why distinctive names still
win — discoverability comes from tagline and description fields,
not keyword-stuffing the plugin name.

Closes #166
@glacierphonk glacierphonk merged commit 56e05a7 into main Mar 21, 2026
2 checks passed
@glacierphonk glacierphonk deleted the 166-wp-exception branch March 21, 2026 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

principles.md: add WordPress-specific exception for descriptive naming

1 participant