"WordPress" is one name attached to two genuinely different things, running on top of a stack this site has already covered in real depth from three separate directions. This chapter sorts out both — what you're actually about to learn, and what it's actually built on — before any dashboard tour begins.

WordPress.org vs. WordPress.com — Two Very Different Things Behind One Name

WordPress.org is free, open-source software — a program you install on your own web hosting, that you fully own and control. WordPress.com is a commercial hosted service, run by a company called Automattic, built using that same open-source software but wrapped in its own hosting, its own rules, and its own tiered pricing. Same underlying name, same underlying code — genuinely different products.

Why WordPress's Market Share Actually Matters

That scale has real, practical consequences worth knowing before you invest time learning it:

• An enormous plugin and theme ecosystem — tens of thousands of free and paid options covering almost any feature a site might need
• A huge base of documentation and community support — a problem you hit has very likely already been solved and written up publicly
• A genuinely marketable, employable skill — WordPress site management and development are real, in-demand job categories, not a purely academic exercise

The Stack Underneath — LAMP, and Three Courses Already on This Site

WordPress isn't a mysterious black box — it's a PHP application, storing its content in a MySQL (or MariaDB) database, typically served by Apache or Nginx on Linux. That's the classic LAMP stack (Linux, Apache, MySQL, PHP), and this site has already covered every layer of it, separately, in real depth.

What This Course Covers

Installation and initial setup, the dashboard and its core concepts, the Block Editor, themes, plugins, media and content organization, user roles, comments, and ongoing maintenance — everything a site owner genuinely needs, in the order it's actually needed. WordPress Intermediate/Advanced picks up from there with real PHP development: custom themes, custom post types, plugin development, and security hardening.

Hands-On Exercises

WordPress Fundamentals 1 named the LAMP stack WordPress runs on without asking you to build any of it yourself. This chapter is the one moment in this course where that stack becomes directly visible — not because you need to build it, but because knowing what's happening underneath makes every setting in the next few chapters make sense rather than feel arbitrary.

Hosting Requirements

Any host advertising WordPress support needs to provide, at minimum: a current PHP version, a MySQL or MariaDB database, and enough disk space for WordPress core plus whatever media and plugins accumulate over time. HTTPS support is effectively mandatory today, not optional — covered in full technical depth in HTTPS/TLS Fundamentals, and specifically for a Debian-hosted setup, in Setting Up a Web Server on Debian's own Let's Encrypt chapter.

One-Click Installers — The Common Path

Most hosting providers offer a one-click WordPress installer (Softaculous is a common example) built into their own control panel. It handles creating the MySQL database, downloading WordPress, and running the setup wizard automatically — for the overwhelming majority of site owners, this is genuinely the right choice, not a shortcut to feel guilty about.

The Manual Install — What Actually Happens Underneath

Understanding the manual process is worth doing once, even if you'll use a one-click installer afterward — it demystifies exactly what that installer is automating for you.

1. Create a MySQL database and a database user with privileges on it — the same fundamental operation covered in MySQL Installation & Administration
2. Download the WordPress software and upload its files to your hosting
3. Visit the site in a browser — WordPress detects there's no configuration yet and launches its own famous "five-minute install" wizard
4. Enter the database connection details when prompted, then choose a site title, an admin username, and an admin password

wp-config.php At a Glance

This single file, generated during installation, is WordPress's own core configuration — the first file WordPress reads on every single page load, before anything else happens.

define( 'DB_NAME', 'wordpress_db' );
define( 'DB_USER', 'wp_user' );
define( 'DB_PASSWORD', 'a-strong-password' );
define( 'DB_HOST', 'localhost' );

$table_prefix = 'wp_';

define( 'WP_DEBUG', false );

• DB_NAME / DB_USER / DB_PASSWORD / DB_HOST — the database connection details, the exact information a manual install prompts for
• Authentication unique keys and salts — long random strings (generated automatically, not shown above) that make WordPress's own login cookies harder to forge
• $table_prefix — every WordPress database table starts with this prefix (wp_ by default); changing it away from the default is a small, genuine hardening step, revisited properly in WordPress Intermediate/Advanced's own security chapter
• WP_DEBUG — toggles PHP error/warning output; left true accidentally on a live site can leak technical details to visitors, so this should always be false once a site is genuinely live

An Initial Security Checklist

Hands-On Exercises

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:

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.

Which One Should You Use?

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

Every Post and Page from WordPress Fundamentals 3 is actually written using this chapter's own subject: the Block Editor, nicknamed "Gutenberg" after the inventor of the printing press. This chapter goes past "click here to add text" into how the editor is actually structured, and two features — patterns and reusable blocks — that look similar on the surface but work in genuinely different ways.

What Gutenberg Actually Is

