Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Smashing WordPress

Smashing WordPress

Beyond the Blog
Turn WordPress into a product catalog or support hub without making updates and editors a headache.
by Thord Daniel Hedengren 2010 352 pages
3.76
247 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Build with WordPress as a publishing engine, not a ready-made blog.

Think beyond the default. The book’s central argument is that WordPress is a flexible publishing platform, not merely software for chronological blog posts. Themes control how material appears, plugins add capabilities, and WordPress’s content tools can support very different kinds of sites. The author points to editorial publications, corporate websites, and image-heavy projects as plausible uses, while acknowledging that WordPress is not the right choice for every job.

Start with a working base. The book assumes familiarity with HTML and CSS and some PHP. It focuses on the self-hosted WordPress available from WordPress.org, with examples grounded in the 3.3 era and this edition published in 2012. Its larger lesson is to understand the platform’s parts before building beyond its defaults.

Analysis

The distinction between a product and a platform is useful because it changes the first design question. Instead of asking which blog theme looks closest, a builder asks what content people create, how they find it, and who maintains it. That is a stronger starting point for any software project. Flexibility, though, is not proof of fit: a platform that can be adapted to a task may still require too much custom code or upkeep. The book’s most durable counsel is to evaluate the work the site must do before celebrating what the software can do.

Protect the core; put custom work in themes, plugins, and configuration.

Keep updates safe. WordPress core means the internal files that make the platform run. The book’s rule is not to edit those files, because upgrades can overwrite changes and custom edits can disrupt other parts of the system. Site-specific work belongs in the designated layers, especially the `wp-content` folder, with `wp-config.php` reserved for installation settings.

Use the right extension point. Themes supply templates and presentation; plugins extend site functionality; configuration sets installation behavior. A theme may use template tags to display a site title, or a plugin may add a new capability. The WordPress Codex, the platform’s documentation wiki in the book’s time, is presented as the reference for functions and implementation details. Treat core edits as a warning sign to reconsider the design.

Analysis

This is an example of separation of concerns serving as a maintenance strategy, not just a tidy coding preference. When platform code, design, and added behavior have clear boundaries, upgrades become less like surgery and more like replacing a component. The same principle appears in modular systems engineering: isolate the parts most likely to change. The boundary is not absolute, and configuration files can still take a site down when edited carelessly. The practical test is whether a change can survive a core update and remain understandable to the next person responsible for the site.

Use the Loop to decide which content appears, and where.

Understand the content engine. The Loop is the theme code that retrieves posts matching WordPress’s current request and displays them. A home page, category archive, and single-post page can use the same basic mechanism while returning different material. Inside the Loop, template tags output details such as a title, link, excerpt, or full text. A theme can keep this code in reusable template parts rather than repeating it across files.

Add queries deliberately. The book demonstrates separate queries for a featured story and category columns, then warns that extra loops can mean extra PHP work and database queries. Use the main query when it suffices, and use a separate query when the page genuinely needs another content set. Reset post data after a custom query so later template output refers to the right post.

Analysis

The Loop makes the page feel less like a fixed document and more like a view over a changing collection. That is a powerful mental model: the same content can be sorted, filtered, and presented differently without being rewritten. It also encourages builders to distinguish data selection from display. The tradeoff is that a page assembled from many queries can become difficult to reason about, and may burden a server. A useful design review asks both what the visitor needs to see and whether each query earns its place.

Turn products, recipes, and support questions into first-class content.

Model the material. A custom post type is a separate, post-like content type created for material such as books, recipes, or products. Custom taxonomies add distinct ways to classify that material. In the book’s recipe example, Recipes are a post type, Ingredients act like tags, and Dishes act like categories. In its product example, Books have their own archive and can be displayed with cover images and summaries.

Match structure to use. A support site can treat submitted problems as posts, then distinguish unresolved questions from documented solutions. The book also sketches a links directory and a job board built from WordPress content. Custom post types do not automatically appear in the ordinary post stream, so the theme must request and display them. Keep the content model available when changing themes by registering it outside the theme when possible.

