Last night around 10:15 decided to head out for dinner, and somewhat randomly picked the Cuban restaurant Guantanamera because it was nearby. Sat down in a booth near the bar, facing the band, and ordered some mojitos. Over the din of the other diners I thought “hey this house band isn’t half bad.”

Within a few minutes of listening it became very apparent that beyond “not half bad” they were actually really remarkable. What a treat! Ordered a steak and sank in, letting the music (and mojito) flow over me. A half hour later a lady from one of the front tables got up to sing with the band — which isn’t always a good thing. They started on The Man I Love and it was sublime. The song started out as a ballad but then they kicked it up to a fast afro-Cuban beat, and the singer scatted over the beats for a good 4-5 minutes. It turns out it was Janis Siegel of the Manhattan Transfer! I felt particularly fortunate as I had been bummed to miss the Manhattan Transfer show at the Montréal Jazz Festival in June, but here, of all the most random places, was one of my favorite members performing at a small family joint in Midtown West.

Janis sat down after one song but a string of similarly talented musicians came in and out of the band until the restaurant started to close down. I didn’t recognize any of them but the music was so good.

There was a recording device above the band that was collected by a fellow who I caught up with outside the restaurant as he was hailing a taxi. His name was Paul Siegel and he’s the co-president of Hudson Music which is a music education group (with a website powered by WordPress). I learned the percussionist leader of the house band was Pedro Martínez and Paul follows and records him several times a week at different venues. Apparently Guantanamera is a long-time musician hang-out where even folks like Eric Clapton sat in with the band.

Only in New York.

On the new Chic & Geek website (no relation to Chic Meets Geek events) I was invited to do a “Questionnaire de Proust” style interview which has just been published in French. Lots of little tidbits that I’ve never talked about before. (Translation here.)

The heading structure of your pages is one of the very important aspects of on-page SEO. It defines which parts of your content are important, and how they're interconnected. Because they have different goals, a single post needs another heading structure than your blog's homepage or your category archives. This post intends to give you the basic pointers to get your heading structure right for those three different cases.

If you've ever heard of this new kid on the block called HTML5, or maybe even consider yourself an expert on it, please note that this post still treats headings in the HTML4 / XHTML1 way of using headings. I'll briefly talk about headings in HTML5 in the end, it's a whole 'nother ball game!

This post will cover:

1. 5 basic principles about headings
2. The headings for your homepage
   1. The issue of full posts on archive pages
3. Heading structure for your single posts / single pages
4. Structure of headings for your category / tag / taxonomy pages
5. Headings and HTML5
6. Conclusion: re-think your blog's headers

5 basic principles about headings

Let's get these things straight before we do anything about our heading structure:

1. The most important heading on the page should be the H1.
2. There is usually only one H1 on any page.
3. Sub-headings should be H2's, sub-sub-headings should be H3's, etc.
4. Each heading should contain valuable keywords, if not, it's a wasted heading.
5. In longer pieces of content, a heading is what helps a reader skip to the parts that they find interesting.

Based on headings, there are tools out there that can, and will, make an outline for your content. If you were to make an outline for this article, it would look like this:

• [h1] The heading structure for your blog
  • [h2] 5 basic principles about headings
  • [h2] The headings for your homepage
    • [h3] The issue of full posts on archive pages
  • [h2] Heading structure for your single posts / single pages
  • [h2] Structure of headings for your category / tag / taxonomy pages
  • [h2] Headings and HTML5
  • [h2] Conclusion: re-think your blog's headers

The most widely known, and probably also the easiest, tool capable of doing this is the W3 Validator.

The headings for your homepage

So while we can (and will) discuss some specifics in the comments, your homepage should probably have a structure that looks like this:

• H1: Blog's name
• H2: Your blog's tagline, if it's "keyword-rich"; if not, all your recent posts should have an H2.
• H3: Your recent posts, or, if those have an H2, this could be used for somewhat older posts.
• H4: related content in the sidebar, like the heading of an "about" widget.
• H5: Unrelated headings in your sidebar, footer, etc.

