| 开发者 | weblazer |
|---|---|
| 更新时间 | 2026年9月17日 18:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/.Unlike traditional carousels that force you to insert a dedicated "Carousel" block and rebuild each slide by hand, Any Block Carousel Slider turns the Gutenberg blocks you already have (Query Loop/Post Template, Group, Gallery) into a slider via a simple toggle. With a Query Loop for instance, legacy solutions usually require limiting the loop to one post per slide and duplicating layouts. Here, one block is enough: single action, zero duplication, maximum performance.
Yes. The Gutenberg carousel slider block plugin reads style variables generated by your theme (classic or full site editing) and applies the carousel slider without breaking the initial grid.
No heavy JavaScript libraries (like Swiper.js or Slick). The plugin uses native CSS scroll-snap for smooth layout and scrolling, accompanied by an extremely lightweight frontend script (~40KB raw source, <15KB minified/gzipped) to manage navigation arrows, pagination dots, autoplay, and loop behaviors.
Enable the Query Loop Gutenberg block (or Post Template), configure your filters and rendering, then check Carousel. For Post Template blocks, switch the layout to Grid so you can control the number of cards displayed per viewport. Posts are automatically aligned on a scrollable line with snap and CSS arrows. This is the main advantage over traditional carousel slider plugins that don't support Query Loops natively.
Yes. The plugin respects existing inner Gutenberg blocks. A Group block containing image, text, buttons, or forms is transformed as-is in carousel mode.
Switch the block layout to Grid in the Gutenberg sidebar (Layout panel) and set the desired column count for each breakpoint. The carousel inherits the same grid settings, so adjusting the Grid controls is the recommended way to decide how many slides remain visible.
Yes, when your products are rendered via the Query Loop/Post Template block (for example by querying the product post type or a WooCommerce pattern). A dedicated integration for the legacy Products block remains on the roadmap, but today you can already build product sliders by using the Query Loop to target WooCommerce content.
Yes! The plugin includes built-in infinite looping (Loop mode) and automatic slide progression (Autoplay with configurable delay) controllable directly from the Gutenberg block settings. You can also customize, show, or hide navigation arrows and pagination markers independently.
Yes, without limit. Each Gutenberg block manages its own CSS variables for the carousel slider.
In your theme or via a CSS snippets plugin, override the variables:
css
.wp-block-group.is-carousel {
--carousel-button-bg: var(--wp--preset--color--primary);
--carousel-marker-size: 0.8rem;
}
If the navigation buttons look offset or partially hidden, wrap the carousel-enabled block inside a parent Group (or another container block) so the wrapper can provide the proper padding and overflow context for the controls.
Yes! Navigation buttons, pagination dots, and scroll behavior all use standard HTML and CSS supported by every modern browser (Chrome, Firefox, Safari, Edge). The plugin uses native scroll-snap for smooth scrolling and lightweight JavaScript for interactive navigation controls.
.wp-block-cover) to allow images to stretch full-width.resolveEditorPadding) in the Gutenberg editor to retrieve original spacing settings from block attributes and inline element styles, preventing arrows from collapsing to the edge.checkAndUpdateColors ReferenceErrors in the console.::scroll-button and ::scroll-marker pseudo-elements.--wp--style--elements--button--color--*).carouselShowArrows and carouselShowMarkers block attributes for fine-grained carousel controls.abcs-hide-arrows and abcs-hide-markers classes.min() and clamp().prefers-reduced-motion.