Helm Core Principals

Strongarm vs defaultconfig

From https://www.drupal.org/node/2208823#comment-8550141 @lsolesen: I'd say that's true. Use defaultconfig for things you want to have sane defaults but seem likely that the user of the Feature will change and strongarm directly for things that need to be set to a particular value for your Feature to work. I hope that helps!

Featurizing content types

Fields

Most content types should have an instance of field_media. This field is defined in helm_page.

Feature structure

helm_page
--app
----app.manifest
----icon.png
--modules
----helm_page_display
----helm_page_content

Main module permissions (done in defaultconfig)

Permissions: create page content
Permissions: edit own page content
Permissions: edit any page content
Permissions: delete own page content
Permissions: delete any page content
{ any taxonomy-related permissions }

Main module variables (done in strongarm)

field_bundle_settings_node__page
menu_options_page
menu_parent_page
node_options_page
node_preview_page
node_submitted_page

Note: node_options_page should include the moderation value (this requires workbench_moderation to become visible):

  $strongarm->value = array(
    0 => 'status',
    1 => 'revision',
    2 => 'moderation',
  );

Main module variables (done in defaultconfig)

Variables: pathauto_node_article_pattern

Display module permissions (done in defaultconfig)

Permissions: administer panelizer node page breadcrumbs
Permissions: administer panelizer node page content
Permissions: administer panelizer node page context
Permissions: administer panelizer node page defaults
Permissions: administer panelizer node page layout
Permissions: administer panelizer node page overview
Permissions: administer panelizer node page settings