Dissection of a WordPress theme: Part 2

Apr 22, 2005 | Tags: , , , , , , | Written by Administrator

Web design is a notoriously tricky subject. Often we give up any thoughts of innovation when the process of realising them is such hard work. Part two of this WordPress dissection continues to try and explain the basic workings of the software, how this relates to the layout, and how anyone can personalise their blog.

The focus will be on finalising the basic layout from part one, and then finishing the header and footer sections. Both of these are important as they stylistically define a blog and act as visual focal points – do it well and people will want to read your blog, do it badly and they may not even bother.

Web designs

Websites are consistently at the mercy of numerous difficulties. They must be able to present information to people who run different software, on different platforms, in different languages, and with different levels of visual awareness.

In the early days of the web this was relatively easy. People did not expect much and were impressed just by the availability of a website. Layouts were chunky and appeared to be created by programmers. Most of them were.

Today the emphasis is on making a attractive site that is elegant and clean and works transparently of the content. WordPress has, to a large extent, achieved just that, and makes full use of the latest design methodologies. It is therefore important that any WordPress theme discussion attempts to retain this ‘standards conforming’ philosophy.

Accessibility and Google friends

Accessibility is a term used to describe the process of making a website accessible to those who may be viewing it on something other than a high resolution monitor, or who may even be visually impaired.

A key issue here relates to font size. We don’t want to design a theme with an impossibly small font, and neither do we want to prevent the chosen font being re-sized to suit personal preference.

A secondary issue regards Google. Most of us want our content to appear in Google’s pages, and there are a lot of things we can do to improve its ranking. One of the simplest is simply arranging our page such that content is delivered before menus and other non-content. Why? It seems that Google gives preference to data at the front of an HTML page.

Putting the content first also makes the website a better experience for non-graphical users. There are not many of these, but there are some.

Captain, we have a problem

So what does this have to do with the second part of the guide? My original plan was to cover the header, footer, and sidebar here, and finish the series with the content. Thirty minutes into writing part two and I realised my previous design was far from complete, and that it was going to take time to explain why.

Fortunately the problem was not a big one. In fact, I could easily have explained it as a design decision and skipped straight ahead. Instead, let's look at what I previously proposed:

Desired layout

This is a standard website design and worked perfectly until the content section became taller than the sidebar. This had a strange effect:

Actual layout

The content has wrapped around the sidebar! In itself this is not a big issue and is easily fixed, but it became apparent how unfinished the previous design was. It’s time to make amends.

Some statistics

Before we do that, I want to show some statistics from my own website.

Mozilla Firefox 43%
IE6 43%
Apple Safari 6%
Opera 3%
Others 5%

Taking into consideration that WordPress attracts more non-IE users, it's obvious that we must cater for many different browsers on several platforms.

Options

Variations on a common theme will be presented as options. These will change appearance or add extra functionality to the theme, and the intention is to cover a wider range of ideas without forcing a particular style.

An option will be presented as follows:
Option Option 1 – Some description

Help me to save time by reading these instructions!

If you are asking a question please read the FAQ to see if it has already been answered. All support questions should be directed to the support forum. Thanks!

Share This

Comments (page 8 of 8)

  1. John (author) :

    Oct 23, 2007 2:03 am

    The printed one is newer. They should both be reliable.

  2. author
    Cesco :

    Oct 22, 2007 7:36 pm

    Hi John,

    Thanks for this great tutorial. I bought the printable version of it and there are several differences with what's online ("Fluidity without the breakdown, notably"). Which should I rely on?

    Cesco

  3. John (author) :

    Jul 19, 2007 4:48 am

    Amanda, does this FAQ entry help?

  4. Amanda :

    Jul 13, 2007 7:46 pm

    I've managed to improve it a bit by fiddling with the percentages after reading another here comment on one of the other questions. It's not perfect because the sidebar doesn't sit flush right.

    Another strange thing is that the colour of the post headings changes half way down the page in IE - not in Firefox. Why would that be given that they're controlled by the same code? Very odd...

    Thanks again
    Amanda

  5. Amanda :

    Jul 13, 2007 7:31 pm

    Thankyou for a great tutorial. Beginning with that and no previous experience of CSS I've made the site I wanted. The only problem is when I checked it on IE and find that the sidebar is dropping down below the posts - it displays fine in Firefox.

    Can you tell me where I start looking for the problem?

    Amanda

  6. John (author) :

    Jul 6, 2007 8:02 pm

    Elear,

    You should give your header element the same width as your page:

    #header { width: 700px}

    It is also likely you will need to remove the left-padding from #headerimg. The same goes for the footer

  7. Elear :

    Jul 6, 2007 3:21 am

    hello!

    Thanks for the nice tutorial!

    Well, my site is not working completely. I think that I missed a part where to configure the approiate spacing or something in the content, because it is placing the posts not aligned with the header and footer

    Also, comment CSS is not working! :(
    Sorry my english!

    PD: http://futuroesplendor.mud.cl/capsulecorp

  8. Will :

    Jun 18, 2007 9:51 am

    This guide is what got me on the road to learning CSS. I am no designing websites commercially and fluent in CSS. Thanks for this fantastic resource - it has proved itself to be invaluable to me.

  9. John (author) :

    Apr 17, 2007 6:56 am

    Bryan, all I can suggest is to make the elements smaller and see if it starts working in IE. Sometimes with a percentage width, a fixed padding/margin can confuse IE so it thinks there isnt enough space and pushes elements out of the way.

Pings & Trackbacks

axlelabs.thischick.com, bardak.com.ru, blogging.typepad.com, cssquestions.wordpress.com, gailoverholt.com, isice.twbbs.org, lorelle.wordpress.com, mingus.tvu.ac.uk, photomatt.net, radioball.net, sector40.net, skoleweb.mrfylke.no, tekapo.com, theselfstarters.com, tyj.yutgaubartsei.com, vanus01.host.sk, wordpr.ectio.us, clydeshome.net, daveschalkboard.com, emilyrobbins.com, grantpalin.com, information-page.com, jou.ufl.edu, netlexfrance.com, noulakaz.net, ohisee.com, pixietail.com, shaghaghi.net, summerstorm.ca, whogivesfx.com, xxiaa.net

Leave a comment


XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

Help me to save time by reading these instructions!

If you are asking a question please read the FAQ to see if it has already been answered. All support questions should be directed to the support forum. Thanks!

Home | Software | Terms & Conditions | Sitemap | John Godley © 2008
Close
E-mail It