Pages | IMI Life Science

Pages

Manage site pages.

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.

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.

Find And Manage Pages

  • Choose content: Pages lists website content. Help lists articles with paths starting with help/. Both collections use the same search, status filters and actions.
  • Find a page: Search by title or page path. Select a status, or select Published, Drafts or Needs review in the overview. Needs review includes pending approval and rejected content. Overview totals describe the selected collection, not the search results.
  • Sort and browse: Sort by recently updated, title or views in the last 30 days. Choose 25, 50 or 100 rows per page. Search and filter changes return to page one. Filters remain selected when switching collections; use Clear filters to show all content.
  • Keep your view: Search, collection, status, sort and pagination are stored in the URL. Browser Back restores the previous directory view after opening the editor. Choose columns controls optional details; page titles and editing actions always remain available.
  • Edit or create: Open a page title or its pencil icon to edit. Create Page starts a blank page; From Template uses the existing template picker.
  • Page actions: Open the three-dot menu to duplicate, copy the page path, publish a draft, unpublish a live page or delete. Publish and Unpublish require confirmation. Publishing a page while filtering drafts removes it from those results after refresh.
  • Delete carefully: The confirmation identifies the page and its path. Deleting published content may break existing links. Cancel changes nothing; a failed operation leaves the dialog open and shows an error so you can review and retry.
  • Traffic and freshness: Views covers the last 30 days. N/A means analytics is loading or unavailable, not zero traffic. Last updated falls back to the creation date when no update date exists. Refresh pages reloads the directory.