webjoke.de

Most things need regular care and maintenance to ensure they continue to run effectively, and your website is no exception. When it comes to website maintenance, one of the strongest parallels is with car maintenance. A vehicle only runs smoothly with routine check-ups, even if it looks perfect on the outside. You stay on the safe side when the engine is checked, parts are updated, and small issues are fixed before they turn into larger, more expensive repairs.

I’m excited to share that I’ll be teaming up with Lullabot’s Andy Blum to deliver an in-depth front-end theming training at DrupalCon Chicago 2026.

This training is especially meaningful to me because it brings together a large part of the work I’ve been doing at Dripyard over the past few years. Teaching and sharing hard-earned lessons is one of my favorite parts of being involved in the Drupal community.

Drupal completes 25 years this January 15th, 2026! Let’s celebrate Drupal with 25 compelling reasons why it remains a secure, scalable, open-source CMS trusted by enterprises and governments worldwide.

Join us THURSDAY, January 15 at 1pm ET / 10am PT, for our regularly scheduled call to chat about all things Drupal and nonprofits. (Convert to your local time zone.)

We don't have anything specific on the agenda this month, so we'll have plenty of time to discuss anything that's on our minds at the intersection of Drupal and nonprofits. Got something specific you want to talk about? Feel free to share ahead of time in our collaborative Google document!

All nonprofit Drupal devs and users, regardless of experience level, are always welcome on this call.

This free call is sponsored by NTEN.org and open to everyone.

Information on joining the meeting can be found in our collaborative Google document.

Today we are talking about Recording Podcasts, The tech used, and How Drupal Can help with guest Stephen Cross. We'll also cover Chosen as our module of the week.

For show notes visit: https://www.talkingDrupal.com/535

Topics

• Podcasting and Second Signal Media
• Evolution of Podcasting
• Tech Essentials for Podcasting
• The CEO's Video Strategy Transformation
• Overcoming the Fear of Speaking on Camera
• The Importance of Consistency in Content Creation
• Editing vs. Authenticity in Video Content
• Choosing the Right Environment and Equipment
• Setting Realistic Goals for Your Podcast
• Recording Workflow Recommendations
• Tools and Tips for Improving Audio Quality

Resources

• Basic Editing with Kdenlive
• Audio clean-up tools
• Izotope
• Secret sounds

Guests

Stephen Cross - stephencross

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Andy Giles - dripyard.com andyg5000

MOTW Correspondent

Martin Anderson-Clutz - mandclu.com mandclu

• Brief description:
  • Have you ever wanted to give users on your Drupal site a more intuitive alternative to native HTML multiselect widgets? There's a module for that.
• Module name/project name:
  • Chosen
• Brief history
  • How old: created in Jul 2011 by shadcn but recent releases are by Bálint Nagy (nagy.balint) of Hungary
  • Versions available: 3.0.6, 4.0.3, and 5.0.3, the last of which works with Drupal 10.2 or 11
• Maintainership
  • Actively maintained
  • Security coverage
  • Test coverage
  • Number of open issues: 221 open issues, 4 of which are bugs against the 5.x branch
• Usage stats:
  • Almost 38,000 sites
• Module features and usage
  • With the module installed, your Drupal site will selectively replace select elements with a more intuitive widget, leveraging the Chosen library. In the module's configuration you can specify how many options should trigger Chosen, and also specify form field selectors to explicitly include or exclude.
  • The three active branches of the module reflect usage of different forks of the Chosen library. Notably, the 5.x versions use a fork that no longer requires jQuery, and allows Chosen to be enabled for mobile devices.
  • In addition to the module configuration, you can also force a custom form's select element to use the Chosen library simply by adding the "chosen-select" class to the form array.
  • Back in episode #409 we talked about Tagify, which in some ways is similar, but is designed specifically to work with entity reference fields. That makes it less "general purpose", though Tagify does also include some additional capabilities, such as being able to include labels or icons on results based on a property of the result.
  • Years ago I used another popular project called Select2 for turning multiselects into listboxes that included a search filter, but that project relied on a library that required jQuery but is incompatible with jQuery 4. So, Select2 has been officially replaced by Tagify, but Chosen could also be useful if your field is not an entity reference.
  • There are a variety similar modules you can also look at, including Choices.js, Selectize, and Selectify, but Chosen is by far the most widely used, even if you're only looking at numbers for the 5.x branch

