Guidance on content types

I have used Drupal for a few years now but have a request that I am not quite sure how to accomplish in Drupal. I want to have a content type called "Sidebar" which has a few fields (Title and body). Then I want another Content type called "Website Page" that has some fields but also a "Sidebar" section that has a checkbox option for "Sidebar" which then adds that sidebar content to that page. I want to be able to add different Sidebar nodes, which the title pulls to that section of the Website Page Section area.

Taxonomy upgrade extras: 

When to use Entityform

When I was first researching Entityform and other survey form modules, I had four basic questions I was trying to resolve.

  1. I don't want to create a survey form, so why would I want to use a survey form module?
  2. How does Entityform help solve my problem?
  3. When should I use it
  4. How is it different from other solutions?

After doing some research and talking with Tedbow, this modules author, I think I can start to answer these questions.

I don't want to create a survey form, so why would I want to use a survey form module?

I just had this same discussion with a friend of mine the other day. She wanted to include a signup form at the bottom of an event content type node. This sign up form would allow people to register for the event. (Yes, I know she could’ve used the signup module. However she needed more functionality than the signup module offered.) I suggested she use either Entityform or Webform. Her immediate response was "I want to create a signup form, not a survey form". And therein lies the confusion of “survey” form modules.

Is Drupal the right tool for the job?

Drupal is a powerful and flexible content management system for building virtually any kind of website. What are you looking for Drupal to do for you? The following are some areas that Drupal champions:

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

Blog module (single and multi-user blogs)

The Blog module (a core module in Drupal 7 and earlier) allows authorized users to maintain a blog. Blogs are a series of posts that are time stamped and are typically viewed by date as you would view a journal. Blog entries can be made public or private to the site members, depending on which roles have access to view content.

Note that the Blog module is not needed for a "single-user" blog (a site that only has one individual blogging). For that use case, it's simpler to create a custom content type. The Blog module is usually used when there is a need for a number of blogs, written by different users, running on one site. For more information on creating a single-user blog, see this Single User Blog recipe.

The Blog module was removed from Drupal 8 core but it can still be installed and enabled as a contributed module.

Subscribe with RSS Subscribe to RSS - content types