How do I let clients edit their website without breaking the design?

Add Dyrected to the website and give the client an Editor account.

Dyrected separates the website's content from its design. Your client can update approved text, images, pages, and repeatable items through a focused dashboard. They cannot change the layout, typography, components, content structure, or access rules.

If your website was built with Lovable, Bolt, v0, Cursor, Replit, or Windsurf, follow our [step-by-step setup guide](/guide). If you prefer working directly with code, use the [Dyrected documentation](https://docs.dyrected.com).

1. Choose what the client can edit

Decide which content the client needs to manage after launch.

This could include:

• Page copy
• Images
• Services
• Team members
• Articles
• Events
• Products
• Contact details
• Other content already present on the website

Do not give the client controls for layout, spacing, typography, animation, or responsive behaviour.

The client should control what the website says. You should continue controlling how the website presents it.

Our setup guide includes a prompt that inspects the existing website and suggests what should be editable. It does not assume the website has conventional sections such as pricing or testimonials.

The AI explains its suggestions in plain language, then asks you to approve them before installing Dyrected.

2. Use structured fields

Avoid giving the client one large blank page editor.

Create fields that reflect the content already displayed on the website. A service might have a name, description, image, and link. An event might have a title, date, location, and registration URL.

The existing component still controls how that information looks.

A client can change a service name without changing its font. They can add an event without building another card. Every new item follows the design you already created.

You can also add limits that protect the layout, such as recommended heading lengths, required fields, and image guidance.

3. Offer approved page blocks when needed

Some clients need to create flexible pages rather than edit fixed fields.

Dyrected lets you define approved content blocks based on your existing components. The client can add or arrange those blocks without creating arbitrary layouts.

For example, you might provide blocks for:

• A text section
• An image gallery
• A call to action
• A list of related entries
• A component specific to that client's website

The client chooses from parts you have already designed. They do not receive a blank canvas or controls for changing the design system.

Only create blocks the website genuinely needs. A smaller block library is easier for clients to understand and harder to misuse.

4. Set the client's permissions

Invite the client with an Editor role rather than giving them administrative access.

Decide whether an editor can:

• Create new content
• Edit existing content
• Publish changes
• Hide content
• Permanently delete content

Do not grant an action simply because the CMS supports it.

A client may need to hide an old service without permanently deleting it. A writer may need to create articles while someone else approves publication.

Editors should not be able to change the Dyrected configuration, content structure, access rules, site settings, or team members.

Dyrected enforces these permissions in the content layer. They are not merely hidden buttons.

5. Connect the existing website

You do not need to rebuild the frontend.

Dyrected supplies content to the components already used by the website. Your existing design, routes, styling, and deployment process remain in place.

For an AI-built website, open our [setup guide](/guide). It provides one staged prompt that:

1. Separates editable content from the design.
2. Asks you to approve the client editing experience.
3. Installs Dyrected and connects the approved content.

The installation prompt reads the current Dyrected documentation, configures access rules, and works through large websites in small verified batches.

Developers who want to configure the integration directly can start with the [Dyrected documentation](https://docs.dyrected.com).

6. Test the editor before handoff

Sign in using the same Editor role the client will receive.

Make sure the field names use language the client understands. If the client calls entries "properties," do not label them "inventory records."

Test the website with less convenient content:

• A longer heading
• A missing optional image
• More items than the page currently displays
• A differently shaped photograph
• An empty description

The layout should remain usable.

If the design only works with the original copy, it is not ready for client editing yet.

7. Give the client a clear handoff

Show the client where to sign in and make one update together.

Explain the boundary:

> You can update the existing content through this dashboard. Send requests for new layouts, new fields, or design changes to us.

The client no longer needs to contact you for ordinary updates. You still handle work that changes the website's structure or design.

Managing several client websites

Dyrected keeps each client site, editing team, content structure, and permissions separate.

You can use the same handoff process across your projects without forcing every client into the same website template.

Each client receives a dashboard based on their own website. You get a consistent way to manage access and structural changes across the sites you maintain.

Give clients control without giving up the design

You do not need to choose between handling every content request and giving clients unrestricted website access.

Add Dyrected, define what the client can edit, set their permissions, and connect the content to the existing components.

[Follow the AI-builder setup guide](/guide) or [read the Dyrected documentation](https://docs.dyrected.com) to get started.

[Join Dyrected early access](/early-access) and create your first client site.