What’s the difference between a Post and a Page?

Screen shot of a page that uses a filter to show a list of only one type of post.
Screenshot of our Portfolio page, which uses a filter to show a list of only one type of post.

In the r/WordPress subreddit user named only_sort_by_new asked a great question about how to use pages and posts (lightly edited)

Help deciding on if something is a Post/Page and how to organize a sauce review site with Categories/Tags?

Currently working on my first site which is suggesting and reviewing sauces. I love trying any type of new sauces, so wanted to start writing some blog posts and reviewing specific sauces.

The issue is, that I am very confused and stuck on how to layout a site like this. Is each type of sauce a Page and then when I write a blog Post mentioning the sauce, I just tag that sauce? I imagine I will make many blog posts that reference a specific sauce… that is why I am thinking that I might need a Page (not a Post) for each sauce/sauce type. And every blog post mentioning that sauce (via Tags) will pop up on that sauce page.

So would the above breakdown above be Pages that use Parent/Child structure? Or are those actually Posts too and I just use Categories in a hierarchical way? Or need to utilize tags for this to work?

Reddit user u/only_sort_by_new

When it comes to the front end of a website neither WordPress nor Google makes much of a distinction between posts and pages.

Instead the best way to look at them is…

  • pages are typically accessed through navigation. So think of menus, “learn more” links, and callout “card” links on main pages.
  • pages are also used for permanent “behind the scenes” pages like quiz results, thank you pages, shopping cart and other checkout pages.
  • posts are more often found through searches, incidental links in text, and especially in lists. (The “blog” page is a list. So are “related posts.”)
  • the biggest difference is that posts are typically organized by categories and tags rather than menus.

While we don’t typically think of e-commerce products as “posts” it can be a good idea to think of posts the way we typically look at products in e-commerce. You browse catalogs and search for products instead of navigating through menus for them. There might be menu items for categories of things, but adding every item in your shop to the navigation menu would be waaay too unwieldy for the average shopper.

Think about posts the same way. Typically you’ll have just a handful of navigable pages, while you might have hundreds of posts.

In the original poster’s particular case it makes more sense (and is probably easier) to create each sauce as a post and use categories and tags to help find them on their site.

They can then choose from a ton of “posts” or “loop” plugins, blocks, modules, and widgets to display the right sauces on more structured pages.

Here’s a simple example would be our own Portfolio page. It’s a permanent page available through the navigation menu, with a few paragraphs of explanations, and then a “posts” module a filter set to choose (query) only posts marked in the “Portfolio” category. We go a step further on our Website Updates, Repairs, And Upgrades page with a different “posts” module with filters that limit results to posts in the Portfolio category and the “rebuilt website” tag.

Bottom line, though, is that pages are meant to be navigated to with menus and buttons; posts are meant to be listed, filtered, searched for, or “mentioned” in in-text links.

FacebooktwitterredditpinterestlinkedinmailFacebooktwitterredditpinterestlinkedinmail
Posted in , tagged with: #

David Innes, RealBasics.com

I've been building and maintaining websites since 1997 and building and supporting similar hypertext-driven software since 1987. I've done maintenance, support, and maintenance for physical and digital systems since 1981. And no, I still haven't seen it all but by now I usually know where to look. More about David Innes...