Search

Commerce /books/commerce Worked example: a course catalogue /books/content-types/custom-entity-types/course-catalogue Content types and custom entities /books/content-types Two engines, one platform /books/template-languages/shared-model/two-engines-one-platform Add the areas and their input types /books/start-here/first-page-end-to-end/add-the-areas Forms and data capture /books/forms Twig in Core dna /books/template-languages/twig/twig-in-core-dna The external-id pattern /books/apis/client/external-ids Which template renders a record /books/template-languages/shared-model/which-template-renders-a-record The three things that always need a fragment /books/choosing-how-to-build/hybrid-builds/always-a-fragment Make an area an attribute instead of content Tick Attribute on the layout area and it leaves the content form for the Attributes tab, button or cog, depending on where it lives. Templates read it exactly as before; only the author's form changes. /how-to/area-as-attribute Two ways to build a site /books/start-here/building-on/two-ways-to-build js-forms-conditionals.js reference /books/forms/reference/js-forms-conditionals What an environment is, and telling them apart /books/performance-and-deployment/managing-environments/environments The shape of a theme repo /books/start-here/setting-up/repo-shape Core dna in one page /books/start-here/building-on/core-dna-in-one-page What the index holds /books/search/indexing/how-indexing-works Render a custom entity listing and detail page The listing renders the definition's template with the records under the plural identifier plus _pagination; the detail renders the layout's template with the record under the identifier and as record. Both are 404 without a template. /how-to/custom-entity-listing-and-detail Start with a placeholder template /books/start-here/first-page-end-to-end/your-first-page Bundle boundaries /books/theme-repo/anatomy-of-a-theme-repo/bundle-boundaries Rendering and styling /books/forms/presentation/rendering-and-styling Render the areas in both engines /books/start-here/first-page-end-to-end/render-the-areas Bundle size /books/performance-and-deployment/making-pages-fast/bundle-size Render a collection, handling both global and local components On the frontend, a collection element's getComponent() already returns the global component when the element points at one, so one loop serves both. Guard for blank, and pass only new variable names down. /how-to/render-a-collection Nest a component inside another and keep heading levels valid A component with a collection of its own can hold components; the heading level is the thing that breaks. Keep the current level in the template context: read it, print, raise it for children, restore it afterwards. /how-to/nest-components-heading-levels Build a global header and footer an author can edit A global component is stored once, versioned, and edited by authors without a deploy. Give it a component layout, an identifier, and fetch it in the base template with _globalComponents.get(). Its template reads areas as any component does. /how-to/global-header-and-footer Editing component collections /books/apis/writing-content/component-collections Response models /books/template-languages/shared-model/response-models Take a payment inside a form A donation form: a Payment element on its own last step, set to Authorize & Capture, the platform's payment script in the layout, and a receipt sent from the form's Completed event, because the platform sends none. /how-to/take-a-payment-inside-a-form Nothing changed: the four checks /books/start-here/first-page-end-to-end/nothing-changed Template resolution order /books/template-languages/shared-model/template-resolution-order Performance, caching, deployment and go-live /books/performance-and-deployment Documenting a template's inputs /books/theme-repo/rendering/documenting-inputs What is yours and what is the platform's /books/start-here/building-on/yours-and-the-platforms Code deploys, content does not /books/performance-and-deployment/managing-environments/content-does-not-deploy Moving configuration between sites /books/performance-and-deployment/managing-environments/moving-configuration The APIs: REST, GraphQL and custom endpoints /books/apis Three worked emails /books/hooks/sending-email/worked-emails What the controller hands the template /books/theme-repo/rendering/rendering-a-record Relationships between records /books/content-types/custom-entity-types/relationships Global template variables /books/template-languages/shared-model/global-template-variables Porting a template set /books/template-languages/side-by-side/porting-a-template-set Fonts and third-party scripts /books/performance-and-deployment/making-pages-fast/fonts-and-third-party-scripts Create an input type for a design-token dropdown A select input type whose option keys are CSS classes and whose labels are what the author reads. Define it once, reuse it on every layout that offers the choice, and print the key straight into class="". /how-to/design-token-input-type Shaping the response with properties /books/apis/rest/properties Fields, groups and static elements /books/forms/building/elements Blogs and posts /books/content-types/built-in-content-types/blogs-and-posts Handover /books/performance-and-deployment/after-launch/handover Search fields: mapping areas into the index /books/search/indexing/search-fields Listing and detail templates /books/content-types/custom-entity-types/routes-and-templates