Curso WordPress Studio
11 aulas · 3 idiomas
5 min · WordPress Studio 1.17.x
In this lesson · 5 min
Feedback tied to the element, problem, and outcome.
Contextual review
Select the element, describe the problem, and state what must remain.
Present Annotate as a bridge between visual inspection and change. The comment gains context because it is attached to the exact point on the page.
Request quality
×
No problem, intent, or boundary.
✓
Explain why and preserve the tone.
Compare a vague comment with a verifiable request. The latter connects change to the brief and protects characteristics that already work.
Useful annotation
Where to change.
What is not working.
What should improve.
What to preserve.
Use the formula to create two annotations, not a giant list. A few coherent changes are easier to review and demonstrate.
Change cycle
Capture feedback in context.
Ask for a plan before changes.
Inspect the diff and screenshots.
Keep the same checkpoint pattern used with Studio Code. An annotation does not authorize any implementation; it opens a verifiable conversation.
Checkpoint
If a change does not strengthen the brief, it does not enter this round.
Up next 07 · Preview
Finish by showing before and after. Name which message or action became clearer instead of judging only whether it looks nicer.