Analysis

A good content model is a quiet form of user experience. Editors see familiar, separate work areas instead of one crowded post form, while visitors gain clearer paths through products, ingredients, or resolved questions. This is close to database normalization: distinct things should have structures that reflect their distinct roles. But more fields and categories are not automatically better. Every new type creates rules that editors must learn and administrators must preserve. Start with recurring differences in the work, not hypothetical future needs.

Use child themes to customize appearance without forfeiting parent updates.

Keep changes separate. A child theme is a theme that inherits from a parent theme and stores its own customizations separately. WordPress looks for a template file in the child theme first, then uses the parent’s version if none is supplied. This lets a designer change colors, add a page template, or replace one specific content layout without copying the entire parent theme.

Override only what matters. A parent theme update can then improve the base while leaving the child theme’s changes intact. The book also notes an important exception: both themes’ `functions.php` files load, so duplicate function names or conflicting behavior require care. If the child theme replaces nearly every template and accumulates extensive new functionality, it may have outgrown its purpose and be better treated as a separate theme.

Analysis

Child themes encode a valuable asymmetry: inherit what is stable, override what is distinctive. That is the same logic behind layered design systems, where a shared base supports many local expressions. The approach works best when the parent remains a dependable foundation. If the child must continually fight the parent’s assumptions, inheritance becomes hidden coupling rather than leverage. The book’s caution against excessive overrides is therefore important. Reuse saves effort only while the reused structure remains a genuine fit.

Keep lasting site features independent from the theme’s appearance.

Separate behavior from design. A plugin is the better home for functionality that should continue when a site changes themes. The book’s examples include custom post types, custom taxonomies, and shortcodes, which are small tags embedded in content that trigger programmed output. If a shortcode exists only in the old theme’s `functions.php`, changing themes can leave its raw tag visible in published posts.

Use theme code selectively. The book proposes a functionality plugin for portable features, while reserving `functions.php` for behavior tied to one design, such as registering that theme’s menus or widget areas. WordPress hooks are named points where code can attach to platform events or content processing. Hooks let plugins add behavior without editing core files, but the book warns that plugins can add database work and slow pages.

Analysis

Portability is a form of reversibility. A site that can change its visual identity without losing its content rules has more room to evolve, and that reduces the cost of future decisions. This distinction also resembles the separation between an application’s data model and its presentation layer. Still, portability has a cost: a large collection of plugins can make dependencies harder to track. The important question is not whether code belongs in a plugin by definition, but whether the feature has a life beyond the current design.

Make WordPress simpler for editors than it is for developers.

Design for the actual operator. The book urges builders to trim the administration interface for clients and colleagues. Limit permissions to what each user needs, remove irrelevant controls, avoid unnecessary plugins, and provide clear menus and widget areas. Custom fields can store useful details, but the default key-and-value interface may confuse less technical editors. A tailored meta box or a plugin with clearer input controls can make the same data safer to manage.

Make the workflow teachable. Page templates can give different sections distinct layouts, while posts can serve news and announcements. The author recommends supplying a short manual that explains the site’s own conventions, rather than expecting users to navigate general documentation. A good 404 page should also help visitors recover through search, useful links, recent content, or a way to report a broken path.

Analysis

This is a reminder that an admin screen is part of the product, even though visitors never see it. Interface design succeeds when the likely action is obvious and the cost of a mistake is low. Reducing controls can help, but hiding too much may remove useful flexibility or make the system brittle when requirements change. The strongest solution pairs a simplified interface with concise guidance and appropriate permissions. In other words, usability is not merely less clutter; it is a good match between the tool and the person doing the work.

Treat speed, backups, and security as design requirements.

Plan for failure. The book recommends keeping WordPress updated, using strong passwords, avoiding a predictable administrator account, limiting user privileges, and protecting administrative traffic with SSL where the host supports it. Backups must cover both the database, which stores content and settings, and `wp-content`, which holds uploads, themes, and plugins. A host’s backup service is useful, but the book argues for maintaining an independent copy as well.

