Page Editor | IMI Life Science

Page Editor

Visual builder.

Concurrent Editing

  • Automatic Locking: A lock is acquired when you start editing.
  • Read-Only Mode: If another user is editing, the page becomes read-only, and you will see their name in a banner.
  • Lock Expiry: Locks expire after 1 hour of inactivity.
  • Force Release: Administrators can unlock a page if needed.
  • Align text: Use Header Text Alignment for the section heading and Card Text Alignment for slide titles, descriptions, and links.
  • Size images: Set a Default Image Fit for the block, then override it on individual slides when needed. Cover crops to fill, Contain preserves the whole image, Fill stretches, Scale Down never enlarges the source, and None uses its natural size.
  • Link images: When a slide has a Link URL, both its image and text link open that destination. External links open in a new tab.

Image-Backed Banner Presentation

  • Choose Cover to fill the banner; use Contain only when the complete uncropped artwork must remain visible.
  • Set Image Opacity to 100% for a full-strength image, then use Gradient Overlay to darken it without fading the source.
  • Under Design & Branding, set both Title Color and Text Color to White for reliable contrast.

Rich Text Tables

  • Insert a table: Add or edit a Rich Text block, choose the table icon, then set the row count, column count, and optional header row.
  • Change its structure: Place the cursor inside the table to add or remove rows and columns, or delete the table.
  • Preview responsive behavior: Wide tables scroll horizontally on smaller screens and automatically use the active storefront palette and typography.

Scroll Animations

  • Enable per page: Open Page Settings > Advanced and select Scroll animations. It is off by default.
  • Preview before publishing: Live Preview includes the unsaved setting. Check desktop and mobile, then save and publish the page.
  • Supported content: Stats and Key Statistics count numeric values up with staggered reveals. Text and Value Proposition reveal their text and media once on entry. Text-only statistics remain readable without a counter.
  • Respect accessibility: Visitors who prefer reduced motion see the final content immediately. Returning to a section does not replay its animation.
  • Turn it off: Clear Scroll animations, then save and publish. Existing page history retains the setting for restore.

Optional Block Presentation

Last updated: 2026-09-08. These settings affect only the blocks you explicitly configure. Review the draft in Live Preview before publishing.

  • Color gaps: In Design & Branding, keep the required Space Before/After Block and choose Spacing Background. Clear the swatch to restore the original transparent margins. A card's Section Background controls its surrounding section independently.
  • Adjust bold emphasis: Text and Rich Text blocks expose Bold Text Weight in the Design tab. Choose Bold (700) for stronger bold-marked text, or Use existing emphasis to retain the original display.
  • Change selected text colors: Select the characters in the content editor and use Text Color. Remove color lets the block's Text/Title Color take effect; explicit inline colors otherwise retain priority.
  • Customize document-card actions: In the Document Download block's Button section, select Download, Link, or No button. Link supports a custom Button Label, Button Link, and optional new tab without download behavior. Existing document settings are retained when changing modes.

SI Unit Style

Purpose: Review displayed quantities against common NIST SI conventions before saving content for IMI Life Science.

  • Review warnings: The SI unit style panel identifies the field, highlights the affected text and cites the NIST section. Warnings remain visible while a supported issue exists, including in collapsed block content.
  • Apply a correction: Use Fix field or Apply safe fixes to correct deterministic spacing, range, dimension and uncertainty notation in the current draft. Save normally afterwards; applying fixes does not save or publish.
  • Check spacing: Leave a space between the number and unit, including percent and degree Celsius. Plane-angle symbols stay next to the number. Repeat units for dimensions and range endpoints.
  • Review ambiguous values: Parts-per notation, mixed units, quantity qualifiers, ambiguous hyphens and some shared-unit expressions need manual review. The helper does not convert magnitudes, guess prefixes or certify full SI compliance.
  • Respect ownership: Read-only values keep warnings without correction controls. Change unit metadata in the attribute definition. Source and translated drafts save separately; links, identifiers, numeric values and technical configuration are retained.

NIST SI guide, Chapter 7

Last Updated: 2026-09-14

Custom Block Tabs and Accordions

