Header Issue in Mobile View

Also, give this a try and see if it works –

background-size: cover;

Add this to your header image

Let me know if that works.

Yes anytime you customize a child theme’s css and update the css file, then everything will be overwritten. I always recommend saving your customizations at the bottom of your css file and transferring it to the newly updated file whenever there is an update.

You could also add a custom.css file to the theme and link to it from their style.css file which means future updates won’t effect it.

You can also add css code to your Genesis Theme Settings…..but if you do that, I’d recommend saving your css somewhere locally just in case you accidentally reset your settings.

A year ago I asked a few other developers within the Genesis community if this was a good idea, but most of them didn’t think it was necessary since child themes don’t get that many updates as the framework. I still think its a good idea to offer a way to have the css separate from the child theme since it makes it easy to track and separate what you’ve added.

Do any of the suggestions in my previous comment work, or would you prefer something different/better? I just want to get an idea of what people would want.

The way I’ve done it in the past is to use the “link” method, which would allow me to create a custom.css file and add in the updates within the file just as if I was using the style.css file. If you think this is a good idea, then I may create a quick tutorial on how to do this.

This is something you can easily do. Just simply create a css file (just copy the style.css file and rename it to custom.css).
Then add this to your original style.css file –

@import url("custom.css");

This is how you would link to your external css file (custom.css) from your original style.css. This method is actually safer than adding styles on your theme settings page. If you accidentally reset your settings, then all of the styles that you created will disappear, but if you do it in the way I suggested, the code will always be there and will never be overwritten since it’s a separate file.

It’s actually better to do it this way and NOT include a custom.css file with child themes. If we did include them, it would overwrite any changes you made to your own custom file. I think its better if you manually create the custom css to keep everything separate and untouchable from theme files.

For functions files, I would just organize and keep all of your addon codes in a particular place and transfer them to the newly updated functions file if there is ever an update to this particular file. Functions files aren’t really that big of an issue since not many things are updated. These files can easily be managed and there isn’t really a need to create an “external” functions file. I would just keep everything organized.

Yep that’s it.

For the functions file, thats just the way Genesis is setup, and what they recommend. The best I can do is create a tutorial on how to modify certain things like the header/logo, etc. Hopefully I’ll have these soon.