Before you start
Use a permitted website project with staging configured, an available native design release and no unresolved requirements. Save the intended WordPress staging page first and note its page number from post= in its editor address.
What to do
- Open the intended project and native design release. Review the staging domain and requirements, then choose Prepare staging and enter the existing WordPress page number. Select the intended design page when requested.
- If continuing earlier work, use Find previous preparations for that saved page and select the matching request and release instead of starting another preparation.
- Use Open WordPress for the prepared target. When a companion editor needs the prepared handoff, use Copy staging request only with that trusted editor for the exact project, staging page and request.
- After the companion connection is ready, refresh the WordPress connection and use Read reviewed design. Inspect the reviewed change and target before choosing Save to staging when that action is offered.
- Check the saved result before retrying an uncertain operation. Record the verified staging save only when the saved result confirms it was applied. Inspect the actual WordPress page and keep its review and production-publication steps separate.
What happens next
A verified staging-save record belongs to that project, release, request and existing WordPress page. It does not by itself accept the design review or publish production.
If something goes wrong
Missing permission, an unsaved or wrong page number, unresolved requirements or an unavailable companion connection can block preparation. Use the existing request’s refresh and result controls after an interruption. Retry is offered only for a confirmed unapplied attempt; do not assume a timeout means nothing was saved. If the integration is unavailable, ask the project administrator rather than using another site or a whole-database copy.
