5 ms·

Those who use it, how does it compare to joomla? Joomla is the closest I have come to having to maintain a full blown php cms and I found that to be quiet bloat

by robryan 15y ago

Those who use it, how does it compare to joomla? Joomla is the closest I have come to having to maintain a full blown php cms and I found that to be quiet bloated as well.

eropple 15y ago
Drupal has a lot of problems. It's still much better than Joomla, IMO--Joomla has a lot of really deep architectural WTFs and I find it much harder to work with, both as a software developer and as an end user. CCK and Views allow you to do fairly complex stuff within Drupal without writing code. There's definitely an upper bound on performance with such a method, but you can get stuff out the door pretty quickly. Joomla doesn't really have an equivalent, and adding new content types in Joomla isn't novice-friendly. (Also, Drupal's Taxonomy is way, way nicer than Joomla's arbitrary Categories/Sections stuff.)
snorkel 15y ago
I haven't used Joomla but have worked on Drupal sites. It is possible to build a reasonable and scalable sites in Drupal, but often times you'll find instead is novice web devs have chosen Drupal because they know very little about relational databases and don't want to know anything about database design. Drupal gives you custom object storage and custom object views without having to write any code, so you can imagine the skill set of the people this appeals to and the kinds of architecture their sites have.
- zdw 15y ago
  On the flip side, just because you know how to write code doesn't mean your designs are going to be good. The "everything is a node with attributes" concept that Drupal requires makes you think first about data, then about presentation. For example, if you want an organized list of data, you make custom nodes (the model), then a view, which is a decent design pattern for most sites. Views are incredibly powerful and can do nearly everything most sites would want. Compare this to other CMS's that make it difficult or impossible to tack on functionality without writing a lot of raw database code (not to pick on them, but Wordpress developers seem to have this problem in spades). Also, Drupal treats caching as a first class integrated system, which makes performance much better than other options.
  - justatdotin 15y ago
    yep, everything-is-a-node-with-attributes makes me think about my data; realise it doesn't fit drupal's rigid content heirarchy; remember that, no, views are not nearly powerful enough; and go back to django.
skore 15y ago
Joomla has very extensive community issues. I've written a bit about it over here[1] and you can check out Johan Janssens (Joomla co-founder in exile) blog[2] for more in-depth analysis. The bottom line is - take a look at Nooku[3] - especially if you're looking for a framework that makes sense (a corresponding CMS is underway). [1]http://valanx.org/index.php?option=com_content&view=article&id=140:going-forward-from-joomla&catid=25:skore-blog&Itemid=99 http://valanx.org/index.php?option=com_content&view=arti... [2]http://johan.janssens.me/ http://johan.janssens.me/ [3]http://nooku.org/ http://nooku.org/

by robryan 15y ago

Those who use it, how does it compare to joomla? Joomla is the closest I have come to having to maintain a full blown php cms and I found that to be quiet bloated as well.

eropple 15y ago

Drupal has a lot of problems. It's still much better than Joomla, IMO--Joomla has a lot of really deep architectural WTFs and I find it much harder to work with, both as a software developer and as an end user. CCK and Views allow you to do fairly complex stuff within Drupal without writing code. There's definitely an upper bound on performance with such a method, but you can get stuff out the door pretty quickly. Joomla doesn't really have an equivalent, and adding new content types in Joomla isn't novice-friendly. (Also, Drupal's Taxonomy is way, way nicer than Joomla's arbitrary Categories/Sections stuff.)

snorkel 15y ago

I haven't used Joomla but have worked on Drupal sites. It is possible to build a reasonable and scalable sites in Drupal, but often times you'll find instead is novice web devs have chosen Drupal because they know very little about relational databases and don't want to know anything about database design. Drupal gives you custom object storage and custom object views without having to write any code, so you can imagine the skill set of the people this appeals to and the kinds of architecture their sites have.

zdw 15y ago
On the flip side, just because you know how to write code doesn't mean your designs are going to be good. The "everything is a node with attributes" concept that Drupal requires makes you think first about data, then about presentation. For example, if you want an organized list of data, you make custom nodes (the model), then a view, which is a decent design pattern for most sites. Views are incredibly powerful and can do nearly everything most sites would want. Compare this to other CMS's that make it difficult or impossible to tack on functionality without writing a lot of raw database code (not to pick on them, but Wordpress developers seem to have this problem in spades). Also, Drupal treats caching as a first class integrated system, which makes performance much better than other options.
- justatdotin 15y ago
  yep, everything-is-a-node-with-attributes makes me think about my data; realise it doesn't fit drupal's rigid content heirarchy; remember that, no, views are not nearly powerful enough; and go back to django.

skore 15y ago

Joomla has very extensive community issues. I've written a bit about it over here[1] and you can check out Johan Janssens (Joomla co-founder in exile) blog[2] for more in-depth analysis. The bottom line is - take a look at Nooku[3] - especially if you're looking for a framework that makes sense (a corresponding CMS is underway). [1]http://valanx.org/index.php?option=com_content&view=article&id=140:going-forward-from-joomla&catid=25:skore-blog&Itemid=99 http://valanx.org/index.php?option=com_content&view=arti... [2]http://johan.janssens.me/ http://johan.janssens.me/ [3]http://nooku.org/ http://nooku.org/