Definition
...
Component: an individual object or configured setting provided by a feature.
example: a “gallery” view, the “comment_gallery” variable.
Design Strategy
In general, Kalamuna features should be built around discrete sets of functionality. Content Types, Fields, Views, Fields, Panels Pages, and other components related to a set of functionality will all in the same feature.
...
Be specific, but avoid too many features! Planning things out broadly will help keep the dev team on the same page, minimize the amount of spec per issue, and promote a bigger picture strategy to the build overall.
example strategy docs: SYN features planning, USFI distro upgrade
| Info |
|---|
Kit is a design specification for Features and Themes: https://www.drupal.org/project/kit. It is a bit dated (so is Drupal 7) but still applies. Check it out! |
...
override and extend panopoly features cleanly
features_override is now much better, so we prefer that.
Open Atrium already overrides Panopoly… so this is how do you override an override!
resources
- https://kalamuna.atlassian.net/wiki/display/KALA/Panopoly+Override
- https://github.com/kalamuna/panopoly_override
Features are Modules!
Once a feature is generated, it will contain .module file. You can put any code in here you would otherwise put in a custom module.
...
update field settings see this wiki article for more
disable modules
display related things
...