UIkit

A lightweight and modular front-end framework
for developing fast and powerful web interfaces.

UIKit is a new revolutionary framework that took the light in July of 2013 as a result of solutions of YOOTheme - popular theme provider and was tested on lots of their templates. And now it's coming to Drupal!

Group 7.x-1.x

The Group module for Drupal 7 is based around the Entity API. Individual groups have a "Group Type" in the module, which is an Entity. Since it's an Entity, it has fields.

It also has specific permissions and roles, which apply to any Group of this Group type.

Group 8.x-1.x

Placeholder page for the Group (version 8) documentation, about anything that does not apply to the 7.x version of the Group module.

Note: refer to Additional resources for a link to a video that demonstrates how to use the Group module.

Custom entities as group content

To allow your custom entity to be added to a group, you must expose it as a GroupContentEnabler plugin.

e.g.

Drupal8: HOWTO detect whether an entity reference field is a taxonomy term reference and flag it for targeting in field.html.twig and your CSS

Now that the Taxonomy term reference field has been removed in favor of Entity reference it begs the question how one is supposed to specifically target taxonomy term reference fields in Twig templates and in your CSS.

The following (which currently involves checking for the existence of a particular method) may not be very pretty, but it works.

In your THEME.theme:

How to hide group settings on node edit forms

If you want to control how group members create and interact with group content through other means than the group settings on the node edit form (or just allow admin users to change what group content is in), it can be useful to hide that setting. One way to do this is to create a custom module and use this code that hides the form for all users except those with role id 5 (replace HOOK with your module name):

Pages

Subscribe with RSS Subscribe to RSS - Designers/themers