New blocks to expand pattern and theme designs

[creativecoder]

This issue tracks new blocks that will help expand possible designs for themes and patterns. Most represent common design patterns on the web that aren't yet possible with the default block library:

• Add Shape Divider block #16351
• Add an Icons block #16484
• New block: Accordion block #21584
• New Breadcrumbs Block #21943
• Block "Slider" #34075
• New Block: Tabs #34079
• Scrolling Marquee Block #41730
• New Block: Slider Container (CSS based) #43369
• Core Block suggestion: Theme Style Toggle #48249
• Create a "Back to Top" Block #50433

Related

• Design Tools Overview
• Discussion in Proposal for Core Blocks in the Directory

[creativecoder]

There is no open issue for it, but users seems to be interested in a style variation toggle for the front aka "dark mode" toggle block. This was mentioned multiple times in the post for Twenty Twenty-Five.
-- from #58773 (comment)

@carolinan Thanks for the suggestion! This issue seems related Core Block suggestion: Theme Style Toggle #48249; I've added it above.

[Luehrsen]

I appreciate the effort to expand WordPress’s capabilities, but I have concerns about the inclusion of blocks proposed here in core. These blocks feel highly opinionated, catering to specific design trends or preferences, and I question whether they align with the broader needs of WordPress users. Just because something is "common" does not warrant it being in core.

WordPress has always excelled by providing a lean, reliable core while enabling customization through plugins. Adding blocks with such opinionated use cases directly to core risks bloating the platform and complicating the experience for users who don’t need them. These features seem far better suited for plugins rather than core functionality.

Including blocks like these also introduces long-term maintenance challenges. Every block added to core requires ongoing updates, compatibility checks, and support, which places an unnecessary burden on resources that could be focused on improving foundational features.

Beyond the impact on core itself, including these blocks into core has a devastating effect on the WordPress extender ecosystem. Third-party developers who build and maintain plugins for such features are undercut when core begins to integrate functionality that previously thrived in the ecosystem. This stifles innovation and reduces the incentive for developers to contribute, ultimately weakening one of WordPress’s greatest strengths: its vibrant, diverse ecosystem of plugins and tools.

I strongly believe that providing these types of blocks could essentially be the purpose of canonical plugins. By placing features like these blocks in canonical plugins, WordPress can strike a balance between expanding its capabilities and preserving the lean, extensible foundation that has made it successful.

I believe WordPress thrives when core focuses on providing the essential building blocks, leaving more niche or stylized elements to be implemented through plugins or canonical plugins. By following this approach, we can maintain the core’s flexibility and performance, protect the ecosystem that has always supported WordPress, and empower users to add only the features that suit their specific needs.

[creativecoder]

Thanks for your feedback, @Luehrsen .

I'm no longer working on WordPress, so I'll close this issue. If anyone else wants to shepherd it, feel free to re-open this one or create your own issue.