There's a great illustration on this page (http://drupal.org/node/171194) but I'm actually finding it a little confusing because it doesn't quite match what I'm reading elsewhere.

The problem is that the illustration shows four arrows going to the top, bottom and sides. Those four areas are highlighted in pink. There is no arrow pointing to the center "content" area (which is in blue). The callout for the arrows says "block regions".

This clearly implies that the blue area is not a "block region". However, http://drupal.org/node/171224 seems to suggest that it is.

It's all a little confusing, because when I think of a "block" I do tend to think of something that goes in a sidebar (not sure if that's right or not) but a region could be anywhere that I want to put stuff. Is a "block region" a different beast than a plain "region"?

Comments

Jeff Burnz’s picture

Technically you are right - since blocks can be placed within the content region. Ideally there should be an additional "brown" block region below the 3 blue nodes in the centre, since blocks placed in the content region sink to the bottom by default.

leehunter’s picture

So, if any region could be used for anything, should we even be calling them "block regions" at all? Should we just call them all "regions"?

jhodgdon’s picture

I've updated the Regions page so I think it is clearer that regions are for content or blocks.

I'm not very good at doing image editing. I agree with #1 that the image should be modified so it says "regions" instead of "block regions", and so that the bottom section of the content region should be brown to indicate that that is also a region where blocks can go.

Can someone who is better at image editing (or who has better tools than I do) make that image edit? If you do not have permission to edit the page, maybe you could edit the image and post an updated image here, and a doc admin can attach it to the page?

jhodgdon’s picture

Tagged for easier reference of what needs doing here

Jeff Burnz’s picture

Ask dvessel, I think he built those pages and probably has the original images.

jhodgdon’s picture

I've sent dvessel a message, thanks!

dvessel’s picture

Hello! I know the illustration isn't exactly right. I didn't want to explain visually in exact detail since the overall message could be easily lost. That illustration isn't alone on this either. I was going for the general idea.

If I wanted it to be exact, I'd have to show that the "content" region is special since the content *will always* print out in the page template as $content no matter how the regions are defined from .info. This quirk or special case will most likely be remedied in 7 but for now it's hard to illustrate without making it more visually complex.

dvessel’s picture

Oh, and to be clear, that's why it's labeled as "block region" because the content is never handled through regions. The default settings make it seem like it but it's really not.

jhodgdon’s picture

But you can add blocks to the Content region...

dvessel’s picture

Yes, adding blocks to the content region is handled through the block system but the page content is completely separate.

The illustration shows that the content area is not a block which is true. It's only when a theme contains a region named "content" that the page body or content merges with any blocks assigned to the region. I know this is confusing but hopefully this issue will remedy that for the next release. #428744: Make the main page content a real block

As far configuring the block admin page, there's no distinction but from a theming perspective they are not the same. I should make that clear in the docs regarding the region settings.

dvessel’s picture

Whoops, I didn't even realize that it was already committed for 7. :)

dvessel’s picture

Status: Active » Needs review

I updated the notes on the regions handbook page. http://drupal.org/node/171224

Although the previous edits were done with the wrong assumptions, it still applies since any content can be assigned to it through the api function.

jhodgdon’s picture

Status: Needs review » Fixed

I think things are clear enough now. Thanks!

Status: Fixed » Closed (fixed)

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

sun.core’s picture