Templates and Layouts
Templates and layouts control page structure. A template defines the overall page shell: regions, header/footer areas, and where the main content goes. A layout (canvas layout) is the grid or slot arrangement inside which builders drop components. Understanding the difference is a classic exam point: templates are the page-level frame; layouts are the arrangement of content within a region.
Site Studio uses a canvas - the drag-and-drop editing surface. Within the canvas, layout canvases provide rows and columns (a grid system) so components align predictably. Regions in a template mark where Drupal-rendered content or component canvases appear. Master templates apply site-wide structure; content templates can be tied to content types so nodes get a consistent layout.
Traps:
- Confusing a template (page frame) with a layout (inner grid).
- Assuming a template change updates existing pages - templates affect rendering, but per-page canvas content is stored separately.
- Forgetting that a content template can be assigned per content type, changing how all nodes of that type render.
- Overlooking responsive behavior: layouts define breakpoints, and column stacking differs per breakpoint.
Worked rule of thumb
If the question is about header/footer, page regions, or site-wide frame → think template. If it's about rows, columns, and where components sit inside a region → think layout/canvas. If it's about making all "Article" nodes share a structure → think content template tied to the content type.