wow, this is such an incredibly old topic on drupal - css hacks, template file hacks, theme modifications, it goes on an on (including modules for this function).

in the spirt of Omega's super clean interface, would it be reasonable to request a simple admin interface option on theme settings to:

1) hide all formatting guidelines and tips on content (nodes)
2) ditto for comments

this can be done by modifying template, but why? why not build in once and then enable as a function for users? that seems much easier....

Comments

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Active » Closed (won't fix)

Hmm.. I guess the simple answer is: No. Hiding these things is generally a bad idea as they are there for accessibility reasons and serve a purpose. If you want to hide them, you have to remove them in the templates or in the CSS yourself I guess. If, for whatever reason, you find that you are doing this multiple times in different projects and want to cut down on repeating code, you can of course also create your own Omega based base theme that you can then use as a basis for your project-specific subthemes. Although, in all seriousness, I want to make it clear that these elements are there by purpose. Hiding them completely is probably not what you really want anyways. Maybe make them look nice, or wrap them in a nice JS widget. But removing them -- You should reconsider that :)

zilla’s picture

zilla CreditAttribution: zilla commented

i always wind up hiding them with some simple css, usually with css injector or occasionally an edit to the file itself.

i do think you're right though, that it should be in there always in drupal - but it seems like there's this very ambiguous approach to deciding what gets built into core that impacts the user experience (e.g. i can go all the way down to hiding labels when managing field display, but when i'm editing an input filter i don't get a really simple checkbox like "hide tooltips and formatting guidelines for..." ? all themers would benefit from this kind of simple change, the same way they do with anything else in core that alters output site-wide