• I’ve been using MovableType for about 10 years. I’m finally making the switch to WP.

    My MT based blog is here. My WP sandbox blog is here.

    Some day, I might build a template that I am interested in sharing but I roll my own most of the time. I am very comfortable in CSS and html, less so with php/javascript.

    The Thematic template gets me most of the way to the design I want. I am beginning to make the needed changes to make it my own. I’m using a child template as recommended. I want to make changes to the meta data in the html <head> area. Thematic builds the <head> section using php functions.

    Assuming that I am never going to give this template to anyone else, what are the benefits of hunting down the appropriate functions in order to make the changes I want over simply coding the <head> section by hand?

    Specifically, I would like to use a Google fonts for body text. Because I am very comfortable with CSS I think I don’t want to involve installing WP plugins when I can just edit the head.php and the CSS and be done.

    So, let the education begin. Should I simply code up my own head.php, which is essentially what I’ve done in MovableType, or are there compelling reasons to use WP’s functions to build the head.php??

    Thank you in advance,
    Smittie

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Smittie

    (@smittie)

    After reading this thread, I am really wondering what the advantages are? I went through The Ultimate WordPress Theme Tutorial and I did learn some useful php/wordpress code to use in the <head> section. I also understand the value of codematically produced <head> sections in templates used by those who do not wish to code. I’m just not sure what the best approach for my needs is.

    Smittie

    I don’t think that there’s anything wrong with sticking the Google font code in the head. I’ve done it many many times. I usually do this, when working on client sites and when I know that it will never change. I’ve also inserted the google analytics code in there, typekit, meta tags, google verification code…. you name it. I’ve done it. ??

    Thread Starter Smittie

    (@smittie)

    Hey Christine, thanks for the reply.

    When you insert things into the head.php, is there a rhythm or reason as to where it should go from WordPress’s point of view? I understand the implications with regard to the browsers.

    Also, the best way to do that is to copy the head.php file into the child directory and edit it from there, correct?

    The best way is indeed in the header.php of the child theme.
    I haven’t really given it much thought as to where in the header the lines go. I try not too put too much crap in there of course. Just the necessary.

    Thread Starter Smittie

    (@smittie)

    So, I have to admit, I’m finding this a little frustrating. Based on The Thematic Guide there appears to be some advantage to putting additions to the <head> section in the function.php file instead of putting them directly into the head.php file. However, I can find no clear documentation on what those advantages are. There are seven function calls in the Thematic head.php file. Where are those functions defined? The same function names do not exist in the Thematic functions.php file. I’d like to be able to look at the function being called so that I can understand where it pulls the information from.

    I am new to WordPress and php. If the answers to these questions are obvious, I apologize for my ignorance. I’ll be happy to RTFM, if I can just find the FM.

    Smittie

    Thread Starter Smittie

    (@smittie)

    OK, maybe I found the FM: Theme Development.

    I’m reading it now.

    Smittie

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Head Tags: coded vs direct’ is closed to new replies.