[development] proposal for theming nodes

[Kobus Myburgh]

Hi,

I feel that putting ANY structural HTML in the extra field will again influence theming, which will make this whole exercise null and void. On the other hand, if you don't add the HTML, you won't have any guarantee that your theme will be functioning correctly, because with so many things to customize, you are bound to look something over.

I assume the solution to the latter is to set up a standard (CORE) Drupal site, enable all modules, create a node of each and every type, add a coment, some forum posts, some RSS feeds, or whatever else is needed, and export the database. Use that on a site where you're developing a theme - if all those elements display correctly, your theme must be okay, or what?

Regards,

Kobus


>>> boris at bryght.com 12/14/2005 6:14:38 PM >>>
On 12/14/05, Bèr Kessels <ber at webschuur.com> wrote:
>
> Hi,
>
> way too often i have to hack modules or even core (upload) to make it
> *not*
> append HTML to $node->body.
>
> I think this practice of appending stuff to the body is very bad, since it
> makes it impossible to add thatdata elsewhere, without duplication.


We've noticed this now with trackbacks and other such items (even book
module navigation, althought this may have been fixed now) appearing in
"full text feed" mode in RSS...you have to do special checking in your
module to exclude extra data when it's being uses in the RSS feed.

The hard part, imho is to convert **all** core modules to use this. and with
> All i mean all :). Taxononomy, for example, should add its terms in there,
> while book module should add its navigation.


Taxonomy I don't think so, but book module navigation, certainly. Which
brings up the point...do we then need an extra.tpl.php? Or options in
taxonomy that says "Append taxonomy terms after node body"? Best not to
touch the taxonomy issue for now, I think.

--
Boris Mann
http://www.bryght.com 
Vancouver 778-896-2747 / San Francisco 415-367-3595
IM boris_mann at jabber.org / SKYPE borismann