Drupal Taxonomy

Design singular Drupal taxonomy vocabularies with machine names and validation scripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solves?

This Skill helps you correctly implement Drupal taxonomy, ensuring vocabularies are used effectively for categorization and curated landing pages, rather than being misused for simple filtering or overly complex data structures. This leads to a more organized and performant site.

Core Features & Use Cases

  • Purpose-Driven Modeling: Get guidance on whether taxonomy or another entity type (like an entity reference) is best suited for your content organization needs.
  • Singular Naming: Ensure vocabulary names are singular, concise, and clearly describe their purpose.
  • Clear Display Patterns: Outline how taxonomy terms should be displayed and avoid overloading them with functionality better suited for richer entities.
  • Use Case: When organizing blog posts by "Category," use this Skill to confirm that a Category vocabulary is appropriate, its machine name is category, and it's used to generate category landing pages.

Quick Start

Propose a topics vocabulary with singular machine name suggestions, purpose description, and guidance on when to use entity references instead.

Frequently Asked Questions about Drupal Taxonomy

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

FAQPage Schema
How do I organize content with Drupal taxonomy vocabularies?

Drupal taxonomy vocabularies categorize content using singular-named terms and machine names. Design vocabularies for specific purposes—like a `Category` vocabulary with machine name `category` for blog posts—to create organized, filterable content structures and curated landing pages without overcomplicating your data model.

When should I use taxonomy versus entity references in Drupal?

Use taxonomy for simple categorization and term-based landing pages. Use entity references when you need richer data modeling with custom fields, relationships, or attributes. Taxonomy excels at tagging and filtering; entity references suit complex, multi-attribute content organization.

What's the best way to name Drupal taxonomy vocabularies and terms?

Use singular, concise names that clearly describe purpose. A vocabulary name like `Category` with machine name `category` is clearer than plural forms. Singular naming ensures consistent, predictable naming conventions and improves site maintainability and translation workflows.

How do I prevent misusing Drupal taxonomy for filtering instead of categorization?

Taxonomy should organize content for navigation and curated landing pages, not simple filtering. Apply guardrails in your site-building process: validate that each vocabulary serves a categorization purpose, has clear display patterns, and generates meaningful term pages rather than shallow filter groups.

What access and translation considerations apply to Drupal taxonomy?

Drupal taxonomy vocabularies support role-based access control and multi-language translation. Plan term visibility by user role, document translation workflows for multilingual sites, and configure field settings to ensure taxonomy displays correctly across languages and user permissions.