Control the workload. Many plugins, repeated loops, and remote services can slow a page, especially when they each query a database or wait on another server. Caching can reduce repeated work. The Transients API is WordPress’s mechanism for storing temporary data with an expiration time, useful for content such as fetched RSS feeds. Measure the purpose of every addition, and test recovery before a move or major change.

Analysis

Reliability is often treated as an operational concern that can be postponed until launch. The book correctly folds it into construction: a site’s real design includes what happens when credentials are guessed, a host fails, or an external feed stalls. The two-part backup model is especially practical because database content and uploaded files fail in different ways. Performance advice also benefits from restraint. A plugin count alone says little; the relevant issue is what each plugin does, how often, and under what traffic conditions.

Choose WordPress by workflow fit, not by technical possibility.

Begin with the publishing job. The book sees WordPress as a strong option for text-centered editorial sites, simple company websites, and projects that benefit from an accessible publishing interface and extensions. Static Pages can hold durable information, while posts handle news. Custom content types can separate a catalogue, recipe collection, or knowledge base. RSS feeds and supported embeds can bring in outside material, while social buttons can help readers share published work.

Know the boundary. A small shop or digital-product sale may work with plugins and payment services, but a complex store deserves a careful comparison with dedicated commerce software. Community tools and forums can extend WordPress, yet the right platform depends on the project’s needs. The book’s recurring standard is practical: choose the simplest setup that gives editors the workflow and visitors the experience the site requires.

Analysis

The platform’s broad reach is both its appeal and its trap. Demonstrating that a job board or store can be assembled in WordPress does not establish that it is the least costly system to operate. A sound choice weighs initial development against future maintenance, editor training, performance, and migration risk. The book’s examples are most useful as prototypes for thinking, not universal prescriptions. They show how publishing primitives can be recombined, while leaving the builder responsible for deciding when a specialized tool is the more honest fit.

Analysis

The book’s most important contribution is not a catalogue of WordPress features. It is a way to think about the platform as a set of separable responsibilities. Content is stored and organized, themes determine presentation, plugins add durable behavior, and configuration controls the installation. The Loop connects the request to the material displayed. Once those boundaries are understood, the shift from blog to catalogue, knowledge base, or corporate site becomes less mysterious: the builder is designing a content model and workflow, not merely repainting a page.

That flexibility has a cost. A permissive system makes it easy to add content types, templates, widgets, and plugins, but each addition creates expectations for editors and maintenance obligations for developers. A custom field that saves time for the person who built the site may become a confusing task for the client. A plugin that produces a clever layout may introduce external dependencies or extra database work. The book repeatedly returns to the right counterweight: choose the narrowest tool that accomplishes the actual task, and place it where it can survive the changes it should survive.

Its examples also illuminate how technical structure shapes organizational behavior. Separate editorial areas for books or recipes tell contributors what belongs where. A restrained administration interface reduces accidental choices. A manual turns undocumented conventions into shared practice. These are not secondary details; they determine whether a site remains usable after its original developer leaves.

The material is historically situated. Its code, plugin recommendations, and platform assumptions reflect WordPress around version 3.3 and the web technologies of 2012. Readers should treat implementation snippets as artifacts of that era and verify current APIs, security practices, and compatibility before using them. The durable value lies in the architecture: preserve the core, model content deliberately, separate portable behavior from presentation, and judge success by how well the publishing system serves both its operators and its audience.

Summary in 30 Seconds
WordPress can power catalogs, recipe collections, and support hubs when content types and taxonomies match the material. Keep custom behavior in plugins and presentation in themes, so changing a design does not erase useful features. Child themes preserve customizations through parent updates. Simplify the admin workflow for editors, and plan for security, backups, and performance. The code examples reflect WordPress around 2012, so verify current APIs and practices.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.76 out of 5
Average of 247 ratings from Goodreads and Amazon.

