Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #3341

    Hi there,

    I am successfully using child theming to make my modifications to the Display theme. However, if I want to have my own copy of style2.css, so my changes don’t change the original, I have two questions:

    1. does my child style2.css file have to be in a similar directory structure inside my child theme folder, or can it just be in the same child theme directory as my version of style.css?

    2. Does my style2.css need to IMPORT the original style2.css?

    Hope I’m making sense. Let me know if you need clarification.





    as far as I know you don’t need to use exactly the same structure but you must set a reference (@include, etc. in your child theme stylesheet). Have a look at this page:


    Exactly how to make mods to Child Theme Skin files hasn’t been exactly clear in codex and elsewhere. Hopefully this will help:

    1. Copy header.php to the Child folder

    2. Create a css file to hold your skin mods. e.g. For style1.css call it something like style1M.css

    3. Insert the style1M.css <link> statement in the header, immediately after the style1.css <link> statement (around line 36)

    That should do it.


    Thanks for the hint skane :)


    Not at all. So many people here are helping each other, it just seems like the thing to do.

    I consider my suggestion above a hack, since I haven’t seen it described in Codex. It’s working well for me with the Newscast theme.

    However, in an ideal world, I think the Child style.css file should be able to handle everything using @import url(style1.css); placed after the @import url(style.css). For example, it seems logical in a cascading world where the Child style.css should control everything that it would: 1. import and execute style.css, then 2. any mods to style.css, and then 3. import and execute style1.css, and then 4. any mods placed after that. However, the original header.php is executing style1.css (again?*) AFTER it processes the Child. *once during @import in the child and again because of the header <link> stmt.

    Maybe the WordPress developers have something to say about this?

Viewing 5 posts - 1 through 5 (of 5 total)

The topic ‘How to child theme skin files’ is closed to new replies.