[css] Add admin-post css to entry-wrappers.

[stormy]

Title:
[css] Add admin-post css to entry-wrappers.

Area:
styles, entries

Summary:
When you mark a comment as an official admin/mod hat comment, it applies the admin-post class to the comment's comment-wrapper, but the same does not happen when you mark an entry as official. The entry-wrapper does not gain a admin-post class. I suggest that it does so you can use css to format those posts separately from others.

Description:
When you mark a comment as an official admin/mod hat comment, it applies the admin-post class to the comment's comment-wrapper, but the same does not happen when you mark an entry as official. The entry-wrapper does not gain a admin-post class. I suggest that it does so you can use css to format those posts separately from others. Personally, I'd love to use this as a way to call more attention to those specific entries without having to use a .poster class and have everything marked by a specific user stand out.

An additional suggestion related to this: At current the class .admin-post gets added to comments when they are made official moderator comments. It might be easier to suggest this css is changed to .admin-comment if it is a comment and .admin-post if it is added to an entry. This isn't a necessary step because you could format with ( .entry-wrapper .admin-post AND .comment-wrapper .admin-post ) but it might just be cleaner for those who don't like listing multiple classes together to specify.

Poll #14085 [css] Add admin-post css to entry-wrappers.

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
24 (63.2%)

Should be implemented with changes. (please comment)
1 (2.6%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
13 (34.2%)

(Other: please comment)
0 (0.0%)

Comments

[green_knight]

(Aside: when I pressed the answer button on my rlist, I got a 'form is invalid' response, from the single entry page it was fine, though the button turned into a weird shape).

admin-comment and admin-post would be a good thing, but it would break the formatting of existing comments, so it will need a different name. In general, I'd support two classes.

[anaraine]

While I support the idea of a class for admin posts (whichever way you feel like doing it, I don't mind listing multiple classes to specify)... does Dreamwidth already have a way to mark "official/mod" posts? (Not just by using a specific icon, I mean.) I thought that was something still in development... or even still just in dw_suggestions.

[azurelunatic]

It went live last release; this would supplement it to make them easier to style unmistakably.

[habite]

I support the idea of having a separate class for admin-posts... Say, for example, in the css the entry could automatically be given a border (or different border to normal posts) with the option for the admin(s) to edit it via custom css? That way it's optional for those who don't want admin posts to appear any different.

[arethinn]

Are there other uses for marking a post/comment "admin" besides gaining different styling for it? I'm confused why someone would want to do what you describe.

[azurelunatic]

Only users in official positions in a community can make admin flagged comments or entries, so it's a way of authenticating that the user has authority to make official community statements.

It also serves to distinguish between that user speaking as just another community member, or with authority.

It's new, so it hasn't been used as much as previous workarounds like special icons or tags.

[habite]

If, for example, the community in question was a fic-exchange community or a contest community, it would be super useful to have the ability to tell at a glance which posts are 'official' posts, as opposed to posts by regular members.

[arethinn]

I understand the philosophy, but how then is a reader supposed to know that the comment or post is flagged admin, if you have suppressed special styling? I'm just not sure how it would then serve the purpose it's supposed to serve. Is it marked on the post/comment in some other way (which would seem to conflict with the desire to make them look identical to regular user posts)?

[arethinn]

Sure, but if you suppressed the styling, how would you then tell at a glance?

[habite]

Well I imagine the whole thing would work in much the same way that ticking 'admin post' does when you're posting a comment; if you tick 'admin post' when writing the entry, the specialized styling is used, if you leave it unchecked then the entry appears as normal.

Suppressing the styling would be optional in the cases of admins who wanted their entries to appear the same as regular members (such as if they are posting stories as a response to a contest, for example).

[stormy]

Replying on my phone so excuse the short comment. Admin posts and comments are already enabled and display a special icon as well as additional text without any additional CSS code. An additional CSS class just allows users to make a post or comment on customized pages display differently. Personally, I have considered making the post easier to view when scrolling with borders and/or different colors.

[azurelunatic]

But -- I see why someone who thinks that the stock appearance of admin post flagged items is ugly might want to make it appear as much like a normal entry or comment as possible in their own style or for a community they moderate, but the use case you describe, for admins who want to look like normal users -- I don't think that's a helpful use case. Admins who want to look like normal users would just not check the box.

[habite]

Oh sorry - that's what I meant; that they would not tick the box, which would in turn suppress the styling.

[azurelunatic]

So summing up some of the other comments, it sounds like the main use case is to either leave it with the existing subtle differences, or take advantage of the css class to either tastefully or ... not so tastefully ... highlight the admin posts so they're much easier to spot.

When kaberett's changes to the support board to highlight the different types of comment there with dashes as well as changes to line color came into effect, I was surprised and very pleased with how much cognitive overhead it removed for me. I hadn't thought I was spending so much of my attention on telling the comment types apart by color, and yet the removal freed up so much attention.

[arethinn]

I hadn't been aware there wasn't some kind of quite obvious visual difference by default - I thought the point of this was mainly so that could be suppressed if wanted and thought "then why mark them admin in the first place if it leaves no difference at all". If it's so that it can be skinned as arbitrarily desired (including no different styling), that makes more sense.

[azurelunatic]

Most "please add a CSS class" requests are for skin-as-arbitrarily-desired, yeah.

As for the existing state, it depends on what you think of as obvious -- there's a red rosette and text in either the subject line or comment header, but it's something that I personally could miss at 3am with no glasses on my phone, and that people with less available attention span/lower vision might miss entirely.

[ratcreature]

Also, the red rosette is really ugly (IMHO), so I rather keep tagging my admin posts "admin" in the comm I mod rather than using the official flag and having to see that thing. So I would like the CSS styling would allow alternative markers that got rid of the red rosette thing entirely and showed the status in another way.

[denise]

Ha. I was just going through the code to try to implement this, and discovered that .admin-post classes existed on mod-hat comments and sticky mod-hat entries, but not non-sticky mod-hat entries. I bet it was a bug/oversight that it wasn't added with everything else!