Luca Lusso Modernizing Drupal 10 Theme Development __exclusive_

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Sorry, you do not have permission to ask a question, You must login to ask a question.

Luca Lusso Modernizing Drupal 10 Theme Development __exclusive__ -

He showed the client a preview. The carousel that used to stutter on scroll now ran at 120fps. The CLS (Cumulative Layout Shift) score went from 0.45 to 0.02.

He updated his Drupal Slack status: “Modernizing Drupal themes, one component at a time. #SDC #Drupal10 #NoMoreSpaghettiCSS” luca lusso modernizing drupal 10 theme development

Luca closed his laptop, poured one last espresso, and looked out the window. Another legacy system, modernized. Another team, liberated. He showed the client a preview

He’d been called in as a freelance front-end architect. The client, a fast-growing tech magazine, complained that their site felt “sluggish” and that their designers were “fighting the theme.” Luca had seen this before. The previous developer had simply ported a Drupal 7 theme forward, layering patch upon patch. The styles.css file was 8,000 lines of spaghetti. The JavaScript was a jQuery meatball. And the template files ( html.twig , page.html.twig ) were littered with deprecated variables. He updated his Drupal Slack status: “Modernizing Drupal

npm init -y npm install tailwindcss postcss autoprefixer --save-dev Then, he enabled the new, experimental single_directory_components module that had just landed in Drupal 10.3. Instead of scattering template, CSS, and JS across three different folders, he created a new directory: components/ .