القائمة
App Router structure, React components, client vs server, and rendering patterns in kickstart-next.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | next-app |
| description | App Router structure, React components, client vs server, and rendering patterns in kickstart-next. |
getPage("/") and passes the result to the default import from @/components/Page."use client"). It initializes live preview in useEffect, subscribes to ContentstackLivePreview.onEntryChange, and refetches via getPage(path) when the URL path changes.Page (import Page from "@/components/Page"). The function implementing it is named ContentDisplay inside the file; treat the public name as Page when wiring props.next/image for assets, sanitized rich HTML via isomorphic-dompurify and dangerouslySetInnerHTML, and modular blocks with VB_EmptyBlockParentClass for empty Visual Builder state.page?.$ / block $ attributes onto DOM nodes so Live Preview can bind fields.next/image for remote images. Remote hostnames must stay allowed in next.config.mjs (images.remotePatterns and optional env hostname).@/* maps to the repo root per tsconfig.json (e.g. @/lib/contentstack, @/components/Page).PR checklist and severity guidance for kickstart-next contributions.
Contentstack Delivery SDK, live preview, getPage, env overrides, and content model alignment for kickstart-next.
Local setup, Contentstack seeding, env vars, CI expectations, and PR ownership for kickstart-next.
Next.js, Tailwind v4, PostCSS, package scripts, and image optimization configuration for kickstart-next.
Test layout and policy for kickstart-next—currently no automated tests; credentials and CI context.
TypeScript compiler options, ESLint setup, and Contentstack entry typing conventions for kickstart-next.