Purple Blocks
Purple Hub
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).
- Have an Admin role in Purple Hub to access and use Purple Blocks. Learn more: Purple Hub: Overview of roles & rights
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.
If you move the mouse pointer over a block in the list, you will find a description of the use case of the block.
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.
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 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.