Twenty years ago, I argued passionately that breaking backward compatibility was one of Drupal's core values:

The only viable long-term strategy is to focus exclusively on getting the technology right. The only way to stay competitive is to have the best product. [...] If you start dragging baggage along, your product will, eventually, be replaced by something that offers the same functionality but without the baggage.

I warned that preserving backward compatibility would be the beginning of the end:

I fear that this will be the end of Drupal as we have come to know it. Probably not immediately, maybe not even for several years, but eventually Drupal will be surpassed by technology that can respond more quickly to change.

Twenty years later, I have to admit I was wrong.

So what changed?

In 2006, Drupal had almost no automated tests. We couldn't commit to backward compatibility because we had no way to know when we broke it. Two years later in 2008, we embraced test-driven development.

Drupal's test code now exceeds production code by more than two to one. Source: Drupal Core Metrics.

By 2016, we had built up significant test coverage, and with that foundation we adopted semantic versioning and committed to backward compatibility. Semantic versioning gave us a deprecation policy. We can mark old code for removal and clear it out every two years with each major release. The baggage I feared never really accumulated.

Today, according to the Drupal Core Metrics dashboard, Drupal Core has more than twice as much test code as production code. I didn't fully appreciate how much that would change things. You can't promise backward compatibility at Drupal's scale without extensive automated testing.

Our upgrades are now the smoothest in the project's history. And best of all, Drupal didn't end. It's still a top choice for organizations that need flexibility, security, and scale.

I recently came across an interview with Richard Hipp, SQLite's creator. SQLite has 90 million lines of tests for 150,000 lines of production code. That is a whopping 600-to-1 ratio. Hipp calls it "aviation-grade testing" and says it's what lets a team of three maintain billions of installations.

I suspect our test coverage will continue to grow over time. But Drupal can't match SQLite's ratio, and it doesn't need to. What matters is that we built the habits and discipline that work for us.

In 2006, I thought backward compatibility would be the end of Drupal. In 2026, I think it might be what keeps us here for another twenty years.

Thank you to everyone who wrote those tests.

It does make me wonder: what are we wrong about now? What should we be investing in today that will slowly reshape how we work and become an obvious advantage twenty years from now? And who is already saying it while the rest of us aren't listening?

AI is moving quickly into the Drupal ecosystem, but the conversation around it has often been fragmented and uneven in quality. Drupal AI TV, launched by the Drupal AI Initiative, responds to this by focusing less on promotion and more on consolidation. Its core value lies in curation: selecting existing, publicly available sessions and placing them in a single, structured space where professionals can assess current thinking and practice around AI in Drupal without wading through unrelated material.

The range of content is notable for its balance. Alongside technical demonstrations, there is clear attention to ethical questions, organisational readiness, and the realities of integrating AI into existing systems. This signals a pragmatic stance toward AI adoption, one that recognises both its potential and its constraints. By including case studies and workflow-focused sessions, Drupal AI TV grounds abstract AI discussions in the day-to-day decisions faced by developers, content teams, and digital strategists.

As the platform grows, its usefulness will depend on how well it maintains this curatorial discipline. Regular updates are important, but relevance and depth matter more than volume. If Drupal AI TV continues to prioritise informed, experience-based perspectives, it can become a steady reference point for teams evaluating when and how AI meaningfully fits into their Drupal projects, rather than another channel that adds to the noise.

With that, let's move the spotlight to the important stories from the past week.

DISCOVER DRUPAL

• Drupal AI Initiative Launches "Drupal AI TV" to Curate Top AI Resources for Community
• Uppy for Drupal: Advanced File Uploading with Inline Image Editing Support
• Drubernetes v3 Replaces Nginx Ingress with Envoy Gateway for Modern Kubernetes Architecture
• Kevin Quillen Releases Offline htaccess Testing Plugins for VS Code and JetBrains IDEs

EVENTS

• Drupal 25th Birthday Party Set for January 15 in Zurich
• Drupal Pune Meetup to Celebrate 25 Years of Drupal on January 10
• Drupal Celebrates 25 Years at New Year Reception in Mechelen
• DrupalCamp Costa Rica 2026 Returns as Free, Multi-Track Tech Event for Web, AI, and Open Source
• Acolono and Drupal Austria to Host In-Person Drupal 25 Celebration in Vienna
• Japan Forms Committee to Launch Official Drupal Association; DrupalCamp Tokyo 2026 Announced

