Site Title Justification & Child Theme Question

  • seanptfrancis

    #49136

    Hello –

    I’ve searched for answers to these 2 questions, but couldn’t find any so apologies in advance if they have in fact been answered before.

    Q1. My site title is centered in the middle of the header image and looks fine. However, I was wondering if it were possible to left justify it and if so, how?

    Q2. I recently updated the theme to 2.2 which unfortunately messed up my fonts, colors and spacing. It’s taken me 4 days (don’t laugh) to put things back the way I like them. Now there’s version 2.3 to update to, but I don’t want to make the same mistake twice. All my customization is done through the GUI. I have not edited any underlying code, so I was wondering how I can protect my customizations and still upgrade? Is a child theme the answer and if so, how would you create one from a (customized) parent?

    Thanks for any help, tips or tricks.

    Admin

    Syahir Hakim

    #49138

    Q1. My site title is centered in the middle of the header image and looks fine. However, I was wondering if it were possible to left justify it and if so, how?

    Copy and paste the following code into Additional CSS section in the Customizer:

    .header_title, 
    .header_desc {
    	text-align: left;
    	padding-left: 15px;
    }
    

    In the future, we might add this as an option as quite a few users have asked about it in this forum.

    Q2. I recently updated the theme to 2.2 which unfortunately messed up my fonts, colors and spacing. It’s taken me 4 days (don’t laugh) to put things back the way I like them. Now there’s version 2.3 to update to, but I don’t want to make the same mistake twice. All my customization is done through the GUI. I have not edited any underlying code, so I was wondering how I can protect my customizations and still upgrade? Is a child theme the answer and if so, how would you create one from a (customized) parent?

    The big changes occurred moving from Graphene 1.* to Graphene 2.*, due to the changes that we had to make to the theme to make it relevant with today’s web technologies. In order to bring features like responsive layout, we had to dismantle the old CSS framework used in the theme and replace it with a modern one.

    This caused some issues for the theme’s users, particularly those who had customized the theme heavily by using custom CSS or child theme. In fact, that was the reason we held out for so long before introducing responsive layout into Graphene – we knew we couldn’t make it without disrupting some portions of the theme’s users.

    It’s now 2018, and users of the old Graphene were getting more and more disadvantaged due to the fact that the theme was stuck in the old framework. For example, Google had started penalising search ranking of websites that are not responsive back in 2015. Smartphones are causing images and icons in Graphene to look blurry. These issues and many others could not be easily solved with old technology.

    So we made the decision that we had to move on. If it’s any consolation, it might took you 4 days to adjust your site again after the update, but it took us half a year to bring you a modernised Graphene with tools and features that eliminates the disadvantages that the old Graphene had.

    Moving forward, future updates of the theme will not be anywhere nearly so disruptive since the major structural changes had already completed moving from 1.9.4.3 to 2.0. Therefore, you can continue making changes via the WordPress GUI as long as those are sufficient for your needs. If you run into any problem, you can always come here for support.

    seanptfrancis

    #49156

    Thank you so much for your reply. The left justification worked like a charm.

    Regarding the theme update, thanks for the explanation. I wasn’t complaining about the 4 days I spent changing things and I really appreciate all the work you put into making Graphene as good as it is. Thanks again and all the best!

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

You must be logged in to reply to this topic.