next-landing-page-demo

Use for existing content collections in the DatoCMS landing page demo starter that feed current routes and sections but are not layout, docs, or section wiring: blog posts, authors, tags, testimonials, pricing tiers, changelog entries, and legal pages. Covers post, author, tag, testimonial, pricing_tier, change_log, and legal_page records; /posts, /posts/[slug], /posts/author/[slug], /posts/tag/[slug], /legal/[slug], /changelog/[slug], PostExcerpt, and section fragments that link these records. Do not use for shared layout, docs pages, new section components, new route-backed types, preview mapping, or generic DatoCMS imports unless the request is tied to these starter records.

Use for documentation-area work in the DatoCMS landing page demo starter: documentation home, documentation pages, docs tree structure, docs sidebar, highlighted docs pages, docs home footer text, docs page Structured Text rendering, docs metadata, and /docs routes. Handles Documentation Home, Documentation Page, app/[locale]/(docs-layout)/**, components/DocumentationSidebarItem/**, components/FeaturedDocumentationPages/**, components/DatoStructuredText/**, QuoteBlock, and docs code/quote rendering. Do not use for regular marketing page sections, shared header/footer/layout, blog/pricing/testimonial/changelog content records, new non-docs routes, or generic DatoCMS schema work.

Use when changing shared site layout behavior in the DatoCMS landing page demo starter, even if the user does not say layout: header, navigation bar, menu items, dropdown menus, logo, accent color, theme color, top notification bar, footer logo, footer subtitle, footer legal links, social media links, language selector, and fields on the Layout singleton that affect shared shell surfaces. Handles app/[locale]/(common-layout)/query.graphql, app/[locale]/query.graphql, components/Header/**, components/Footer/**, and components/CustomColor/**. Do not use for page body sections, docs pages or docs sidebar, blog/content records, new route-backed pages, preview links, SEO route mapping, or generic DatoCMS schema work.

Use for route-level infrastructure in the DatoCMS landing page demo starter: adding or changing record-backed routes, static params, metadata, draft/live preview wrappers, Web Previews URL mapping, SEO-analysis route mapping, and route-aware cache/draft behavior. Covers app/[locale]/(common-layout)/**, app/[locale]/(docs-layout)/**, components/WithRealTimeUpdates/**, app/api/draft/preview-links/route.tsx, app/api/seoAnalysis/route.tsx, route query.graphql/meta.ts/page.tsx/Content.tsx/RealTime.tsx files, and optional staticParams.graphql files. Do not use for ordinary page section edits, shared layout content, docs content edits, existing content record changes, or generic Next.js routing outside this starter.

Use for regular marketing page section work in the DatoCMS landing page demo starter, especially requests to add, remove, reorder, restyle, or wire page sections on Page.records through Page.sections. Trigger on natural requests such as changing hero variants like split image, right image, background image, or gradient, moving a section on a page, or showing a changelog teaser. Covers Hero, Feature List, Brands, Video, Detail, Testimonials, Pricing, Featured Posts, Team, FAQ, Stats, About Intro, All Posts, Redirect, and Changelog section blocks plus their display variants. Handles app/[locale]/(common-layout)/[slug]/query.graphql, app/[locale]/(common-layout)/[slug]/Content.tsx, and components/blocksWithVariants/** fragments/renderers. Do not use for shared header/footer/navigation/theme layout, docs pages/sidebar, existing content record maintenance, route/preview/SEO mapping, or generic DatoCMS schema work.