Proposal: Meshery UI Restructure Plan

52 views
Skip to first unread message

Mia Grenell

unread,
Apr 10, 2026, 6:27:14 PM (13 days ago) Apr 10
to Meshery Developers, James Horton
Dear Meshery Open Source Contributors,

Over the past six years, Meshery UI has benefited from contributions by hundreds and hundreds of individuals, each bringing their own objectives and approaches. This has resulted in a fundamentally strong codebase - 87% TypeScript with RTK Query and Sistent already widely adopted - but also significant technical debt: overlapping styling systems, duplicate icon libraries and concepts (like 22 scattered modals), three separate color/theme implementations, and eight files exceeding 1,000 lines. The attached design document outlines a disciplined plan to address this sprawl without a full rewrite or any coordinated downtime.

James Horton and I have worked on a Meshery UI Restructure Design Spec which contains 5 phases to this cleanup. Please comment at-will. Please participate in the execution initiative (issue #18654) at-will.

The proposal focuses on making @sistent/sistent the single source of truth for every component, token, color, and theme, while eliminating Material UI imports, breaking down giant files, and reshaping the directory structure for better discoverability. It is structured in five incremental phases, starting with lightweight guardrails (ESLint rules and docs) and progressing through theme consolidation, folder reorganization, and monolith decomposition. All changes will ship via small, independent PRs. We invite you to review the full plan, share your thoughts, and contribute to any phase that aligns with your interests - whether it's tackling a specific component, improving documentation, or helping with testing to prevent visual regressions.

As is our routine, let's take some time to perform cleanup and maintenance. This time, the whole kit and caboodle or as you Yanks might say, the whole enchilada.

Best regards,
Mia Grenell and James Horton
Meshery Maintainer and Contributor
Reply all
Reply to author
Forward
Message has been deleted
0 new messages