Drupal Node Bundles

Configure Drupal 10 node bundles with consistent naming and view modes.

34|12|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/theodorosploumis/drupal-best-practices --skill drupal-node-bundles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Drupal Node Bundles
Source: https://github.com/theodorosploumis/drupal-best-practices/tree/main/ai/skills/nodes
Command: npx skills add https://github.com/theodorosploumis/drupal-best-practices --skill drupal-node-bundles

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you design and manage Drupal node bundles (content types) with consistency, preventing common issues like naming conflicts, redundant displays, and difficult maintenance. It ensures your content structure is robust and easy to evolve.

Core Features & Use Cases

  • Consistent Naming: Apply singular, concise, and human-friendly machine names for node bundles and fields.
  • Reusable View Modes: Promote the use of generic view modes (e.g., "Full", "Teaser") to reduce theme complexity and ensure consistent content display.
  • Clear Revision & Translation Policies: Get guidance on when to enable content revisions and translations, aligning with your content workflow needs.
  • Use Case: When creating a new "Article" content type, use this Skill to ensure its machine name is article, it reuses existing "Teaser" and "Full" view modes, and revisions are enabled for editorial control.

Quick Start

Draft an article node bundle plan with machine name suggestions, required fields, and view mode reuse. Highlight when revisions and translations should be enabled.

Frequently Asked Questions about Drupal Node Bundles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Drupal content types with consistent naming conventions?

Use singular, concise machine names for node bundles—for example, `article` instead of `articles` or `article_content`. Avoid special characters and ensure each bundle name justifies its existence rather than duplicating an existing type. This prevents naming conflicts and simplifies maintenance.

What are view modes in Drupal and why should I reuse them across content types?

View modes control how node content displays in different contexts. Reusing standard modes like 'Full' and 'Teaser' across multiple bundles reduces theme complexity, ensures consistent content display, and makes your site easier to maintain and evolve over time.

When should I enable revisions and translations on a Drupal node bundle?

Enable revisions when your content workflow requires editorial control, audit trails, or version history. Enable translations when your site serves multiple languages. Both decisions depend on your content management needs and should be explicitly justified during bundle planning.

How do I plan a new Drupal node bundle before creating it?

Draft the bundle with a singular machine name, list required fields, identify which standard view modes apply, and decide on revision and translation policies. Validate your plan using a bootstrap script to ensure it meets naming and structural constraints before implementation.

What's the best way to avoid redundant content types when site building in Drupal?

During planning, evaluate whether a new bundle is truly necessary or whether fields and view modes can be reused on an existing type. Consistent naming and reusable view modes let you consolidate similar content into fewer, well-designed bundles.