Drupal-Site-Builder Questions and Answers

Drupal’s issue queue guidelines clearly distinguish between different issue types. A Bug Report is used when existing functionality is broken or not working as intended. In this case, the module is functioning correctly—it simply does not provide a UI—so option A is incorrect.

A Feature Request is the correct issue type when asking for new functionality or enhancements to an existing module. Requesting a web-based UI for a module that currently only provides Drush commands is a classic example of a feature enhancement, making option C correct.

Option B (“Plan”) is typically used for outlining larger initiatives or coordinated development efforts, not for requesting a specific feature. Option D is incorrect because Drupal issue queue best practices emphasize clear, descriptive, and professional issue titles , avoiding urgency or misleading wording like “Module Broken!!!” when it is not actually broken.

Drupal.org documentation encourages contributors to categorize issues properly and write clear, concise summaries so maintainers and the community can effectively review and respond. Therefore, submitting a Feature Request with a clear subject line is the correct and recommended approach.

Drupal’s recommended way to let visitors narrow a Views listing by a field value is to add that field as a filter criterion and then expose the filter to site visitors . The core Views documentation explains that filters can be exposed so users can interact with the data shown in the view, instead of hard-coding separate displays or relying on free-text searching.

This question specifically says the recipes are tagged with a curated taxonomy vocabulary of ingredients. Drupal’s User Guide uses Ingredients as an example of a field that should be a taxonomy term reference , because the allowed values come from a managed list that can grow over time. That means the correct filter is the Recipe content type’s Ingredients taxonomy-reference field in the View. Since visitors should be able to choose the ingredients they have on hand, the exposed filter should allow multiple selections .

The other options are not the standard Drupal site-building solution. Separate displays per ingredient do not scale, a combined-text search is not a structured taxonomy filter, and a menu block is navigation rather than a proper Views filter.

In Drupal 10 and Drupal 11 Views, the correct place to add a CSS class to each rendered row is the Format → Settings → Row class option. Drupal core’s Views API shows that style plugins can provide a Row class text field, and when the display uses fields, this option explicitly supports field tokens . The documentation in core states: “You may use field tokens … for all fields.” That means you can add the Manufacturer field to the View and use its token in the Row class setting so each row gets a class derived from that field’s value. Drupal then token-replaces the value for each row and sanitizes it into a valid CSS identifier.

The other options do not match how Drupal Views handles per-row CSS classes. Attachments do not assign row classes to the main display, a separate custom field is not required for this built-in capability, and group-by options are for grouping results rather than applying row-level CSS classes. So the Drupal-native, documented method is to put the Manufacturer field token directly into the Row class setting in the display’s Format settings .

In Drupal 10 and Drupal 11, user accounts are fieldable entities , which means you can add custom fields directly to user accounts through the administrative UI. Drupal’s field documentation explains that fields can be added to various entity types, including users , not just content types. So if you want each user to choose a favorite weapon, the correct site-building approach is to add a field such as Favorite weapon to the User entity using the Manage fields interface for user accounts. This makes option A correct.

This approach is also flexible. The field could be a plain list, an entity reference, or a taxonomy term reference if the site needs a controlled list of weapons. The important point is that the selection belongs to the user profile/account , because the requirement is about storing a preference for each user.

The other options are not the correct primary solution. Option B creates taxonomy terms but does not by itself provide the user-selection field. Option C uses content and Views instead of storing a value on user accounts. Option D is incorrect because Drupal users are not modeled as a content type. Therefore, adding a field to user accounts is the proper Drupal-native solution.

Drupal 10 and Drupal 11 let you control block display through visibility conditions on the block configuration form. Drupal’s block management documentation explains that a block’s visibility can depend on page-specific visibility settings and also on user role conditions. For page visibility, Drupal specifically notes that the front page is an exception and must be entered as < front > . To show a block only on the homepage, you add < front > in the Pages visibility settings and choose “Show for the listed pages.”

To limit the block to a specific audience, you use the Roles visibility condition and select the exact role that should see the block. In this case, that is Premium customer , not the broader Authenticated user role, because selecting Authenticated user would show the block to all logged-in users who have that role, not just premium customers. Drupal core’s block form API also confirms that block visibility is built through configurable visibility conditions in the block UI.

