As mentioned in http://groups.drupal.org/node/11921 : the text "Block configuration" on the user account edit page isn't very helpful for people who don't know what "block" is in a Drupal context. (The gdo post describes a user who thought it was about blocking.)
I suggest:
Change "Block configuration" to "Enable block display".
Below the check boxes, add the following help text: "A block is a piece of content (usually text or links) which is displayed on some or all pages in addition to the main content, usually in a sidebar. Above is a list of blocks which you can choose to turn on or off."
Comment | File | Size | Author |
---|---|---|---|
#28 | jamesan_266153-28.patch | 1.36 KB | JamesAn |
#25 | jamesan_266153-25.patch | 1.36 KB | JamesAn |
#18 | jamesan_266153-18.patch | 1.37 KB | JamesAn |
#16 | jamesan_266153-16-admin.png | 32.71 KB | JamesAn |
#16 | jamesan_266153-16-user.png | 17.82 KB | JamesAn |
Comments
Comment #1
catchI'd go for 'Block display settings' or 'Configure block display' rather than 'Enable' - since we might be disabling blocks here too. Looks good though.
Comment #2
KingMoore CreditAttribution: KingMoore commentedHow about:
Personalize Blocks
or
Personalize Block Display
or
Personalize Displaying Blocks
Comment #3
KingMoore CreditAttribution: KingMoore commentedOr
Blocks To Display
Comment #4
IceCreamYou CreditAttribution: IceCreamYou commentedAnything with the word "block" followed by a noun will cause confusion. The reason the word "block" is confusing is because it is often taken in the sense of the verb "to block."
I suggest "Personalize blocks" with the help text "A block is a piece of content (usually text or links) that appears on various pages as a complement to the main content. Checking a box below will enable that block, allowing its content to appear."
Comment #5
KingMoore CreditAttribution: KingMoore commentedWas thinking about this last night a bit, I like 'Personalize Blocks' as well. I also like something like:
Select Blocks to Display
Personalize Which Blocks Display
to Display gives a bit more context to the first time user. Help text should be present as well.
Comment #6
mot CreditAttribution: mot commentedIt could be possible to direct the sites users to the drupal wording page ... ^^
Comment #7
mot CreditAttribution: mot commentedNo conclusion. Looks like it should be like it is. Closing.
Comment #8
zirvap CreditAttribution: zirvap commentedI still think this would be an improvement, so I'm opening it again, and changing component to "usability". Hopefully that'll get more eyes on it.
I think catch's suggestions in #1 are the best ones here (better than mine), but any of the suggestions here are better than the current text.
Mot: Next time you want to close an issue, you should set it to "fixed", "won't fix", or "by design". It will then be automatically closed after two weeks. More info at http://drupal.org/node/156119. (Kudos to you for cleaning up the issue queue, btw :-)
Comment #9
mot CreditAttribution: mot commentedThen maybe a Patch is needed?
Comment #10
karschsp CreditAttribution: karschsp commentedtagging for novice queue to incorporate catch's suggestions from #1 into a patch.
Comment #11
JamesAn CreditAttribution: JamesAn commentedI've changed 'Block configuration' to 'Configure block display' as per #1.
Comment #12
JamesAn CreditAttribution: JamesAn commentedGah.. always forget to change the issue status.. ^^"
Comment #13
eojthebraveI don't think that just changing the title of the fieldset is enough. As IceCreamYou mentions in #4 it would be good to provide some text that explains what your getting by checking/un-checking one of these blocks. As it is if a user doesn't know what a "block" is in the context of Drupal there is no way for them to know why they would want to turn a block on/off. All they can really do now is try it and hopefully notice that something has changed.
Perhaps outside of the scope for this patch, but what if blocks that are listed on the user's account page could provide a short/configurable description. Currently they only show the name of the block, which may or may not be helpful in trying to guess what extra content/functionality you gain from enabling that block.
Marking as needs work, I think we should at least in-corporate the help text from #4, or something similar.
Comment #14
JamesAn CreditAttribution: JamesAn commentedMakes sense to me.
This patch:
I agree it'd be useful to implement a way to provide a short/configurable description for blocks that are listed in user account pages. Let me see if I can whip something up.
Comment #15
JamesAn CreditAttribution: JamesAn commentedtestbot?
Comment #16
JamesAn CreditAttribution: JamesAn commentedOops. Uploaded two patches. They're identical.
I got my hands all dirty with the system schema and whatnot. Turns out, adding a field to the block table takes a bit more work as it's referenced outside the block module (in the system module and perhaps other places).
Sadly, I only have access to Ajaxterm to SSH to my webdev box. My work computer is a bit restrictive.. =( So before I spend more time on this, I made two mock-ups: one for the admin block config page and another for the user account setting page.
Yes/no?
Comment #17
eojthebravePersonally I'm not 100% sold on "Configure block display" and am more inclined to "Personalize Blocks" as mentioned in #4. But could go either way.
I like the mockups in #16. Perhaps change the text underneath the description field to "Shown if users can customize the visibility of this block."
Could these descriptions be used on the admin/build/block page as well? Might help there as well. Clarify what a block contains. Some of the block titles can be a little ambiguous. If we go down this route I think the description field should be moved up underneath the block title field.
Comment #18
JamesAn CreditAttribution: JamesAn commentedI'm increasingly leaning towards "Personalize blocks" as well. It's not consistent with the well-used comp-sci-ish vernacular, but I think it's a whole lot friendlier to a non-technical user than "configurations".
Voila! The patch that rewords it as "Personalize blocks".
I think adding descriptions should be another issue, lest we risk eating kittens here. When this minor fix gets a green light, we can make an issue of creating block descriptions for that "Personalize blocks" area and perhaps even the admin/build/block page. I get confused about the functionality of various blocks on that page as well and placing a more verbose description underneath the block title field makes sense to me.
Comment #19
IceCreamYou CreditAttribution: IceCreamYou commentedI am, obviously, a fan of the approach in #18 - patch looks good although I haven't actually tested it.
Comment #20
mr.baileystagging...
Comment #21
catche.g., a list of links
no comma required after e.g.
I'm not sure about 'boxes of content'. Homepage sites use 'widgets' - there's probably other more common terms. Blocks are boxes of content doesn't seem that much more explanatory than 'Blocks are blocks of content'. Also a block might be a menu, or who's online - not necessarily decribable as content.
Also some blocks are enabled by default, and some aren't, so the second sentence won't always be accurate.
how about just this:
"Enable or disable optional blocks using the checkboxes below."
Then it's up to the admin of the site to give the block a decent description.
Comment #22
IceCreamYou CreditAttribution: IceCreamYou commentedHow about this:
Blocks consist of content or information that complements the main content of the page. Enable or disable optional blocks using the checkboxes below.
Comment #23
eojthebraveI like that. I'm worried that catch's example doesn't provide enough information without implementing block descriptions. Leaving us in pretty much the same place we started. What is a block and why would want I want to enable/disable one?
Comment #24
catch#22 works for me. Forgot to mention I think "Personalize blocks" is good as well.
Comment #25
JamesAn CreditAttribution: JamesAn commentedI like #22 too. Clearer. None of that 'blocks are blocks of blocks' silliness. Putting the 2nd sentence in the active present voice is much more engaging.
Comment #27
IceCreamYou CreditAttribution: IceCreamYou commentedThe description has a semicolon after it instead of a comma in the latest patch.
Comment #28
JamesAn CreditAttribution: JamesAn commentedSilly me.. ^^"
Comment #29
catchLooks good. I really hope we can replace this form with nice [x] links on the actual blocks themselves or something, but until then might as well be clear.
Comment #30
webchickThis looks like a good, concise description of what blocks are. Committed to HEAD, thanks!
Comment #33
Bruno Vincent CreditAttribution: Bruno Vincent commentedHow do I completely get rid of that option?
Make it gone or non collapsible, with maybe a display-none tag?
I want completely gone ;)