[development] nodify.module idea: 'everything is a node'

[fago]

Am Samstag, den 20.01.2007, 11:54 +0100 schrieb Dries Buytaert:
> On 19 Jan 2007, at 21:31, Nedjo Rogers wrote:
> 
> > Questions:
> > - does this approach sound useful?
> > - who's working on something similar? better?
> > - pitfalls?
> > - anyone wanting to work on this?
> 
> I've said it before and I'll say it again; the nodification of such  
> objects is not a good idea for a variety of reasons. Three obvious  
> reasons are: it does _not_ become easier for your users, it does  
> _not_ become easier for the average developer (unless you're a Drupal  
> expert, the code becomes more difficult to understand), and it will  
> be an incredible resource hog.
> 
> -1 for 'comments as nodes', 'users as nodes' or 'categories as nodes'.


Initially I was also a fan of the "everything is a node" approach.
However nowadays I think different.


Imo nodes are and should be site content - and nothing else. But people
want to use that great tools that are available for nodes for other
things too. To break out in this direction, we could generalize the API
around all the different things (nodes, users, taxonomy, comments, ..).
Such a generalized API would make things a lot easier for developers.

I agree with Bèr that there would be need for a such a general "drupal
object". So nodes, users, taxonomies, comments, .. could be all such a
"drupal object", which all share the same API. With that, tools might
become more powerful as they could be written easily to work with any
kind of drupal object.



@usernodes:
The usernode module is useful as it enables views to list users. Also
it's useful to theme the user page like any other node. 
But I don't think users should be nodes - users are no site content.
However the user page is or might be - so perhaps this should be a node.
Which leads to another point - the user profile: site-content.

So perhaps some more things should be a node - or rebuilt as another
general drupal object.

regards,
fago