More typographic hierarchy or control in discussion styling please

I love GoPlan's visual cleanliness but the complete lack of any decent typographic hierarchy within the styling of discussion content is crazy. Basecamp's isn't great but it is a lot better!

For example, an h2 in GoPlan looks exactly the same as some emboldened text.

Please, either get some decent, clean styles going on or give control to the account admin with a customisable stylesheet!

I'd happily make some specific CSS suggestions if that helps.

I’m sad

Inappropriate?

Reply to this idea

1 person likes this idea

I like this idea! Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.

The company implemented this idea.

The best point from the company

Fred Oliveira, Official Rep, replied on October 27, 2009 16:21
We did a few tweaks here and there and changed the typography CSS for the discussions. This is how it looks after the changes. Thoughts? This should go live as soon as we update the live running code (which should be really soon).

I’m happy

The company thinks this is one of the best points

Remove this from best good points

Create a customer community for your own organization

Plans starting at $19/month

EMPLOYEE

Remove Inappropriate?
Delete or Edit for 15 minutes

Fred Oliveira, Official Rep, replied on October 14, 2009 17:16

Hey Jonathan,

You are absolutely right. I'm a typography addict myself and I know how frustrating the display of discussions is sometimes. We'll definitely improve it soon. We have a couple of ideas of our own, but if you feel inclined to send in suggestions, please do, we appreciate your thoughts.

Thanks!

I’m confident

this is one of the best points

Add a comment This is one of the best points Mark as a company good point
EMPLOYEE

Remove Inappropriate?
Delete or Edit for 15 minutes

Fred Oliveira, Official Rep, replied on October 27, 2009 16:21

We did a few tweaks here and there and changed the typography CSS for the discussions. This is how it looks after the changes. Thoughts? This should go live as soon as we update the live running code (which should be really soon).

I’m happy

The company thinks this is one of the best points

Add a comment This is one of the best points Mark as a company good point
Remove Inappropriate?
Delete or Edit for 15 minutes

Jonathan Schofield replied on October 27, 2009 16:45
Hi Fred,

Thanks, that looks a lot better. A couple of further (subjective?) thoughts...
1. How about more vertical space above headings than beneath them. This helps to associate them visually with the content they are a heading of, especially when there are multiple heading levels present.
2. Though it may interfere with your nicely minimal aesthetic, a subtle rule above <h2>s might help reinforce stronger visual breaks in lengthy posts
I’m thankful
this is one of the best points

3 Comments Add a comment This is one of the best points
Remove
Jonathan Schofield commented on October 27, 2009 16:54

And another thought...

130 character long line lengths is pushing the bounds of good readability. How about some well-placed use of max-width?
Remove
Fred Oliveira, (Official Rep), commented on October 27, 2009 17:13

We're already using max-width to constrict the discussions to 650px width. While it is still pushing the boundaries of readability (about 12 words would be perfect), I found it to be a good compromise. I'll have a second look and see if with a few font-size adjustments it can get a tad better.

I'll definitely improve the spacing on headings. Thanks again for the awesome feedback you've been sending in. Cheers!
Remove
Jonathan Schofield commented on October 27, 2009 18:29

Ah yes, I see that 650px is what you have already and that that equates to about 120-130 characters in GoPlan as is. I suppose that upon reflection I might lobby for a slightly bigger body text font size on the same width in #content?