A slide deck that can be used for introducing some of the main features of Drupal to enterprises. This is a relatively high-level (mostly-non-technical) presentation geared toward an audience that has little or no previous knowledge of Drupal, but it familiar with general concepts of content management systems.

1. Evaluating Drupal for the
Enterprise

2. Can Drupal succeed in
the enterprise?

3. Yes.
(short answer)

4. Verizon

5. Fast Company
Verizon

6. Nokia
Fast Company
Verizon

7. Nokia
Fast Company
Verizon
Examiner.com

8. Nokia
Fast Company
Verizon
AOL
Examiner.com

9. Nokia
Fast Company
Verizon
AOL
WhiteHouse.gov
Examiner.com

10. Nokia at&t
Fast Company
Verizon
AOL
WhiteHouse.gov
Examiner.com

11. Nokia at&t
Fast Company
Verizon
AOL Sony Music
WhiteHouse.gov
Examiner.com

12. Nokia at&t
Yahoo! Fast Company
Verizon
AOL Sony Music
WhiteHouse.gov
Examiner.com

13. Nokia at&t
Yahoo! Fast Company
Verizon
AOL Sony Music
Grammys.com
WhiteHouse.gov
Examiner.com

14. Nokia at&t
Yahoo! Fast Company
Verizon
AOL Sony Music
U.S. House of Representatives
Grammys.com
WhiteHouse.gov
Examiner.com

15. How?
(long answer)

16. Modular Architecture

17. No vendor lock-in

19. Content Management
System

20. Content Management
Framework

21. What is a content
management system?

22. What is a content
management system?
A content management system (CMS) is the collection of procedures
used to manage work flow in a collaborative environment.
http://en.wikipedia.org/wiki/Content_management_system

23. CMS

24. CMS
• Database-driven repository of content

25. CMS
• Database-driven repository of content
• Robust taxonomy

26. CMS
• Database-driven repository of content
• Robust taxonomy
• User roles and permissions

27. CMS
• Database-driven repository of content
• Robust taxonomy
• User roles and permissions
• Flexible display of content

28. CMS
• Database-driven repository of content
• Robust taxonomy
• User roles and permissions
• Flexible display of content
• Separate data from presentation

29. CMS
• Database-driven repository of content
• Robust taxonomy
• User roles and permissions
• Flexible display of content
• Separate data from presentation
• ...and much much more

30. What is a content
management framework?

31. Build and Extend

32. Build and Extend
• Over 7,000 contributed modules

33. Build and Extend
• Over 7,000 contributed modules
• Extendable developer framework (PHP)

34. Build and Extend
• Over 7,000 contributed modules
• Extendable developer framework (PHP)
• Back office integration via web services or
direct API integration

35. Build and Extend
• Over 7,000 contributed modules
• Extendable developer framework (PHP)
• Back office integration via web services or
direct API integration
• Rabid developer community

36. Content Aggregation

37. Content Aggregation
• RSS

38. Content Aggregation
• RSS
• Other databases

39. Content Aggregation
• RSS
• Other databases
• Other APIs

40. Content Aggregation
• RSS
• Other databases
• Other APIs
• Bi-directional

41. Scaleability

42. Scaleability
• Multiple caching mechanisms

43. Scaleability
• Multiple caching mechanisms
• CSS and JavaScript aggregation

44. Scaleability
• Multiple caching mechanisms
• CSS and JavaScript aggregation
• PHP caching

45. Scaleability
• Multiple caching mechanisms
• CSS and JavaScript aggregation
• PHP caching
• Memcache

46. Scaleability
• Multiple caching mechanisms
• CSS and JavaScript aggregation
• PHP caching
• Memcache
• Content delivery networks

47. Scaleability
• Multiple caching mechanisms
• CSS and JavaScript aggregation
• PHP caching
• Memcache
• Content delivery networks
• Multiple web heads and database servers

48. What makes Drupal
great?

49. Community

50. Community
• Over 800,000 registered users on drupal.org

51. Community
• Over 800,000 registered users on drupal.org
• ~4,000 committers

52. Community
• Over 800,000 registered users on drupal.org
• ~4,000 committers
• ~3,000 people at DrupalCon Chicago (March, 2011)

