canvas-component-naming
Use simple, generic names. Never prefix component names with the project or site name. Components should be reusable and their names should describe their purpose, not their origin.
Use kebab-case for component names (for example, machineName,
src/components/<name>/, and story filenames).
When copying and modifying an example component, keep the original name unless the component serves a fundamentally different purpose. When creating a new component without an example, choose a simple, descriptive name.
# Correct - simple, descriptive names
footer
hero
navigation
contact-form
# Wrong - prefixed with project/site name
More from acquia/nebula
nebula-scrape-url
Capture web page screenshots and HTML for design reference. Use when the user
10canvas-component-utils
Use utility components to render formatted text and media correctly. Use when
9canvas-component-metadata
Define valid component.yml metadata for Canvas components, including props,
9canvas-styling-conventions
Style Canvas components with Tailwind CSS 4 theme tokens and approved utility
9nebula-project-structure
Project folder structure and package manager detection for Nebula. Reference
8canvas-component-upload
Upload validated components to Drupal Canvas and recover from common upload
8