The document compares two popular open source content management systems, WordPress and Drupal. It discusses their communities, use of web standards, themes and customization options, and other features. Both systems have large, active communities that contribute to their ongoing development. WordPress uses web standards and has an easy-to-use interface for creating themes. Drupal provides more flexibility and power through its module system and theming architecture, which allows for deeper customization.

1. OPEN SOURCE CONTENT MANAGEMENT SYSTEMS A LOOK AT TWO POPULAR CMS SYSTEMS, WORDPRESS & DRUPAL

2. WHICH CMS IS RIGHT? Many people struggle with the question of which CMS is best for their application. So let’s debate them. Open Source Commercial Build Your Own

3. The Great Debate - or -

4. Open Source thrives on community. How are Wordpress & Drupal’s communities? Community

5. Wordpress: Community The Community is what drives Open Source. Widespread Well Informed Constant Development Very Opinionated Corporate Uses

10. Sure it it a cool system…but how the hell do you use it!?!? Documentation & Source Code

13. Standards…we don’t need no stinking standards. Web Standards

14. Wordpress: Web Standards XHTML/CSS Dependent upon Designer JS Frameworks

15. Who is your daddy and what does he do? Suitability and Usability

16. Mais…dat site looks beautiful…how you did that? Theme Creation

17. Index.php header.php style.css footer.php THE LOOP Sidebar.php Contains XHTML/CSS info, constant header, etc. The heart and soul of Wordpress Themes, calls to the database for the content. Close off the HTML document, other information. Contains navigations, widget, other code.

18. Drupal: Community “ Don’t Hack Core” “ The Drop is always moving” Corporate backed (Acquia, IBM, Yahoo)

19. Drupal: Terminology Blocks – Navigational Aides / Sidebar Items Node – Content stored in Drupal. A site can have multiple nodes types (page, story, poll, event) Taxonomy – Powerful Category System Module – Add-on that provides extra functionality Hook – Programming Call to Change Behavior Path – The URL used to determine which function to call

20. Drupal: Common Hooks hook_menu – Defines Menu Items and Page Callbacks hook_perm – Defines user permissions hook_nodeapi – Acts on nodes defined by other modules hook_db_rewrite_sql – Rewrites database queries

21. Drupal: Themeing Supports Multiple Engines including Smarty, and PHPTAL PHPTemplate is the default engine Using PHP is okay, too.

22. Drupal: Theme Creation PHPTemplate allows you to override the look of certain pieces of a site by creating *.tpl.php files. node.tpl.php block.tpl.php page.tpl.php page-front.tpl.php It also allows you to define down to be more specific page-user-1-edit.tpl.php would override the look of the edit page for user #1.

23. Drupal: Multisite It is possible to use the same code base to run multiple sites The /sites folder naming scheme determines which site’s settings and database to use. test.coreb.net can be setup to use a different database by making a new folder /sites with a new settings.php file. /sites/net.coreb.test and /sites/net.coreb can run different sites. You can also share database tables between sites.

24. Drupal: Other Features Inline Editing - “Viewing a page and editing a page are almost the same” Multiple Database Support – MySQL, PostgreSQL officially supported Community Support for Oracle, DB2, and MS SQL Server Cache - Depending on the settings, Drupal will cache portions of the site to speed page load time. Developers are also able to utilize this cache. JQuery – The JQuery engine has been in Drupal Core since version 5. Localization – Locale Module allows a site to be translated into different languages (string replacement)

25. Drupal: Other Features Install Profiles – Allows you to customize the initial installtion with specific modules and settings. (Blog, Wiki, News, Conference) Powerful APIs – Form API, Content Construction Kit, View, Actions

26. Widescreen Test Pattern (16:9) Aspect Ratio Test (Should appear circular) 16x9 4x3