2

[Anonymous]

Anonymous

#17457

Ken,

So what if I already have like 100 tweaks in my css file? Can I just use that file as my child css file, and make future tweaks to that one?

What would be be best way to “transition” into a child theme?

Thanks.

[Syahir Hakim]

Syahir Hakim

#17458

Quote:

So what if I already have like 100 tweaks in my css file? Can I just use that file as my child css file, and make future tweaks to that one?

Your child theme’s style.css file should only contain the CSS tweaks, and not the theme’s entire original style.css file. I’ve seen many people copy the theme’s entire style.css file into their child theme, and apart from being unnecessary, the results are a mess.

You can probably use some kind of diff software to easily find the changes that you’ve made, and the put those into the child theme.

[Anonymous]

Anonymous

#17459

lol… I was really hoping you weren’t going to say that.

Sounds good, though. I understand the importance of keeping things simple, clean, and organized when it comes to code.

Maybe Dreamweaver CS3 has this option. I’ll check it out.

[Kenneth John Odle]

Kenneth John Odle

#17460

This is how I handled it: https://forum.graphene-theme.com/graphene-support/activating-child-theme-and-moving-over-parent-css-changes

Ken

[Anonymous]

Anonymous

#17461

Yeah…. my css file has 8,955 lines of code in it… yikes!!

Looks like I need to run to the store for a re-fill of Big Red and Doritos…. gonna be a loooooooooooooong night!!

Thanks Ken. This is pretty much how I figured I would have to do it.