Try creating a custom menu. I hope you are creating child theme for all of your clients – otherwise your customisations will be over-written the next time the client upgrades WordPress.
Hi Esmi,
I hope you don’t mind me picking your knowledge. Usually what we do is copy twenty ten, rename the folder to twentyten2, rename the style.css “theme name” to twentyten2.( we do not put Template: twentyten”
Now, i understand from reading this: http://codex.wordpress.org/Child_Themes
What we would need to do. I guess what I’m failing to understand is if I’m going to change the header.php, page.php, footer.php, and in some cases we have to change a lot more to create very custom designs.
What is the benefit of using a child theme versus just doing what we are doing. Any advice would be great as I have seen your extensive knowledge being displayed on this forum, which makes you a great asset to all of us. =)
-x
Providing you’re not changing every single theme file, a child theme still gives you the option of picking up new features in the parent theme with minimal work on your part. Post formats, for example. However, I guess it boils down to how much customisation you’re carrying out. The more extensive the changes, the less you stand to benefit from the child theme route as opposed to creating a new standalone theme.
oh, btw, yes, the custom menu is a great idea. The only drawback is that if a users adds a sub page, then they have to modify the custom menu as well.
Then again, we can’t always get what we want. =)
You could try ticking the “Automatically add new top-level pages” box associated with the custom menu but I appreciate that it could be a two-edged sword.
well, we do offer what we call banner design websites where were only focus on the header and then everything else falls under the typical twenty ten layout. Taking your advice we will use child theme there because I under your point completely.
