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

[tamouse]

+1 on this