Using Live Preview to Check Page Updates

Opening live preview from the page editor

In Sherkety ERP & Website Platform, start from the Content area in the admin section and open the page entry you want to review. Live preview is most useful after you have already made edits in the content editor, such as changing a heading, updating body text, replacing a button label, or adjusting a section’s content. If you have been working through save checks already, use the same review habits from Validating Saving and Reviewing Content Changes before relying on the preview.

1. Open the page you are editing from Admin > Content.
2. Look at the editor toolbar for the Live Preview control.
3. Select Live Preview to open the draft view in the preview pane or preview tab.
4. Confirm you are previewing the correct page by checking the page title and the page address label shown in the editor.
5. Check the language shown in the editor before you begin reviewing the page.

Live preview shows the draft version of the page you are currently editing. That means it is meant for checking changes before they appear on the public website. If you changed wording in a text field, updated a translated title, or adjusted a section’s content, those draft updates should appear in preview for review. This lets you inspect the page as it will look after publication without changing what visitors currently see.

Keep the difference clear while reviewing:

• Live preview shows your draft work for checking and approval.
• Public page shows the currently published version seen by visitors.

Opening live preview does not publish anything. It is only a review step inside Sherkety ERP & Website Platform, so you can safely inspect page updates before making them visible.

Checking layout changes before publishing

Live preview is especially helpful when you changed more than plain text. If you edited headings, body sections, banners, images, or call-to-action areas, the preview lets you confirm how those pieces actually sit on the page. A content form can look correct while the finished page still feels crowded, uneven, or out of order, so always review the rendered result.

1. After editing a section, open Live Preview from the page editor.
2. Scroll through the page from top to bottom.
3. Check that each section appears in the intended place on the page.
4. If you moved, added, or removed content blocks, confirm the order matches your intended layout.
5. Make another edit if needed, then refresh the preview so the latest draft version is shown.

As you review, pay close attention to visual details that are hard to judge in input fields:

• Heading length and whether it wraps awkwardly
• Spacing above and below sections
• Alignment between text, images, and buttons
• Whether banners or call-to-action blocks feel balanced
• Whether removed content left an obvious gap

This is also the best place to catch problems caused by recent structure changes. For example, a section may appear lower than expected after reordering content, or a longer heading may push a button onto a new line. If you edited repeating items or structured sections earlier, compare the preview against the intended arrangement you set in the editor.

When the preview does not reflect your latest layout change, update the draft in the editor and reload the preview view before continuing. Review the page as a visitor would scroll through it, not just as a list of fields.

Reviewing wording and links in the preview

Once the layout looks right, read the page in live preview as if you were a first-time visitor. This step helps you catch issues that are easy to miss while typing into fields, especially when text looks fine in the editor but feels unclear or cramped on the page itself.

1. Read the page from the top heading down through each section.
2. Check headline text, subheadings, body copy, and button labels exactly as they appear in preview.
3. Review any formatted text to make sure paragraph breaks, lists, emphasis, and linked text display correctly.
4. Select buttons and links in preview where available to confirm the wording and destination make sense.
5. Return to the editor to adjust any text that feels outdated, awkward, or too long for the page design.

Focus on the content visitors actually read and click:

• Main page heading
• Introductory text
• Section titles
• Button labels
• Linked text inside paragraphs
• Closing call-to-action wording

Rich text deserves extra attention. In the editor, a paragraph may look complete, but in live preview you may notice missing spacing, broken lists, or emphasized text that draws too much attention. Linked text should also read naturally inside the sentence, not feel pasted in.

If the preview allows you to follow links, use that to confirm the label matches the destination. A button that says Learn More should open the expected page, and any external link should match the intended destination entered in the editor. If navigation is limited in preview, at least confirm the visible label and nearby text are correct.

This side of previewing is less about editing fields and more about reading for clarity. Shorten text that wraps badly, fix wording that still reflects old messaging, and update labels that no longer match the page’s purpose.

Switching languages to verify multilingual presentation

If the page is available in more than one language, use live preview to review each language version separately. A page can look polished in one language and still have missing translations, mixed-language buttons, or layout issues in another. Sherkety ERP & Website Platform includes language-aware content editing, so preview should be part of every multilingual review.

1. In the editor, change the language using the available language selector.
2. Open or refresh Live Preview for that language.
3. Confirm the page title, body text, and button text appear in the selected language.
4. Repeat the check for each language you maintain for that page.
5. If something still appears in the default language, return to the editor and review that field’s translated content.

Check the most visible language-sensitive content first:

• Page title
• Navigation label, if shown in the page setup
• Section headings
• Body text
• Call-to-action text
• Button labels

Live preview is also where you can spot fallback behavior. If a translation is missing, some content may still appear in the default language. That is useful during editing because it shows you exactly which parts still need localized text before publication.

