Exercise 3: Why a Real Production Theme Would Likely Be a Child Theme Instead — Possible Solution ==================================================================== WHAT A CHILD THEME OFFERS, PER WORDPRESS FUNDAMENTALS 5 ------------------------------ A child theme inherits all the styling and functionality of an established parent theme while letting customizations be made safely, in a separate place - meaning a huge amount of already-built, already-tested functionality (responsive layouts, accessibility considerations, cross-browser handling, and far more) comes "for free" from the parent theme, rather than needing to be built and tested from scratch. WHY THIS WOULD BE THE MORE PRACTICAL CHOICE IN A REAL PROJECT ------------------------------ Per this chapter's own closing tip-box, "a genuine production version of a theme like this would often be built as a child theme of an established base theme... rather than entirely from scratch." Building entirely from scratch - as this capstone does - means every single piece (styling, responsive behavior, accessibility, browser compatibility) has to be built and verified individually. A professional, production-focused project would rarely justify that cost when a well-established, already-mature parent theme could provide most of that groundwork, leaving only the genuinely custom pieces (the post type, the contact form, the specific design) to actually be built. WHY THIS CAPSTONE DELIBERATELY DOESN'T BUILD IT THAT WAY ------------------------------ Per this chapter, this capstone "builds from scratch deliberately, specifically to demonstrate every piece explicitly rather than to model the most efficient real-world starting point." If this capstone had been built as a child theme, several of the pieces this course spent nine chapters teaching (the theme file structure, header.php/ footer.php with wp_head()/wp_footer(), the full template hierarchy) would be inherited invisibly from the parent theme rather than shown explicitly - defeating the actual teaching goal of this capstone, which is to make every mechanism from every prior chapter directly, visibly present in one real project. WHY THIS DISTINCTION IS WORTH STATING EXPLICITLY, NOT LEFT IMPLICIT ------------------------------ Without this closing note, a learner might reasonably assume building entirely from scratch is simply how real WordPress themes are always built in practice - the honest scope note corrects that impression directly, distinguishing "the pedagogically clearest way to demonstrate every concept" from "the way a professional would actually approach this specific project," so the learner leaves with an accurate, not just complete, picture. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains what a child theme concretely offers per WordPress Fundamentals 5's own material, connects that benefit to why it would be the practical real-world choice, and explains precisely why this particular capstone's own teaching goal required building from scratch instead, using this chapter's own explicit reasoning.