So long WordPress
WordPress’s recent move to block people “affiliated” with hosting provider WP Engine from creating WordPress.org accounts has intensified long‑standing concerns about project governance, vague legal language, and the outsized personal control of its founder. Commenters argue this behavior is damaging the broader ecosystem that made WordPress successful—an ecosystem already strained by dark‑pattern plugin economics and a cult‑like community culture—and many are now weighing alternatives such as static site generators, other CMSs, or forks like ClassicPress. While WordPress remains dominant and attractive for non‑technical users, several voices see this moment as a warning against over‑reliance on any single platform or “benevolent dictator.”
Affiliation Checkbox & WP Engine Conflict
- A major flashpoint is a new WordPress.org registration checkbox requiring users to assert they have no “affiliation” with a specific hosting company.
- Commenters argue the term is intentionally vague; leadership has reportedly refused to define it beyond “ask your lawyer,” which many see as chilling and hostile.
- Dispute over whether simply being a customer, ex-employee, or vendor counts as “affiliated” drives fear of legal exposure and discourages participation in official events and infrastructure.
- Some see the checkbox as a strategy to create legal leverage against the host rather than a genuine community rule.
Legal, Governance, and Nonprofit Issues
- Several see potential antitrust issues (Sherman/Clayton Acts) and suggest contacting regulators.
- Confusion is clarified: WordPress.org is not part of the nonprofit foundation; it is effectively under personal control, staffed by a for‑profit’s employees.
- The foundation appears tiny in revenue, leading many to view the nonprofit as largely symbolic while .org is used commercially (e.g., hosting referral money).
- There is concern about blurred lines between nonprofit, for‑profit, and personal control, plus worries about SLAPP‑style legal threats against critics.
Community Culture & Ecosystem Problems
- Multiple comments describe the WordPress culture as cult‑like, insular, and dominated by “toxic kindness” and groupthink.
- The plugin/hosting ecosystem is widely criticized as full of upsells, dark‑pattern billing, and borderline scams; “nulling” plugins triggers heated ethical arguments despite GPL.
- Some report refund battles and a sense that end users are treated as marks once the market matured.
WordPress’ Practical Strengths
- Despite criticism, many stress why WordPress dominates:
- Huge plugin/theme ecosystem and brand recognition.
- Cheap, ubiquitous PHP/MySQL hosting.
- Non‑technical users and marketing teams already know the admin UI.
- Agencies can ship functional sites quickly (including e‑commerce) and hand them to clients with minimal dev involvement.
Alternatives & Migration
- For technical users, static site generators (e.g., Hugo) are praised for blogs and marketing sites, but lack integrated CMS, forms, and “minor server‑side” features.
- Serverless functions and “jamstack” approaches help, but CRUD and richer interactivity remain clunkier than WordPress for many.
- Suggested alternatives include Drupal (with mixed experiences), ClassicPress, HTMLy, various headless or Laravel‑based CMSs, and new/open‑source projects, but none match WordPress’ ecosystem scale.
Broader Lessons
- Commenters generalize this as a warning about over‑reliance on a single platform and on “benevolent dictators.”
- Calls are made for better open‑source governance models where power is not concentrated in a single individual and where community interests cannot be easily overridden.