Writing prompts for content, layout, and styling

Documentation / Agentic editing and connections

A useful editing prompt identifies the website and page, describes the desired result, and states what must remain unchanged. Give the assistant permission to read first. Separate a proposal from permission to save, because ordinary page tools write directly to saved content.

Specify the target and constraints

Include the page URL or ID, content language, and the section or block when known. A dot-address such as pageId.sectionId identifies an existing object only after the assistant reads that page. Describe the audience, approved facts, tone, and length for copy changes. For layout, identify the elements to rearrange and the mobile behavior you expect.

Protect unrelated content explicitly. For example:

Read the English services page on the selected website. Propose a shorter introduction and a two-column benefits section using managed blocks. Keep the header, navigation, URLs, template, translations, and availability unchanged. Do not save until I approve.

Do not include credentials, private customer submissions, or unrelated personal information in a prompt.

Choose the authoring model

Ask for managed blocks when you want normal visual editing afterward. Specify custom design only when you accept its source-based editing boundary. State whether custom work covers the body alone or the header and body. A custom header must remain a real Beeboo header, with canonical title bindings.

Review and approve

Request a description of changed fields and any affected links. Approve a specific proposal rather than an unrestricted redesign. Ask the assistant to use the current page version, then read back the result and check desktop and mobile rendering.

If validation fails, revise the unsupported markup or behavior instead of asking the assistant to bypass safeguards. If a save conflicts, read again before proceeding. See design and styling and saving and recovery.