Ask most people what a website builder's "blog" feature is for, and they'll say exactly what you'd expect: writing blog posts. Fair enough, that's what it says on the tin. But if you've ever needed a running list of anything else, a menu, a portfolio, a staff page, you've probably assumed that meant a separate tool, or a developer, or a plugin nobody wants to babysit.
You don't need any of that. The same tool that runs a blog runs all of those, because "blog" was never really the feature. The real feature is called a Collection, and the blog is just the one Collection every Cantrip website starts with.
Here's the plain version: a Collection is anywhere you'd repeat the same shape of thing more than once. A blog post has a title, a date, a body, maybe some tags. A menu item has a name, a description, a price. A finished job has a title, some photos, maybe a client quote. Different content, same underlying idea: one record, then another just like it, then another.
Cantrip ships quick-start presets for the obvious ones (Product, Blog Post, Employee, Testimonial), but you're not stuck with those. Go to your website's Collections page, click "New Collection," and name it whatever your business actually calls the thing: Menu, Portfolio, Projects, Team, Press. You decide whether each entry gets its own page or just shows up in a list. Turn on dates if timing matters, add an author if more than one person is posting, enable tags if you want visitors to filter. If you're selling one item at a time, you can even hook up Stripe payments right on the entry. There's also a setting that lets an entry link out somewhere else entirely, handy for a press mention, a downloadable menu PDF, or a job listing hosted off your site.
Compare that to doing this on WordPress. A custom post type there means installing a plugin, one that can quietly break or vanish the moment you deactivate it, or writing actual PHP into your theme's functions.php file. Neither is a "quick edit" for someone who signed up for a website builder specifically to avoid touching code. On Cantrip it's a form. Name it, check a few boxes, done.
One real limit here: a Collection doesn't build itself. You're still typing in each menu item or portfolio piece one at a time, same as you would a blog post. Nothing scrapes your old site and populates it for you. What you're saving isn't typing, it's the part where you'd otherwise need someone with a dev environment just to make "Menu" a thing your website understands in the first place.
If you've only ever touched the one Collection Cantrip gives you by default, it's worth a five-minute look. A personal chef with a rotating weekly menu, a contractor with a growing list of finished jobs, a photographer who wants a real portfolio instead of a plain gallery section: none of that needs a second tool. It's the same feature you're already using, just named for what you're actually building.