The Block Editor became WordPress's own default editor in WordPress 5.0 (2018), replacing the older "Classic Editor" — a single large text box closer to a traditional word processor.

Blocks — The Fundamental Unit

Everything in the content area is a block — a paragraph, a heading, an image, a list, a quote, a button, a columns layout. Each block carries its own settings and toolbar, and blocks can be nested inside one another (a Columns block, for example, contains multiple Column blocks, each of which can hold any other block inside it).

• Inserting a block — the "+" inserter, or typing / followed by a block name to search the block library directly from the keyboard
• Rearranging blocks — drag handles, or the up/down arrows in each block's own toolbar
• Block-specific settings — the right-hand sidebar shows settings specific to whichever block is currently selected, separate from the "Document" tab covering post-level settings (visibility, publish date, categories, featured image)

Patterns — Ready-Made Block Arrangements

A pattern is a pre-designed group of blocks — a "hero section" combining a heading, paragraph, and button in a specific layout, for example — inserted as a single starting point rather than assembled block by block from scratch.

Reusable Blocks — A Genuinely Different Thing, Despite Looking Similar

A reusable block (in newer WordPress versions, sometimes labeled a "synced pattern") is also a saved group of blocks — but with one critical difference from an ordinary pattern: editing a reusable block updates it everywhere it's used, simultaneously. A pattern, once inserted, becomes an ordinary, independent set of blocks you can freely edit without affecting anything else; a reusable block stays permanently linked across every page it appears on.

A First Look at Full Site Editing

Modern WordPress themes built specifically for it — "block themes" — extend the Block Editor beyond just Post and Page content into the site's own header, footer, and overall template structure, a capability known as Full Site Editing (FSE). This is a genuinely newer, still-evolving part of WordPress, and many widely-used themes are still "classic" themes where FSE doesn't fully apply.

Hands-On Exercises

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

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).

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.

Hands-On Exercises

Themes handled appearance in WordPress Fundamentals 5. This chapter covers the other half of "extending WordPress without touching its core files" — plugins, which add or change functionality rather than looks. Like themes, plugins are treated here as a trusted black box you install and use; WordPress Intermediate/Advanced's own plugin-development chapter is the one that builds one from scratch.

What a Plugin Actually Is

A plugin is PHP code that extends or modifies what WordPress can do — a contact form, an SEO toolkit, a security scanner — without ever touching WordPress's own core files directly. Plugins do this by hooking into specific points in WordPress's own execution, through a mechanism called actions and filters. This chapter treats that mechanism as a black box for now; WordPress Intermediate/Advanced 5 opens it up in full, framing it as the single most important WordPress-specific concept for a developer — and explicitly building, from scratch, the kind of tool this chapter only ever installs as a finished product.

Finding & Vetting a Plugin

Like themes, plugins come from the official WordPress.org directory (searchable directly in the dashboard) or from premium marketplaces. Unlike a theme, though, a bad plugin choice can genuinely break site functionality or open a real security hole — vetting matters more here, not less.

Installing, Activating — and a Real Difference From Themes

From the dashboard: Plugins → Add New to search the directory, or upload a .zip file directly. As with themes, installing and activating are two separate steps.

Plugin Conflicts — A Real, Common Problem

Because multiple plugins run simultaneously, two plugins occasionally modify the same thing in incompatible ways — producing a broken page, a fatal error, or unexpected behavior with no obvious cause.

Essential Plugin Categories

An Honest Caveat: Plugin Bloat

Hands-On Exercises

Posts and Pages hold your content; themes and plugins shape what surrounds it. This chapter covers what ties everything together — the media you upload, how posts get organized for browsing, and the menus and small content blocks that make a site actually navigable.

The Media Library

Every image, video, and document uploaded to a site lands in the Media Library (Media → Library), a central place to browse, search, and reuse anything already uploaded rather than uploading duplicates.

• Alt text — a written description attached to each image, read aloud by screen readers and shown if an image fails to load; genuinely important for accessibility, not an optional metadata field
• Automatically generated image sizes — WordPress creates several resized versions of every uploaded image (commonly thumbnail, medium, large, and the original full size) so the right size can be used in different contexts without manual resizing
• Featured image — one image chosen to represent a Post, used in blog listings, social-media link previews, and anywhere a theme displays a post's own thumbnail

Categories vs. Tags — A Distinction Worth Getting Right

Both organize Posts specifically — per WordPress Fundamentals 3's own compare table, Pages don't use either by default — but they solve genuinely different organizational problems.

Navigation Menus

Appearance → Menus lets you build a navigation structure by adding Pages, Posts, Categories, or custom links, then dragging them into the order and nesting you want (nested items become dropdown submenus in most themes).

Widgets