Layout can also change between languages. A short English heading may fit on one line, while the translated version wraps onto two lines and changes the balance of the section. Review these differences carefully in preview instead of assuming the design will behave the same way in every language.

For more detailed field-by-field translation work, continue with Editing Multilingual Fields and Localized Content Variants after you finish your preview review.

Comparing draft updates with the published page

Live preview is most effective when you compare it directly with the currently published page. This helps you confirm exactly what will change once you publish, especially when you have updated several sections over time or worked in multiple languages.

1. Keep your draft open in Live Preview.
2. Open the current public version of the same page in a separate browser tab.
3. Place the two views side by side if possible.
4. Compare each major section from top to bottom.
5. Confirm that every visible difference is intentional before you publish.

Look for differences such as:

• Updated headings or body text
• Replaced images or banners
• Reordered sections
• Added or removed call-to-action blocks
• Changed button labels
• Updated translated content in another language

This side-by-side check is useful when a page has gone through several rounds of editing. You may remember changing a headline but forget that you also replaced a section image or moved a block lower on the page. Comparing draft and published views makes those differences obvious.

If something looks wrong in preview, do not assume the draft is broken immediately. A mismatch can happen for a few simple reasons:

• The latest edits were not saved to the draft yet
• You are viewing the wrong language version
• The preview needs to be refreshed after a recent change
• An image or page asset has not updated in the current view yet

Use the published page as your baseline and the live preview as your approval copy. If the draft shows exactly the changes you intend, you are in a much safer position before selecting Publish.

Fixing common live preview problems

Most live preview issues come from a small number of review mistakes: the wrong page is open, the wrong language is selected, the latest draft was not saved, or the preview is still showing an older render. Before reworking content, check those basics first.

If the preview does not update after you edit content, save your draft and refresh the preview. Then confirm you are still editing the same page entry in Content. This is especially important when you have several tabs open or switch between similar pages.

If the wrong language appears, check the language selector in both places you use during review:

• The language currently selected in the editor
• The language shown in the preview controls or previewed page state

A layout that suddenly looks broken often points back to a recent content change rather than a preview problem. Review the last items you changed, especially:

• Moved sections
• Hidden or removed blocks
• Replaced images
• Longer headings or button labels
• Updated rich text with lists or extra spacing

Links and buttons can also appear incorrect during preview. If a button label is right but the destination seems wrong, return to the editor and review the link target you selected or entered. If a previewed link does not fully navigate, that may be a limitation of the preview view rather than a content problem, so focus first on whether the label and target setup are correct.

When troubleshooting, use this quick check:

If the page still looks wrong after these checks, return to the editor, correct the content, and open live preview again before publishing.

Overview

Live preview in Sherkety ERP & Website Platform is the review step that lets you inspect draft page changes before they appear on the public website. It is most useful after editing page text, section order, banners, images, buttons, or translated content in the Content area. Instead of judging a page only from form fields, you can open the draft view and see how the page actually reads and flows.

Use live preview to confirm four things:

• The right content appears on the right page
• The layout still looks balanced after edits
• Wording, formatting, and links read correctly
• Each language version displays as expected

This guide focused on checking the rendered page, not on how to save or validate edits. If you need to revisit draft review and save confirmation, see Validating Saving and Reviewing Content Changes.

A good live preview review usually includes:

• Opening the correct page entry
• Confirming the page title and language
• Scrolling through the full draft page
• Comparing draft and published versions
• Fixing any mismatched wording, layout, or translation issues before publishing

Treat live preview as your final visual check. It helps you catch issues that are easy to miss in the editor, such as awkward line breaks, mixed-language text, outdated button labels, or sections appearing in the wrong order. When used consistently, it reduces the chance of publishing a page that looks different from what you intended.

Prerequisites

Before using live preview in Sherkety ERP & Website Platform, make sure you already have access to the admin area and can open the Content section for editing. Live preview is part of the page editing workflow, so you need to be inside a page entry rather than only browsing the public website.

You should have the following in place before starting:

• You can sign in to the admin area
• You can open Admin > Content
• You have permission to edit the page you want to review
• The page already contains draft changes you want to inspect
• You know which language version you are checking

It also helps if you have already completed the earlier editing steps covered in these related guides:

• Editing Multilingual Content in the Editor
• Managing Repeating Content and Structured Items
• Previewing Changes Before Saving Content
• Managing Multilingual Fields in the Content Editor
• Editing Structured Content and Repeating Items

For the smoothest review, keep these practical conditions in mind:

• Save recent edits before assuming preview is wrong
• Review one page and one language at a time
• Keep the public page available in another tab when comparing changes
• Reopen or refresh preview after major edits to section order or media

If your next task is to refine translated fields after checking the page visually, continue with Editing Multilingual Fields and Localized Content Variants.