Themes

WordPress Fundamentals

Chapter 5 · Themes

Everything written so far — Posts, Pages, blocks — has a home to live in visually, and that home is a theme. This chapter treats a theme deliberately as a black box: how to choose, install, and customize one, without yet opening it up to see how it actually works. That part is WordPress Intermediate/Advanced's own job, starting with its very first chapter.

What a Theme Actually Is (For Now, a Black Box)

A theme is a package of files controlling a site's visual appearance and layout — colors, typography, page structure, how a blog listing or a single post is arranged on screen. Crucially, a theme doesn't hold your content. Every Post and Page, per WordPress Fundamentals 3's own material, lives in the MySQL database, entirely separate from whichever theme happens to be active. Switching themes changes how that content looks, never what it actually is.

Choosing a Theme

Type	What to know
Free themes	Available directly from the official WordPress.org theme directory, searchable right inside the dashboard
Premium/paid themes	Sold through third-party marketplaces, often with more built-in design options and dedicated support
Block themes	Built specifically for the Full Site Editing capability previewed in WordPress Fundamentals 4 — headers, footers, and full page templates are all editable as blocks
Classic themes	Still very widely used — page structure is defined in PHP template files rather than editable blocks (the exact subject of WordPress Intermediate/Advanced's own opening chapters)

Before installing any theme, check

When it was last updated (an abandoned theme is a real security and compatibility risk, previewing WordPress Fundamentals 10's own maintenance material), its rating and number of active installs, and whether it's compatible with your current WordPress version.

Installing a Theme

From the dashboard: Appearance → Themes → Add New. From there you can search the official directory directly, or upload a theme's .zip file if it came from a premium marketplace. Installing a theme doesn't activate it — a separate "Activate" step actually switches the live site over to it, and only one theme can be active at a time.

Customizing a Theme

Appearance → Customize opens the Customizer — a live-preview editor for classic themes, showing changes on the actual site as you make them: site identity (logo, title, tagline), color schemes, menu assignment, and homepage settings (a static page vs. a stream of latest posts, directly connected to WordPress Fundamentals 3's own Posts-vs-Pages material).

Block themes replace this with the Site Editor

On a block theme, much of what the Customizer used to handle moves into the Site Editor instead — the same Full Site Editing capability WordPress Fundamentals 4 previewed, now applied to the whole site's structure rather than just individual post/page content. Which interface you see depends entirely on which type of theme is currently active.

Child Themes — Why They Matter (A Concept, Not Yet a How-To)

A child theme inherits all the styling and functionality of a "parent" theme, while letting you make your own customizations safely, in a separate place.

The real problem this solves

Directly editing a theme's own files is a genuine, common WordPress mistake: the next time that theme receives an official update, every one of those direct edits gets silently overwritten and lost. A child theme keeps customizations in a completely separate set of files that an update to the parent theme never touches — the safe way to customize anything beyond what the Customizer or Site Editor already exposes.

Deliberately left as a concept for now

This chapter stops at understanding why child themes exist. Actually building one — the real file structure, a style.css header declaring the parent theme, and the PHP needed to properly load the parent's own styles — is covered directly in WordPress Intermediate/Advanced's own opening chapter, which formally opens the black box this chapter deliberately left closed.

Hands-On Exercises

Exercise 1

A site owner switches their active theme from one design to a completely different one. Explain what happens to their existing blog posts, using this chapter's own material.

📄 View solution

Exercise 2

A developer directly edits a theme's own PHP files to add a custom feature. Weeks later, the theme author releases an update, and the custom feature disappears entirely. Explain exactly what happened and what should have been done instead.

📄 View solution

Exercise 3

Explain why a site's active theme being a "block theme" or a "classic theme" changes which customization interface a site owner actually sees.

📄 View solution

Chapter 5 Quick Reference

A theme controls appearance only — content lives separately in the database and survives any theme switch
Free (WordPress.org directory) vs. premium (marketplaces); block themes (Full Site Editing) vs. classic themes (PHP templates)
Check last-updated date, ratings, and active installs before installing any theme
Install via Appearance → Themes → Add New; installing ≠ activating
The Customizer (classic themes) or Site Editor (block themes) handle live customization
Child themes — safely customize without losing changes on the next parent-theme update; the how-to is deferred to WordPress Intermediate/Advanced's own opening chapter
Next chapter: Plugins