Install
This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/adampickering/untangling-my-site/archive/refs/heads/main.zipUntangling IA — "My WordPress" fork
A fork of lucasmendes-design/untangling-playground,
kept deliberately small so the diff is the argument.
The first commit is the upstream prototype verbatim. Everything after it
changes one of four things, each marked in the source with a FORK NOTE
comment explaining what it serves and why.
What changed
| # | Change | Was | Now |
|---|---|---|---|
| 1 | One visible route to support | Help & Learn tab (videos, courses, guides) |
Get Help — a single sidebar entry to support |
| 2 | Menu icon | dashicons-cloud |
The W mark |
| 3 | Customer language | Hosting · My site · Your audience · Plan |
My WordPress · Overview · Your visitors · Your plan |
| — | New sidebar entry | — | Pricing & Plans |
| — | Mock Jetpack sidebar item | present, linked to # |
removed (duplicated a real Jetpack install) |
| 4 | One upgrade surface | (n/a — see below) | Free-plan banner reconstructed, then removed by default |
| — | Menu position | 1, above Dashboard | 2.1, directly below Dashboard |
On the naming
Customers write "my WordPress site" or "my WordPress". Nobody arrives asking about their hosting — that is our word for it, and the cloud icon is the same word in picture form.
On #4
The upstream prototype has no wp-admin-wide upsell banner, so there was nothing to delete. Production does have one on free sites, and it is half the problem: once this menu carries plans and upgrades, a free customer is being sold to twice on one screen, in two visual languages. It is reconstructed here only so the two states can be compared:
?untangling_banner=on— two upgrade surfaces?untangling_banner=off— one upgrade surface (the default)
What deliberately did not change
- The Launchpad, which should be the real component. "Launchpad" is not customer vocabulary either, but the naming belongs with the component, not with this fork.
- Backups / Scan / Activity Log / Staging. Still an open question. Nothing here designs for either answer.
- The plans and pricing treatment, which needs real design time — a compact in-page summary linking out to a fullscreen pricing page. Separate pass.
Run it
Copy untangling-prototype.php and quickstart-config.php (as
0-untangling-config.php) into wp-content/mu-plugins/.