Drupal Theming

Use a single descriptive word without theme or base-theme prefixes as your Drupal theme's machine name. This approach keeps naming simple and avoids namespace conflicts while maintaining clarity across your theme structure.

Organize SCSS by responsibility into separate folders: variables, mixins, entities, and components. Use semantic class prefixes like `twig-` and `js-` to distinguish template-driven styles from JavaScript-targeted selectors, keeping your stylesheet structure predictable and maintainable.

Yes, extending Classy provides a solid foundation with existing Twig templates and semantic markup. It lets you override only essential templates—like 404, 403, maintenance, and login pages—while inheriting sensible defaults for the rest of your theme.

Leverage Twig preprocessing logic to dynamically generate semantic classes in your templates rather than hardcoding them. This approach reduces duplication, keeps class naming consistent across components, and makes styles easier to track and modify.

Use `twig-` prefixes for classes generated and managed by Twig templates for styling purposes, and `js-` prefixes for classes targeted by JavaScript interactions. This separation prevents accidental style breakage when JavaScript selectors change and clarifies intent in your markup.

Override templates only when markup structure must change—such as for documented exceptions like 404, 403, maintenance, and login pages. For styling needs, use preprocessing and SCSS instead to minimize overrides and keep your theme lightweight and maintainable.