Re-evaluate block inserter category order to stop placing Otter above Core blocks

Impact: 60 · Confidence: 95 · Complexity: 10 · Suggested issue type: Improvement

Description

Problem

The Otter block category is currently forced to the top of the Gutenberg block inserter view. This pushes fundamental Core blocks (like text and media) further down the list. Users find this obtrusive as it disrupts muscle memory and standard editing workflows, even leading to plugin deactivations.

Desired Behavior

Otter should register its block category with a priority that respects native WordPress workflows. The category should ideally appear below essential Core block categories (Text, Media, Design) rather than pinning itself to the very top.

Acceptance Criteria

• The Otter block category appears after core WordPress categories in the block inserter.
• No negative impact on the visibility or functionality of the blocks once the category is opened.
• Verified inserter ordering in both the standard block editor and the Site Editor.

Customer Context

A user uninstalled the Otter Blocks plugin after 21 hours of use. The primary reason cited in their feedback was frustration that Otter's blocks show up first in the block inserter.

Root Cause Analysis

The root cause is a UX friction point stemming from aggressive plugin visibility tactics. By forcing the Otter category to the top of the inserter, it prioritizes plugin exposure over the user's need to quickly access basic Core blocks. The customer needs a frictionless editing experience where the most frequently used blocks (usually Core ones) remain at the top.

Alternative Suggestions

Instead of adding a user-facing toggle to control block order (which adds unnecessary configuration), update the block category registration to use a lower priority value or respect Gutenberg's default category ordering. Placing Otter just below the Core categories will maintain good visibility without frustrating users interpreting it as intrusive.

Reasoning

The customer deactivated the plugin because the Otter block category is aggressively forced to the top of the Gutenberg block inserter. This placement disrupts the user's muscle memory, forcing them to scroll past Otter's blocks to reach standard Core blocks. Instead of treating this as a request for a new feature or setting, the best course of action is to improve the default behavior by lowering the category registration priority.

Source: WordPress.org uninstall/deactivation feedback (July 14-20, 2026), clustered and triaged from the plugin feedback export.
Generated by feature-request-triage workflow (ID: feature-request-triage_6a5f82a375bd84.27517485) in manual-transcript preview mode; filed after human review.

No file or test is named. Start by searching the block category registration and its priority, then verify the inserter order in both the standard block editor and Site Editor. Done means Core categories appear first, Otter remains visible and functional when opened, and both editor contexts show the intended order.