Last updated: 2026-09-14. Published custom blocks keep their existing definition version and saved content.

  • Tabs: Each tab displays its own content. Choose the default tab in the block definition. Visitors can switch tabs with the arrow keys and use Home or End to reach the first or last tab.
  • Accordions: Each section contains its own collapsible content. Default Open expands the first section initially. Allow Multiple lets several sections stay open; otherwise opening one closes the previous section in that block.
  • Preview: Check each tab and accordion section in Live Preview before publishing. Nested and reused custom blocks keep their interaction state independent.

Repeated Content Items

Last updated: 2026-09-14. These controls apply only when the selected custom-block definition explicitly exposes an item collection. Existing definitions keep their original fields.

  • Edit a collection: Add an item, fill its fields, and use the arrow controls to change its position. Remove affects only that item. The displayed count shows the definition's item limit.
  • Preserve the draft: Item changes stay in the owning editor's draft until its normal save action. Opening the editor does not convert or save existing content. Read-only views disable item changes.
  • Handle invalid content: An invalid collection displays an error instead of being silently reset or shortened. Ask the block publisher to review its saved values and compatible definition version.

General builder activation, complete storefront inline editing and localized item workflows are still pending. Do not force an existing definition into item mode; continue using its published fields until a compatible version is available.

Custom Block Version Checks

Last updated: 2026-09-14. Top-level custom blocks are checked before page saves, publication, version restoration and block translation saves.

  • Keep the selected version: Each custom block uses its saved definition version. Saving a page does not silently switch to the newest version. A translation must use the same version as its source.
  • Resolve a rejected save: Check the block's version and repeated item values. Missing or deleted definitions, active draft versions, duplicate item identities and excessive item counts are rejected before the page is changed.
  • Restore carefully: A valid snapshot restores its block values and version pins. If its custom definition is unavailable, ask the block publisher to restore the compatible definition or replace the affected placement explicitly.

General repeatable builder activation and localized item workflows remain staged. These checks do not make every nested block or content-owner workflow feature-complete.

Custom Blocks Inside Page Layouts

Last updated: 2026-09-14. Custom children inside Content Composition, Column Layout and Tabbed Content are checked before page saves and lifecycle changes, including children in inactive tabs.

  • Resolve a rejected layout: Check every nested custom block's selected version and repeated item values. A missing version, active draft, invalid item identity or excessive item count prevents the whole save; existing page content is retained.
  • Keep compatible versions: Each child uses its own saved version. Page saves and version restoration do not automatically upgrade children to the latest definition.
  • Simplify excessive nesting: A root layout supports up to 16 child-placement levels and 500 combined placements and tab groups. Split larger layouts into smaller page sections before saving.

Translation saves check nested item values, but preserving nested versions, item identities and structure across languages remains a separate staged workflow. General repeatable builder activation and other content-owner integrations are not yet complete.

Restoring Pages From Trash

Last updated: 2026-09-14. Restoring a page checks its saved custom blocks and every stored block translation, including children inside supported page layouts.

  • Keep saved content: Successful restoration keeps block identities, item order, selected definition versions, translations and the previous publication status. A restored draft remains a draft; a restored published page becomes public again.
  • Resolve a rejected restore: The page stays in trash if a definition is unavailable, repeated values are invalid or a top-level custom translation changes its source version. Ask the block publisher to recover the compatible definition, or arrange a reviewed content repair before retrying. Restoration never drops invalid content or upgrades a version automatically.
  • Refresh stale results: A page that is missing or already restored returns a not-found response. Refresh the Pages list instead of repeatedly restoring it.

These checks do not complete repeatable authoring in every content engine or prove that translated nested structure matches its source. Those workflows remain staged.

Custom Blocks In Saved Templates

Last updated: 2026-09-14. Template saves, updates, duplication, imports and page creation check saved custom block versions and repeated values, including supported nested layouts.

  • Keep compatible versions: Templates retain each custom block's saved version. Imported templates require that exact definition version at the destination; imports do not install definitions or choose newer versions automatically.
  • Review import results: Invalid items are skipped with an error before their template or category is created. Valid items can still be imported. Check created and skipped counts; an import response does not mean every item succeeded. Each batch allows up to 500 templates.
  • Recover a rejected action: Restore the compatible definition through its publisher or use a reviewed valid template. Rejected updates keep the existing template unchanged, and rejected page creation does not increase its usage count.