DRUPAL COMMUNITY

• Drupal Association Invites Community to Celebrate 25th Birthday with Photo Wall
• Drupal Turns 25 and Calls on Community to Share 25 Words of Celebration

ORGANIZATION NEWS

• Kanopi Studios Acquires Chapter Three to Strengthen Drupal Services

We acknowledge that there are more stories to share. However, due to selection constraints, we must pause further exploration for now. To get timely updates, follow us on LinkedIn, Twitter, Bluesky, and Facebook. You can also join us on Drupal Slack at #thedroptimes.

Thank you.

Alka Elizabeth
Sub-editor
The DropTimes

This week, Drupal turns 25. From its beginnings as a student message board to becoming one of the world’s most powerful open-source content management platforms, Drupal’s story is one of community, innovation, and quiet influence at global scale.

For everyone who has built, scaled, or relied on Drupal over the years, this milestone is worth celebrating — and for us at ComputerMinds, it’s also a moment to reflect on our own history alongside the platform.

From Early Experiment to Global Platform

When Drupal first appeared in 2001, it wasn’t trying to be a CMS in the way we think of one today. What set it apart early on was flexibility: a modular architecture, a strong developer ethos, and a belief that complex digital experiences could be built collaboratively and openly.

Fast-forward 25 years and Drupal now powers everything from government services and universities to media platforms and global enterprises. It has weathered huge shifts in the web — from Web 2.0 and mobile, to APIs, headless architectures, and composable digital platforms — while staying true to its open-source roots.

That ability to evolve without losing its core values is a big part of why Drupal is still here, and still relevant.

One of the First Drupal Agencies (Back in 2004)

At ComputerMinds, we spotted Drupal’s potential early. In 2004, when Drupal was still a relatively niche technology, we became one of the first agencies to specialise in it.

Back then, choosing Drupal wasn’t the obvious or “safe” option. But what we saw was a platform that could be shaped to fit ambitious ideas — not the other way around. That belief has guided our work ever since.

Our First Drupal Project: Video Sharing Before It Was Cool

Our very first Drupal project is one we still smile about.

We worked on a video-sharing website at a time when streaming video on the web was far from mainstream. Bandwidth was limited, browsers were inconsistent, and the idea of user-generated video content was genuinely revolutionary.

Drupal gave us the flexibility to experiment, to build custom functionality, and to push beyond what most platforms could handle at the time. It felt bold. It felt future-facing.

I still remember the day when the CEO came in with a worried look on his face, and then proceeded to show us something called "YouTube" which was "doing something similar, but is nothing to worry about".   

25 Years On — Still Building with Drupal

A quarter of a century later, Drupal continues to be the platform of choice for organisations that need:

• Flexibility without lock-in
• Scalability and security at enterprise level
• The freedom to integrate with anything
• A strong, values-driven open-source community

At ComputerMinds, we’ve grown alongside Drupal — from early experimental builds to complex, mission-critical digital platforms. The tools have evolved, the architecture has matured, but the underlying reason we chose Drupal in 2004 remains the same today.

Happy Birthday, Drupal

A Drupal migration that wraps values in paragraphs Drupal Drupal 10.x Drupal 11.x Planet Drupal jstrecker 2026.01.09 @ 13:50

Sometimes the way that we’ve structured a site’s content originally is no longer ideal after several years. Here I’ll share an example of using a Drupal migration to restructure content. This example transforms an entity reference field to a paragraph field that wraps the entity reference.

• Read more about A Drupal migration that wraps values in paragraphs
• Add new comment

If you think Drupal is designed only for developers, and that marketing specialists have to ask for every change, it's time to update your knowledge. Nowadays, marketers can think of a campaign one day and build a landing page the next. This is possible thanks to the committed community and thousands of modules. Three of them have completely changed the way landing pages are built and deserve a special mention. In this article, we will show you how to create pages using with drag & drop method.

AI is no longer on the horizon — it’s fully here, and reshaping nearly every corner of the digital world. It’s no longer news that with the right approach, AI tools can quietly and tirelessly simplify and streamline much of the work across various areas. Search Engine Optimization, with its many routine and repetitive tasks, is no exception.

Join Johanna and Jess as they dive deep into their experiences and insights working with Drupal in the nonprofit sector. Learn about their early careers, the evolution of Drupal's development, the significance of community in nonprofit tech, and the origins and importance of the Nonprofit Summit at DrupalCon. Discover how their community initiatives foster collaboration and support among nonprofit technologists, and get a glimpse into the upcoming summit details. Perfect for anyone interested in Drupal, open-source technology, and nonprofit organizational challenges.

