snxraven/ravenscott-blog
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update article

Browse Source
This commit is contained in:
Raven Scott 2024-10-13 03:10:39 -04:00
parent a9db77194e
commit d0ad514d40
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
markdown/The Missteps of WordPress and Automattic: A Looming Threat to the Community.md
View File

@ -116,7 +116,7 @@ Overall, the community sentiment following the interview with Matt Mullenweg ref
As one user, @sluffmo, summed it up: “All he’s achieved is showing the WP community that one immature, greedy dude throwing a tantrum can screw up their site without warning. Who cares about WP Engine? Time to pick another CMS.” This comment encapsulates the risk Automattic faces if they continue down this path—alienating the very developers and users who have built their success. As one user, @sluffmo, summed it up: “All he’s achieved is showing the WP community that one immature, greedy dude throwing a tantrum can screw up their site without warning. Who cares about WP Engine? Time to pick another CMS.” This comment encapsulates the risk Automattic faces if they continue down this path—alienating the very developers and users who have built their success.
## UPDATE: 10.12 # UPDATE: 10.12
### ACF Plugin Taken Over by WordPress.org ### ACF Plugin Taken Over by WordPress.org
In a surprising and contentious move, WordPress.org has forcibly taken over control of the Advanced Custom Fields (ACF) plugin, a popular tool used by developers to customize their WordPress sites, without the consent of the ACF team. This action has left many in the WordPress community shocked and concerned about the future of the plugin, which has been trusted for over a decade. In a surprising and contentious move, WordPress.org has forcibly taken over control of the Advanced Custom Fields (ACF) plugin, a popular tool used by developers to customize their WordPress sites, without the consent of the ACF team. This action has left many in the WordPress community shocked and concerned about the future of the plugin, which has been trusted for over a decade.