Homepage

LiquidLayout

Last edit: Oct 13, 2026

Layout (app/views/layouts): Liquid that wraps the content of pages and emails

type LiquidLayout implements AdminSharedAttributesInterface {
  body: String
  created_at: JSONDate!
  format: PageFormat
  id: ID!
  manually_managed: Boolean
  metadata: HashObject
  path: String!
  physical_file_path: String
  updated_at: JSONDate!
}

Fields

body (String)

Liquid source of the layout. The content of the page or email using the layout is inserted with

created_at (JSONDate)

Timestamp of when the object was created, set automatically by the system

format (PageFormat)

Format of the pages the layout is used for, html by default

id (ID)

Unique identifier of the object

manually_managed (Boolean)

When true, the resource is managed outside of files: pos-cli deploy and sync never overwrite or delete it

metadata (HashObject)

Free-form data attached to the resource with the metadata key of its file (or the metadata argument of an admin mutation)

path (String)

Path of the layout, starting with layouts/, for example layouts/my_layout.
Pages and emails refer to it without the layouts/ prefix

physical_file_path (String)

Path of the file the resource comes from, relative to the app directory, for
example views/pages/index.liquid or
modules/my_module/public/views/partials/header.liquid. Identifies the resource
in deploy, sync and admin mutations

updated_at (JSONDate)

Timestamp of when the object was last updated, set automatically by the system

Interfaces

AdminSharedAttributesInterface

Attributes shared by resources that can be deployed from files with pos-cli
(pages, partials, layouts, notifications, authorization policies, schemas, assets etc.)

Questions?

We are always happy to help with any questions you may have.

contact us