For show notes visit: https://www.talkingDrupal.com/cafe012

Johanna Bates

Johanna Bates (they/them, hanpersand on drupal.org) is co-founder and co-principal of DevCollaborative, a company that builds accessible and sustainable Drupal and WordPress sites exclusively for nonprofit organizations.

Johanna began their formal tech career at WGBH in Boston in 2000 as a front-end developer. They have been building Drupal sites since 2004, and have been co-moderating NTEN's Nonprofit Drupal Community and its monthly chats for over a decade.

Johanna was involved in early Nonprofit Summits at NYCcamp starting back in 20-teens 2015, and helped bring the Nonprofit Summit to DrupalCon North America in 2017.

Jess Snyder

Jess Snyder (jesss on drupal.org and Drupal Slack) is Director of Web Systems for WETA, the flagship public media station for Washington, DC, and has over 20 years of experience in website development.

Jess is an organizer for NTEN's Drupal Community of Practice as well as Drupal GovCon. She also co-chaired the triumphant return of the Nonprofit Summit to DrupalCon Portland 2024 and its sequel at DrupalCon Atlanta 2025.

When not Drupaling, Jess sits on the Board of Directors for the National Academy of Television Arts and Sciences.

Topics

• Meet the Speakers: Johanna and Jess
• Johanna's Journey in Nonprofit Tech
• Jess's Path in Public Broadcasting
• The Importance of Community in Nonprofit Tech
• Organizing Nonprofit Summits
• Challenges and Changes in Drupal
• The Value of Open Source for Nonprofits
• Comparing Drupal and WordPress
• Concerns About JavaScript in Content Editing
• Importance of Accessibility in Content Management
• Guardrails for Content Editors
• The Nonprofit Summit: Origins and Evolution
• Summit Format and Community Building
• Sponsorship and Event Details
• Getting Involved in the Nonprofit Drupal Community
• Conclusion and Final Thoughts

Guests

Johanna Bates - hanpersand Jess Snyder - jesss

I built a dashboard that tracks Drupal Core's code quality over time, across major releases from Drupal 7 through Drupal 11. It measures lines of code, cyclomatic complexity, maintainability index, anti-patterns, and API surface area. Think of it as a health report for Drupal's codebase.

The dashboard updates automatically and is available at https://dbuytaert.github.io/drupal-core-metrics/.

The charts tell a clear story of steady, hard-won progress. A story to be proud of and worth sharing. Code quality is dramatically better than it was in Drupal 7: lower complexity, easier to maintain, fewer anti-patterns, and dramatically better test coverage. Drupal now has nearly twice as much test code as production code!

Drupal Core's API surface has modernized too. As Drupal shifted from procedural to object-oriented patterns, global procedural functions gave way to classes implementing interface methods, services, plugins, and events.

By tracking these metrics publicly, I hope to inform decisions about both code quality and developer experience. When we refactor complex code, we can measure the impact. We can set goals and track progress.

All charts use static code analysis. Static analysis measures the code as written, not what it feels like to work with it or to learn Drupal as a new developer. As a next step, I'd love to measure developer experience more directly. Dynamic analysis might help, for example by tracking call stack depth, or how many files and APIs you have to touch to make a simple change.

The dashboard is open source, and contributions are welcome at https://github.com/dbuytaert/drupal-core-metrics.

Special thanks to catch for multiple rounds of feedback. As the most active Core Committer over the past 12 months, his input was invaluable.

Drupal celebrates its 25th anniversary on January 15, 2026. The Drupal Association is organising a global celebration week starting January 8. At The Drop Times, we invite communities worldwide to join the moment by organising local gatherings or sharing how they’re celebrating this open-source milestone.

What’s the fastest way to understand Drupal AI and bring it into your DNA? Build things!

If you want to turn curiosity into capability, join us for “Play to Impact”, a two-day Drupal AI hackathon in Brussels on 27–28 January 2026. Hosted by the Drupal Community of Practice @ European Commission and EUIBAs, the event brings makers together to prototype practical solutions that help teams do more with less—without compromising trust, governance, or human judgment.

What you’ll work on

Across two distinct challenges, you’ll work hands-on with the Drupal AI ecosystem, including:

