When I was first researching Entityforms and other survey form modules, I had four basic questions I was trying to resolve.
- I don't want to create a survey form, so why would I want to use a survey form module?
- How does Entityform help solve my problem?
- When should I use it
- 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 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.Read more
Drupal is a powerful and flexible framework for building virtually any kind of website. Below are some circumstances in which Drupal is a particularly compelling choice.Read more
When the Content Translation module is enabled you can translate site content into different languages. Working with the Locale module (which manages the enabled languages and provides translation for the site interface), the Content Translation module is key to creating and maintaining translated site content.
Configure content translation
- Navigate to the Permissions page (Administration > User permissions in Drupal 6, or Administration > People > Permissions in Drupal 7) and assign the “translate content” permission to the appropriate user roles.
- Navigate to the Languages page (Administration > Settings > Language in Drupal 6, or Administration > Configuration > Regional and language > Languages in Drupal 7) and add and enable desired languages.
Enable translation support for a content type
- Navigate to the Content types administration page (Administration > Content > Types in Drupal 6, or Administration > Structure > Content types in Drupal 7).
- Select a content type you want translated, and select "edit", then "Workflow settings" for Drupal 6 or "Publishing options" for Drupal 7.
A single web site could contain many types of content, such as informational pages, news items, polls, blog posts, real estate listings, etc. In Drupal, each item of content is called a node, and each node belongs to a single content type, which defines various default settings for nodes of that type, such as whether the node is published automatically and whether comments are permitted. (Note that in previous versions of Drupal, content types were known as node types.)
When you first install Drupal with the default installation profile (in contrast to the minimal installation profile), you will have two content types defined: "Article" and "Basic page". When you enable other core and contributed modules (by visiting Modules), you will find that you have other content types available; you can also create your own content types (see below).
Content types in Drupal 7 & 8
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.Read more