Add a body class to http://exampleuser.dreamwidth.org/tag/each-tag

[marahmarie]

Title:
Add a body class to http://exampleuser.dreamwidth.org/tag/each-tag

Area:
Styles

Summary:
Currently the post view that shows your entries organized by tag (for example: http://marahmarie.dreamwidth.org/tag/book+reviews) has the same body class as the front page of our journals, that is, it uses the .page-recent body class. I'd like to suggest that we add a body class specifically for the entries-organized-by-tag view, so that it gets the new body class .page-tag (not to be confused with .page-tags, which is currently in use on the Visible Tags page, the one that simply lists all your tags on one page).

Description:
As a casual (but slightly obsessed) DW CSS designer, I'm often confounded by not being able to style every page view on DW individually. Because we have a sorting feature on our DWs that lets users browse full posts by each tag used on them, I want to style those pages to work as well and look as good as all the other pages on our DWs do. But the front pages of our journals and the tag views of our posts? They share the same HTML body class (.page-recent), which means tag views can be sort of weird-looking because they inherit .page-recent's styling, which often does not work on the tags view of our posts for an assortment of reasons. Which makes me think: why not just add a new, separate body class so we can style those pages, too? I humbly suggest we add the body class .page-tag to all views on our DWs that sort posts by the tags used on them (for example: http://marahmarie.dreamwidth.org/tag/book+reviews would get the new .page-tag body class, as would all other similar page views on our DWs).

Poll #11750 Add a body class to http://exampleuser.dreamwidth.org/tag/each-tag

Open to: Registered Users, detailed results viewable to: All, participants: 39

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
6 (15.4%)

Should be implemented with changes. (please comment)
12 (30.8%)

Shouldn't be implemented.
3 (7.7%)

(I have no opinion)
17 (43.6%)

(Other: please comment)
1 (2.6%)

Comments

[ninetydegrees]

+1 for separating tagged-entry pages from recent pages the way the reading page inherits from the recent page but can be set apart.

-1 for naming the body class .page-tag as this would be very confusing imo. (The tags page has /tag in its URL and an -s is so easy to add/remove). Something more explicit like .page-entries-tag might work better.

[swaldman]

Wot she said ;-)

[kyrielle]

Ooo, changing to this. :)

[turlough]

+1

[susanreads]

+1

[kerravonsen]

+1

[marahmarie]

Voted "with changes" to show favor to your version of the idea; I guess it would be confusing to not go with a body class with a much clearer name.

[tamouse]

+1 on this

[stasha2g]

+1

[matgb]

My change: where possible have it something like .tag-ACTUAL-TAG

In other words put the tag itself into the class, so you can if you wish style each separate tag (one of the blogs I read does this for its electoral law section, that has a much more "professional" look than the main site.

I'd say if possible any punctuation within the tag name should be replaced by a hyphen.

[marahmarie]

Hmmmm. That would allow you as many variations on your page layout as you have tags (and I have about 200 of them, give or take a handful, so this could get really crazy fast). But I do like the idea. But not enough to see it implemented as a variation on mine - at least, not yet. For someone who wants a cohesive look to their DW it's probably overkill, but for designers really wanting to head way far out there in their designs, it does sound great.

My whole reason for the suggestion is my tagged views are not conforming to each other because they have to follow .page-recent's CSS, a page which I have set up to work with the Previous and Next links up top (and that page *always* has Previous and Next links, so it always works).

But on some of my tagged views, there are not enough entries to spawn those nav links, so the top of the page doesn't line up right (perfect example being the link I used for my OP, http://marahmarie.dreamwidth.org/tag/book+reviews. If things were lined up right on that particular tag view, the hr line under the first sidebar title and the hr line under the top entry would sit right across from each other, perfectly. Like so: http://marahmarie.dreamwidth.org/101800.html).

But because the page is following .page-recent's CSS, I can't use my special CSS rules for .page-entry and .page-reply to fix that mess up. Thus, my Suggestion was born.

[cesy]

I'd like to give it both classes, so that CSS designers can do what they like - either one consistent one, or specific ones.

[marahmarie]

I think doing so might lead to a lot of on-the-fly HTML body class name generation which could be a churn on the servers and might slow page loads down - I'm not saying it's a bad idea, either, just that it might come at a cost, so in the meantime I still prefer simply adding a body class for more granular styling options on that page view than we have now.

[matgb]

You already get classes added for the poster name and similar, it shouldn't be extra strain to simply get the S2 layer to give more info.

[marahmarie]

OK... (I know you understand this stuff better than I do, so I'll demure to your opinion of it in this instance)...