As you can see, I differentiate between "related" widgets and unrelated widgets. It's no use at all to have an H3 heading saying "Our Sponsors". An H4 heading saying "About this SEO blog" could be useful though, if "SEO blog" is what you want to rank for.

The issue of full posts on archive pages

Maybe you've seen it, maybe you didn't yet, but this sort of heading structure creates a problem. If you're displaying full posts on your front page, your sub headings would be H2's, just like your post titles. That's wrong, of course, and a good example of why we should be separating our content and markup a bit more then we're doing now, but that's not an easy fix. Basically, if you're displaying a post on an archive, category, tag or home page, each H2 should become an H3, H3 should become H4, etc.

No code samples yet, but my mind is working on this now, so it might come soon.

Heading structure for your single posts / single pages

This one is simple:

• H1: post / page title
• H2's and H3's: subheadings and sub-subheadings
• H4: your blog's name, and possibly related widgets
• H5: same as above: sidebars etc.

Makes sense right? The most important line on the page is the post or page title, second come the subheadings. Your blog title still has some value because, if the post is good, people will search later on for "Yoast WordPress SEO", for instance.

Structure of headings for your category / tag / taxonomy pages

If you actually want your category and tag pages to rank, meaning you've given them some unique content and are making them interesting for people, the heading structure should basically be the same as the homepage, with this difference:

• H1: category / tag title
• H2's: post titles
• H3: blog's name
• Rest: repeat from homepage.

Headings and HTML5

In HTML5 the entire method of dealing with headings changes, and while it's a bit harder to grasp for people at first, the new system makes a lot more sense for content management systems. In short: headings and heading structures are section specific there, where section could be any part of a page. It would take too long to explain here, but if you're interested, read the header section of Mark Pilgrims excellent Dive into html5.

Truth be told, Mark doesn't talk about how search engines deal with HTML5 headers yet. In all honesty: I couldn't tell you yet. Simply a case of "not enough data to tell".

Conclusion: re-think your blog's headers

Now it's time for you to take some action. Go and use the W3 Validator now to check your blog's outline. If you've read an understood all the above, you should now be able to determine whether your theme is doing a good job. If you're using a premium theme or a theme that you downloaded from WordPress.org, I'd love for you to share your results in the comments!

The heading structure for your blog is a post from Joost de Valk's Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Lorelle VanFossen has published a recap of her Mind Blowing WordPress Plugins session given on August 29th at OpenCamp in Addison, TX.

To Lorelle, “a mind blowing WordPress Plugin is one that breaks the rules. It is unique and original in its implementation, and pushes WordPress. It might not be a Plugin that everyone must have on their site. It might not be a Plugin that even interests you. What these will do is to get you to look at the incredible diversity of Plugins available.”

Her recap not only briefly covers the topics discussed during her session, but she also lists all of the plugins that were featured, and that list is well worth exploring. Even if you think your blog couldn’t possibly use any more plugins, you might find something that you (or rather your blog) just can’t live without.

I really enjoyed attending WordCamps in Houston, Savannah, and Salt Lake City the past few weeks. You can always find upcoming WordCamps here, and I’m currently planning on attending Jerusalem (this Sunday), Portland (September 18-19), and Philippines (October 2). I’m looking forward to meeting more of the WordPress community and also answering your questions in the Town Hall sessions.

If one theme sneak peek wasn’t enough for you to drool over this week, here’s a second one to help keep your mouth watering. Glider will feature a simple and modern design, and will sport some awesome javascript effects. The theme will offer a great solution for those looking to create a personal website complete with blog and portfolio functionality.

On a side note, those chomping at the bit to get their hands on our upcoming shortcodes collection can rest easy. Shortcode development is going great, and you can expect their release very soon!

Not too long ago, Aaron Brazell published an interview with Copybloggers, Brian Clark where he explains the reasons for why he left DIY Themes. In that interview, there was no mention of StudioPress or Brian Gardner in relation to the future for Brian Clark. Fast forward to today and if you take a look at the footer on StudioPress.com, you’ll see the following:

© Copyright 2010 Copyblogger Media LLC · StudioPress™ is a trademark of Copyblogger Media LLC

