AddFunc Slides vs WP Swiper

AddFunc Slides’ native and intuitive custom post type (called Slides) and taxonomy (called Slidesets) utilizes the powerful content management and editing features built into WordPress core. That is what makes it easy to grasp and manage. It includes administrative features such as quick edit, bulk edit, column sorting and a properly placed Slide Settings page (under Slides, not under the general Settings section). AddFunc Slides was made for CSS coders/themers, as well as for average WordPress users. It comes as a plug & play package with it’s already active default stylesheet, providing a basic but robust slideshow presentation interface. This stylesheet can be turned off in Slides->Settings, allowing a CSS coder full control over the entire look and feel of slideshows including transitions. The vanilla JavaScript slideshow script only changes classes and does not use the style attribute, meaning all state changes can be animated by CSS. One of the things that makes Slides so easy to manage is the Edit button displayed with each Slide on the front-end when you’re logged in with Editor privileges. When you see a Slide in your slider that you want to edit, simply click the Edit button and you’re now editing that very Slide. Slides can also be moved from one Slideset to another with a couple of clicks. No need to migrate Slides by copy & paste. Slides are just like Posts or Pages, with the standard Visual/Text editor, revisions, publication settings, featured image (used for thumbnails), etc. The big difference is that they are made for slideshows. Additional specialized Slide options allow you to upload/select a main image using the Media Library (so you can keep that separate from the editor content), link the main image to any Page, Post or other URL/URI, select the nature of the Slide (Imagery or Content) and set the Slide’s priority (any numeric value). You can even upload/select a background image (also using the Media Library), so there is no need to use your stylesheet to do a CSS background-image for each Slide. Specialized buttons in the editor (TinyMCE) make it easy to add the CSS classes of a set, appropriate for slideshow objects and supported by the default stylesheet. These include four directional options (left, right, up and down), two rotational options (clockwise and counter-clockwise), an incremental option (with up to six increments) and a decremental option (with up to six decrements). These classes can also be styled or animated by CSS and can therefore be repurposed for any need a web developer deems them best suitable for. We gave these buttons generic names for that very purpose. The shortcode [slides] supports parameters for every feature the slideshow script has to offer, while not requiring any of them at all (except where customization is necessary, of course). These features include * slideset — Selects a specific Slideset by slug * auto — Automates Slide transitioning * speed — Duration each Slide is displayed * prevnext — Adds "Previous" and "Next" buttons * pause — Adds a Pause button * tabs — Adds tabs/pager with optional labels and/or thumbnails * tabsfirst — Outputs tabs before the slideshow instead of after * stoppable — Stops automated transition upon user interaction * pauseonhover — Pauses automated transition upon hover/mouseover * fullscreen — Adds Fullscreen button (note limited browser support)[http://caniuse.com/#search=fullscreen] * swipe — Adds touchscreen swipe capability. (By default, left = next Slide, right = previous Slide. Also includes up = next Slide, down = previous Slide, and a few other combinations thereof) * class — Adds CSS class(es) to the slideset container * order — The order in which Slides are displayed * orderby — What the display order is based upon — date, priority (if set in Slide options), name, ID, random A Help Tab is available (when editing any Post, Page, etc.) with simple but detailed instructions on how to write [slides] shortcodes, including all options available, as well as currently created Slidesets. The Slides Widget supports all of the same options as the shortcode, with a comprehensive set of on/off settings and multiple choice boxes. And of course for you themers, if you would like to do_shortcode in your theme files, that option is available as well. We have big plans for AddFunc Slides. We created it because we couldn’t find any other slideshow plugin that works anything like this one does. That’s really the basis by which we build all of our plugins — to fill a needed gap. We hope that you find this plugin to be as vastly useful as we do.

WP Swiper adds a flexible carousel block to the WordPress editor. Each slide accepts standard nested blocks, so you can combine images, headings, buttons, video, and other block content without using a separate page builder. Highlights Build slides with nested WordPress blocks. Choose from seven editable in-block starter templates without adding extra block types. Create horizontal or vertical responsive carousels. Configure navigation, pagination, autoplay, loop mode, free mode, and transition effects. Set responsive breakpoints, spacing, offsets, and slides per view. Add background images, focal points, overlays, thumbnails, and custom navigation icons. Drag image files into the editor to create slides. Load frontend assets only when a slider is detected, with an optional global-loading setting for custom setups. Use the bundled Swiper 14 runtime without a jQuery dependency. Accessibility Since version 1.4.6, WP Swiper removes non-visible slides from the accessibility tree and keyboard tab order. Focusable content is restored when its slide becomes visible, including in responsive layouts that display multiple slides. This behavior addresses one carousel accessibility barrier, but it is not a certification that WP Swiper or a website using it conforms to WCAG. Conformance must be evaluated for the complete published page and depends on the carousel configuration, slide content, theme, and other integrations. Site authors remain responsible for accessible content and configuration. Provide meaningful image alternatives, logical headings, readable contrast, and clear control labels. If autoplay is enabled, enable the pause/play control so users can stop rotation. Rotation stops when keyboard focus enters the carousel and restarts only after an explicit user request. See the W3C carousel accessibility guidance. Privacy WP Swiper does not include analytics, advertising, tracking, or telemetry. Images selected through the editor are handled by the standard WordPress Media Library and REST API. Support and development For usage questions, use the WordPress.org support forum. Report reproducible bugs and feature requests on GitHub. Security issues should be reported privately according to the repository security policy. Development is supported through Buy Me a Coffee. Developer filter The wpswiper_frontend_js_register_args filter can change the dependencies and loading arguments used for the plugin’s frontend script. add_filter( 'wpswiper_frontend_js_register_args', function ( $args ) { $args['deps'][] = 'jquery'; $args['args'] = array( 'in_footer' => true, 'strategy' => 'defer', ); return $args; } ); See the wp_enqueue_script() documentation for supported loading arguments. Frontend lifecycle WP Swiper automatically initializes blocks added after page load. Navigation and AJAX integrations can also call window.wpSwiperInit(element), window.wpSwiperDestroy(element), or window.wpSwiperReinit(element) with a .wp-swiper block wrapper. Runtime configuration corrections dispatch a wp-swiper:warning browser event with a structured diagnostic. Initialization failures dispatch wp-swiper:error, and explicit destruction dispatches wp-swiper:destroy. Contributing WP Swiper is developed openly on GitHub, and community contributions are welcome. Report reproducible bugs through the GitHub issue tracker. Suggest focused improvements and new features. Improve documentation, translations, accessibility, or test coverage. Submit pull requests after reviewing the contribution guide. Please report security issues privately according to the security policy.