drupal-nodes

Node bundle standardization enforces consistent machine names (singular, no special characters), reuses view modes like Full and Teaser across bundles, and documents revision and translation policies. This prevents naming drift, reduces redundant display configurations, and clarifies editor workflows.

Plan bundles by proposing machine names, descriptions, required fields, and view mode strategy upfront. Justify each bundle by display or behavior differences, reuse existing view modes unless documented exceptions exist, and validate configurations against drift using the included validation script.

Enable revisions and translations based on documented workflow requirements, not defaults. The Skill provides guidance to determine when content editing history or multi-language support justify the overhead for each bundle type.

View mode reuse is encouraged across bundles unless a specific exception is documented. By planning display strategies upfront and leveraging Full and Teaser modes consistently, you reduce configuration redundancy and simplify themers' workload.

Yes. The included validation script detects naming drift and configuration inconsistencies against your bundle plan, flagging deviations from singular machine names, undocumented view modes, or policy violations.

A Drupal 10 site-building environment and understanding of your content types' display and behavior requirements. The Skill guides machine naming conventions, field selection, and view mode planning for consistent bundle modeling.