Overview

When enabling the Canvas module by default, all blocks of the site are added as possible elements to be used by Canvas. This does not necessarily make sense, since there are blocks that, due to internal logic, dependencies, or their intended purpose, are not designed to be used within Canvas.

This results in an overload of information on the components page and also creates management issues. Navigating through one, two, or three pages is not the same as having to search through 10 or more pages to enable or disable components.

It would be very useful to be able to define whether a block should be available for use in Canvas or not.

Comments

oskar_calvo created an issue.

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented

We already provide this for SDCs #3535958: Allow SDCs to be marked to be excluded from UI. However, I don't know what would this mean for Blocks because they are only being used in the UI?

One of the ideas I've had has been to always add new Blocks to a new folder "Blocks" and provide a way to disable them from Canvas UI. This wouldn't be a full solution to this but would probably reduce the friction at least a little bit. Wondering if you have thoughts on this?

lauriii’s picture

lauriii
he/him
Primary language Finnish
Location Finland
commented

Another option to consider would be to create a separate panel for Blocks (like we have for Code). It would be possible to then add Blocks from there to Library (like we allow for Code). Only Blocks that have been added to Library can be added to page.

This would provide consistency with Code Components but at the same time wouldn't it be strange to have a panel for just adding blocks to the library in Canvas UI? With Code Components at least you can still use the the components within other Code Components and edit them.