![](data:image/svg+xml;charset=utf-8,<svg height="50" width="50" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
![](data:image/svg+xml;charset=utf-8,<svg height="225" width="300" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
We have two separate needs and experiences for the WordPress back-end. Site owners and users need a different suite of tools and interfaces from what we developers/implementers need. Let's talk about splitting the back-end interfaces to serve both
UX
The Flawed Strategy of Assigning Site Owners as Editors
![](data:image/svg+xml;charset=utf-8,<svg height="200" width="300" xmlns="http://www.w3.org/2000/svg" version="1.1"/>)
Many times developers will assign the site owner as an editor to hide away all of the extra screens and menus that they've added into the back-end. But we are doing the site owner a disservice when s/he is not given full access to her/his website.
Developers, We’ve Made the WordPress Back-end Complex and Disconnected
There's an alarming trend in the WordPress back-end: we developers are polluting the back-end and building disconnected, complex solutions for the site owners. I understand the path that lead us to this state. But now it's time to stop and think