Node design mockup, from bottom-up

Vrijdag, 14 January 2005

This shows a mockup of the node form in a bottom-up method.

Drupal is modular, and thus the forms can -and will- look different afor every site. Because of this fact, it is undoable to design an interface for each situation. An example: The mockups all show taxonomy, but I have some sites running that do not use taxonomy at all, not for blogs, nor for other pages.

Therefore I have suggested numerous times to start bottum-up:

First define regions, (that is this mockup)

Second define elements (a text-are is an element, but so is a taxonomy selector)

Third define where modules should place these elements. (tab >&gt region)

But please not that by no means, I mean to propose the exact regions like presented in the images. We must discuss these regions in a structural way and then agree upon a set of regions. These regions should then all bne placed in the nodeapi. But again: These regions are just brainstorm-ideas!






In case it is not clear: form side != sidebar right

Submitted by Ber on 14 January, 2005 - 18:43.

I assumed it is clear, but though that Gerhard;s comment might cause some confusion: The proposed form_side is not the same as sidebar-left! You should read the tabbed square, containing the form, as the main area ina drupal page. A lot of regions might appear around it, but normally only the header, sidebars and footers will.

I like this approach. We shou

Submitted by Gerhard Killesreiter (niet geverifiëerd) on 14 January, 2005 - 16:33.

I like this approach. We should extend it to have side region on both sides.

makes sense for templating

Submitted by robertDouglass (niet geverifiëerd) on 14 January, 2005 - 16:10.

Hi Ber,

this idea makes sense to me from the perspective that these regions could then become variables in a templating system, and could therefore be moved around. It is a constant frustration to me that by the time stuff gets to the template in the current system, there is a big long glob of HTML called $content and the templater cannot do anything to it. It takes the programmer who is willing to override certain theme functions to be able to change the stuff in $content, and not all changes are even possible. Splitting content into regions, even if we call them 1 - 5, makes great sense to me.

+1

Robert