Add a vocabulary to a content type

To use taxonomy terms to organize your content, the vocabulary must be associated with the content type.

Panopoly Apps Data Model

Content Types, Users, and Other Entities

In all probability, your app will add a few new fields to existing data models or create some new entities.

Create a Namespace

All machine names should be namespaced with the title of your app. For example, all Panopoly News fields, content types and views have "panopoly_news" applied to them.

Configure content types for entity translation

Enabling entity translation for a content type

With Entity Translation enabled for "Node", you can set the translation mode (Entity Translation or Content Translation) for each Content Type. To enable translation mode for a particular content type, you need to edit the content type and click on the 'Publishing options' tab and choose under Multilingual support:

  • "Enabled, with translation" for Content Translation
  • "Enabled, with field translation" for Entity Translation

Note that the i18n submodules "Field Translation"*, "Multilingual Content" and "Multilingual Select" do NOT need to be enabled to use Entity Translation properly, and SHOULD NOT be enabled to use Entity Translation properly with an upgrade path to multilingual websites in Drupal 8.
* Multilingual Select is architecturally incompatible with Entity Translation.
* Field Translation might be needed though if you want to translate field labels.
* Multilingual content and its dependency Content translation might be needed though if you want to translate content type strings such as content type names and descriptions.
See https://drupal.org/node/2107219#comment-7963411

How to enable translation for particular fields

Working with content types and fields (Drupal 7 and later)

In Drupal, a Content Type is a pre-defined collection of data types (Fields) which relate to each other by an informational context. In this sense, "context" means "parts that should be considered as a correlated whole."

Content, the Drupal Way

Organizing content in Drupal can be very liberating — or very frustrating, depending on what methods you're used to using.

Almost all information in Drupal is stored as a 'node', the basic unit of content. By default, there is no hierarchy or structure imposed on these nodes: they do not reside in specific 'sections' of your site, and different kinds of nodes (images, blog posts, news articles, etc.) are not automatically grouped or sorted into different groups. Rather than hard-coding specific hierarchies or styles of display, Drupal treats your content as a giant soup, with each piece of content having properties like a title and an author, a 'published' flag, a publication date, and so on. Specific kinds of pages, specific sections of your site, and so on are created by pulling up any content with certain properties and listing it.

Some examples can help clarify this concept.

  1. Default front page

Pages

Subscribe with RSS Subscribe to RSS - content type