Feature Request: Add Ability to Disable Block

[chrisvidal]

to be bale to disable a block.

helpful for testing purpose when client is not sure if he wants to remove a block or not and see how it looks.

that would avoid to delete the block and hen have to redo it again later on.

[artistro08]

Excellent Suggestion. I'd take pull requests for this if it fits the following criteria:

• The switch for each block is put inside the column_options.yaml and section_header.yaml files
• The logic for the switch should live in the builder.htm and section.htm partial files.
• The switch should appear under the "General" tab at the bottom of the block.

[chrisvidal]

ok let me confirm a few things.

point 1: you are referring to the columns here and not the block, is that correct? you want to have the switch as well in the columns options on top of the blocks?

point 2: yes i agree the logic should be in the builder.html file for the blocks, and also the section.htm file for the columns

for the point 3, I think you mean to put the switch at the top of the General Tab and not at the bottom, correct?

[chrisvidal]

I made a PR to add the disabled capacity at the blocks levels first.

[artistro08]

Point 1: The Column options yaml file contains the content that is re-used throughout the blocks (bad naming convention there I know)

Point 2: Awesome

Point 3: I think it would look better at the bottom since it won't be as used as the other options but still needs to be there.

[chrisvidal]

I updated the section_header.yaml blueprint to add the swith on the block. I didnt use column_options.

[artistro08]

The switch should exist on both the section and the column blocks. Would add granular control.