• Agentic AI automation tools that streamline everyday work for content editors
• The newly released Canvas page builder, plus its experimental Canvas AI features

Why this matters (and why now)

Drupal AI is moving quickly, and this is a chance to be part of that—not by watching, but by building alongside the people leading it.

Two days working together in person creates something different: you'll learn faster, make connections that last, and leave with something real you've made.

The European Commission is hosting because they believe this matters. We do too.

Who should attend

This is intentionally cross-functional. You’ll fit right in if you’re in:

• Marketing and digital teams focused on performance and content impact
• Content, UX, and brand teams improving journeys and accessibility
• Agencies, integrators, and Drupal practitioners building solutions for customers

You will be joined by many key members of the AI Initiative such as Freely Give’s AI experts, Marcus Johansson, the AI Initiative’s official tech lead and the head of innovation Jamie Abrahams.

How it works

Participants get access to a structured program that transitions into onsite collaboration at the European Commission premises in Brussels and culminates in team pitches to an expert jury.

Top teams receive recognition and visibility across the Drupal community—amplifying both their contributions and their career profile.

Join us

More information and registration details. 

If you’re new to Drupal AI, the all new Drupal AI TV is a good on-ramp.

Bring your ideas—and let’s build impact together.
 

File attachments:  hackathon2026.png

"DrupalCon Chicago 2026, happening March 23–26 at the Hilton Chicago offers incredible value for web professionals and enthusiasts alike with professional training options, sector-focused summits, deep dive sessions and workshops, a full hands-on Drupal in a Day introduction seminar and contribution opportunities."

Look. I know you’ve seen that everywhere at this point, but hear me out. It’s been over a decade since DrupalCon North America has seen the interior of the continent (since 2014 in Austin, to be specific). Every year either the Techies on the West coast fly 6 hours east or the Govvies on the East coast fly 6 hours west. What if we all just met in the middle?

Enter… Chicago.

Image

Image Source: Photo by Neal Kharawala on Unsplash

We’ve got one of the most connected airports on the continent, and a smaller one too if you want. Both airports are connected to downtown with $2.50 public transit rides. Take the train if riding the rails suits you. Parking downtown isn’t even that bad. 

We have 20 Michelin Star restaurants. We have over 200 neighborhoods, each with their own unique character (if you can take your eyes off of our skyscrapers… we invented those too, you know). 

Ok, fine, we know what ya’ll really want… how about a city with its own design system and municipal typeface?

But enough about me. I asked some other Drupal folks what one thing they recommended you check out during your time here at DrupalCon. You’ll literally be staying “in the Loop” and there’s no better home base for exploring the city. Here’s what they had to say:

• The Chicago Cultural Center is an often-overlooked gem right in downtown Chicago, and it’s free! Inside contains incredible architecture, insanely detailed stained glass domes, and a nice Chicago gift shop. ~ Avi Schwab (froboy) (oops, yea that’s me again)

• DrupalCons are the time of large group dinners and there is no better place than The Purple Pig, north of the Hilton on Michigan Ave. I have fond memories of the last DrupalCon Chicago participating in the "bite-bite-pass" rule and trying so many amazing dishes.
  P.S. Don't let anyone trick you into drinking Malört, the local legendary spirt. Choose so boldly, or not at all, and that's ok. ~ Kevin Thull (kthull)

• Try a Chicago hot dog and Italian beef. Deep dish is good too… You’d be surprised how many times I heard the traditional food in the USA was just burgers and fries and yet every city has their own thing, but you don't know when you landed and have 5 days to get everything else done. ~ Bernardo Martinez (bernardm28)

• [In the Pilsen neighborhood,] the food was amazing, the art, the murals, and the people were SOOO nice.  ~ My Wife ~ Eric Wheeler (sikofitt)

• The Chicago History Museum is great and not too far from the venue. For an iconic Chicago dog place, visit Wiener Circle. (Editor’s note: but … be prepared.) ~ Doug Dobrzynski (dobrzyns)

• Gaze in wonder at both big pointy teeth and tiny pointy teeth at the Field Museum! Get tacos from one of the trucks on Monroe St. outside the Art Institute. Or take the CTA Pink Line to 18th St. for tacos at Taqueria El Mezquite or the more upscale (but still casual) 5 Rabanitos.
  Also near the Pink Line is the National Museum of Mexican Art, which has a great collection. There are also too many kinds of pizza to count. ~ Brian Smith (brianbrarian)