53. Community
• Over 800,000 registered users on drupal.org
• ~4,000 committers
• ~3,000 people at DrupalCon Chicago (March, 2011)
• ~240 people at Florida DrupalCamp 2011

54. Community
• Over 800,000 registered users on drupal.org
• ~4,000 committers
• ~3,000 people at DrupalCon Chicago (March, 2011)
• ~240 people at Florida DrupalCamp 2011
• Dedicated security team

55. Community
• Over 800,000 registered users on drupal.org
• ~4,000 committers
• ~3,000 people at DrupalCon Chicago (March, 2011)
• ~240 people at Florida DrupalCamp 2011
• Dedicated security team
• “Come for the code, stay for the community.”

56. Training and Support

57. Training and Support
• Acquia - led by Dries Buytaert, Drupal project lead

58. Training and Support
• Acquia - led by Dries Buytaert, Drupal project lead
• Lullabot

59. Training and Support
• Acquia - led by Dries Buytaert, Drupal project lead
• Lullabot
• Mediacurrent

60. Training and Support
• Acquia - led by Dries Buytaert, Drupal project lead
• Lullabot
• Mediacurrent
• MindComet

61. Training and Support
• Acquia - led by Dries Buytaert, Drupal project lead
• Lullabot
• Mediacurrent
• MindComet
• DrupalEasy

62. Distributions

63. Distributions
• Open Atrium - “intranet in a box”

64. Distributions
• Open Atrium - “intranet in a box”
• Acquia Drupal - core + common modules

65. Distributions
• Open Atrium - “intranet in a box”
• Acquia Drupal - core + common modules
• Drupal Commons - online communities

66. Distributions
• Open Atrium - “intranet in a box”
• Acquia Drupal - core + common modules
• Drupal Commons - online communities
• Pressflow - high-performance Drupal

67. Distributions
• Open Atrium - “intranet in a box”
• Acquia Drupal - core + common modules
• Drupal Commons - online communities
• Pressflow - high-performance Drupal
• COD - conference organization

68. Distributions
• Open Atrium - “intranet in a box”
• Acquia Drupal - core + common modules
• Drupal Commons - online communities
• Pressflow - high-performance Drupal
• COD - conference organization
• Managing News - RSS/Atom based news tracker

69. Taxonomy

70. Taxonomy
• Defined vocabularies

71. Taxonomy
• Defined vocabularies
• Free tagging

72. Taxonomy
• Defined vocabularies
• Free tagging
• Hierarchical vocabularies

73. Taxonomy
• Defined vocabularies
• Free tagging
• Hierarchical vocabularies
• Shared across multiple types of content

74. Code

75. Code
• Always looking forward

76. Code
• Always looking forward
• Not afraid to modernize APIs

77. Code
• Always looking forward
• Not afraid to modernize APIs
• Never gets stale

78. Code
• Always looking forward
• Not afraid to modernize APIs
• Never gets stale
• Aggressive development pace

79. Code
• Always looking forward
• Not afraid to modernize APIs
• Never gets stale
• Aggressive development pace
• Testing framework

80. Code
• Always looking forward
• Not afraid to modernize APIs
• Never gets stale
• Aggressive development pace
• Testing framework
• Total control of your site

81. What makes Drupal
difficult?

82. Challenges

83. Challenges
• Learning curve

84. Challenges
• Learning curve
• Finding developers

85. Challenges
• Learning curve
• Finding developers
• Complex admin area for site administrators

86. Enterprise-Specific
Challenges

87. Enterprise-Specific
Challenges
• Limited paid support options

88. Enterprise-Specific
Challenges
• Limited paid support options
• Finding developers available for full-time hire

89. Enterprise-Specific
Challenges
• Limited paid support options
• Finding developers available for full-time hire
• Shifting to an open-source mindset

90. Wrap Up

91. Drupal is...

92. Drupal is...
• A web application framework

93. Drupal is...
• A web application framework
• Community-strong

94. Drupal is...
• A web application framework
• Community-strong
• Always moving forward

95. Thank you
Presentation created Feb, 2011 by Michael Anello - @ultimike - michael@anelloconsulting.com