Presentation given to the DU ASIS&T student chapter's TechBytes session on January 30, 2102.
- 1. Ten Things IveLearned AboutDrupalNina McHalemilehighbrarian.net
2. Thing 1: Talk the Talk 3. Thing 1: Talk the Talk Takethe time to learn the terminology You will save time in the long run You will be able to follow documentationmore easily Resource: Drupal Glossary drupal.org/glossary 4. Thing 2: Start with a Sandbox 5. Thing 2: Start with a Sandbox Drupal Gardens: Free, hosted sandbox:drupalgardens.org Acquia Dev Desktop: A bundle of Drupal, Apache, MySQL and PHP todownload to your computer: network.acquia.com/downloads Caution: Do NOT use bundled software inproduction, as they are often not secureenough out-of-the-box for live environments 6. Thing 3: I Probably Have TooMany Content Types 7. Thing 3: I Probably Have TooMany Content Types Create content types conservatively Avoid modeling content types on the orgchart Take a user-centered approach to content External users (customers) Internal users (staff) Resource: Tips for Creating Drupal ContentTypes for Library Web Sitesmilehighbrarian.net 8. Thing 4: If I Cant SeeIt, Permissions Are Set Wrong 9. Thing 4: If I Cant SeeIt, Permissions Are Set Wrong Asyoure developing, you may often findyourself surprised that what you (thoughtyou) just created isnt there Every time you add a module, permissionsneed to be granted accordingly If your user cant see it, be sure to checkthe permissions of role that user is assignedto 10. Thing 5: Build First. Then Theme. 11. Thing 5: Build First. Then Theme. Stephanie Pakrul, Foundation Drupal 7 Develop custom content types first You cant hang the curtains until thehouse is built Tip: Use a highly configurable theme tochange colors, font, and add your logowhen developing so that the site feelslike yours. 12. Thing 6: Make Life Easy forContent Creators 13. Thing 6: Make Life Easy forContent Creators Give them exactly what they need, and nomore, to do their jobs on the web site Use the principle of least privilege While very few people might actually set outto sabotage the librarys web site, when theyhave too many options, they can becomeoverwhelmed Resource: Improving the Drupal UserExperience journal.code4lib.org/articles/4578 14. Thing 7: Theres a Module for That 15. Thing 7: Theres a Module for That Todate, there are 9545 modules If you seek functionality beyond whatsincluded in core, check modules Most popular: Views Pathauto WYSIWYG Google Analytics 16. Thing 8: Keep It Up, Back It Up 17. Thing 8: Keep It Up, Back It Up When you adopt a CMS, you adopt amaintenance and backup regime Maintain core, modules, at planned, regularintervals Back up directory structure and database asneeded A site that is not regularly maintained willbreak beyond repair A site that is not kept current will eventuallybecome a security threat unto itself, andpossibly its home environment 18. Thing 9: Get Connected Find out who in your local community develops in Drupal Join their mail list Go to local meetups Find out what libraries (everywhere) similarto yours are doing Create a professional network in whichyou can get help, ask questions, growideas, and collaborate 19. Thing 9: Get Connected Makean account on drupal.org: Join the Libraries group: groups.drupal.org/libraries Join the drupal4lib mailing list: drupalib.interoperating.info/node/88 Watchfor ALA LITA Drupal IG activities:connect.ala.org/node/71787 GO TO DRUPALCON DENVER! 20. Thing 10: Do it The Drupal Way 21. Thing 10: Do It The Drupal Way Drupalis very flexible, extensible, andmodular; respect this! Design: create a subtheme rather thanaltering theme files directly Function: Do not hack core! If you wish to develop functionality that isnot in core, see if theres a contributedmodule If not, develop the module 22. Questions? Commentsemail@example.com