π Description
In Spectra V2, users had the ability to individually enable or disable specific blocks directly from the Spectra dashboard. This was a useful performance and workflow feature β users could turn off blocks they don't use (e.g., Dynamic Content) to keep their editor clean and avoid loading unnecessary assets.
In Spectra V3, this block management option is no longer available, which is a regression from V2.
π Steps to Reproduce
- Install and activate Spectra V3 (tested on v3.0.0-beta.2).
- Navigate to the Spectra Dashboard.
- Look for an option to enable/disable individual blocks (e.g., Dynamic Content, Countdown, etc.).
- Observe β no such option exists in V3.
For reference, in Spectra V2:
- Navigate to Spectra > Blocks
- A list of all blocks is shown with individual toggle switches to enable/disable each block.
β
Expected Behavior
Users should be able to navigate to the Spectra dashboard and:
- See a list of all available Spectra blocks.
- Toggle individual blocks on or off based on their needs.
- Disabled blocks should not load their assets (JS/CSS) on the front end or appear in the block inserter.
β Actual Behavior
In Spectra V3, there is no option to manage individual blocks from the dashboard. All blocks are loaded regardless of whether the user needs them or not.
π‘ Why This Matters
- Performance: Loading unused block assets (CSS/JS) increases page load time unnecessarily.
- Editor UX: Users prefer a cleaner block inserter without irrelevant blocks cluttering the list.
- Migration friction: Users upgrading from V2 to V3 expect feature parity and are confused by the missing option.
π Environment Details
| Detail |
Value |
| Spectra Version |
3.0.0-beta.2 |
| V2 Feature |
Available |
| V3 Feature |
Missing |
π References
π§ͺ Suggested Test Cases
Priority: High β direct regression from V2, impacts performance control and editor experience.
π Description
In Spectra V2, users had the ability to individually enable or disable specific blocks directly from the Spectra dashboard. This was a useful performance and workflow feature β users could turn off blocks they don't use (e.g., Dynamic Content) to keep their editor clean and avoid loading unnecessary assets.
In Spectra V3, this block management option is no longer available, which is a regression from V2.
π Steps to Reproduce
For reference, in Spectra V2:
β Expected Behavior
Users should be able to navigate to the Spectra dashboard and:
β Actual Behavior
In Spectra V3, there is no option to manage individual blocks from the dashboard. All blocks are loaded regardless of whether the user needs them or not.
π‘ Why This Matters
π Environment Details
π References
π§ͺ Suggested Test Cases
Priority: High β direct regression from V2, impacts performance control and editor experience.