Skip to content

[Feature]: Make OpenClaw Feel Like WordPress: A UX Revolution for Effortless Configuration #66138

Description

@alexandre-leng

Summary

Enhance the OpenClaw dashboard with a UX-first layer to make configuration simple, guided, and accessible to a much broader audience, drawing inspiration from WordPress for UX and for securely adding ClawHub plugins.

Problem to solve

OpenClaw is powerful, but its configuration experience remains too technical and fragmented for many users. Even simple changes can feel complex due to the lack of clear guidance and the need to understand internal concepts.
We shouldn’t have to go through OpenClaw onboarding every time we want to modify something, and we should be able to change it easily directly from the dashboard.

Proposed solution

Introduce a powerful UX layer on top of the existing system, without a full rebuild, to make OpenClaw instantly intuitive. The goal is to turn a highly powerful platform into something as smooth and accessible as the best modern tools.

Instead of navigating complexity, users are naturally guided. Every configuration becomes visual, simple, and supported by contextual onboarding that appears when needed, making changes effortless instead of tedious.

Inspired by WordPress, the dashboard evolves into a modular, plugin-driven experience where features can be installed and configured in a few clicks through clear, intuitive interfaces.

The result is a platform that feels easy from the start, while still offering full depth for advanced users.

Alternatives considered

Relying only on documentation or minor UI tweaks would not significantly reduce complexity. Without adding a true UX layer and guided experience, the platform will remain difficult to approach for a large portion of users.

Impact

This impacts a wide range of users, especially newcomers and non-technical profiles. The severity is high as it directly affects onboarding and daily usage. The issue occurs frequently during setup and configuration changes. The consequences include slower adoption, increased errors, and unnecessary complexity that limits the platform’s reach and usability.

Evidence/examples

No response

Additional information

Image

Image

Image Image Image ![Image](https://github.com/user-attachments/assets/040e7c6c-d8d8-49bf-86ef-d2e0cd3c1a6c)

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low-priority cleanup, docs, polish, ergonomics, or speculative work.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:needs-security-reviewClawSweeper marked this issue as needing security-sensitive review.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.enhancementNew feature or requestimpact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.impact:securitySecurity boundary, credential, authz, sandbox, or sensitive-data risk.issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions