UMN Usability: Preview feature for blocks

webchick - January 22, 2008 - 23:51
Project:Drupal
Version:7.x-dev
Component:usability
Category:bug report
Priority:normal
Assigned:Unassigned
Status:active
Description

Especially for custom blocks, but even for programmatic, module-derived blocks, it'd be really neat to be able to hit a "preview" button and know instantaneously what the block's content going to look like before it's live on the site.

Currently, the process for adding a custom block to the site goes like:

  1. Go to admin/build/block/add.
  2. Enter the block body. Also enter in some wacky visibility stuff so your inevitable mistakes aren't visible to your larger website audience.
  3. Save the block page.
  4. Move the block to one of your regions so it's visible.
  5. Gasp in horror at your awful missing </ul> or whatever horrible thing you messed up that completely breaks your site's layout.
  6. click "configure" on the block.
  7. Edit the body, trying to get it right this time.
  8. Save the block page again.
  9. Repeat steps 5-8 until horror gasping subsides.
  10. click "configure" on the block one last time.
  11. Set the visibility on the block how you actually want it.
  12. Save the block page one last time.

That's an awful lot of steps.

How about this?

  1. Go to admin/build/block/add.
  2. Enter some body text. Be bold. Leave off as many tags as you want.
  3. Click "Preview"
  4. Fix as necessary.
  5. Set the visibility how you want it.
  6. Save the form.
  7. Move the block to proper the region.
  8. Go treat yourself to a nice tea, since you just got 5-10 minutes of your life back.

This would work basically like node previews, where on the customize form there's a preview button that, when clicked, would display the block content in the content area, so that you could see what it looked like iteratively before actually saving it to the database.

Maybe it also makes sense to have a preview icon on the main admin/build/block page to save you a click if you want to know what the "OG Details" block will do when enabled. Not sure.

#1

Michelle - January 23, 2008 - 04:34

Awesome idea. I usually go make a story node to test out blocks. This is much better.

Michelle

#2

ScoutBaker - January 23, 2008 - 08:14

+1 This would be a terrific enhancement.

#3

catch - January 24, 2008 - 15:46

Great idea. Like Michelle, I made a node with a path called block_test once just for setting visibility to, then promptly forgot about it until six months later. It's no fun.

Preview icon on admin/build/block - this'd make lots and lots of sense with drag and drop. I imagine it'd not be a trivial thing to do though. There's also the chance you enable a nasty broken php input format block and WSOD yourself (until refresh I guess, but still).

#4

awakenedvoice - February 28, 2008 - 14:31

This is definitely a much needed feature. The blocks feature in drupal is excellent but creating and editing multiple blocks consumes more time than necessary because I need to save, activate the block, check the block (usually in another browser tab), then repeat if changes are necessary.

#5

catch - February 29, 2008 - 06:19
Title:Preview feature for blocks » UMN Usability: Preview feature for blocks
Category:feature request» bug report

Since this came up in testing I'm retitling this.

#6

flobruit - March 21, 2008 - 17:41

Another improvement that I would add to this is the ability to assign a new block to a region directly on admin/build/block/add (similarly to how one can assign a new CCK field to a fieldgroup on the field creation page).
The current workflow is:

  1. Create the content for a new block at admin/build/block/add.
  2. Submit the form, the user gets taken to the top of admin/build/block.
  3. Scroll down to the bottom of the page (can be long) and try to find the block I just created in the "disabled" section.
  4. Drag and drop or set region for my new block.
  5. Scroll down to the save button and save changes.

Suggested:

  1. Create the content for a new block at admin/build/block/add.
  2. Choose region.
  3. Submit.

This really only makes sense in combination with the suggested preview functionality.

#7

Sutharsan - August 31, 2008 - 15:54
Component:block.module» usability

Moving all usability issues to Drupal - component usability.

 
 

Drupal is a registered trademark of Dries Buytaert.