Selecting Modules for a Successful Drupal Project

Techniques to pick well-written, supported, and secure modules to help make your Drupal projects successful.

Transcript

1. Selecting Modules for a Successful Drupal Project
2. Intro 2 Mark Shropshire (shrop) @shrop Mark brings 20 years of experience leading technical teams to his role as Mediacurrent’s Open Source Security Lead. He is a leader in tech community organizing, blogging, podcasting, and public speaking within the Drupal community. Mark is passionate about architecting systems to solve workflow problems and improve efficiencies using open source software. Mark is the maintainer of the Gaurdr Drupal security module suite. Over his 20 year career leading technical teams, Mark gained experience in IT roles at a large urban research university and nationally recognized, award winning graphic communications company. Open Source Security Lead /in/markshropshire
3. About 3 Mediacurrent helps organizations build highly impactful, elegantly designed Drupal websites that achieve the strategic results they need. • Single-source provider • Specializing in Drupal since 2007 • Headquartered in Atlanta, GA • Team of 60+ Drupal Experts including development, design and strategy • Clients include: Large Enterprise and high- profile global brands
4. Style Guide Contents Define the requirements Selecting a module Community contribution 4 3 2 1 4 What are the options?
5. Define the requirements 1
6. 6 Well written software requirements ensure solutions that satisfy users and reduce risk. Define the requirements
7. 7 Software requirement patterns • User stories • Test scenarios • Wireframes and diagrams • Documentation Define the requirements
8. 2 What are the options?
9. 9 Custom module • Maximum flexibility • Security risks • More expensive What are the options?
10. 10 Single-purpose Drupal module • Possible if requirements are narrow • Must accept module’s feature set • Possible cost savings • Improved support because open source • Improved security because open source What are the options?
11. 11 Multiple contrib/custom Drupal modules • Small building blocks working together • Possible cost savings • Improved support because open source • Improved security because open source What are the options?
12. 3 Selecting a module
13. 13 Search! Always search for existing modules. There are often several modules/solutions available. Reference: https://www.drupal.org/node/340271 and https://www.drupal.org/node/266179 Define the requirements
14. 14 Review a module’s project pages • Known and/or active maintainers? • Number of module downloads • Maintenance/development status • Issue queue health Reference: https://www.drupal.org/node/1066982 Selecting a module
15. Review a module’s project pages 15 Example: https://www.drupal.org/project/oauth Selecting a module
16. 16 Review the code • Drupal API usage • Run phpcs and review results • Identify security issues • Module architecture review Reference: https://www.drupal.org/coding-standards Selecting a module
17. 17 Tools to evaluate modules • Drupal VM • Drush quick-drupal • simplytest.me Selecting a module
18. 18 What about themes, distros, and other projects? • Module review process applies • Further testing could be required Selecting a module
19. 19 Drupal 7 vs. Drupal 8 • Review process very similar • Expose Drupal 7-isms that should not appear in Drupal 8 projects • Coding standards differences • Great opportunities for community contribution Selecting a module
20. 4 Community contribution
21. 21 How can I get involved in the community? https://www.drupal.org/getting-involved-guide Q A Community contribution
22. 22 How can I contribute to development? https://www.drupal.org/contribute/development Q A Community contribution
23. 23 What to do if a module isn’t supported and/or the maintainer isn’t responsive? https://www.drupal.org/node/251466 Q A Community contribution
24. @Mediacurrent Mediacurrent.com Q&A slideshare.net/mediacurrent