You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We shouldn't have a WP flavored composer guide, it needs to be better incorporated into existing and related docs instead.
Sometime between removing EA copy from docs and announcing GA, we should:
1. Consolidate Introduction page of the WordPress Composer guide into the Integrated Composer guide
Also, the standalone doc Composer Fundamentals should be repurposed as the new Introduction page for the Integrated Composer guide. There won’t be much to preserve from the WP intro page once this is done.
2. Consolidate Create a Composer-managed WordPress Site with Bedrock into the Integrated Composer guide on a new page focused on site creation which covers both Drupal and WP (the Introduction page of the Integrated Composer guide is doing that today, but it’s stale info for WP and an intro page is more appropriate for conceptual content as suggested in 1i above)
@rachelwhitton for 2, a single doc seems like it would be pretty long, especially if I'm moving this content out of the Drupal page and into the IC page and doing the equivalent for WPCM. I propose separate pages for each, especially since we link out to them from the introduction.
Sounds good, to recap our sync we discussed separate WP page, but leaving the Drupal site creation process in the intro page. We discussed also removing /drupal to be redirected to /supported-drupal not much there worth preserving but the last line needs to be moved over
Follow-up action items from copy review of #9205
We shouldn't have a WP flavored composer guide, it needs to be better incorporated into existing and related docs instead.
Sometime between removing EA copy from docs and announcing GA, we should:
The text was updated successfully, but these errors were encountered: