# Design Salesforce Lightning pages, and review them like a design.

> The SyncOnAI 360 Lightning Page Builder draws a Salesforce Lightning page as the page, with its regions and components where they really sit. X-Ray explains what each part is and depends on, Diff compares a draft with the org's page side by side, Persona preview shows it as a given profile, and pages ship through approval.

Source: https://synconai360.com/features/lightning-pages

## Key facts

- **1:1**: Page drawn with regions and components where they sit
- **2**: Versions side by side: your draft and the org's page
- **Any**: Profile can be previewed before release
- **0**: AI required: pages can be built and deployed without it

## Why Lightning page changes are hard to review

Lightning App Builder is good at editing a page and poor at explaining one. Reviewing a change means opening two orgs side by side and guessing how it will look to each user.

- **No design review.** There is no simple way to see what a draft changes compared with the page in production.
- **Hidden dependencies.** Components on a page depend on fields, Apex and visibility rules that are not visible on the canvas.
- **One user's view.** Builders see the page as themselves; users with other profiles see something else.
- **Changes straight to production.** Page activations often happen directly in production, without review or a way back.

## How does the builder show a Lightning page?

The page is drawn as the page: its regions and components where they really sit, not a list of components in a sidebar. The builder explains the page in plain sentences before you edit it, and every edit is recorded as a version you can step back through.

Open a page by naming it in the chat, from the chat's start screen or from the builder itself. Lightning pages are synced with the rest of the org's metadata, so existing pages open as they are.

- Regions and components in place
- Plain-language overview first
- Versioned edits

## What does X-Ray show on a Lightning page?

X-Ray shows what each part of the page is and what it depends on: the component, the fields it displays, the Apex or data behind it. Reviewers can understand a page without knowing how it was assembled.

Combined with lineage, it answers the question a page change usually raises: if this field moves or disappears, what else relies on it?

- Each part identified
- Dependencies for each component
- Lineage for the fields behind them

## How do you review a Lightning page change?

Diff turns a change into a design review: your draft and the org's page side by side, so reviewers see exactly what moved. Persona preview shows the page as a given profile would see it, so a change can be checked for every audience before it ships.

Pages ship as proposals with named checks and a before and after view, and production needs approval from an admin other than the author.

- Draft and org side by side
- Preview per profile
- Proposals with approval

## What can the Lightning Page Builder not do yet?

A live preview with real records, changing the page template, and editing advanced visibility rules are not available yet. The builder says so rather than offering a partial version.

Everything else on the page can be built, reviewed and deployed, with or without the AI model: a page can be started and deployed entirely by hand.

- No live record preview yet
- No template changes yet
- No advanced visibility editing yet
- Works without AI

## How do Lightning page changes fit with the rest of the org?

Lightning pages are synced with the rest of the org's metadata, so they appear in search and in the change history like any other component, and each deployed page change leaves a receipt with the version it can be rolled back to.

Persona preview, X-Ray and Diff are review tools rather than extra steps: a change can be explained, checked for each profile and compared with the live page in the time it used to take to describe it in a ticket.

- Pages in search and change history
- A receipt for every page deploy
- Review in minutes, not tickets

## Changing a Lightning page

1. **Open.** Name the page in chat or open it in the builder.
2. **Edit.** Change it by hand or with AI previews.
3. **Inspect.** Use X-Ray to check what each part depends on.
4. **Review.** Diff against the org and preview per profile.
5. **Ship.** Propose, approve and deploy with a receipt.

## Page changes, with and without design review

| Without | With SyncOnAI 360 |
|---|---|
| Two orgs open side by side | A built-in side-by-side diff |
| Dependencies invisible on the canvas | X-Ray for every part |
| Seen only as the builder | Preview per profile |
| Activated straight in production | Proposals with approval and rollback |

## Who uses the Lightning Page Builder

- **Salesforce admins.** Change record pages by working on the page as it renders, explained in plain sentences first, then check it for each profile with persona preview before it ships.
- **Business analysts and product owners.** Review a page change as a side-by-side design diff rather than a list of metadata, and understand what each part of the page shows and depends on with X-Ray.
- **Consultancies.** Rework a client's record pages with every edit versioned, reviewed as a diff and approved by a second admin for production, so page changes arrive as governed releases.
- **Salesforce developers.** See which components, fields and Apex sit behind each region of a page, and how moving a field affects everything else that relies on it.

## Frequently asked questions

### What is the Lightning Page Builder?

A builder that draws Salesforce Lightning pages as they render, with X-Ray, a side-by-side diff against the org and persona preview, shipping through approval.

### Does it replace Lightning App Builder?

It works alongside it. Pages remain ordinary Lightning page metadata in your org.

### Can we preview a page as another profile?

Yes. Persona preview shows the page as a given profile would see it.

### Can it show real records?

Not yet. A live preview with real records is not available.

### Can we change the page template?

Not yet. Changing the template and editing advanced visibility rules are not available.

### Do we need AI to use it?

No. A page can be started and deployed without the AI model.

### How are page changes approved?

As proposals with checks and a before and after; production needs an admin other than the author.

### Is it on every plan?

Yes. Every plan includes every feature.

### Where do we start from?

Name the page in the chat, pick it from the chat's start screen, or open it in the builder. Existing pages are synced with the org, so they open as they are.