[drupal-docs] Drupal vs Mambo

[Charlie Lowe]

Morbus Iff wrote:
> 
> Yah. User profiles. Ones I've done are based on skill
> level: http://www.libdb.com/project_goals#profiles
> 

...

> 
> I'm not sure I entirely like that breakdown (they meld too much, IMO),
> but I coulda swore there was previous discussions on this list regarding
> profiling like that (regarding how the books should be split, I 
> thought). I wasn't paying attention to that discussion, however.
> 

Hmmm...Not quite profiling. It's more of a rhetorical approach to 
organizing the features/concepts into scannable sections. And you are 
right about there being some overlap. The idea is to go from general 
user to more advanced users to developers with the "overlap" generally 
showing up in the earlier section but not repeated in the latter.

I guess it makes more sense in my mind at the moment :) Here's what's 
sort of floating around in my head (very rough outline). Each would need 
to be expanded to include features that apply:

[all of this on one, scannable page]

[general intro paragraph about Drupal]

*Users* Drupal allows users to easily publish content to the web (text, 
html, graphics). Connects users in communities (forums, weblogs, 
comments. Has some popular social software capabilities. Constantly 
refined for usability.

*Site administration* Administration menu provides system logs, access 
control, module settings, help

*Web design*.  Powerful theme system. Taxonomy for organizing content. 
Flexibility because of node architecture as basic content type. Block 
and menu modules for further site architecture flexibility.

*Development* Scalable, modular, secure, API, clean code, active 
community, GPL