CMS collection, explained
Think of a collection as a spreadsheet with a design attached. The collection is the sheet, the fields are the columns and each item is a row. Change a row and every place that shows it updates.
Each item starts with a name and a slug, and you add the fields you need: plain text, rich text, images, dates, switches, options, links and references to other collections.
Collections keep content and layout apart. An editor can publish a new case study by filling in a form, and the design stays the same. That is the main reason teams move repeating content out of static pages.
Decide what deserves a collection before you build. Anything that repeats and grows, like posts, jobs or locations, is a good fit. A one-off page usually is not. Site plans also limit collections and items, so check the current numbers.