Save as Template removes source values but retains validated custom versions and supported nested layout structure. New custom bindings in the template editor and general repeatable builder activation remain staged.

Template Import And Page Creation Failures

Last updated: 2026-09-14. Each imported template and any newly required category are saved together. Creating a page from a template saves the page and its usage increment together.

  • Review partial imports: A database-rejected item leaves no new template or orphan category and does not prevent later valid items from importing. Existing category details remain unchanged. Previously accepted items stay committed.
  • Retry a confirmed failed page creation: If the database rejects either the page or usage update, neither is committed. Resolve the reported problem before retrying; successful concurrent page creations each add one use.
  • Check uncertain outcomes: A network interruption can hide a successful commit. Inspect the template inventory or requested page slug before retrying. Imports still create new templates and are not an idempotent upsert.

Structure-only template authoring and other repeatable-block integrations remain staged. These persistence guarantees do not activate those workflows.

Repeatable Template Limits

Last updated: 2026-09-14. A repeatable item's template permits at most eight primitives, including wrappers and their descendants. A Stack or Card with seven content primitives reaches the limit; eight content primitives inside that wrapper exceed it.

  • Check the whole template: Each repeatable group has its own eight-primitive limit and two-level item depth. The complete definition still has a 40-node limit and five-level depth.
  • Keep item counts separate: The number of repeated content items is a different limit. Adding item values does not create new definition nodes.
  • Resolve rejected versions: Definition saves, publication and historical version restoration enforce the structural limits. Older oversized versions are not trimmed, rewritten or upgraded automatically; a publisher must prepare an explicit corrected version.

Binding authoring and other repeatable workflows remain staged. Passing these server checks does not activate the complete feature.

Add a Page Block

Last updated: 2026-09-14. In the Page Editor, open the command palette with Ctrl+K or Cmd+K and choose Add Block, or use Add Section.

  • Choose a block: Search or filter by category in the shared picker. On narrow screens, use the category dropdown.
  • Keep the insertion position: Select an existing section first to insert after it; with no selection, the new section is appended. The new section becomes selected and the draft has unsaved changes.
  • Cancel safely: Escape or Close dismisses the picker without changing content or the selected section. Focus returns to Add Section.
  • Save deliberately: Choosing a block does not save or publish the page. Save the draft, then reload to confirm the stored result before using publication actions.
  • Check editing access: Adding blocks requires page-management permission and source-language editing. It is unavailable while the page is loading, has a load error, is saving, or is in a translation view.

Resolve a Rejected Builder Edit

Last updated: 2026-09-15. Adding, moving or duplicating a primitive, or loading a preset, checks the resulting definition before changing your draft. A rejected edit displays the structural limit and leaves content, selection, unsaved status and undo/redo history unchanged.

  • Count wrappers and children: Each repeatable item template permits eight primitives across two levels. One Stack or Card with seven content primitives reaches the limit. Stack and Card are the supported wrappers; other layouts and nested repeatable groups are not permitted inside the template.
  • Check the complete definition: The full tree permits 40 primitives and five levels, including the root. A layout's direct-child capacity also applies to moves and duplicates. Repeated item values do not add definition nodes.
  • Repair explicitly: Remove excess primitives or unnecessary wrappers before retrying. Existing definitions still load without automatic trimming or binding conversion; removal and undo/redo remain available. Save a corrected definition version through the owning workflow instead of changing published content or version pins.

These checks cover structure, not the complete repeatable authoring rollout. Explicit binding authoring and the remaining repeatable integrations are still staged.

Save Custom Blocks as a Template

Last updated: 2026-09-15. Save the page first, then use Save as Template to reuse its block types, order and supported page settings. Custom blocks placed directly or inside supported nested layouts retain their exact saved definition versions.

  • Start with new content: Source text, repeated item values, media, links and instance overrides are not copied. The source page and its history remain unchanged. Add new values after creating a draft page from the template.
  • Resolve a rejected save: Missing, ambiguous, unavailable or active-draft custom versions prevent template creation. Recover the exact compatible version through its publisher or explicitly correct the source placement; the operation never substitutes a newer version.
  • Check the remaining limits: Native leaf content still clears. Adding new custom bindings in the template editor remains unfinished. Existing templates are not repaired automatically.

