Keep your eye on the details

Build with your coding agent, then refine typography, color, spacing and layout visually. Keep shared design choices in the project and see how the page responds at different screen sizes.

Aa.

Give the design a consistent vocabulary

Use the same design language as the page develops. Tokens define shared values; utilities apply them where the layout needs them.

  • Color and type

    Keep reusable visual choices in Local tokens.

  • Layout and spacing

    Refine supported utility-based styles.

  • Responsive design

    Check the composition across viewport widths before delivery.

Refine the source in Local

Select a supported style target in Local Design and adjust its utilities. Stable targets help the editor identify the intended source element, so reusable styling remains part of the template your team maintains.

Review the source and run the compiled build after design changes.

Aa.

Aa.

Make supported adjustments in WordPress

Studio gives supported WordPress blocks visual controls for spacing, color, layout and typography. Islands with compatible style targets can also carry per-instance adjustments. Reset a CMS choice to reveal the original Local styling.

Check the change where it will be used

Visual refinement belongs in the same review cycle as the rest of the page. Shared design changes reach WordPress through a reviewed release.

  1. Select

    Work on a supported source or instance target.

  2. Adjust

    Refine the intended style and breakpoint choices.

  3. Check

    Review small and large screens and run the appropriate build.

  4. Deliver

    Review the release or saved frontend result in its actual context.

Design editing questions

Can every element be edited visually?

The editor works with supported blocks and declared stable style targets.

Can each repeater row have a different override?

Repeated occurrences of one target share the instance override; individual row styles are not available.

Do token changes update the live site immediately?

Shared token changes reach the site through a reviewed compiled release.

Give your design choices a clear home

Start with supported style targets and shared tokens. Use the visual controls to refine the page, then check the result in the context where people will use it.