Search

Memory or timeout errors on a listing page /faq/question/memory-or-timeout-errors-on-a-listing-page Markup that differs by environment /books/theme-repo/page-edges/environment-markup Site data and feature flags /books/theme-repo/page-edges/site-data Images /books/performance-and-deployment/making-pages-fast/images Messages after a redirect /books/theme-repo/page-edges/flash-messages Robots and the sitemap /books/theme-repo/page-edges/robots-and-sitemap Roll back a page to an earlier revision Every save keeps the revision before it. Find the one that was right and send its id as activeRevision on the page: it is live again at once, with no new revision. Then base the next edit on it with originRevision, or the edit brings back what you rolled back. /how-to/roll-back-a-revision When a custom entity beats a page /books/content-types/custom-entity-types/custom-entities Share a partial between several page types Put the fragment in includes/, pass what it needs by name, and never let it read the page's record directly, because the record arrives under a different name on every page type. Document its inputs at the top. /how-to/share-a-partial Change one area of a page without touching the rest patchRevision copies the live revision and changes only the layout areas you name. Send originRevision, the layout area as areaContent(name), and activeRevision: true inside the patch: the change goes live in one request, and every other area, collections included, stays as it was. /how-to/change-one-area Sign-in with an external provider returns to an error page /faq/question/sign-in-with-an-external-provider-returns-to-an-error-page Where pages are composed: the decision tree /books/choosing-how-to-build/build-shape-decision/decision-tree Canonical URLs and structured data /books/theme-repo/page-edges/canonical-and-structured-data Move from server-rendered to hybrid without a rewrite A site whose public pages are rendered for every visitor because of one personal element can be moved to cached pages with fragments one element at a time, keeping every template it has. /how-to/server-rendered-to-hybrid Measure first /books/performance-and-deployment/making-pages-fast/measure-first Fetching once instead of per iteration /books/performance-and-deployment/making-pages-fast/fetch-once The cost of nesting /books/performance-and-deployment/making-pages-fast/cost-of-nesting Bundle size /books/performance-and-deployment/making-pages-fast/bundle-size Seed JavaScript state from a template without a second request Data the template already rendered belongs in the page, not in a second request. Encode it into a JSON script tag, parse it once at start-up, and keep per-visitor data out of cached pages. /how-to/seed-javascript-state-from-a-template Migrate a WordPress site's content to pages and blogs Read the posts and pages from WordPress's REST API, write them into a Core dna blog and pages through Core dna's, keep their dates and categories, and produce the redirect map as you go. /how-to/migrate-wordpress-content 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 The first load is huge but subsequent pages are fine /faq/question/the-first-load-is-huge-but-subsequent-pages-are-fine Create the layout /books/start-here/first-page-end-to-end/create-the-layout Add the areas and their input types /books/start-here/first-page-end-to-end/add-the-areas Render the areas in both engines /books/start-here/first-page-end-to-end/render-the-areas Nothing changed: the four checks /books/start-here/first-page-end-to-end/nothing-changed The three query-per-row shapes /books/performance-and-deployment/making-pages-fast/query-per-row The first visitor to a page waits noticeably longer than the second /faq/question/the-first-visitor-to-a-page-waits-noticeably-longer-than-the-second Fonts and third-party scripts /books/performance-and-deployment/making-pages-fast/fonts-and-third-party-scripts My layout does not appear in the picker when I create a page /faq/question/my-layout-does-not-appear-in-the-picker-when-i-create-a-page A partial shared between two page types sees different variables in each /faq/question/a-partial-shared-between-two-page-types-sees-different-variables-in-each Cut a bundle in half with dynamic imports Find the heavy library that most visits never use, load it only when it is needed, and measure what every page saved. /how-to/cut-a-bundle-with-dynamic-imports Set up a base template and extend it One base template holds the document, the head, the chrome and the script queue, and defines blocks. Every page-type template extends it and fills the blocks. Both engines do this the same way. /how-to/base-template-and-extend How-to library Task-shaped pages: a title that starts with a verb, the situation in a few lines, the steps, the working code in both engines, and why this way rather than another. Found from a search, done, and left. /how-to Fetch three entity types in one request with GraphQL A headless home page needs its navigation pages, the latest posts and the header menu. One POST to /cdna-api/graphql from your server returns all three with only the fields you render; this wraps the endpoint's rules in one function. /how-to/graphql-three-entity-types Diagnose "my change is not showing up" The most common question on any project, answered in the order the causes usually turn out to be true, with a marker in the page that settles the first one in seconds. /how-to/diagnose-my-change-is-not-showing-up Create your first layout and template, from the admin to the repo Deploy the template file first, create the layout that points at it in the admin, add the layout areas, then create a page that uses it. The admin only offers templates that already exist on the server. /how-to/first-layout-and-template Build a breadcrumb trail from a record's ancestors getAllParents() returns a page's ancestors from the root down. Label the root "Home" yourself, link the rest with getFullPath(), and build a post's or record's trail from its container instead. /how-to/breadcrumb-trail Port one template from Smarty to Twig Keep the file name, change the contents. Carry escaping across one for one, translate calls second, scope assignments third, then diff the rendered page before and after. Here is one template ported end to end. /how-to/port-smarty-to-twig Link to a record without hardcoding its URL Take a URL from the record with getFullPath(), never from a path typed into the template. Get the record from an author-picked area, from a query by a stable attribute, or from a route name for module pages. /how-to/link-to-a-record Decide between a custom field and a layout area Areas are for content an author composes on a record that has a layout; custom fields are for structured attributes on records that do not. Pages and posts take areas; people, menus, categories, tags and SEO settings take fields. /how-to/custom-field-or-area Call the REST API from the browser with the CSRF token A same-origin script sends the session cookie by itself; for a signed-in visitor the platform also wants the session's CSRF token on every write. Put _csrfToken in a meta tag, send it as X-Csrf-Token, and keep that page out of the cache. /how-to/call-the-rest-api-from-the-browser Add the platform's form scripts to a form layout Load js-forms.js and its stylesheet with the page's nonce, wrap the steps in a .coredna-js-form container, print the form's conditionals for js-forms-conditionals.js, add js-payment-element.js for a payment, and point the container at a result callback, so a failed submission shows its errors to the visitor. /how-to/add-the-form-scripts-to-a-layout Developer Documentation Dev Templates, APIs, jobs and module references for engineers building on core dna. /developer-docs Posts API Reference /developer-docs/api-reference/blogs/posts Post Comments API Reference /developer-docs/api-reference/blogs/post-comments Books API Reference /developer-docs/api-reference/books Common API Reference The records no single module owns: input types, layouts and their areas, layout categories, categories, global components and tags. 26 endpoints across six pages. /developer-docs/api-reference/common Languages and lookups API Reference /developer-docs/api-reference/common/lookups Question Comments API Reference /developer-docs/api-reference/faq/question-comments