Reuse Nested Layout Structure

Last updated: 2026-09-15. Save as Template retains ordered children in Content Composition, Column Layout and Tabbed Content, including mixed nesting. Supported composition display settings, child layout identities, column assignments, tab keys and the default tab are retained. Tab labels reset to neutral names.

  • Content stays separate: Source text, repeated values and item IDs, media, links, product references and instance overrides are not copied. Native leaf blocks start empty. Existing renderer defaults may still appear until new values are entered.
  • Resolve invalid structure: Malformed supported layouts, invalid nested custom versions and structures exceeding 16 child-placement levels below a root or 500 combined placements and tab groups per root prevent template creation. Correct the source structure without replacing its exact custom versions with newer ones.
  • Review the draft: Create a draft page from the template, enter new content and review every tab before publishing. Only the three supported layout formats are preserved; other container formats are not certified.

Multiple Page URLs

  • Primary URL: In Page Settings & SEO, keep the primary slug as the page's main address.
  • Add alternate URLs: Under URL Aliases, select Add URL alias and enter a relative path such as company/team. Add up to 20 aliases.
  • Save changes: Aliases share the same content, translations and publication status. Published pages expose saved URL changes immediately; draft pages remain private.
  • Resolve validation errors: URLs must be unique across pages and cannot use reserved application routes. Use letters, digits, hyphens, underscores and single slashes between path segments.
  • Remove a URL: Use its trash button and save. Removing an alias does not change the primary URL. Use Redirects for permanent URL forwarding.
  • Copies and history: Page copies have no aliases. Content-version restores do not replace the page's current URLs.

Open A Form From A Call To Action

  • Choose an action: In the block's CTA destination settings, choose Open form in modal instead of Navigate to URL.
  • Select a form: Choose a published managed form, such as Contact us. Unpublished forms cannot be selected.
  • Save and preview: Save the page draft and test the CTA in the storefront preview. The form opens over the current page and submits without changing its URL.
  • Publish: Publish the page to make the CTA available to visitors. Existing navigation CTAs remain unchanged.
  • Supported blocks: Hero, text, hero slider/carousel, carousel cards, image grids, brand showcases, resource lists and custom LinkTo destinations support modal forms. CTA banners retain their existing form action.
  • Submission tracking: Validation, workflows and lead attribution use the managed form's normal submission pipeline. Published pages using a modal form prevent that form from being deleted.

Edit Rich Text as HTML

  • Edit HTML: Use the code icon in an editable rich-text toolbar to open its current HTML. Visual editing remains the default, including compact fields and labels.
  • Apply: Return supported HTML to the visual editor, then use the parent record's normal Save or Publish action. Applying source alone does not save the record.
  • Supported markup: Source uses the same rich-text format as the field. Unsupported tags or attributes may be removed or normalized. Scripts, unsafe links, and event handlers are removed; existing server validation and design rules still apply.
  • Cancel: Cancel, close, or press Escape to discard the source draft. Opening source or applying unchanged source does not change the record. If content changes elsewhere while the dialog is open, cancel and reopen it before editing.
  • Mail variables: Keep placeholders such as {{firstName}} and {{accountUrl}} intact, including placeholders in link addresses. The source dialog does not expose internal variable-chip markup.
  • Read-only content: HTML editing is unavailable when the field is read-only. Plain-text fields and structured block settings are not HTML editors. A failed Apply retains the source draft for correction.

Key Statistics Hover Effects

  • Open the controls: Select a Key Statistics block in the page editor and expand Hover Effects. These settings also apply to Key Statistics nested inside layouts.
  • Disable all effects: Turn off Enable Hover Effects to remove hover color, size, and shadow changes.
  • Disable color changes: Keep Enable Hover Effects on and turn off Change Color on Hover. Values, labels, and icons keep their normal colors.
  • Disable size changes: Keep Enable Hover Effects on and turn off Change Size on Hover. Cards no longer grow; the shadow effect remains while hover effects are enabled.
  • Save and preview: Save the page draft and check its preview, then publish when ready. Existing blocks keep all hover effects enabled until changed. Turning hover effects off preserves the individual color and size choices for re-enabling. Page scroll animations are controlled separately.