Other Content Entities

Model non-node content entities with Drupal naming and translation conventions.

34|12|Updated Mar 10, 2019
One-click install
npx skills add https://github.com/theodorosploumis/drupal-best-practices --skill other-content-entities
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Other Content Entities
Source: https://github.com/theodorosploumis/drupal-best-practices/tree/main/ai/skills/other-content-entities
Command: npx skills add https://github.com/theodorosploumis/drupal-best-practices --skill other-content-entities

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you avoid inconsistent content modeling for non-node entities like media, paragraphs, and comments. It ensures these entities follow established best practices, preventing maintenance headaches and improving content editor experience.

Core Features & Use Cases

  • Standardized Naming: Apply consistent, singular machine names and clear descriptions across all content entities.
  • View Mode Reuse: Promote the reuse of display view modes to maintain a cohesive look and feel across your site.
  • Translation Handling: Get guidance on managing translations, especially for complex, nested entities like paragraphs.
  • Use Case: When creating a new Image media bundle, use this Skill to ensure its naming, fields, and display settings align with your site's overall content strategy, making it easier to manage and translate.

Quick Start

Help me design a media image bundle with node-style naming, recommended view modes, translation handling, and image style naming focused on intent.

Frequently Asked Questions about Other Content Entities

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

FAQPage Schema
How do I apply consistent naming conventions to media and paragraph bundles in Drupal?

Apply node-style singular machine names and clear descriptions to all content entities—media, paragraphs, and comments—to maintain consistency across your site structure and simplify long-term maintenance and editor workflows.

What's the best way to handle translations for nested entities like paragraphs?

Establish explicit translation strategies for nested entities by reusing view modes and applying consistent naming, ensuring multilingual content renders correctly across bundles and maintains coherent display settings.

How should I name image styles in Drupal to align with content intent?

Use descriptive, intent-based naming for image styles rather than dimension-only labels, linking style names to their functional purpose—such as cross-bundle display or UI presentation context—for clarity and maintainability.

Can I reuse view modes across different content entity types in Drupal?

Yes; promoting view mode reuse across media, paragraphs, and comments maintains a cohesive visual experience and reduces redundant configuration, supporting consistent content modeling best practices.

Why does consistent content modeling matter for non-node entities?

Inconsistent naming and display settings for media, paragraphs, and comments create maintenance overhead and confuse editors; standardized node-oriented conventions prevent fragmented content strategies and improve site scalability.

Do I need to treat comments differently from paragraphs when applying these standards?

No; extend the same node-oriented conventions—machine names, view modes, translation handling—to comments as you do paragraphs and media, creating unified content modeling across all entity types.