Skip to main content

Laravel CMS Content Collections

Content manager

Structured content that stays reusable and searchable.

This page helps you decide when content should become a reusable record instead of copy inside a page section.

Collections are where repeatable records live before pages, widgets, search, SEO, package features, or API output reuse them.

Example: a resource record can appear in a library, campaign landing page, related-content widget, and sitemap without four copied versions.

Table

Sortable collection rows

Editors can scan status, owner, last update, and publish readiness before opening a record.

Status
Draft
Owner
Editor
Locale
EN
Media

Reusable assets with alt text

Media belongs to records and pages through explicit relationships, not hidden template paths.

  • Image variants
  • Alt text
  • Visibility
  • Usage trail
Taxonomy

Tags, categories, and facets

Structured classification supports listings, filters, related content, and SEO output.

Topic Audience Package
Locales

Translation readiness is visible

Teams can see what exists, what is stale, and which public pages still need localised copy.

English live French draft German missing
Reusable records Update once, reuse across pages. A collection record can power landing pages, detail pages, cards, search, feeds, and package widgets.
Example : Update once, reuse across pages.

A person profile can appear on an about page, a case study, an author byline, and a speaking-event listing without becoming four separate copies. That is the practical value of keeping repeatable content out of page markup.

Place records
Search and SEO Content stays structured enough to index. Titles, excerpts, media, taxonomy, dates, authors, and canonical URLs can stay in predictable fields.
Why this matters : Content stays structured enough to index.

Structured records give search, sitemap, Open Graph, related-content, and reporting packages something dependable to read. The frontend can still be custom, but the important content facts are not trapped inside a finished HTML blob.

Feature tour
Next steps

Next steps for content modeling.

LayoutBuilder Previous concept Review how LayoutBuilder places approved sections and records on pages. Continue Publishing Practical next step Follow a collection-backed change through preview, review, publish, and cache refresh. Continue Packages Related reference Use package guidance when collections feed blog, search, SEO, or discovery packages. Continue