Why Drupal is Rockstar?
0 likes941 views
The document outlines a presentation on becoming a "rockstar" with Drupal. It discusses Drupal's large open source community and code base. It covers best practices for code structure, naming conventions, deployment strategies like Features and Configuration Management. It also summarizes caching options like Memcache, Varnish and Boost as well as security practices and the flexibility provided by Drupal's hooks, API and thousands of contributed modules. The presentation concludes with an overview of the command line tool Drush and its uses in deployment, site management and more.
![Drush:
Drush:
Remote
Management
Site alias.
Ex: drush @[SITE].[ENV] vset maintenance_mode 0 -y](https://image.slidesharecdn.com/whydrupalisrockstar-140221074400-phpapp01/85/Why-Drupal-is-Rockstar-67-320.jpg)
Ad
More Related Content
What's hot (15)
Similar to Why Drupal is Rockstar? (20)
Ad
More from Gerald Villorente (20)
Ad
Recently uploaded (20)
Why Drupal is Rockstar?
- 1. 2014 DevOps Day – Philippines February 22, 2014 Microsoft Philippines 8th Floor, 6750 Ayala Ave., Makati City
- 2. { Drupal } : Being a Rockstar Gerald Z. Villorente DevOps Engineer | Drupal Developer | Open-Source Enthusiast
- 3. Agenda: Agenda: Community Code Deployment Security Performance Flexibility Documentation Drush Content Management
- 4. Community Drupal is one of the largest open-source community in the planet.
- 8. Medium IRC, Stackoverflow, D.O forum, ...
- 9. Code Drupal is one of the largest open-source community in the planet.
- 10. PHP
- 12. 25,585 Modules
- 13. 1,941 Themes
- 15. 2,540 Code commits Just this week.
- 16. 5,420 Issue Comments Just this week.
- 17. Coding Standard The Drupal Coding Standards apply to code within Drupal and its contributed modules.
- 18. Indenting and Whitespace Use an indent of 2 spaces, with no tabs.
- 19. Operators All binary operators (operators that come between two values), such as +, -, =, !=, ==, >, etc. should have a space before and after the operator, for readability.
- 20. Casting Put a space between the (type) and the $variable in a cast: (int) $mynumber.
- 21. Control Structures Control structures include if, for, while, switch, etc. Note: Don't use "else if" -- always use elseif.
- 22. Alternate control statement syntax for templates In templates, the alternate control statement syntax using : instead of brackets is allowed.
- 23. Line length and wrapping In general, all lines of code should not be longer than 80 chars. Lines containing longer function names, function/class definitions, variable declarations, etc are allowed to exceed 80 chars. Control structure conditions may exceed 80 chars, if they are simple to read and understand. Conditions should not be wrapped into multiple lines.
- 24. Function Calls Functions should be called with no spaces between the function name, the opening parenthesis, and the first parameter; spaces between commas and each parameter, and no space between the last parameter, the closing parenthesis, and the semicolon.
- 25. Function Declarations Arguments with default values go at the end of the argument list.
- 26. Class Constructor Calls When calling class constructors with no arguments, always include parentheses. This is to maintain consistency with constructors that have arguments.
- 27. Arrays Arrays should be formatted with a space separating each element (after the comma), and spaces around the => key association operator.
- 28. String Concatenations Always use a space between the dot and the concatenated parts to improve readability.
- 29. PHP Code Tags Always use <?php to delimit PHP code, not the shorthand, <? .
- 30. Semicolons The PHP language requires semicolons at the end of most lines, but allows them to be omitted at the end of code blocks. Drupal coding standards require them, even at the end of code blocks.
- 31. Example URLs Use "example.com" for all example URLs, per RFC 2606.
- 33. Naming Conventions: Naming Conventions: Functions and variables Functions and variables should be named using lowercase, and words should be separated with an underscore. Functions should in addition have the grouping/module name as a prefix, to avoid name collisions between modules.
- 34. Naming Conventions: Naming Conventions: Persistent Variables Persistent variables (variables/settings defined using Drupal's variable_get()/variable_set() functions) should be named using all lowercase letters, and words should be separated with an underscore. They should use the grouping/module name as a prefix, to avoid name collisions between modules.
- 35. Naming Conventions: Naming Conventions: Constants Constants should always be all-uppercase, with underscores to separate words. (This includes pre-defined PHP constants like TRUE, FALSE, and NULL.) Module-defined constant names should also be prefixed by an uppercase spelling of the module that defines them. In Drupal 8 and later, constants should be defined using the const PHP language keyword (instead of define()), because it is better for performance. Ex: <?php const CACHE_TEMPORARY = -1; ?>
- 36. Naming Conventions: Naming Conventions: Global Variables If you need to define global variables, their name should start with a single underscore followed by the module/theme name and another underscore.
- 37. Naming Conventions: Naming Conventions: Classes See - https://drupal.org/node/608152
- 38. Naming Conventions: Naming Conventions: File names All documentation files should have the file name extension ".txt" to make viewing them on Windows systems easier. Also, the file names for such files should be all-caps (e.g. README.txt instead of readme.txt) while the extension itself is all-lowercase (i.e. txt instead of TXT).
- 39. Helper Modules
- 40. Helper Modules: Helper Modules: Coder Using PHP_Codesniffer, Coder includes “Coder Review” module that can be use to check the Drupal coding standard of your custom modules, themes, css, and javascript.
- 41. Helper Modules: Helper Modules: Dreditor A browser plug-in for reviewing patches and more.
- 42. Helper Modules: Helper Modules: PAReview A set of scripts for reviewing project applications, which runs some coding tests.
- 43. Helper Modules: Helper Modules: PAReview A set of scripts for reviewing project applications, which runs some coding tests.
- 44. Helper Modules: Helper Modules: Grammar Parser Provides an automated way of rewriting code files in compliance with code standards.
- 45. I hate doing manual code review! Can I automate it? DLA!
- 46. DevOps Loves Automation If you're using version control, you can take advantage the “ hook” feature in automating all reviews. You can combine Bash/PHP/Perl/Python script, Drush, and Coder to do the job.
- 47. Deployment
- 48. Deployment: Deployment: Features Enables the capture and management of features in Drupal. A feature is a collection of Drupal entities which taken together satisfy a certain use-case.
- 49. Deployment: Deployment: Configuration Management Enables the ability to keep track of specific configurations on a Drupal site, provides the ability to move these configurations between different environments (local, dev, qa, prod), and also move configurations between completely different sites (migrate configurations) without the use of modules with all configuration being owned by the site.
- 50. Deployment: Deployment: hook_update_N() Perform a single update. Called by update.php or drush updb.
- 51. Security Drupal is one of the most secure open-source CMS/CMF project on the planet. Don't argue with me!
- 53. Security: Security: Security Team Perform analysis of core or contributed project code. Resolve reported security issues in a Security Advisory. Provide assistance for contributed module maintainers in resolving security issues. Provide documentation on how to write secure code. Provide documentation on securing your site.
- 54. Performance Good integration with Varnish, NginX, Memcache, etc
- 55. Caching
- 56. Caching: Caching: Memcache Git /ɡɪt/ is a distributed revision control and source code management (SCM) system with an emphasis on speed. - Wikipedia
- 57. Caching: Caching: Varnish Varnish is an HTTP accelerator designed for content-heavy dynamic web sites.
- 58. Caching: Caching: Boost Boost provides static page caching for Drupal enabling a very significant performance and scalability boost for sites that receive mostly anonymous traffic. For shared hosting this is your best option in terms of improving performance.
- 60. Flexibility
- 62. Flexibility: Flexibility: API Application Programming Interface, a particular set of code and specs that software programs can follow to communicate with each other.
- 64. Documentation
- 65. Drush The coolest CLI tool to manage your Drupal site.
- 67. Drush: Drush: Remote Management Site alias. Ex: drush @[SITE].[ENV] vset maintenance_mode 0 -y
- 76. Content Management: Content Management: Taxonomy A powerful category system (taxonomy) that allows you to organize and tag content.
- 77. Content Management: Content Management: Content Types Article, News, Events, Listings, etc ...
- 78. Questions?
- 79. Thank You!
- 80. References: References: 1. http://drupal.org 2. http://drupal.stackexchange.com 3. https://drupal.org/community 4. https://drupal.org/coding-standards 5. https://drupal.org/developing/best-practices 6. http://stauffer.com/blog/2013/03/22/why-drupal-greatest-cms-earth 7. http://drush.ws 8. https://github.com/drush-ops/drush