Register Starter ACF Fields with Corresponding Bootstrap Components #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to include an easy API for sharing field definitions and templates between components and blocks. This can allow us to design back-end experiences that offer easy support for both the block editor and the default ACF fields input.
Planned support for components/blocks include:
Carousel (use existing slider/swiper but include ability to select number of visible items via data attribute)(moved to Add carousel component #10)By default, the developer will have access to use and style these components.
They can also register or de-register which components are available as blocks in the editor by using the configuration array.
It may be beneficial to build a CLI command to quickly scaffold all the necessary components to speed up the process of creating new components/blocks and to reduce documentation overhead.