inclind / inclind_gutenberg_blocks Goto Github PK

While working on the updates I noticed that with AdvAgg and Aggregated JS files it was failing to find the Drupal global variable. We should investigate this and ensure that with the default settings of AdvAgg and aggregated JS/CSS files enabled that the custom blocks load without issue.

Button

• Change blue and yellow to primary and secondary
• Icon settings are not working
• Remove or make optional arrow when the transparent background is chosen

Call to Action

• Fix layout (Place button inside col-12 wrapper)

In some instances, WP Gutenberg blocks will import SCSS files inside of JS files. This causes the compilation process to fail. We should investigate what's causing this and see if this can be resolved.

It looks like the babel step passes and then browserify fails:

• Successfully compiled 5 files with Babel.
• Error: Cannot find module './styles/style.scss'

Have the ability to change variables and set them to Guttenberg for a specific project.

• Add Drupal UI to set default variables in the admin form (colors, background, size);
• Ability to export through configs.

Create a Wiki page within this repository for each custom Gutenberg block defined by this module. The objective is to have an index of blocks we can review during the design process to determine which blocks would be useful and confirm the functionality (i.e. variables) fit with requirements.

Each page should present:

• Screenshots demonstrating the block
• Screenshots of the administrative interface.
• Instructions for customization (if any).

Currently, there is no method implemented in the module for compiling scss files.

Node Sass is likely the best bet for this:

• https://github.com/sass/node-sass

We should determine what the next steps for this module are as far as conversion of WordPress Gutenberg blocks goes.

So far we have converted the dropcap block from Atomic Blocks. There are several other blocks available there that we could proceed with.

• Atomic Blocks

Additional options:

• Stackable – Gutenberg Blocks
• Advanced Gutenberg Blocks
• Otter Blocks
• Block Gallery – Photo Gallery Gutenberg Blocks
• Ultimate Blocks
• Gutenberg Blocks Design Library
• Page Builder Gutenberg Blocks – CoBlocks
• Bokez — Awesome Gutenberg Blocks
• Kadence Blocks – Gutenberg Page Builder Toolkit
• Editor Blocks for Gutenberg

The custom blocks are using deprecated functions. These should be updated to the suggestions in the Chrome console.

We should determine if we want to implement a build process for the module. If so, we will likely want to exclude the dist directory and have the build process push that in.

When copying the blocks over from one of our recent projects it appears that there is no default styling included with the blocks on the front-end. Both the front-end and the back-end could use some basic stying attached to them to have a reasonable default starting display for each block type.