Smashing WordPress receives mixed reviews, averaging 3.78 out of 5 stars. Readers praise its technical depth and usefulness for intermediate to advanced WordPress developers. The book covers theme and plugin development, customization, and security. Some appreciate its clear examples and code snippets, while others find the writing style challenging. Critics note outdated information and typos in code examples. Many readers recommend it as a valuable reference for those looking to extend WordPress functionality beyond basic blogging.

Your rating:
4.3
102 ratings
Want to read the full book?

Glossary

The Loop

Displays queried content

The Loop is the theme code that checks whether WordPress has content for the current request, iterates through matching posts, and outputs them. Template tags inside it can display titles, links, excerpts, full text, and other post details. Separate queries can support additional content blocks, but each should be used deliberately and post data should be reset when needed.

Template Hierarchy

Chooses a display template

The Template Hierarchy is WordPress’s system for selecting which theme file handles a request. It checks for a specific template, such as one for a category or individual post, then falls back through more general templates until it finds one, usually ending at index.php. Developers can use this order to customize particular views without creating a separate file for every page.

Child Theme

Extends a parent theme

A Child Theme is a separate theme that depends on a parent theme. WordPress uses a matching template from the child when present, otherwise it falls back to the parent. This lets a site preserve custom styles and selected template changes while updating the parent. Both themes’ functions.php files load, so function names and behavior must be managed carefully.

Custom Post Type

Creates a content category

A Custom Post Type is a post-like content type added alongside WordPress’s built-in posts and Pages. It gives a distinct kind of material, such as books, recipes, or products, its own editing area and can support selected features such as titles, excerpts, images, and comments. Themes need suitable templates or queries to display this content.

Custom Taxonomy

Adds classification terms

A Custom Taxonomy is an additional system for classifying content. Its terms can behave hierarchically, like categories, or nonhierarchically, like tags. A recipe site might use one taxonomy for ingredients and another for dish types. Taxonomy registration is often best kept in a plugin when the classifications must remain available after a theme change.

Action Hook

Runs code at an event

An Action Hook is a named point in WordPress execution where a theme or plugin can attach a function to run. For example, code can attach to a hook that runs while the page header or footer is assembled. Hooks allow developers to add behavior without modifying core files, and themes can define their own hooks for extension.

Functionality Plugin

Keeps features theme-independent

A Functionality Plugin is a site-specific plugin used to hold useful behavior that should persist when the site changes themes. The book suggests moving portable features such as shortcodes, custom post types, and custom taxonomies out of a theme’s functions.php. The theme can then focus on presentation, while the plugin continues providing the underlying behavior.

Transients API

Stores temporary cached data

The Transients API lets WordPress store temporary data with an expiration time. A theme or plugin can check for cached data, fetch fresh information when no valid copy exists, and save the result for later requests. The book uses RSS feed output as an example, since fetching and parsing remote feeds repeatedly can slow a site.

oEmbed

Embeds supported media URLs

oEmbed is a method for turning a URL from a supported media provider into embedded content. In the book’s WordPress examples, an editor can place a supported video or image URL in a post and let WordPress generate the embed, sized according to media settings. Support is limited to providers recognized by WordPress or added through an extension.

About the Author

Thord Daniel Hedengren is a Swedish web developer, designer, and author known for his expertise in WordPress. He has written multiple books on web development and content management systems, with a focus on WordPress. Hedengren's writing style is described as technical yet accessible, providing in-depth explanations and practical examples for developers of various skill levels. His work with Smashing Magazine, a popular web design and development resource, has contributed to his reputation in the field. Hedengren's books often cover advanced topics, making them particularly valuable for those looking to expand their WordPress skills beyond the basics.

Download PDF

To save this Smashing WordPress summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.31 MB     Pages: 16

Download EPUB

To read this Smashing WordPress summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.36 MB     Pages: 19
Want to read the full book?
Follow
Listen1 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
600,000+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...