Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Harnessing the power of Calais tagging, administrators can create Topic Hubs based on site’s most popular tags. Topic hubs are highly configurable and contain a series of pluggable content modules, like “Most Read” content for this topic, “Most Commented” stories, most active contributors, and links to other related topics. To top it off, integration with Calais Geo allows for plotting all of your content for a Topic Hub content on a map.
For example, a topic hub of “healthcare” may have related topics of “homeopathy” and “medicine”. Through topic hubs, readers can explore all content related to subjects they are interested in. And, different from other news topic pages, these are configured automatically instead of being curated by editorial staff.
Topic Hubs 6.x-1.x iintegrates with Panels2 for full control over layout and content.
Composite Layout allows your nodes to be displayed in complex layouts. Currently, two and three column layouts are provided. You can also add other nodes, blocks, and even CCK fields to your node's layout. The content area of your node is divided into zones and you decide what should appear in those zones. Zones are essentially the same as Drupal blocks, but they apply to nodes rather than the entire site.
You can think of Composite Layout as Drupal blocks for nodes.
There is overlap in functionality between Composite Layout and Panels. Both address the issue of complex layouts, but each has a different approach.
Here is an informal comparison:
Panels is more powerful and flexible (I think, I'm not a Panels expert).
Composite Layout is simpler (I hope).
The user interface is different. You may prefer one or the other.
Composite Layout applies on content types, so it can be turned on for any node. Furthermore, you can have more than one composite layout node type.
If you use the Content Construction Kit, Composite Layout allows you to manage the layout of your CCK fields.
Otherwise, it will probably come down to personal preference as to which is more suitable.
Translation helpers enables other modules to respond to changes in the "source translation" of a set of translated content. This functionality is useful for modules that track data by the "source translation" (node.tnid value).
This module doesn't do anything on its own. You should install it only if it's suggested or required by another module you're using.
The module also provides other methods for modules to use with translated content.
Drupal 8
A Drupal 8 version won't be needed. Translation Helpers addresses use cases related to the model of translation used in the Drupal 7 core Content Translation module, in which each language has its own node. Drupal 8 has switched to fields-based translation, in which the awkward workarounds of D7 will be a thing of the past.