Start with a working structure. Make it yours.

Choose Shop when visitors need to understand and browse products, and Services when they need to compare service offers and find the next step. Blank is a different starting point when neither managed preset matches the project. Making this choice early gives the content a stable structure and makes later requests easier to review.

Name the site and identify the business it represents before preparing large amounts of copy. A website name, a business display name and a public domain have different jobs. Keep them understandable for the people managing the project, and confirm the intended public address independently when the site is ready for publication.

• Choose Shop, Services or Blank deliberately.
• Name the website before building its content.
• Identify the business and expected public address.

A managed preset is a controlled structure with supported content and modular changes. It is not a promise that an assistant can replace any part of the base with arbitrary code. Frame editing requests around the supported content: the business facts, catalog records and website-specific pages the editor exposes.

When a requested design change falls outside that structure, confirm the available controls before assuming it can be published safely. A consistent base is valuable because both people and AI can understand the same model. Preserve that consistency when planning future improvements rather than turning each store into a separate, undocumented implementation.

• Use the content controls provided by the preset.
• Check support for a requested module change.
• Keep base-template changes separate from routine editing.

Manual editing is useful when you know the exact field to change. AI assistance is useful when you want a coordinated proposal across several fields or items. Both should lead to a result you can inspect. Review the affected content and source scope before applying the proposal, especially when the website shares its business catalog with other drafts.

Draft revisions protect against stale updates. If another editor changes the site after a proposal is prepared, refresh the current state and review again. Treat this as a normal collaboration safeguard rather than repeatedly submitting the old proposal. Verify the saved draft once the change has been accepted.

• Compare the proposal with the current content.
• Review every affected website in the shared scope.
• Refresh after a conflicting or stale edit.

A page should not depend on large, unprepared images pasted into the layout. Managed images pass through an optimization pipeline before use, reducing the need to store and deliver unnecessary original bytes. Check the resulting asset rather than assuming the source image will look identical at every size.

Inspect the image in the actual page context on desktop and mobile. A technically optimized image can still be the wrong crop or communicate the wrong offer. Use accurate product descriptions and relevant text around it, and keep an accessible page understandable without depending entirely on imagery. Optimization supports performance; it does not replace visual review.

• Use assets the business is permitted to publish.
• Confirm optimized image delivery in the draft.
• Inspect crop, context and readability on mobile.

Creating a managed website, preparing its runtime and publishing content are different steps. Confirm the site's publication requirements rather than treating a saved draft as a live release. Review the final content, public links and website-specific purchase or contact path before authorizing publication.

A custom domain adds ownership and DNS responsibilities. Confirm who owns the registration, which account manages its records and how access can be transferred. Purchasing a domain is not an automatic side effect of creating a website. After release, open the intended public URL independently and check that it serves the reviewed site, including its images and important navigation links.

• Verify the draft before publishing.
• Confirm domain ownership and DNS access.
• Check the live address after release.