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."

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

catch’s picture

Category: feature » bug

I'd go for 'Block display settings' or 'Configure block display' rather than 'Enable' - since we might be disabling blocks here too. Looks good though.

KingMoore’s picture

How about:

Personalize Blocks
or
Personalize Block Display
or
Personalize Displaying Blocks

KingMoore’s picture

Or
Blocks To Display

IceCreamYou’s picture

Anything 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."

KingMoore’s picture

Was 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.

mot’s picture

It could be possible to direct the sites users to the drupal wording page ... ^^

mot’s picture

Status: Active » Closed (fixed)

No conclusion. Looks like it should be like it is. Closing.

zirvap’s picture

Component: user interface text » usability
Status: Closed (fixed) » Active

I 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 :-)

mot’s picture

Then maybe a Patch is needed?

karschsp’s picture

Component: usability » block.module
Issue tags: +Novice

tagging for novice queue to incorporate catch's suggestions from #1 into a patch.

JamesAn’s picture

FileSize
1.16 KB

I've changed 'Block configuration' to 'Configure block display' as per #1.

JamesAn’s picture

Status: Active » Needs review

Gah.. always forget to change the issue status.. ^^"

eojthebrave’s picture

Status: Needs review » Needs work

I 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.

JamesAn’s picture

Makes sense to me.

This patch:

  • rerolls against the latest code,
  • includes the fieldset description "Blocks are boxes of content (e.g., a list of links) that complement the main content. Checking a box below will enable that block, allowing its content to appear.", and
  • breaks up the array declaration according to #394586-10: DBTNG: Trigger module.

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.

JamesAn’s picture

Status: Needs work » Needs review

testbot?

JamesAn’s picture

Oops. 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?

eojthebrave’s picture

Personally 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.

JamesAn’s picture

FileSize
1.37 KB

I'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.

IceCreamYou’s picture

I am, obviously, a fan of the approach in #18 - patch looks good although I haven't actually tested it.

mr.baileys’s picture

Issue tags: +Usability, +D7UX

tagging...

catch’s picture

Status: Needs review » Needs work

e.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.

IceCreamYou’s picture

How 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.

eojthebrave’s picture

I 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?

catch’s picture

#22 works for me. Forgot to mention I think "Personalize blocks" is good as well.

JamesAn’s picture

Status: Needs work » Needs review
FileSize
1.36 KB

I 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.

Status: Needs review » Needs work

The last submitted patch failed testing.

IceCreamYou’s picture

The description has a semicolon after it instead of a comma in the latest patch.

JamesAn’s picture

Status: Needs work » Needs review
FileSize
1.36 KB

Silly me.. ^^"

catch’s picture

Status: Needs review » Reviewed & tested by the community

Looks 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.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

This looks like a good, concise description of what blocks are. Committed to HEAD, thanks!

Status: Fixed » Closed (fixed)
Issue tags: -Usability, -Novice, -D7UX

Automatically closed -- issue fixed for 2 weeks with no activity.

Bruno Vincent’s picture

How do I completely get rid of that option?

Make it gone or non collapsible, with maybe a display-none tag?

I want completely gone ;)