Widgets are small, self-contained content blocks placed into designated areas a theme provides — commonly a sidebar or a footer — things like a search box, a list of recent posts, a category list, or custom text. In modern WordPress, the Widgets screen itself is built using the same block system introduced in WordPress Fundamentals 4, rather than a separate, older widget interface.

Hands-On Exercises

WordPress Fundamentals 3's own "Pending Review" status was left unexplained — a status that only makes sense once more than one kind of user exists. This chapter introduces exactly that: the role system controlling who can do what on a WordPress site, presented here purely as dashboard behavior. WordPress Intermediate/Advanced 8 revisits every one of these same roles and shows they have real, enforceable teeth in actual PHP code, not just a label in a dropdown.

Why Roles Exist

Any site with more than one person touching content needs different levels of trust — a guest writer shouldn't be able to change site-wide settings, and a content manager shouldn't necessarily be able to create new user accounts. WordPress solves this with five built-in roles, each bundling together a different set of permissions.

The Five Default Roles

Roles Are Really Just Named Bundles of Capabilities

Underneath the role names, WordPress actually checks individual, granular capabilities — publish_posts, edit_others_posts, manage_options, and dozens more — not the role label itself. "Editor" is simply the name WordPress gives to one specific, pre-assembled bundle of these capabilities.

Assigning Roles

Users → Add New creates an account with a chosen role from the start; Users → All Users → Edit changes an existing user's role. By default, a WordPress user holds exactly one role at a time — though plugins exist that allow finer-grained, custom capability combinations beyond the five defaults.

Choosing the Right Role — A Practical Guide

Hands-On Exercises

WordPress Fundamentals 8's own Subscriber role — an account with no content-creation ability at all — finally has an obvious purpose here: letting a reader comment under a real account rather than anonymously. This chapter covers how WordPress's own built-in comment system works, how to keep it usable despite spam, and the real trade-offs behind common moderation choices.

How Comments Work

A comment form appears beneath Posts by default (Pages can allow comments too, but typically don't by default, matching WordPress Fundamentals 3's own pattern of Pages behaving differently from Posts). Whether comments are open at all — site-wide or per individual post — is controlled from Settings → Discussion.

Discussion Settings — The Real Trade-Offs

Comment Statuses

Comments move through their own set of statuses, echoing the Post statuses from WordPress Fundamentals 3:

• Pending — awaiting moderator approval, not yet publicly visible
• Approved — live and publicly visible
• Spam — flagged as spam, hidden from visitors, kept temporarily in case of a false positive
• Trash — deleted, permanently removed after a set period

Spam — A Genuinely Large Practical Problem

Any public comment form on the internet attracts automated spam almost immediately — WordPress's own popularity, per WordPress Fundamentals 1's own market-share material, makes it a particularly common target for spam tooling built specifically around it.

Engagement — Beyond Just Moderation

A comment section only builds genuine community if someone is actually responding — replying to real comments, not just filtering out spam, is what turns a comment form from a liability into an actual asset. Some sites deliberately choose a third-party comment system (Disqus is a common example) instead of, or alongside, WordPress's own native comments, trading some of WordPress's own direct control for that platform's own spam-filtering and social features — a real option worth knowing exists, even though this course focuses on the native, built-in system.

Hands-On Exercises

A WordPress site is never really "finished" — it's an ongoing responsibility, not a one-time build. This closing chapter covers what keeps a site healthy after launch: updates, backups, and safe ways to test changes before they touch the live site.

Updates — Three Separate Layers

Safe Update Practice

• Back up before any major update — covered in full below
• Read the changelog for anything described as a "breaking change" before updating a heavily-customized site
• Update one thing at a time when troubleshooting becomes necessary — directly echoing WordPress Fundamentals 6's own plugin-conflict isolation technique
• Test on staging first, covered below, for anything beyond a routine minor update

Backup Strategy

A real WordPress backup needs two genuinely separate things, tracing directly back to WordPress Fundamentals 1's own LAMP-stack material:

Staging Sites

A staging site is a private, non-public copy of the live site used to test updates and changes safely before they ever touch the real, live version visitors see. Many hosts (particularly managed WordPress hosts, per WordPress Fundamentals 2's own hosting-type material) offer one-click staging environments built for exactly this purpose.

WordPress Fundamentals — Where This Course Leaves You

Ten chapters have covered everything a site owner genuinely needs: installation, the dashboard, the Block Editor, themes, plugins, media and organization, users and roles, comments, and now ongoing maintenance — all without writing a single line of PHP. WordPress Intermediate/Advanced picks up exactly where the black boxes in this course were deliberately left closed — theme anatomy, the template hierarchy, plugin development, and real, code-level security — starting with the exact theme structure WordPress Fundamentals 5 only ever installed as a finished product.

Hands-On Exercises