So the correct combination is:

A for the role restriction, and B for the front-page-only restriction.

Drupal’s Comment module supports creating different comment types and attaching them to content entities. The official Comment module documentation states that Drupal can create new comment types that can be attached to content entities, and the detailed comment documentation explains that when you create a comment type and choose the target entity type as Content , that comment type becomes available when adding a comment field to a content type.

Drupal’s field documentation also explains that fields on comments are defined at the content-type level , on the Comment fields tab of the content type edit page. When you add a field for comments, each comment on content items of that type gets that field. Drupal even gives an example of adding a field to comments for one content type but not another, which matches this requirement exactly.

So the right solution is to create a new comment type for Places comments, add a Country field to that comment type, and then use that comment type on the Places content type only. The other options either store the data in the wrong place or do not make it specific to comments on Places.

In Drupal 10 and Drupal 11, Views contextual filters are used to dynamically filter content based on values passed through the URL. When filtering content by taxonomy (such as Landmarks), you configure a contextual filter using the taxonomy term field associated with the content type.

To pass a value like a term name in the URL , you must configure the contextual filter to accept term identifiers such as term ID or term name . Drupal Views allows validation and transformation of contextual input, including using the taxonomy term name via settings like “Provide default value” or “Specify validation criteria.” This matches option B.

Option A is incorrect because exposed filters rely on user input via UI forms, not URL path arguments. Option C is unnecessary duplication and not aligned with best practices. Option D is not required because taxonomy reference fields already provide the necessary relationship internally for filtering; explicitly adding a relationship is only needed in more complex multi-entity scenarios.

Therefore, the correct approach is to use a contextual filter configured to accept the taxonomy term (including term name) via the URL, making option B correct.

Drupal 10 and Drupal 11 provide block visibility conditions that allow administrators to control where blocks appear. According to Drupal’s block system documentation, when placing a block through Structure → Block layout , you can configure visibility based on content types, pages, roles, or request paths .

To meet the requirement of showing the "Recent content" block only on Article pages, the correct approach is to place the block in the Sidebar region and configure its visibility condition to Content types → Article . This ensures the block is displayed only when viewing nodes of the Article content type and hidden elsewhere.

Option A is incorrect because using CSS to hide blocks is not a proper Drupal configuration and still renders the block unnecessarily. Options B and C are invalid because Drupal does not provide such settings in content type or site branding configurations.

Thus, using block visibility settings tied to the Article content type is the correct and recommended method in Drupal site building.

Drupal 10 and Drupal 11 recommend using entity references and view modes to display structured entity data (like users) within other entities such as blocks. The requirement is to display a selected user (employee) with their name and picture and allow editors to choose which user appears in the block through the block editing UI.

Option D follows Drupal best practices. First, you create a custom view mode for users (e.g., “Star Performer”) and configure it to display only the necessary fields such as user name and profile picture. Then, you create a custom block type with a user reference field , allowing editors to select a specific user. The display of that referenced user can be configured to use the custom view mode, ensuring consistent formatting.

Option B is less suitable because it relies on Views filtering rather than allowing editors to directly select a specific user. Option A depends on a contributed module unnecessarily. Option C is incorrect because Drupal does not provide a default block type for selecting arbitrary user entities in that way.

Thus, using a user reference field with a dedicated view mode is the correct and scalable Drupal solution.

Drupal’s recommended solution for reusable images with their own metadata is to use Media entities , not ordinary image fields on content. Core documentation and issue work around Media in Drupal explain that moving from regular image fields to media image fields is what enables reuse of the same image asset across multiple pieces of content.

That means the description should live on the media item itself , together with the image, and content types should reference that media item through a media reference field . Drupal field documentation also confirms that fields can be attached to entities and reused appropriately through references. So creating a new media type with an image field plus a description field is valid, and adding a description field to an existing Image media type is also valid. Both approaches satisfy the requirement that the image and its description stay together and can be reused elsewhere.

Option B is incorrect because Drupal core already provides Media for this use case. Option C is not the best content model because a content type represents publishable content, while reusable images-with-metadata are better modeled as Media assets.