I put Los Primos aside today to focus on developing a Child Theme for this blog. It’s been a useful and challenging experience.

Creating a Child Theme is quite simple. It involves the creation of a new CSS file with the same @import css styles as the parent only you change the Theme Name to be Expound Child for instance. You’ll also get this mysterious Template Error if you don’t include a Template: (include exact name of css template without the .css suffix.). Like this:

Template: expound

@import url(‘..expound/css/expound.css’);

Then add whatever CSS changes you want. Chrome’s inspect element function comes in spectacularly handy during this process as you can change whatever you want live on the screen.

Messing with the various php files is interesting as well. You can simply clone the header.php file and make changes within your Child Theme folder but if you want to mess with the searchform.php for instance, I needed to change the original. I couldn’t figure out how to get WordPress to refer to the new searchform in my Child directory. All I wanted to do was change the word “Search” to “GO” so nothing really broke. It just took a while to realize all my changes to the Child’s searchform weren’t being recognized onscreen. The CSS changes nicely and predictably though!

Just spent some time fighting with the darn Los Primos navigation area. All I wanted to do was allow the wider bits of the sub-menu some more space. Christ! It has taken me all afternoon to figure out how to use width:auto and a min-width setting. BUT IT WORKS! HAH! You set width:auto then pick a minimum width for the element (links in this case), make sure you have padding on both the left and the right and account for that in the second min-width setting. Like this:

nav#top ul li a{

nav#top ul .sub-menu li a{
padding:0 10px;


Rob is a graphic design instructor and practicing designer/illustrator. He likes monsters.

Comments are now closed for this article.