-
Notifications
You must be signed in to change notification settings - Fork 4
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
Get Gutenberg blocks to replace Stackable and deprecate Stackable blocks #436
Labels
Comments
We're going to hold off on this for now until Megan and her team have time to absorb a change like this and also until Gutenberg matures a bit more. |
Find my blocks could be useful to find where Stackable is being used. |
Closing in favor of #576 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that Gutenberg blocks have matured, let's deprecate our use of Stackable and use Gutenberg blocks going forward. There are problems with keeping on the latest version of Stackable and the way it is being developed don't align with our needs. We'll need to keep Stackable around for Events that currently use it.
Here's a quick summary of how Stackable blocks are currently used on the site:
We should replace the blocks we only have a few instances of (4 and 5 above) and then cut out only the css we need to render the blocks we keep (1, 2 and 3) and include it conditionally on only the pages that need them. Then we can uninstall the stackable plugin entirely.
Alternatively we could go through all old pages and replace all stackable blocks.
The text was updated successfully, but these errors were encountered: