Keeping your Modules Healthy - Powerpoint
10
Date 7-24-15 Keeping your Modules Healthy By Patrick Koroma @ptkoroma
-
Upload
patrick-koroma -
Category
Documents
-
view
81 -
download
0
Transcript of Keeping your Modules Healthy - Powerpoint
Date 7-24-15
Keeping your Modules Healthy By Patrick Koroma @ptkoroma
Types of Modules
Core
Contrib.
Custom
Need to keep them Healthy
Need to keep them Healthy
Security
Performance & Optimization
New Features
Future Friendly
Author
Drupalgeddon
Author
Page Speed No have duplicate modules
Author
Ability to have access to and use added features - Webform Views Suite - Slideshow - Views- pane
Author
Ready for future enhancemnt either with Contrib. or Custom code - Making sure that your code base is up to date to use Third Party code
Tools and Tips
Version control - GIT
Update Manager
Clean Missing Modules
Missing Module
Follow security news
Timely Update
Vendors
Don’t hack modules Drush - Jennifer Lea Lampton
Coder
Contrib. Vs Custom
PHPCSS HTML5
JavaScriptJQuery
Author
Frequency and LOE you put in to keeping your modules healthy will be influence by the makeup of your code base i.e. your use of contrib. or custom modules.
Why Contrib.
Ease of finding a solution to your Drupal problems - If you have a need there is probably a modules for it
Bug fixes developed by Drupal community
New features developed by Drupal community
Maintainability and meeting the current Drupal standards
The benefit of been part of a vibrant community will urge to contribute to the community
Why to go Custom.
Copyright © Theodoros Ploumis
Did you search and ask enough people?Are you sure that the problem you are about to solve needs a new module and not some combination of existing Drupal modules or modifying your requirement ?
Can you build a module?
Are you sure there is no Drupal module to do your job? - Blair Wadman
Why to go Custom.
• Performance/scalability: You can do just what you need to do, and don’t need to consider other use cases.Logintoboggan has a vast feature set for customizing login functionality, but if I just want to use a tiny feature of it, I will not use it as I don’t want the weight or chance of introducing bugs from the unneeded functionality.
• Simplicity: The use of multiple contrib. modules just to solve one problem can lead to getting more code configuring then the actual functional code(if using features to export configuration,). Small features that generically would require much more processing. For example, auto node title is a great module for configuring an automatic title; however, it requires use of tokens and additional other processing To do it oneself could be around 5 lines instead. This types are things are generally gathered in a single module when developing a single site.
• Stability: You don't need to worry about new features introducing new bugs or undesired functionality.
Tendency to clog you're your code base and have 2 modules doing the same thing in your site when you can have one.
Resources
Go Custom Or Use A Contributed Module?
Keeping Your Drupal Site Up To Date With Git And Drush
The Beginner's Guide to Drupal Security Releases
Eleven tips to keep Drupal up to date with security releases
5 Tips for Keeping Your Drupal Site Organized
When Should I Create A New Drupal Module?
