WordPress themes supply the design, templates, and features that shape a site. When a theme update arrives, direct edits to its PHP or CSS files can disappear, while a child theme keeps those changes separate and lets the parent theme continue working without interference.
A child theme is a small companion theme that inherits the parent theme’s layout and adds selected changes. It is useful on a fresh WordPress installation, including a site still showing the default “Hello world!” post, because you can develop safely and build a recognisable site without rewriting an entire theme.
A parent theme provides the complete visual design and underlying structure. A child theme inherits that foundation, then overrides only the files or functions you need. This separation is the central idea behind safe WordPress customisation. Your posts, media, and settings stay in the database and are unaffected by this separation.
Small changes often contain large consequences. Editing the parent’s header, menu, logo, colours, or footer can break after an update and may affect every page. Keeping your work in a child theme limits that risk and makes changes easier to review, transfer, and remove.
Use a child theme when you need a custom design, extra menu location, small PHP adjustment, or reliable template override. For a completely different layout, a purpose-built theme or custom development may be clearer, but a child theme is ideal for extending an existing WordPress design.
Start with a backup of the site files and database, then make changes on a local copy or private staging URL. Your live domain should remain available to customers while you test menus, forms, checkout, and mobile layouts. WordPress Site Health and the debug log can reveal problems before launch.
Confirm the domain and hosting arrangements before launch. Australian commercial sites often use a .com.au domain, whose eligibility is governed by ACMA rules; check the current requirements instead of assuming any Australian registration qualifies. A provider offering local support during Australian Eastern Standard Time can also simplify troubleshooting for small businesses.
Keep the development setup tidy: one child-theme folder, version control if you use it, and a note of every copied file. Write visible copy in Australian English, using forms such as “customise”, “organisation”, and “licence” for nouns, and set dates as DD/MM/YYYY where that matches local expectations.
Open Appearance > Themes on the WordPress dashboard and identify the active parent theme, then look in wp-content/themes for its folder name. Create a new folder beside it using a clear slug ending in -child, such as my-site-child. The folder name, not the displayed theme name, is the important reference.
Create a style.css file inside the folder and add the required theme headers. This example uses placeholders that must be changed before activation:
/*
Theme Name: My Site Child
Description: Customisations for My Site.
Author: Your Name
Version: 1.0.0
Template: parent-theme-folder
Text Domain: my-site-child
*/
The Template value must exactly match the parent theme’s folder slug, for example twentytwentyfive, while Text Domain should match the child theme slug. Upload the folder with cPanel, an FTP client, SFTP, or your local development tool, then refresh Appearance > Themes so WordPress can detect it.
Put custom CSS in the child theme’s style.css, but ensure that file loads after the parent stylesheet. A small functions.php can register the stylesheet with the correct dependency:
<?php
function my_site_child_styles() {
wp_enqueue_style(
'my-site-child',
get_stylesheet_uri(),
array( 'parent-style' ),
wp_get_theme()->get( 'Version' )
);
}
add_action( 'wp_enqueue_scripts', 'my_site_child_styles' );
The dependency name parent-style is common, but it is not universal. Check the parent theme’s functions.php and replace it with the actual registered handle. Correct load order lets your selectors override the parent without relying on !important. If the parent already loads the child stylesheet, omit the extra enqueue.
To change markup, copy only the needed template, such as header.php, footer.php, front-page.php, single.php, page.php, or 404.php, from the parent into the child. WordPress checks the child folder first through its template hierarchy. For a block-based parent, adapt the approach with theme.json and block-template files instead of assuming every classic template applies.
The child theme’s functions.php is the right place for small additions, hooks, and filters. For example, this code registers a new footer menu that the parent does not provide:
<?php
add_action( 'after_setup_theme', 'my_site_child_setup' );
function my_site_child_setup() {
register_nav_menus(
array(
'footer-utility' => __( 'Footer utility menu', 'my-site-child' ),
)
);
}
The translation string uses the child theme’s Text Domain, so add matching translation files if the site has more than one language. After uploading the code, assign the menu under Appearance > Menus. Similar child functions can adjust excerpts, query results, or admin screens without touching the parent.
Do not copy the parent’s entire functions.php into the child and then edit it. Duplicated function names can cause a fatal PHP error, and future parent improvements will be harder to reconcile. Prefer a documented hook, a filter, or a function that removes and replaces the parent callback when replacement is genuinely required.
Run a functional pass across the home page, posts, pages, search results, menus, forms, 404 page, and any WooCommerce checkout. Test with the parent theme updated, open the site on a phone and desktop, and use keyboard navigation. Run php -l on functions.php to catch PHP syntax errors before uploading.
Local timing matters in a national campaign. Sydney, Melbourne, and Adelaide observe daylight saving, while Brisbane, Perth, and Darwin do not, so scheduled posts and opening hours can appear wrong when a single time is used. Store the intended Australian Eastern Time, label the time zone, and check the date format beside each time.
Test performance on mobile connections used from Sydney through to Perth and Darwin, where conditions can differ widely. A friendly phrase such as “No worries” may suit some Australian small-business brands, but keep form labels and error messages direct. Prices should normally appear in Australian dollars with GST included where the business is GST-registered.
Australian businesses may also have obligations under the Privacy Act 1988 and Spam Act 2003, especially when collecting contact details or sending email campaigns. Check consent, unsubscribe, privacy notice, and security practices, and have local legal or compliance advice reviewed where the site handles sensitive information.
When the files are ready, go to Appearance > Themes, select the child theme, and activate it. WordPress will continue using the parent theme as its foundation. Visit the site immediately, inspect the page source, and confirm that the active theme is the child rather than only its parent. If the default installation post remains, delete or repurpose it from Posts before publishing.
Keep backups, update the parent theme and WordPress core regularly, and give the child style.css a new version number whenever you release a meaningful change. Test updates on staging first. Record any parent files you have overridden, because a major parent release may alter the markup your copied template expects.
| Feature | Parent theme | Child theme |
|---|---|---|
| Main role | Supplies the original design, templates, and functions | Stores custom styles, templates, and extensions |
| Editing | Usually maintained by the theme vendor | Controlled by you |
| Update risk | Direct edits may be replaced | Customisations remain separate |
| Best suited to | Core presentation and layout | Durable brand and feature changes |
| File structure | Existing theme folder | Separate folder containing style.css and optional files |