Your SlideShare is downloading. ×
 Introduction to drupal
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Introduction to drupal


Published on

Introduction to Drupal

Introduction to Drupal

Published in: Education, Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Core Drupal is kept slim and mean, with much added functionality coming by way from community module.
  • Transcript

    • 1. Introduction to DrupalJune 14 , 2013
    • 2. Agenda Introduction to CMS Why Drupal as CMS, Comparison of Drupalwith other CMS. Case studies / Sites using Drupal When to and not to use Drupal ? Where to find drupal and drupal installation ?2
    • 3. Content Management Systems3WebsiteDatabasePublisherReader
    • 4. Open Source CMS4
    • 5. DrupalCome for the software, stay for thecommunityDrupal is an open source content managementplatform powering millions of websites andapplications. It’s built, used, and supported byan active and diverse community of peoplearound the world.5
    • 6. What is Drupal ?• Content Management System (CMS)• Web Application Framework• Open Source• Runs on Apache, PHP and MySQL (PostgreSQL)• Software package which can be customized tocreate websites• And most importantly its FREE!!!! 6
    • 7. drupal-6.9.tar.gz1052 KBWebsites Using Drupal
    • 8. Drupal v/s. other CMS• Open source• Clear, well-documented API• Flexibility• Large User Community• Responsive & Approachable Developer Community• Secure8
    • 9. Drupal is Open Source• No license fees• The code is completely open and transparent.• If we find a bug in Drupal, we can report it, fix it ourselves,and contribute the fix back to the community rather thandepend on the original development team to fix the bugs.• So, Drupal is owned by you, Yes YOU9
    • 10. Clear, well-documented API– Various clients, various requirements BUT you have Drupal– Saves time, effort and money10
    • 11. Flexibility– Get new feature updates with just a click away!– Modular codebase : Simpler, more robust, fast andextendable easily.– User friendly APIs– Change anything, Build anything11
    • 12. Large User Community– Drupal has a strong community of users.– More support , more diversity and less problems solvingtime» 18,128 Modules» 1,491 Themes» 475 Distributions» 20,501 Developers12
    • 13. Responsive & Approachable DeveloperCommunity– Bugs and security issues are quick fix : SpeedDevelopment– Drupal development community : Smart and scrutinized– User feedback is sought, and the development process isvery transparent.13
    • 14. Security• Drupals codebase is very secure.• Prevented from potential exploits.• Combined with the simplicity of keeping Drupal up-to-date,makes it secure.• Patch availability security of previous versions of modules andthemes.14
    • 15. Drupal over a custom application• Writing a custom application is required for a clients website– User authentication & authorization, content theming and display, isalready part of Drupal.– Using existing code is far more• Cost-efficient• Large Developer Community• Secure• Feature complete than within a reasonable budget and timeframe.15
    • 16. Will we use Drupal forever?• At this point in time, we feel that Drupal is the best CMS– There are hundreds if not thousands of other CMS platforms available– There could very well come a time when we feel that it is time to moveaway from Drupal to another platform.• New CMS coming in clearly need to surpass Drupal not only infeatures, but also in philosophy and community. This is the beauty ofopen source –“the tools we use are what we make them”16
    • 17. The bottom line• For most of the projects we build for ourclients results in– Better product– Better price– Smart Resource Usage– Speed Development17
    • 18. Frameworks vs. CMS18Out of the Box FunctionalityFlexibilityProgrammer ZonePublisher Zone
    • 19. Case Studies• The Economist:• Linux Journal:• Our Media:• Now Public:• Gnome Art:• Ubuntu & Cononical:,• IloveBolly:
    • 20. Do it with Drupal20• Share RequirementsDocument• Multilingual• Content• Search• Views• Ads• SEO• Videos• Pictures• Blogs• Recipes• TV Show
    • 21. When not to use Drupal?21• Big Question? What Drupal can’t do wrtyour requirements?• Drupal => CMS + CMF (Partial)• Drupal has a set of predefined workflows.
    • 22. When not to use Drupal?• In Short,• Specifications to meet Drupal’s predefined workflows• Cost Effective – Use Drupal.• If– Too many things fighting against the way it is designed towork,– it becomes clumsy,– slow and expensive – Go for PHP framework such as Zendor SymfonyGOOD News: Drupal 8 will use Symfony as its Framework!!!22
    • 23. Selecting a CMS OR Framework• Dont Let the High Stakes Paralyze You• Prioritize Vision before Detail• Construct Leading Requirements:– Filter for Relevant Technologies– Filter for Your Budget– Consider the Proximity of Community23
    • 24. Where to find Drupal and DrupalInstallation?••<modulename>•
    • 25. Questions?25