Pages and Layouts Overview

Pages, layouts, and partials form the view layer of every Insites application. Together they control what your users see, how URLs map to content, and how you organize reusable UI components. This section covers everything from creating your first page to caching strategies for production performance.

What You Will Find Here

• Pages - The building blocks of your application. Each page maps to a URL and handles an HTTP method. Learn how to create pages, configure routing, set custom response headers, and make content searchable.
• Metadata - Control SEO metadata, Open Graph tags, and Twitter Cards for your pages.
• Layouts - Wrapper templates that provide consistent structure (headers, footers, navigation) across pages. Learn how to create layouts and inject dynamic content from pages.
• Partials - Reusable code snippets for HTML, UI components, and presentation logic. Keep your code DRY and maintainable.
• Redirects - Set up URL redirects for moved content or vanity URLs.
• Custom Error Pages - Replace default error pages with branded alternatives that help your users.
• Assets - Static files like CSS, JavaScript, images, and fonts. Includes the asset pipeline, CDN delivery, and the Assets module integration.
• Context Variable - The global context object that gives your Liquid code access to request data, session state, user information, and environment variables.
• Translations - Build multilingual sites, customize date formats, and define system messages.
• Caching - Fragment, dynamic, and static caching strategies to speed up your application.

How It All Fits Together

When a request hits your Insites application, the platform matches the URL to a page. That page runs inside a layout that provides the outer HTML structure. The page and layout both use partials to render reusable UI components. Static files are served from the assets directory via CDN, and the context variable gives every template access to request parameters, session data, and the current user.

For production, caching lets you store rendered output at various levels, from individual fragments to entire pages, dramatically reducing server load and response times.