Purple Blocks

purple hub summary purple blocks is a block management ui for gutenberg blocks in purple hub this feature allows administrators to control which blocks and block variations are available to editors within the purple hub once you have defined your desired blocks, only those you have selected, will be visible and usable to the editors in gutenberg editor for creating content this guide will walk you through how to manage and configure blocks, ensuring you can control the content structure of your articles (posts) blocks menu in gutenberg editor preconditions have purple blocks enabled learn how to enable purple blocks docid\ xp14iekcck1kihydf efx have an admin role in purple hub to access and use purple blocks learn more purple hub overview of roles & rights docid\ djj5yjjacdplm9qt0qlfk explanation deprecated methods for block management the purple hub previously allowed block management through other methods, such as the d h backend plugin and the block whitelist feature within the purple hub settings these old methods are now deprecated and should no longer be used for new projects users are encouraged to migrate to the new purple block management system understanding blocks and block variations in purple hub blocks are individual components used to build content in articles within the gutenberg editor; block variations are different types or configurations of a block for example, the embed block may have several variations, like youtube, twitter, or other variations of embed blocks with the block management feature 'purple blocks', you can manage both blocks and their variations purple blocks ui in purple hub purple blocks ui in purple hub info box for each block in ui in purple hub if you move the mouse pointer over a block in the list, you will find a description of the use case of the block setting mandatory blocks make a block mandatory to ensure that a particular block is present in all articles, you can configure it as a required block for instance, if every article needs a separator block, you can mark it as required if a required block is missing, the article cannot be published until the block is added a dialogue in the editor will notify the user of the missing mandatory blocks during the publishing process use case for integrations for example, if a specific block is essential for an integration, you can require its inclusion in each article this helps ensure certain blocks (like those necessary for print integration) are always used in specific contexts disabling unwanted blocks disabling a block if there are blocks that are not needed, you can disable them by moving the toggle on that specific block in the purple blocks ui disabling unwanted blocks gives your team a better overview of the blocks available and ensures that only the blocks you want to use in your articles (posts) are included disabling block variations disabling block variations disabling a block will automatically disable all its variants disabling a grouped block (a block with its block variations) will also deactivate any rows or stacks that belong to that group for example, disabling the embed block will hide all of its variants (such as twitter embed block, youtube embed block, etc ) unless you've chosen to keep certain ones active