It has to do with SEO more than anything. Search engines look at the h1 as being the main title. h2's are subtitles. If they see a lot of h1's they may penalize them.
The different heading levels are more about meaning of the content rather than the look. On 06/06/2010 1:51 PM, Bruce Wampler wrote: > Sorry, don't mean to beat this to death, but just a follow up on using > < h2 > for the title on the front page in Twenty Ten. > > I see the code is explicitly there in page.php, but I really don't > understand the reasoning behind this. I can see an argument for using > h2 for posts and h1 for pages, by why treat the front page > differently? Seems to me a post is a post and a page a page, and one > would want consistent treatment for each. > > The default Twenty Ten CSS for each of these makes the titles look the > same anyway, but if you are writing a child theme, and want different > title looks for pages and posts, this decision makes that difficult > for CSS only solutions. > > My solution in the end is to add a modified page.php in the child > theme - but that then breaks the idea of a CSS only child theme. > > Oh well - figuring I needed to start fiddling with override php files > other than functions.php opens up a bunch more theming opportunities, > so I'll go with that. > > Nevertheless - Twenty Ten + child themes is a much better way to build > a theme. I wrote a couple of themes for WP 2, and have just finished a > version of a Twenty Ten child theme, and I must say the new approach > is much more productive and easier. Don't have to worry that you got > every last thing covered - it will be there in the Twenty Ten parent. > Very cool indeed. > _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
