All Sponsors | New England Drupal Camp

Single Directory Components: Everything You Need to Know

Twig was introduced into Drupal core over 10 years ago. Since then, improvements to Drupal’s front-end API have been minimal. Meanwhile, other front-end ecosystems have implemented superior developer experiences including hot-reloading, tooling for automation, component libraries, shared component repositories, and more.Drupal’s front-end developer experience has some catching-up to do, and we believe Single Directory Components (SDC) is the answer! SDC lets the developer add all of a component’s assets into one directory (e.g. template, CSS, JavaScript, and metadata). This component can then be automatically used by display modes or called upon from another template.We’ll answer all the important questions like:- What problem are we solving?- How does SDC work? Will we have slots, props, & all the buzz words?- Can it be integrated with systems like Storybook, Fractal, etc.?- What does converting a component to SDC look like?- How can contrib modules and themes extend this? How can you use it in your projects?- How does this differ from contrib solutions such as SFC, UI Patterns, Emulsify, Compony, and others?- What is the future of SDC in core? Is it done yet?

Attribute-Based Access Control in Drupal

For over a decade, Drupal has relied on the Role Based Access Control (RBAC) to manage access. Though very powerful, it also has its limitations. For example, it can be difficult to scale, and it’s not uncommon for large projects to experience “role explosion.”Enter Attribute Based Access Control (ABAC). A new paradigm in access control management that has been taking off in popularity in the last few years.With ABAC, you can build a highly intuitive and flexible system that grows with the needs of your organization. In this presentation, I’ll give an overview of what ABAC is, how it compares with other authorization models, why Drupal is well positioned to integrate it, and how you can implement it today in Drupal using the Access Policy module.

Do you still need Sass in 2023? | New England Drupal Camp

With so many new features being added to CSS in the past couple years, is Sass still needed in 2023? Is it time to remove Sass from your build process? What can native CSS and PostCSS do that can replace Sass functionality and how is PostCSS being used in Drupal 10?In this session, I will discuss an overview of new CSS features that replace functionality in Sass:* CSS custom properties* Nesting* New color functionsI will also go over some PostCSS plugins that replicate Sass functionality:* Custom media* Imports* MixinsI will also touch on how PostCSS is being used in Drupal 10.Lastly, I will discuss when you might not want to replace Sass *just yet* and how you can use Sass AND native CSS together to take advantage of your existing build process. It’s an exciting time to be a CSS developer and the perfect time to learn more about what CSS can do natively without using Sass.

Session Agenda | New England Drupal Camp