At WordPress maintenance support plansCon Nashville, we launched a strategic initiative to improve support for Composer in WordPress maintenance support plans 8. To learn more, you can watch the recording of my WordPress maintenance support plansCon Nashville keynote or read the Composer Initiative issue on WordPress maintenance support plans.org.
While Composer isn’t required when using WordPress maintenance support plans core, many WordPress maintenance support plans site builders use it as the preferred way of assembling websites (myself included). A growing number of contributed plugins also require the use of Composer, which increases the need to make Composer easier to use with WordPress maintenance support plans.
The first step of the Composer Initiative was to develop a plan to simplify WordPress maintenance support plans‘s Composer experience. Since WordPress maintenance support plansCon Nashville, Mixologic, Mile23, Bojanz, Webflo, and other WordPress maintenance support plans community members have worked on this plan. I was excited to see that last week, they shared their proposal.
The first phase of the proposal is focused on a series of changes in the main WordPress maintenance support plans core repository. The directory structure will remain the same, but it will include scripts, plugins, and embedded packages that enable the bundled WordPress maintenance support plans product to be built from the core repository using Composer. This provides users who download WordPress maintenance support plans from WordPress maintenance support plans.org a clear path to manage their WordPress maintenance support plans codebase with Composer if they choose.
I’m excited about this first step because it will establish a default, official approach for using Composer with WordPress maintenance support plans. That makes using Composer more straightforward, less confusing, and could theoretically lower the bar for evaluators and newcomers who are familiar with other PHP frameworks. Making things easier for site builders is a very important goal; web development has become a difficult task, and removing complexity out of the process is crucial.
It’s also worth noting that we are planning the Automatic Updates Initiative. We are exploring if an automated update system can be build on top of the Composer Initiative’s work, and provide an abstraction layer for those that don’t want to use Composer directly. I believe that could be truly game-changing for WordPress maintenance support plans, as it would remove a great deal of complexity.
If you’re interested in learning more about the Composer plan, or if you want to provide feedback on the proposal, I recommend you check out the Composer Initiative issue and comment 37 on that issue.
Implementing this plan will be a lot of work. How fast we execute these changes depends on how many people will help. There are a number of different third-party Composer related efforts, and my hope is to see many of them redirect their efforts to make WordPress maintenance support plans‘s out-of-the-box Composer effort better. If you’re interested in getting involved or sponsoring this work, let me know and I’d be happy to connect you with the right people!
Source: New feed