This group is for folks working on new themes for Backdrop CMS.
'), + 'private' => '0', + ), + 'documentation' => array( + 'title' => st('Documentation'), + 'body' => st('A place for folks to coordinate efforts at improving Backdrop CMS documentation.
'), + 'private' => '0', + ), + 'core_development' => array( + 'title' => st('Core Development'), + 'body' => st('Join this group for the latest information about core development priorities.
'), + 'private' => '1', + ), + ); + + foreach ($groups as $group_id => $info) { + $group = new Node( + array( + 'title' => $info['title'], + 'body' => array( + LANGUAGE_NONE => array( + array( + 'value' => $info['body'], + 'format' => 'filtered_html', + ), + ), + ), + 'group_access' => array( + LANGUAGE_NONE => array( + array( + 'value' => $info['private'], + ), + ), + ), + 'uid' => 1, + 'status' => 1, + 'promote' => 0, + 'type' => 'group', + ) + ); + node_save($group); + $groups[$group_id]['nid'] = $group->nid; + } + + $group_content = array( + array( + 'title' => st('Refence Module in Core'), + 'body' => st('Move the Entity Reference contrib module into core. It has been refactored to remove any external dependencies. Entity Reference is the most obvious candidate based on the following advantages:
A theme is a collection of files which define the presentation layer of a Backdrop site. The theme determines the appearance of a site. You can also create one or more "sub-themes" or variations on a theme. Only the .info file is required, but most themes and sub-themes will use other files as well.
On the surface, sub-themes behave just like any other theme. The only difference is that they inherit the resources from their parent themes. To create one, a "base theme" entry inside the .info file is needed. From there it will inherit the resources from its parent theme. There can be multiple levels of inheritance; i.e., a sub-theme can declare another sub-theme as its base. There are no hard set limits to this.
'), + 'group' => 'theme_developers', + ), + array( + 'title' => st('Contribute to Documentation'), + 'body' => st('You can help the Backdrop community by contributing to the documentation on this site. Documentation of code is created by the API module from docblock comments within the code, so changes to code documentation are made by submitting a pull request as you would make for any other code change.
'), + 'group' => 'documentation', + ), + array( + 'title' => st('The Backdrop CMS User Guide'), + 'body' => st('The User Guide is a detailed "How-To" for practically everything you need to know to create, customize, and manage a Backdrop website and is intended for people who may be new to content management systems in general and to the Backdrop CMS in particular.
'), + 'group' => 'documentation', + ), + array( + 'title' => st('Core Developers'), + 'body' => st('Core developers should fight the urge to refactor, because small changes in core may result in large changes for contrib. Each major change will be weighed carefully against the principles of the project to determine if the improvements it offers are worth the cost of that change. If a decision is not immediately clear, the issue should be escalated to the Project Management Committee.
'), + 'group' => 'core_development', + ), + array( + 'title' => st('Layouts'), + 'body' => st('The most important consideration when converting themes to Backdrop is the concept that your theme is no longer responsible for the layout of a site. This is because of the introduction of Layout module, Backdrop drag and drop page layout builder.
Layout module now provides ten responsive layout templates including a multi-region stacked layout similar to what was provided in the Bartik theme for Drupal 7.
In the Layouts interface, blocks are provided to place the site header, main navigation, search box, and so on. All these elements can be rearranged by dragging and dropping these blocks into the regions provided by the layout template.
Porting a theme mainly now consists of the application of the old themes style to the new theme. Once this is understood, the conversion itself should be reasonably straightforward.
'), + 'group' => 'theme_developers', + ), + ); + + foreach ($group_content as $info) { + $content = new Node( + array( + 'title' => $info['title'], + 'body' => array( + LANGUAGE_NONE => array( + array( + 'value' => $info['body'], + 'format' => 'filtered_html', + ), + ), + ), + 'og_group_ref' => array( + LANGUAGE_NONE => array( + array( + 'target_id' => $groups[$info['group']]['nid'], + ), + ), + ), + 'uid' => 1, + 'status' => 1, + 'promote' => 0, + 'type' => 'group_content', + ) + ); + node_save($content); + } + + // Update the menu router information. + menu_rebuild(); + + // Rebuild permissions + node_access_rebuild(); +} diff --git a/og_demo/og_demo.module b/og_demo/og_demo.module new file mode 100644 index 00000000..f4e38cce --- /dev/null +++ b/og_demo/og_demo.module @@ -0,0 +1,6 @@ +