• Get "on a Boat" for an Architecture Tour. Visit Chinatown. Take a walk in a park (Grant Park & Millenium Park are closeby, but we have 8,800 acres of them). Catch a show (HAMILTON!!!) at the CIBC Theater or one of many stand-up venues. ~ Norah Medlin (tekNorah)

Image

Image Source: Avi Schwab

That’s… a lot. I’ve been here for 25 years and I still haven’t hit all of those. You’ll have a couple of days (and theoretically conference things to go to as well). 

Speaking of the conference, it’s looking to be a busy one. (Almost as busy as the last time DrupalCon was here and Dries created the Drupal 8 branch on stage.)

If you’re looking to find your people or just reconnect, you can choose from one of seven industry summits on Monday. If you’re not sure where to start, you can sign up for professional training instead. Tuesday and Wednesday will bring a boatload of sessions (still to-be-announced) along with our two keynote speakers — both of whom will give us some insight into what the future will hold, for Drupal and for humanity. Thursday is Contribution Day, where everyone has a chance to give back to the project (it’s not just code!). Or if you’re new to Drupal and looking for more guidance, our free, hands-on, Drupal in a Day program could be right for you.

Image

Image Source: MidCamp Flickr, licensed as CC BY-NC-SA 2.0

Finally, we understand that travel might not be in the cards for you right now. 2025 was a lot. It may not be the right time for you to join us in Chicago. That’s ok. 

If you’re not able to join us, consider supporting Drupal and Open Source by becoming a Ripple Maker for as little as $1, or subscribe to the many Drupal Newsletters (they’re free).

I hope to see you there,

Avi Schwab

DrupalCon Chicago Steering Committee

This post was written by humans. 

Struggling with image alt text in Drupal? Read how Media Accessibility Audit helps you find, fix, and scale accessibility with responsible AI and full editorial control.

We often assume a tool or coding technique must be complex to be impactful, yet oftentimes, the most elegant solutions are the simplest. Before writing custom code or installing a new module, we should investigate if a native browser solution already exists. Developers often overlook this step, missing the fact that native HTML and CSS can frequently replicate the functionality of advanced third-party libraries with far less overhead.

This post explores the power of the native <details> element. By returning to these fundamental building blocks, you can create accessible, high-performance accordions without the weight of unnecessary dependencies.

The <details> and <summary> HTML elements

The <details> element, also known as the Details disclosure element, it's described as...

...an HTML element which creates a disclosure widget in which information is visible only when the widget is toggled into an open state. A summary or label must be provided using the <summary> element.

HTML and CSS have come a long way in the last years, and browser support has improved rapidly. As a result, we can use native solutions to build interactive functionality that previously required JavaScript.

The <details> element reached Baseline Widely available status in January 2020.

The Markup

The markup is simple, but it does require the <summary> element to be nested within the <details> tag. But don't be fooled by the simplicity of the markup, the <details> combined with the <summary> elements pack a surprising set of features. More on this shortly.

<details> <summary>Title summary</summary> ...details content </details>

Standard markup and nesting structure of the <details> and <summary> elements.

While the markup structure above is required, you can still get creative with the markup should the thing you are building has specific markup requirements. See below:

<details class="accordion" name="demo"> <summary> <h3 class="accordion__title">Cras justo odio, dapibus ac facilisis in</h3> </summary> <p class="accordion__content"> Cras mattis <a href="#">consectetur purus</a> sit amet fermentum. Nullam id dolor id nibh ultricies vehicula ut id elit. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros.</p> <span class="accordion__footer">Learn more <a href="#">about this topic</a></span> </details>

A more elaborate example of the <details> and <summary> elements using custom markup while adhering to standards.

Notable <details> features Attributes{.small-h3}

• open: This Boolean attribute indicates whether the details — that is, the contents of the <details> element — are currently visible. The details are shown when this attribute exists, or hidden when this attribute is absent. By default this attribute is absent.
• name: The name attribute specifies a group name. Modern browsers now support the name attribute on <details> elements, allowing you to create exclusive accordions (where opening one closes others) using only HTML.

Uploading files should be as seamless and intuitive as possible, especially if you’re managing a large and bustling Drupal website. Sometimes, third-party upload tools are a great choice because they bring special capabilities to the table, boosting editorial efficiency. One of them is the Uppy tool, a free and open-source JavaScript-based file uploader.