Interesting to say the least. While I don’t know any of the details involving the deal that has gone down, the trademark of StudioPress is now owned by Copyblogger Media LLC which leads me to believe that either some of the assets, the entire company, or a majority of the company has been sold to Brian Clark. Just like you, I’ll have to sit back and wait for the official word on the details involving the deal but it would not surprise me at all if Brian Gardner has sold the company to start a new venture. Brian just seems like the type of guy that has his hands in all sorts of cookie jars and is always experimenting with ideas.

Let the speculation fly.

*Update* – StudioPress has published an official post announcing details of the merger..

Also noteworthy is that the company was NOT sold, but rather merged with other companies to form a new company.

Related posts:

1. An Inside Glance At StudioPress
2. I’m Going To Boston

This is a story (the short version) of my personal journey to becoming an author. Thank you to everyone in the WordPress community that has helped make this happen by allowing me to be a part of the community over the last few years.

The early years

As I was growing up in smalltown Alabama, I always wanted to be a writer. From about the time I could hold a crayon, I was writing something. Writing on the walls. The kitchen table. Occasionally, on paper. From what my parents tell me, I could do this quite well at about the age of 3.

During my pre-teen years, I wanted to follow in my father’s footsteps and write songs, so music and lyrics were my first introduction to how beautiful language could be.

Eventually, I outgrew my songwriting phase. Be glad I did. The world certainly doesn’t need any more boy-band pop songs. I figured I could offer something of a little more substance to the world.

High school

In high school, I had the most wonderful English teacher. She was one of those teachers that understood that literacy is not just about basic reading and writing skills. Literature. Technology. Music. Film. Those are the things that matter. Don’t get me wrong. We still had to do the boring high school English class stuff. But, she opened my mind to the world outside of the small town I was living in.

At some point during my senior year I realized that I wanted to write. I mean really write. It was the first time I’d ever put “write a book” on my list of life goals.

College

I graduated from Auburn University in 2007 with a B.A. in English and a concentration in creative writing and journalism.

When I began college, I didn’t plan on having a degree in English. I was in software engineering. Then I was in hotel and restaurant management. Then I was in software engineering again. Like many other college students, I bounced around majors a few times. It was tough finding something that was both enjoyable and challenging.

Despite protests from friends and a few from my family, I decided to take the plunge and declare myself as an English major. What I found was something that I loved. How could anyone not love reading 20+ books a semester? I had the time of my life exploring ethnographic studies, novels, and even the Bible as literature.

Each professor impacted my life in some way. Each class allowed me to explore other cultures. Each friend I got to know, helped shape me.

By the time I graduated, I had narrowed my list of life goals down to a few things. At the top of that list: Write something that has an impact on someone’s life.

At some point during college, I also started learning HTML, CSS, PHP, and WordPress.

After college

Harsh realization that life is not all roses and peaches.

…Time spent wandering the globe…

I moved back to Alabama last year because I wanted to get back to my roots. I wanted to engulf myself in the white-trash, trailer-park, tobacco-chewing culture that I hadn’t been a part of in so long.

The plan: Observe the culture. Write.

I could give you at least 100 reasons why I haven’t finished a novel yet, but I won’t. There’s no point in trying to justify losing sight of my goal.

I also spent some more time playing around with WordPress during this phase of my life. I suppose that time could’ve been spent working on the great Southern American novel.

An opportunity

A few months ago, I received an email about collaborating on a WordPress plugin development book for Wrox, a company devoted to publishing books “by programmers for programmers.”

At first, I was a bit hesitant to take on any extra WordPress projects. It also meant that I wouldn’t be able to apply for teaching jobs this school year, which was one of my goals for 2010. And, it wasn’t quite what I had in mind when I put “write a book” on my list of life goals.

However, it was an opportunity to write about something I’m passionate about.

The book

We have a great team of WordPress minds melding for what will be an awesome WordPress plugin development book. Brad Williams, Ozh Richard, and I are the writers. We’ve also picked up Andrew Nacin as our WordPress technical editor.

As a sidenote to this: I’m convinced that Andrew is actually a super-advanced robot that has been programmed to do nothing other than write awesome WordPress code. And, I’m happy to have him on the team.

