pages vs. posts — two different kinds of rooms
WordPress has two primary content types, and understanding the difference saves a lot of confusion.
pages are static rooms. your About page, your Contact page, your Services page — these don’t change often, aren’t filed by date, and don’t show up in an RSS feed. they’re the permanent rooms of the house. you build them, you furnish them, and they mostly stay as they are.
posts are more like a bulletin board — or a regularly updated reading room. they’re time-stamped, filed by category and tag, show up in your blog feed, and are designed for content that accumulates over time. articles, updates, news, tutorials — all posts.
a common mistake: putting everything on one giant page instead of giving each thing its own room. a “Services” page with twelve services crammed onto it is like a house where the kitchen, bedroom, and office are all the same room. it works, but it’s exhausting to navigate — and Google notices.
how content is actually stored
all your content — every page, every post, every product, every form submission — lives in the database (the filing cabinet in the basement). WordPress retrieves the right files and assembles them into a page every time someone visits.
this means your content is separate from your design. you can completely change how a page looks by switching themes or editing the template, without touching the words and images in it. the furniture doesn’t care what color the walls are.
custom post types — rooms you build for a specific purpose
out of the box WordPress has pages and posts. but plugins (and developers) can register custom post types — purpose-built content rooms.
WooCommerce adds a Products room. a portfolio plugin adds a Portfolio room. an events plugin adds an Events room. each one has its own structure, its own fields, its own way of being displayed.
if your site has a portfolio, a shop, an events calendar, or a directory, those are almost certainly custom post types — separate content rooms that a plugin built and manages.
a note on content and backups
because all your content lives in the database, a good backup strategy always includes the database — not just the files. backing up the theme and plugins without the database is like photographing the wallpaper but not the furniture. if something goes wrong, you’d get the empty house back but lose everything in it.
related: the database — where all your content actually lives. plugins — the contractors who add new rooms. back to the neighborhood guide.
