Stop hard-coding your team page
A collection is a small database your client edits without touching a database. Here's why structured content beats a folder of one-off pages.
Team members, case studies, blog posts, FAQ entries — built as one-off page-builder pages, every edit means opening the canvas and rebuilding the layout by hand. It works for a handful of items, and then someone adds a new team member and formats their card slightly differently, and nothing lines up anymore.
A collection replaces that with a schema: title, photo, a couple of text fields, whatever the content actually needs. An editor fills in a form instead of a canvas, and the site renders every entry consistently, laid out as cards, a blog list or a changelog timeline depending on what fits.
This blog is a collection, and so is the changelog next to it — same underlying structure, two different templates. Adding a new post is filling in one form, not rebuilding a page from scratch.