Difference between Drupal, Joomla and Wordpress

dfdsf

Multi-User Publishing	Drupal	Joomla!	Wordpress
Content Nomenclature	A Node is any content item. The following are specific types of nodes: Story (article with intro/teaser and main body text fields), Page (static content), and Book (a collection of related pages geared toward collaborative authoring). Books are deprecated	Static Content (Pages) in 1.0 and Articles (Can have an intro text and paginated divisions with an automatically generated table of contents.)	Pages and Posts (Articles). Excerpts and custom fields for posts. Custom fields for pages. Pages can be nested in parent-child relations.
Customizable content types, categories, and organizational logic	Yes, extensible. Content types can be endlessly created and customized. The core Taxonomy module allows customization of the ways content types can be classified according to vocabularies (categories) and terms (subcategories). Further possibilities with tagging modules. Content ordering has improved in 6 but remains janky.	Limited. A fixed section/category structure requires tagging extensions for greater flexibility. A few new commercial extensions exist for creating custom content types. You can have an unlimited number of sections and categories, but every category must have a section. Every content item that is not static must have a section and category or (in 1.5) be uncategorized. In 1.5 uncategorized content replaces static content. Content cannot be assigned to more than one section or category. Content hierarchies three levels deep or greater are created by parent-child item relations in menus. It’s relatively simple to exercise great control over content ordering on the front end and how it appears or is filered in the back end.	Yes, extensible. Page ordering is admittedly “janky” in 2.6 with improvements promised.
WYSIWYG rich text editors [A necessary convenience that will create code that won’t validate according to W3C standards if you let it.]	No, extensible. No rich text editor packaged in basic installation, but you can install several options, including TinyMCE and FCKeditor.	Yes, extensible. Packaged with TinyMCE and a simpler editor. JCE is the most popular editor extension for Joomla similar too but more powerful than tinyMCE. JCE can upload and manage files, resize and crop graphics, create thumbnails, galleries, slideshows, lightbox style effects, etc. JCE’s layout and features can be customized and vary depending on user/group permissions. Yes, extensible.	Yes, extensible. Packaged with a basic rich text editor. TinyMCE and FCKeditor can be installed.
Text filters and lightweight markup [Fine-grained typographical control without full, direct HTML coding or the invalid hash WYSIWYG editors and the Windows-1252 character set often create.]	Markdown with SmartyPants module. Markdown, Tipogrify, Textile.	Textile, Markdown and SmartyPants plugins for 1.0.	Texturize and Textile plugins. Text Control plugin Text Control allows choice of Markdown, Textile1, Textile2, nl2br, WPautop, and "No Formatting" long with the choice of SmartyPants, WPTexturize or "No Encoding" for character encodings. `
Backend administrative interface	No, While it’s possible to use an administrative template that will create a heightened appearance of a back end, there is no clear frontend/backend separation, which can be disorienting. While Drupal 6 has some convenience improvements (like AJAX) and maintains a clean, lightweight, non-graphical design, it’s not well organized. It’s hard to find your way around, even on a basic installation, and even if you learn to love Drupal’s UI, it forces you to takes longer to do many tasks than it should, especially on a heavily extended installation. This is a major drawback to the common user and has been identified as such in recent usability studies, so Drupal is aiming to improve in this area.	Yes. The administrative interface is extremely attractive, uses space well, and is decently organized according to standard interface design principles. It’s easy to find, alter, and move content and modules quickly even in a highly customized installation with many extensions. The UI is lot prettier than Drupal and Wordpress with a lot of icons, dropdown menus, and AJAX, but some of the global content settings are rather buried, and the template manager has an unnecessary extra level of depth.	Yes. A clean, lightweight, and wellorganized interface with very few graphical elements based on standard interface design principles. In its default form it’s not attractive or elegant, and wastes space more than Drupal.
Create and edit pages through front and back end	Yes--it’s all one interface	yes	Depends on template. To edit articles on the front end, you need a template coded to allow this.
Workflow system	Basic, extensible, improved in 6. Multiple extensions give you a lot of control over creating a largely automated workflow system to your specifications. Default configuration allows basic roles-based draft and publishing management.	Basic, extensible. Multiple workflow extensions. Default configuration allows basic roles-based draft and publishing management	Basic, extensible. Simple workflow system by default with Zensor plugin. Default configuration allows basic roles-based draft and publishing management
Revision tracking	Basic  extensible	No extensible but limited options	Yes  new in Wordpress 2.6
Internal messaging for writers, editors, others,etc.	No, extensible	Yes, for backend users. Extensions for general PMS.	No
Nomenclature	Themes and Templates. Templates are page-specific layouts within Themes that correspond to template overrides in Joomla 1.5.	Templates. The term refers to what Wordpress and Drupal users refer to as Themes. Template overrides in Joomla 1.5 correspond to templates and theme overrides in Drupal.	Themes and Templates. Same as Drupal, but Wordpress users seem to refer to templates and themes more interchangeably. Technically templates govern specific page layouts and bundled together constitute a theme.
Edit templates from within the administrative interface	No	Yes. Typically the master index and its associated stylesheets, though it should be possible to include any number of files. Cannot create new template files within the interface.	Yes. Master index, category indexes, and page templates. … XXX
Use multiple templates	Limited, extensible and complicated. You can install multiple themes, but only one can be active as an administrative theme (activates when an admin user is logged in) and one as a front end theme. Templates within a theme and overrides can be coded for more granular theming. Users can be allowed to pick and change active themes and select a theme that will be used on their pages.	Yes. Multiple administrative and front end templates can be installed through the administrative interface with one of each assigned as the default. Additional templates can be installed and assigned to designated pages within the administrative interface’s template manager. Users can be allowed to pick and change active templates. With JCE content items templates can be selected within the content editor where they will then appear.	Limited. Categories, index pages, and static pages can have their own themes or templates, and these can be edited within the administrative interface. Page templates can be selected within the page editor where they will then appear.
Assign modules/blocks/widgets to any page from within the administrative interface	Yes, but managing these assignments on a large site can be extremely difficult. It requires typing the alias or node number of every page on which a block is/is not to appear. Drupal’s blocks correspond to Joomla’s modules.	Yes, but with a few limitations. Modules can be assigned to all pages or menu items very quickly by clicking a list of menu items on every module’s page in the back end, but pages that are not directly associated with a menu item can’t have modules assigned to them unless they are designated to appear on all pages. There is no option to make a module appear on all pages except designated pages.	Yes, but it’s klunky and limited to being a collection of accessories for blog sidebars without a lot of adaptation. Widgets dimly correspond to blocks in Drupal and modules in Joomla, but they have a long way to go before they’re as useful. Themes and plugins can be “widgetized.”
Create and manage menus within the administrative interface	Yes	Yes	No, extensible. Several plugins give control over menus on the front end and/or administrative interface.
Customizable content page layouts and forms	This is done via template overrides, use of the Drupal API, CCK/Content Creation Kit and the Views modules aided by various developer tools and extensions.	This can be done in a limited way via multiple template assignments within the administrative interface. Template overrides in Joomla 1.5 allow more granular control, as do various commercial extensions for forms and content.	Requires direct coding of theme files, overrides, and use of the Wordpress API.
Template engines available	Yes. PHPTemplate has been adapted into Drupal, PHPTal, Smarty, Zen. A certain degree of confusion and lack of standardization prevails.	Limited. Plugin for TBS/TinyButStrong in 1.5. Some basic web-based generators There seems to be little interest in these tools.	No. Basic template generators, WordPreciouss plugin, typical practice is to do all or most design coding from scratch.
Complexity and learning curve for original design	Steepest – If you’re not content to make minimal changes to a stock template, the path to a good, unique template is complex and vexing. It may take a number of extensions, overrides, and understanding of the API to exercise very granular control over page layout and appearance. Drupal requires considerable forethought and work to create a template that doesn’t look bloggy/has more than 2-3 basic page layouts.	Least steep – the major PHP/HTML/CSS coding can be done from within the administrative interface. The module and template managers let you alter page appearance very quickly in Joomla. This is far less so in Drupal and not at all the case in Wordpress. Like the others, advanced, granular page design requires use of template overrides. This is done via the Model View Controller (MVC), which is new in Joomla 1.5. so it’s capabilities have not yet been widely realized.	Steep – The major coding can be done from within the administrative interface, but you’ll need to get into the API to do anything advanced. The way is welldocumented and arguably simpler to learn than with Drupal, but Wordpress lacks a system for automatic script includes whose position and appearance is controlled through the administrative interface. (E.g., Drupal’s blocks or Joomla’s modules.) Wordpress requires considerable forethought and work to create a template that doesn’t look bloggy/has more than 2-3 basic page layouts.
Reception and use by designers and general users	Drupal seems to have had a hard time getting traction with HTML/CSS gurus, but there are a few. Drupal does not fully separate design and content, a major taboo, but it may not be as bad an offender as Joomla in this regard. Advanced design requires some use of Drupal’s API and an advanced understanding of its inner workings. This results in most people using cookie-cutter templates on their Drupal sites. Most Drupal templates seem to include very few block positions, probably because of the greater complexity of creating these positions and managing blocks in Drupal’s interface. The result is a common 3-column bloggy look.	Joomla does not seem to be popular with HTML/CSS gurus, possibly because it was not built as a blogging platform and does not fully separate design and content. Joomla actually uses tables for layout unless prevented by template overrides in Joomla 1.5. Despite this situation, high quality design is common in the popular commercial template market, but it tends to be heavy—thick with javascript eye candy, possibly at the expense of certain design fundamentals. Cookie-cutter Joomla sites with generic templates have become fairly uncommon, but this does not imply the existence of a user base that understands and values depth of quality in design.	Wordpress is probably the most popular CMS among HTML/CSS gurus—most likely because it covers all the bases of standards compliance, simplicity/low bandwidth, design/content separation, and SEO. The pack leaders in open source web design have produced widely used and imitated themes for Wordpress that typically have a minimalist design concept. Since Wordpress is fundamentally a blog engine without anything to compare to Drupal’s blocks and Joomla’s modules, most themes have the bloggy 2-3 column look.
Availability and quality of ready-made templates	Many free templates, some commercial providers, relatively few templates of high quality available by either means compared to Joomla and Wordpress. Most templates created before 2006-07 are junk. Most templates reflect a blog design concept.	Huge number of free and commercial templates, many of high quality and bundled with special scripts and extensions high on eye candy. Most templates created before 2006-07 are junk—narrow fixed width and frequently loaded with tables— but Joomla templates have always included a dozen module positions, creating great flexibility and a non-bloggy appearance. The best Joomla templates today are inexpensive but not free. They typically include documentation, support, .PSD source files, a dozen collapsible (even draggable, minimizable) module positions, several fixed widths and a fluid/variable width option, multiple color options and light/dark sub-themes plus additional scripts--all of which can be controlled in the template manager within the administrative interface. As a result, Joomla produces sites out of the box whose appearance befits a robust enterprise CMS, not a blog. A lot can be done with a little knowledge, which might be regarded as dangerous in some respects.	Large quantity of mostly free templates, many high quality, focus on lightweight and standards compliant design. Junk templates seem to have been rare from the beginning. Since Wordpress is a blog engine and most of its users are bloggers, most Wordpress templates look like blogs, but this may be changing and there are a lot more options than Drupal has.

Want to outsource your projects or services to India then you can contact directly to Author (Mukesh Pandey) is an online marketing expert with lot of technical writing and content management experience. He had worked with many MNC’s. You can contact him by simply emailing him on : mukeshpandey82@gmail.com. An offshore outsourcing company with lot of exposure in Ecommerce and Writing Services: Esteem Web Solutions Company for CAD Services contact:CAD & CAM Services Company.