Skip to content

Conversation

fellyph
Copy link
Collaborator

@fellyph fellyph commented Aug 16, 2025

Motivation for the change, related issues

This pull request moves the image assets to the static folder to avoid duplication of assets and reduce the errors with missing assets.

Based on issue #2516

Steps to test

  • Check out this pull request branch locally.
  • Run npm install
  • Run npm run build:docs and check if the build has no errors
  • Run npm run dev:docs
  • Open the local site in your browser (http://localhost:3000/wordpress-playground/).
  • Navigate through the documentation, specifically checking pages within the Blueprints and Main sections:
    • "Troubleshoot and Debug Blueprints"
    • "About Playground > Build"
    • "Build your first Blueprints"
    • "Web Instance"
    • "Build your first blueprint"
  • Verify that all images load correctly and are not broken.
@fellyph fellyph requested review from akirk and brandonpayton August 16, 2025 12:34
Copy link
Member

@brandonpayton brandonpayton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed the content changes and built and looked at a page or two. This looks good to me. Thank you!

@brandonpayton brandonpayton merged commit 8037056 into trunk Aug 20, 2025
26 checks passed
@brandonpayton brandonpayton deleted the unifying-assets-folder branch August 20, 2025 17:26
fellyph pushed a commit that referenced this pull request Aug 22, 2025
## Motivation for the change, related issues This corresponds to the image paths integrated in the PR #2521 . The assets folder is no longer used, so it will be deleted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants