More Related Content
Similar to 10 Reasons why you should be using features for your Drupal project (20)
10 Reasons why you should be using features for your Drupal project
- 1. 10 Reasons why you should be using features
Florian Lorétan
24. aug 16:00
Microsoft
- 24. What can be exported: exportables
Default Views
Imagecache Presets
Ctools
Panels
Open Layers
Rules
Blocks (via context)
Variables (via strongarm)
- 32. What can be exported: non-exportables
Content Types, including fields and fieldgroups
Roles & Permissions
Menus
Vocabularies
Nodes, Terms & Users (using UUIDs) *
- 39. What can't be exported
Input formats
Things that can only be
identified using sequential numeric IDs
- 53. drush features-list features
drush features-export fe
drush features-diff fd
drush features-revert fr
drush features-revert-all fr-all
drush features-update fu
drush features-update-all fu-all
- 54. drush features-list features
drush features-export fe
drush features-diff fd
drush features-revert fr
drush features-revert-all fr-all
drush features-update fu
drush features-update-all fu-all
- 76. Drupal Images
Modules mp3
Themes Attachments
Content types Nodes
Roles Users
Vocabularies Terms
- 77. Functionality Content
Drupal Images
Modules mp3
Themes Attachments
Content types Nodes
Roles Users
Vocabularies Terms
- 78. Drupal Images
Modules mp3
Themes Attachments
Content types Nodes
Roles Users DB
Vocabularies Terms
- 79. Drupal Images
Modules mp3
Themes Attachments
Content types Nodes
Roles Users DB
Vocabularies Terms
- 86. Fourth Law of Software Development:
“When you let your clients change things,
they break.”
- 87. Fourth Law of Software Development:
“When you let your clients change things,
they break.”
- 88. Fourth Law of Software Development:
“When you let your clients change things,
they break.”
override