Structured content, localisation & export — found from sitemap — Prismic

Cited by

Facts read from this source

• Content modeling definition Report an error

  “Content modeling is the process of converting page designs into structured fields.”

• Content structures Report an error

  “Prismic provides four main structures to model your content: fields, page types, slices, and custom types.”

• Page types SEO uid default Report an error

  “A page type includes search engine optimization (SEO) and unique identifier (UID) fields by default.”

• Reusable type limit Report an error

  “Reusable type: There is no limit to how many pages of this type can be published. For example, a product or generic page.”

• Single type limit Report an error

  “Single type: Only one page of this type can be published. For example, a homepage.”

• Type builder and cli Report an error

  “Page types are created using the Type Builder, a tool for building by hand, or the Prismic CLI, a tool for AI agents.”

• Cli pull command Report an error

  “npx prismic pull”

• Slices definition Report an error

  “Slices are sections of a page — like a block of text, a hero, or a call to action. They are modeled using a collection of fields.”

• Slices per page type control Report an error

  “Developers have control over which slices are available to content writers. For example, a homepage might allow a Hero slice, while a blog post might allow a Quote slice. When needed, slices can be made available to multiple page types.”

• Custom types definition Report an error

  “Custom types represent content that isn’t a page. For example, website settings, navigation menus, and blog categories are modeled using custom types. Pages can reference and display content from custom types as needed.”

• Custom types slices discouraged Report an error

  “Slices are intended for page types and should be avoided in custom types.”

• Field change add behavior Report an error

  “Adding a field: The new field appears with an empty default value.”

• Field change rename behavior Report an error

  “Renaming a field: If the API ID is changed, existing content is not transferred. The renamed field appears with an empty default value.”

• Field change label rename recommended Report an error

  “If you need to rename a field, we recommend updating the field’s label while keeping its API ID. The field’s existing content will be retained”

• Content API model change timing Report an error

  “The Content API will not reflect the content model changes until at least one page is published or archived.”

• Recommended homepage model Report an error

  “For a website’s homepage, use a Single page type named Homepage with the route /. Content writers can only create one homepage, you can build homepage-only slices, and the page is fetched with getSingle().”

• Recommended reusable page model Report an error

  “For general website pages, use a Repeatable page type named Page with the route /:uid. Content writers can create unlimited pages, you can build slices available to any page, and pages are fetched with getByUID().”

• Supported frameworks Report an error

  “Learn how to customize a page file in the Next.js, Nuxt, or SvelteKit guide.”

Scores citing this record

• The Head of Content Structured content, localisation & export
• The Data Protection Officer Structured content, localisation & export
• The Localisation Lead Structured content, localisation & export
• The Localisation Lead Publishing, distribution & integrations
• The Skeptic Structured content, localisation & export
• The SME Marketer Structured content, localisation & export
• The Web Engineer Structured content, localisation & export
• The Web Engineer Publishing, distribution & integrations