I don’t want to get into too many technical details about the book yet. I do want to say that it will be a great resource for professional plugin development. We will put everything we have into making this the best book on creating plugins available for WordPress.

For me, this book announcement is mostly about sharing my personal journey to this point. I am thankful that Wrox, Brad, and Ozh are giving me an opportunity to realize one of my lifelong dreams. And, I hope that all my readers will come along on this journey with me (and buy the book when it’s published).

I was reading an article on Sitepoint about custom write panels the other day when I got heavily annoyed. The direct reason for this was one of their code examples and the authors apparent incomplete knowledge of the WordPress API's most basic functions and constants. In that example, he does the following:

define(  
  'MY_WORDPRESS_FOLDER',
  $_SERVER['DOCUMENT_ROOT']  
);  
define(  
  'MY_THEME_FOLDER',  
  str_replace("",'/',dirname(__FILE__))  
);  
define(  
  'MY_THEME_PATH',  
  '/' . substr(  
    MY_THEME_FOLDER,  
    stripos(MY_THEME_FOLDER,'wp-content')  
  )  
);

That annoyed me, quite a bit. Why? Well because if people write articles about stuff like custom write panels, I expect them to know a bit about the basics of the WordPress API. And well, the WordPress API has constants and functions for these things. So let me introduce you to them in the same order as the author of the articles did his defines above:

ABSPATH constant

Not only is their method inconvenient, it's wrong for a lot of installs. You see, some people install WordPress in a subdirectory, and depending on what you need, there are two different paths you might need. ABSPATH is a constant that always returns the home of WordPress. So if WordPress is in the wp/ subdirectory, it would give you something like: /home/username/public_html/wp/. If WordPress were installed in the root, it would just return /home/username/public_html/. Now I don't know how they're using it, as it's not used in this particular article, but they'd have to be very cautious with that.

TEMPLATEPATH constant

The second two things they're doing are possibly even weirder. First they define a constant MY_THEME_FOLDER, which is basically the path to the current theme. WordPress has a very convenient constant for that: TEMPLATEPATH. Since they're using it in an include, that's probably what they need. Would save about 4 lines of code. Note that what they call a "folder" is actually a path.

get_template_directory_uri()

This is were they really go wrong. You see, they define a constant MY_THEME_PATH, and then use it as a URL in a call to wp_enqueue_style(), in other words: to enqueue a style sheet. Now paths and URLs are different animals altogether, and they don't mix well. Take this example:

• My blog is installed in a subdirectory /wp/
• Because of that MY_THEME_FOLDER has been defined as follows:

  /home/user/public_html/wp/wp-content/themes/example-theme

• The code that sets MY_THEME_PATH turns that into:

  /wp-content/themes/example-theme

• The stylesheet is now included with the following path:

  /wp-content/themes/example-theme/custom/book_panel.css

• This causes a 404 (file not found error) because that directory simply doesn't exist! It should have been:

  /wp/wp-content/themes/example-theme/custom/book_panel.css

The proper way of doing the enqueue would thus have been the following:

wp_enqueue_style(  
    'my_meta_css',  
     get_template_directory_uri(). '/custom/book_panel.css'  
  );

Conclusion

I hope you understand why this annoys me. This is exactly the kind of coding that gives WordPress coders out there a bad name, as 5 - 10% of people out there trying this will not get it to work. If you want to prevent from making such mistakes, there's plenty of resources to learn about these things, or look them up. Two starting points would be the codex and my own cross reference of the WordPress source along with its very convenient WordPress source search function.

Quick tip: paths and URLs in WordPress is a post from Joost de Valk's Yoast - Tweaking Websites.A good WordPress blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Check out my thoughts on WordPress hosting!

Imbalance is a free wordpress theme in modern-minimalist style. Imbalance is a very user friendly, jQuery powered theme which looks really well under any browser and OS. Perfectly fits for your blog, online magazine or portfolio websites.

Pricing: FREE
Requirements: -
Source: http://wpshower.com/free-wordpress-themes/imbalance…