The Dashboard & Core Concepts

WordPress Fundamentals

Chapter 3 · The Dashboard & Core Concepts

With WordPress installed, this chapter covers the two things every later chapter assumes you already know: how to find your way around the admin dashboard, and the single most important content-model distinction in all of WordPress — Posts versus Pages.

A Tour of the Admin Dashboard

Logging in lands you on wp-admin — the dashboard's home screen, with a left-hand sidebar that stays consistent across every screen in WordPress:

Sidebar item	What it's for
Posts	Chronological content — covered in depth below
Media	Every uploaded image, video, and document — covered fully in WordPress Fundamentals 7
Pages	Static, standalone content — also covered below
Comments	Reader comments awaiting moderation — covered in WordPress Fundamentals 9
Appearance	Themes, menus, widgets — covered in WordPress Fundamentals 5 and 7
Plugins	Installed and available plugins — covered in WordPress Fundamentals 6
Users	Accounts and their roles — covered in WordPress Fundamentals 8
Settings	Site-wide configuration — general settings, permalinks, discussion rules

The dashboard home screen itself shows an "At a Glance" summary (post/page/comment counts), recent activity, and a Quick Draft box for jotting down a post idea without leaving the home screen.

Posts vs. Pages — The Distinction Everything Else Depends On

Posts are chronological content — blog entries, news updates, anything meant to be read in a reverse-chronological stream and organized by category or tag. They're what feeds an RSS feed and what a typical "blog" listing page shows.

Pages are static, standalone content with no inherent date-sensitivity — an About page, a Contact page, a Privacy Policy. Pages can be organized hierarchically (a parent page with child pages beneath it) and have no categories or tags by default.

Posts	Pages
Chronological, date-driven	Static, not date-driven
Organized via categories and tags	Organized hierarchically (parent/child)
Included in the site's RSS feed	Not included in the RSS feed
Example: a blog entry, a news update	Example: About, Contact, Privacy Policy

A technical detail worth knowing now

Posts and Pages aren't stored in two separate systems — they live in the exact same underlying database table, distinguished by a single column that records which "post type" each row is. WordPress Intermediate/Advanced 4 shows that this same mechanism is exactly what lets a developer define an entirely new, custom content category beyond just these two — a portfolio item, a product, a testimonial — using the identical underlying system.

Which One Should You Use?

A quick decision guide

Ask: is this content tied to a specific point in time, meant to appear in a chronological stream? Use a Post. Is it standalone, timeless, and meant to always be reachable the same way (like a fixed page in a site's main navigation)? Use a Page. Getting this wrong doesn't break anything technically, but it does mean content shows up in the wrong place — a Contact page accidentally published as a Post would show up in the blog feed alongside articles, which is rarely what anyone actually wants.

Post & Page Statuses

Both Posts and Pages share the same set of statuses:

Draft — saved but not visible to visitors
Pending Review — submitted by a contributor, awaiting approval (relevant once WordPress Fundamentals 8 covers roles)
Scheduled — set to publish automatically at a future date/time
Published — live and publicly visible
Private — published, but visible only to logged-in users with sufficient permission

Hands-On Exercises

Exercise 1

A site owner publishes their "Contact Us" information as a Post instead of a Page. Explain what would go visibly wrong as a result, using this chapter's own material.

📄 View solution

Exercise 2

Explain what this chapter means by saying Posts and Pages are "the same underlying system," and why that detail matters for understanding what a custom post type will turn out to be.

📄 View solution

Exercise 3

Explain the difference between a "Scheduled" and a "Private" post status, and describe a realistic situation where each one would be the right choice.

📄 View solution

Chapter 3 Quick Reference

The dashboard sidebar (Posts, Media, Pages, Comments, Appearance, Plugins, Users, Settings) stays consistent across every screen
Posts — chronological, categorized/tagged, feed into RSS (blog entries, news)
Pages — static, hierarchical, no categories/tags by default (About, Contact)
Posts and Pages share the same underlying database table — a detail that directly explains custom post types later
Shared statuses: Draft, Pending Review, Scheduled, Published, Private
Next chapter: The Block Editor (Gutenberg), In Depth