New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Review/Help needed] Gutenblock for Slider/Slideshow #6608

Closed
strarsis opened this Issue May 6, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@strarsis

strarsis commented May 6, 2018

A modular experience with Gutenberg and sliders, see this alpha https://github.com/strarsis/slider-block/.

The Slider Gutenblock is still a prototype but you can already place a slider block, add/remove slides, add other blocks and even nest further sliders into the slides!

Because it is still alpha there are some bugs though and the slider options aren't configurable yet but this can be a starting point for further improvements.

Either download the repository as archive and extract into plugin folder or clone and develop on it using the existing tools (Create Guten Block generated).

Some features/suggestions/plans/inspiration:

  • Wholly separate slide block for slide-specific transitions and options (#5540).
  • Normalization of underlying slider library so that other slider libraries can be used in future besides from Swiper (though it is already really comprehensive and open source).
  • Separate / freely movable blocks that can be linked to a slider:
    1. Previous/Next button
    2. Pagination
    3. Scrollbar
  • Block-level event/notification system so that the blocks inside the slider slides are notified when they are shown or moving out of sight. This allows even more modularity for other block authors, e.g. for image effect blocks.
  • Declarative approach for slider options: Storing the slider options as HTML data attributes for initialization by script in frontend (theme).
  • Easier sorting/moving of slides, especially when there are many of them.

This was referenced May 6, 2018

@karmatosed

This comment has been minimized.

Show comment
Hide comment
@karmatosed

karmatosed May 7, 2018

Member

@strarsis thanks for working on this. Right now we have a few versions of this in action and I think keeping them all on the same issue makes more sense than opening new ones. Whilst #1958 is closed that is the one I would encourage you to add your insights and updates to. Thanks for working on a suggested option.

Member

karmatosed commented May 7, 2018

@strarsis thanks for working on this. Right now we have a few versions of this in action and I think keeping them all on the same issue makes more sense than opening new ones. Whilst #1958 is closed that is the one I would encourage you to add your insights and updates to. Thanks for working on a suggested option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment